Manage logical-log files
You must manage logical-log files even if none of your databases uses transaction logging. See Logical log for background information about logical logs.
You must log-in as either informix or root on UNIX™ to make any of the changes described in this chapter. You must be a member of the Informix-Admin group on Windows™.
You perform these tasks when setting up your logical log:
- Before you initialize or restart the database server, use the LOGFILES parameter to specify the number of logical-log files to create.
- After the database server is online, estimate the size and number of logical-log files that your system requires.
- If you do not want to use the default values, change the LOGSIZE and LOGBUFF configuration parameters.
- Add the estimated number of logical-log files.
You perform the following tasks routinely:
- Backing up a logical-log file
- Switching to the next logical-log file
- Freeing a logical-log file
- Monitoring logging activity and log-backup status
You perform these tasks occasionally, if necessary:
- Adding a logical-log file
- Dropping a logical-log file
- Changing the size of a logical-log file
- Moving a logical-log file
- Changing the logical-log configuration parameters
- Monitoring event alarms for logical logs
- Setting high-watermarks for transactions
For information about using SQL administration API commands instead of some oncheck, onmode, onparams and onspaces commands, see Remote administration with the SQL administration API and the HCL OneDB™ Administrator's Reference.