Use the START DBE NEWLOG command to create a new log file
with different characteristics as you open the DBEnvironment.
You must be the
DBECreator to use this command.
The START DBE NEWLOG command may be used for the following reasons:
To change the name or size of the current log file.
To enable or disable dual logging.
To return to nonarchive logging mode from archive mode.
The following procedure is recommended when using START DBE NEWLOG
to ensure the safety of log records and the consistency
of the DBEnvironment:
Stop the DBEnvironment.
If in archive mode, back up log files as desired using STORELOG
and RESCUELOG. (You don't need to back up the log files in nonarchive
mode because you can not use them for rollforward recovery.)
Perform a START DBE NEWLOG.
You should specify file names different
from the old log names
in the NAME = clause.
The following example shows how
to start a new log file for the sample DBEnvironment, using
different log file names:
isql=> START DBE 'PARTSDBE.SOMEGRP.SOMEACCT' MULTI NEWLOG
> DUAL LOG,
> TRANSACTION=7
> LOG DBEFILE PartsLg3 AND PartsLg4
> WITH PAGES = 250,
> NAME = 'DBELog3.Log1Grp.SomeAcct' AND 'DBELog4.Log2Grp.SomeAcct';
|
The physical files are created in groups different
from that of the DBECon file, but the account is
(and must be) the same as that of the DBECon file.
The new log file is in nonarchive mode. If you wish, you can start
a new log in archive mode by using the ARCHIVE LOG option in the
START DBE NEWLOG command.
 |
| |
|
 | NOTE:
If you change from archive mode logging to nonarchive mode logging,
rollforward recovery will be impossible beyond the last archive log file. |
|
| |
|
