>>-CREATE--+---------+--LOG--DBSPACE--+-dbspace_identifier-+----> '-LOGICAL-' '-dbspace_name-------' >--+------------------------+---------------------------------->< '-SIZE--size--+--------+-' +-KBYTES-+ +-MBYTES-+ '-GBYTES-'
| Element | Purpose | Restrictions | Syntax |
|---|---|---|---|
| dbspace_name | Name of the dbspace where the logical-log file resides | The space that is allocated for a logical-log
file must be contiguous. The database server does not allow you
to add a log file to a dbspace without adequate contiguous space.
You cannot add a log file during a backup. |
See Dbspace Name. |
| dbspace_identifier | Generated name of the dbspace where the logical
log resides
The database server generates the name when you create a dbslice. |
The dbspace identifier must be an existing dbspace
that was generated when you created a dbslice. The name must be
of the form:
slicename.ordinal The value for slicename must be the same as the dbslice name that you used when you created the dbslice. The ordinal value must be an unsigned integer. |
See Derived Dbspace Identifier. |
| size | The size of the new logical-log file | Value must be greater than or equal to the minimum of 200 kilobytes. If you do not specify a SIZE clause, the size of the log file is taken from the value of the LOGSIZE parameter in the ONCONFIG file. (See changing LOGSIZE in the chapter on managing logical-log files in the IBM Informix: Administrator's Guide.) | Unsigned integer; the default unit is kilobytes. |
The database server must be in quiescent or online mode when you add a logical-log file. Use the onutil CREATE LOGICAL LOG command to add a new logical-log file. You can use the following keywords.
The following example shows how to add a logical log to the root dbspace.
% onutil 1> CREATE LOG DBSPACE rootdbs 2> SIZE 1400; Logical log successfully added.
To monitor the logical-log status, use the onstat -l command. For more information, see The onstat -l Option.