Using the onlog utility to monitor transactions

The onlog utility displays all or selected portions of the logical log. This utility can help you identify a problematic transaction or gauge transaction activity that corresponds to a period of high utilization, as indicated by your periodic snapshots of database activity and system-resource consumption.

This onlog utility can take input from selected log files, the entire logical log, or a backup tape of previous log files.

Use onlog with caution when you read logical-log files still on disk, because attempting to read unreleased log files stops other database activity. For greatest safety, back up the logical-log files first and then read the contents of the backup files. With proper care, you can use the onlog -n option to restrict onlog only to logical-log files that have been released.

To check on the status of logical-log files, use onstat -l.