OMEGAMON XE for DB2 PE includes a predefined situation associated with the Log Manager workspace. You can use this situation to begin monitoring almost immediately, or as a template for creating your own situations. All of the predefined situations are disabled when shipped.
The name, description, logic, and threshold value for the situation follows.
KDP_LOGN_Critical monitors the availability of primary active logs. Active log data sets are allocated to DB2 during start-up processing. When an active log data set is full, it is automatically archived by DB2 to an archive log. When an active log is successfully archived, it is available for reuse.
The availability of active logs is critical to the functioning of DB2. If no active log is available, the DB2 subsystem hangs until one becomes available.
The lack of an active log could be caused by an insufficient number of logs defined at installation time, too small a log data set size, or possibly due to problems encountered during the archive process. A critical condition is detected when the logs available is less than one. The situation's formula is:
KDP_SRM_Log_Manager.Logs_Available LT 1