DB2 Database Availability alarm fires for Standby databases.
A message similar to the following appears in the DB2 agent log file.
ERROR [AGENTNAME-lowPriorityPool-7735-[DB2_Maintenance][]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DB2WorkgroupEditionPartitionProcessor processor of DB2_Maintenance collection.
80: Caused by: com.quest.qsi.fason.core.errorhandling.AgentConnectionException: The database [DATABASE_NAME] identified as a standby, can't open a conntion to this database
The rule is coded to look in the Error log for SQL Code -1776 to identify that the database is HADR. When a database agent user id does not have access to read the DB2 Log file then the rule will not recognize the database as standby.
NOTE: more specifically SQL Code -1776 means that the table space you are trying to access does not exist, or the table space name is incorrect. It could also indicate that the table space is in an unavailable state, or there might be a configuration or permission issue related to accessing it.
The root cause was related to another message in the log file.
ERROR [AGENTNAME-lowPriorityPool-7731-[DB2_Log_Messages][]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DB2LogMessagesInstanceOSProcessor processor of DB2_Log_Messages collection.
java.lang.RuntimeException: Failed to execute collection [DB2_Log_Messages], reason=db2diag: Access denied- Profile:SSH Connection Profile {Host = HOSTNAME, Agent = AGENTNAME, Port = 22, Environment = {}} Query: "echo QUEST_OUTPUT_START; export LANG=en_US.UTF-8; export DB2INSTANCE=INSTANCENAME; export PATH=${PATH}:/udb/home/INSTANCENAME/sqllib/bin; db2diag -merge -gi level!='None' -lastlines 500"
The OS user needs to have access to run these commands (using the example from the error message above)
export DB2INSTANCE=INSTANCENAME;
export PATH=${PATH}:/udb/home/INSTANCENAME/sqllib/bin;
db2diag -merge -gi level!='None' -lastlines 500
An Enhancement ID FGDB2-I-19 has been logged to monitor DB2 without relying on the OS and specifically avoid reading the Error log. This will be reviewed by Product Management for consideration in a future release of the DB2 cartridge.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center