Adding logical-log files manually
You can use an onparams command or ON-Monitor to add logical-log files.
About this task
You might add logical-log files manually for the following
reasons:
- To increase the disk space allocated to the logical log
- To change the size of your logical-log files
- To enable an open transaction to roll back
- As part of moving logical-log files to a different dbspace
Restriction: You cannot do the following actions:
- Add a log file to a blobspace or sbspace.
- Add logical or physical logs to dbspaces that have non-default page sizes.
Add logical-log files one at a time, up to a maximum of 32,767 files, to any dbspace. As soon as you add a log file to a dbspace, it becomes a critical dbspace. You can add a logical-log file during a storage space backup.
You can add a logical-log file in either of the following locations:
- At the end of the file list using the onparams -a command
- After the current logical-log file using the onparams -a -i command
To add a logical-log file using onparams
Procedure
Results
For more information about using onparams to add a logical-log file, see the HCL OneDB Administrator's Reference.
To add a logical-log file with ON-Monitor (UNIX)
- Follow the instructions on adding a log file in Adding logical-log files manually, except use ON-Monitor instead of onparams.
- Select to add a logical-log file.
- In the field labeled Dbspace Name, enter the name of the
dbspace where the new logical-log file is located.
The size of the log file automatically is in the Logical Log Size field. The new log file is always the value specified by LOGSIZE.