Monitor physical and logical-logging activity
Monitor the physical log to determine the percentage of the physical-log file that gets used before a checkpoint occurs. You can use this information to find the optimal size of the physical-log file. It must be large enough that the database server is not required to force checkpoints too frequently and small enough to conserve disk space and guarantee fast recovery.
Monitor physical-log and logical-log buffers to determine if they are the optimal size for the current level of processing. The important statistic to monitor is the pages-per-disk-write statistic. For more information about tuning the physical-log and logical-log buffers, see your HCL OneDB™ Performance Guide.
To monitor the physical-log file, physical-log buffers, and logical-log buffers, use the following commands.
Utility | Command | Additional information |
---|---|---|
Command line Command line or ISA |
onstat -l | The first line displays the following information
for each physical-log buffer:
The second line displays the following information about the
physical log:
The third line displays the following information about
each logical-log buffer:
|
Command line Command line or ISA |
onparams -p | Moves or resizes the physical log. |
Command line Command line or ISA |
onmode -l | Advances to the next logical-log file. |
ISA | Click Advance Log File. |
For more information about and an example of onstat -l output, see the HCL OneDB Administrator's Reference.
For information about using SQL administration API commands instead of some onparams and onmode commands, see Remote administration with the SQL administration API and the HCL OneDB Guide to SQL: Syntax.