>>-DROP--+---------+--LOG--lognum-------------------------------> '-LOGICAL-' >--+-------------------------------+--------------------------->< '-COSERVER--+-coserver_number-+-' '-coserver_name---'
Element | Purpose | Restrictions | Syntax |
---|---|---|---|
lognum | Log file number to drop | The database server requires a minimum of three
logical-log files at all times. The database server must be in quiescent
or online mode when you drop a logical log.
You can drop only log files that have status of Free (F), newly Added (A), or Used and Backed up (U-B). To view the status of the logical logs, use xctl onstat -l. |
Unsigned integer. |
coserver_name | Name of the coserver from which to drop the logical log | The coserver name must have the following format:
dbservername.coserver_number The value of dbservername must be the same as the value in the DBSERVERNAME configuration parameter. The value of coserver_number must be one of the integers that the COSERVER configuration parameter specifies. |
See Coserver Name. |
coserver_number | The number of the coserver on which the dbspace is to reside | The coserver number must be one of the integers that the COSERVER configuration parameter specifies. | Unsigned integer. |
The onutil DROP LOGICAL LOG statement to drop a logical-log file is one of the steps in the procedure for moving logical-log files to another dbspace. The database server must be in quiescent or online mode when you drop a logical-log file.
Use the LOG clause, followed by a lognum to specify which logical-log file you want to drop. (You can obtain the number of a log file from the number field of xctl onstat -l.) After your configuration reflects the desired number of log files, create a level-0 backup of the root dbspace. For information about how to create a level-0 backup, see the IBM Informix: Backup and Restore Guide.
A specific coserver owns and manages each dbspace. This coserver is referred to as the home coserver. You can specify the home coserver with the COSERVER option.
When you do not specify the COSERVER option, the database server drops the logical log from coserver number 1.