IDAA Situations
Use the series of predefined situations associated with IDAA to begin monitoring your system immediately or as templates for creating your own situations.
The names, descriptions, logic, and threshold values for the situations follow.
KD5_IDAA_Avg_QueueTime_Warning IDAA average query wait time exceeded warning threshold. Average query wait time greater then n seconds. High query workload impacts query performance. More accelerator capacity might be needed, bigger model or additional accelerator server. n is customer defined.
KD5_IDAA_Elap_Time_Warning IDAA accumulated elapsed time exceeded warning threshold. The accumulated elapsed time spent in the accelerator when executing requests from the DB2 subsystem. It could be a run-away queries that trigger this situation.
KD5_IDAA_Not_Online_Warning IDAA is not online warning. The Accelerator is not operational. This could be due to planned maintenance, network problems or other issues related to the setup of the Accelerator.
KD5_IDAA_Queue_Length_Warning IDAA current queue length exceeded warning threshold. A high number in this counter can be an indication that the accelerator is not able to process the scheduled work efficiently as the current queue length at the accelerator is large. The elements queued can be queries, loads, replication and maintenance tasks.
KD5_IDAA_Replic_Latency_Warning IDAA average query wait time exceeded warning threshold. When replication latency too high (5min/300s in this sample), it may impact query result correctness as the data on the Accelerator is not current. Note that sporadically high values of this counter might be acceptable and the value should be observed for a certain interval of time. If the value constantly increases or stay on an elevated value, this indicates a potential problem with the replication setup, that might have to be tuned.
KD5_IDAA_Replic_State_Warning There is an issue with incremental update function warning. There is an issue with replication (incremental update) function.
KD5_IDAA_Req_Fail_Warning IDAA failed requests exceeded warning threshold. The number of connections that failed when this DB2 system sent requests to the accelerator. Failed requests shouldn't normally occur.
KD5_IDAA_SQL_Exe_Fail_Warning IDAA SQL execution failed exceeded warning threshold. The number of SQL statements sent by all DB2 systems since accelerator started that were not successfully executed for any reason.
KD5_IDAA_Wait_Time_Warning IDAA wait time spent exceeded warning threshold. The wait time spent in the accelerator when executing requests from the DB2 subsystem. It could be a run-away query that triggers this situation.