You can drop a logical-log file or logslice to increase the amount of the disk space available within a dbspace. The database server requires a minimum of three logical-log files per coserver (three logslices) at all times. You can also drop a logslice to increase the amount of the disk space available within a dbslice. For more information, see Dropping a Logical-Log File or Logslice with onutil.
To make this change, you must log in as either informix or root, and the database server must be in online or quiescent mode.
Log files and logslices are dropped one at a time. Individual log files that have a status of Free (F) or newly Added (A) can be dropped immediately. Dropping a log file with a status of Used (U) is a two step process. First, the log file must also be marked Backed up (B) and must no longer be needed for fast recovery in order for the drop operation to succeed. The log file will then be marked Deleted (D). The server will automatically remove it from the log list and free its disk space after level-0 archives have been taken for all dbspaces on that coserver.
When dropping an individual log file you must use the log file number, which is different from the log unique ID. The log file number does not change as the file is re-used. For information on obtaining a display of the logical-log files and logical log file numbers, see Displaying Logical-Log Records.
Logslices are dropped by name.