logutil may be used to monitor transaction log activity. If you run it with only the "-i" option, or with no options, it sends a summary report to standard output. This report contains statistics, version information, and warning messages. One or both of the two warning messages below may appear, as shown in the following report:
logutil corruptlog
Log File : corruptlog
WARNING: COMMIT BEGIN WITHOUT MATCHING COMMIT END IN LOG FILE
WARNING: START TRANSACTIONS WITHOUT MATCHING ROLLBACKS OR COMMITS
Total Size : 2366 bytes
Number of Records : 79
Mean Record Size : 29 bytes
Number of Transactions : 17
Mean Transaction Size : 139 bytes
Record Version(s) : 1
The warning "COMMIT BEGIN WITHOUT MATCHING COMMIT END IN LOG FILE" means that the last record in the log file is not a type CE (Commit End) record. This means that, during a commit:
In the case of a killed process with an uncatchable signal, or a system failure, the next START TRANSACTION using the corrupted log file will return TRANSACTION-STATUS 12.
The warning "2 START TRANSACTIONS WITHOUT MATCHING ROLLBACKS OR COMMITS" means that there are two transactions that have yet to be committed or rolled back. This could indicate a problem if there are no runtime processes currently using the log file.