Log Manager Situations

Use the series of predefined situations associated with the Log Manager workspace to begin monitoring your system immediately or as templates for creating your own situations.

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 because of 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

KD5_Percent_Log_Avail_Warning indicates that the percentage of active logs available is dropping below the threshold. This indicates that the log files might be too small. This exception can happen when logs are filled up faster than they can be archived. The situation's formula is:

Percent Logs Available = Logs_Available * 100 / Logs_Defined