Dropping logical-log files
You can use an onparams command or ON-Monitor to drop logical-log files.
About this task
To drop a logical-log file and increase the amount of the disk space available within a dbspace, you can use onparams. The database server requires a minimum of three logical-log files at all times. You cannot drop a log if your logical log is composed of only three log files.
- If you drop a log file that has never been written to (status A), the database server deletes it and frees the space immediately.
- If you drop a used log file (status U-B), the database server marks it as deleted (D). After you take a level-0 backup of the dbspaces that contain the log files and the root dbspace, the database server deletes the log file and frees the space.
- You cannot drop a log file that is currently in use or contains the last checkpoint record (status C or L).
To drop a logical-log file with onparams:
Procedure
Results
For information about using onparams to drop a logical-log file, see the HCL OneDB™ Administrator's Reference.
For information about using onlog to display the logical-log files and unique ID numbers, see Display logical-log records.
To drop a logical-log file with ON-Monitor (UNIX™):
- Ensure that the database server is in online, administration, or quiescent mode.
- To drop a logical-log file, select .
- If the log file has a status of newly Added (A), it is
dropped immediately.
If the log file has a status of Used (U), it is marked as Deleted (D).
- To drop a used log file, take a level-0 backup of all the dbspaces.Tip: If the root dbspace has never been backed up, you can drop a used log file immediately.