Db2 Log Space Utilization Test

DB2 UDB database writes log files called transaction log to record all changes to application data in the database. During transactions, modifications to the database by each transaction is serially recorded in the transaction log. Using this information, the DBA can track which transaction made which changes to DB2 UDB Server data. Mainly, Db2 uses transaction logs to restore previosly committed changes and to undo the changes that were not committed when performing crash or roll forward recovery. Lack of adequate space in the transaction log would have serious repercussions on the way the DB2 UDB server carries out database updations; sometimes, critical changes to the database could get lost due to a space crunch. The Db2 Log Space Utilization test enables administrators to constantly track the space consumption by the transaction log, so that administrators are instantly notified of inadequacies, and are prompted to act fast.

Target of the test : A DB2 database server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every database instance on the DB2 database server that is currently active

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


Specify the IP address of the DB2 server in this text box.


Specify the port at which the target host is listening. The default port is 50000.

Username, Password and Confirm Password

To monitor Db2 UDB database server, the eG agent should be configured with the credentials of a user with any of the following privileges SYSADM or SYSCTRL or SYSMAINT or SYSMON. Specify the credentials of such a user in the User and Password text boxes. Confirm the Password by retyping it in the Confirm Password text box.


The test uses a database on the monitored Db2 UDB server. Specify the name of the database in the Database text box.

Include DB

Specify the list of databases that you wish to monitor in a comma-seperated list in the Include DB text box. By default this is set to ALL.

Exclude DB

Specify the list of databases that you wish to exclude from monitoring in a comma-seperated list in the Exclude DB text box. By default this is set to NONE.


If the database server being monitored is SSL-enabled, then set the SSL flag to Yes. If not, then set the SSL flag to No.

Measures made by the test:
Measurement Description Measurement Unit Interpretation

Maximum log used

Indicates the amount of maximum log space that is currently being used.


If the value of this measure keeps growing, it indicates that the log is growing rapidly and may soon run out of space! In such cases, you should clear the transaction log to ensure that there is adequate space to log subsequent transactions.

Currently used space

Indicates the amount of transaction log space that is currently in use.


Ideally, this value should be low. A high value for this measure requires immediate attention, as it indicates that the transaction log is suffering from severe space constraints. There is hence the danger of subsequent database modifications going unrecorded. Typically, excessive space usage can be attributed to too many changes been written to the log, but very little/none to the database. Further diagnosis can alone reveal the root-cause of this deviant behavior.

Total free space

Indicates the amount of log space that is currently available for use in this database.


Ideally, the value of this measure should be high.

Used percentage

Indicates the percentage of transaction log space that is currently in use.


The value of this measure is calculated using the following formula:

Used Percentage = Currently used space/ Maximum log used.