 |
» |
|
|
|
Stores a copy of a log file without accessing the DBECon file.
You use this command to store a log file that cannot be stored
using STORELOG. Scope | |
SQLUtil Only SQLUtil Syntax | |
>> RESCUELOG [APPEND] Log File Name: LogFileName Size Of The Log File: LogFileSize To File Name? StoreFile Rescue Log File(y/n)? { Y[es] N[o] } Parameters | |
- LogFileName
is the name of the log file that is to be rescued (that is, stored).
- LogFileSize
is the size in 512-byte pages of the log file that is to be
rescued.
- StoreFile
is the pathname of the store file. For tape files, this is an
absolute pathname. For disk store files, the pathname may be
an absolute pathname or a pathname relative to the current working directory.
The maximum length of a pathname is 44 bytes.
Description | |
This command lets you store a log file. It is normally used only
with files that cannot be stored with STORELOG.
Normally, this command would only be used following the corruption of
DBEnvironment files through a media failure or some other serious problem.
If you are unable to connect to the DBEnvironment,
use a static SHOWLOG to display log files
that have not been stored, then use RESCUELOG to store them.
If more than one tape
volume is required to store the file, a request will
be displayed on the console. The next tape can then be mounted.
Use the APPEND option to begin the store at the end of a previous
backup. This option is only available if you have selected OMNIBACK
as the backup method using a SET BACKUP command. The default is to
start the store at the beginning of a device.
Authorization | |
Any user may execute this command. Example | |
>> rescuelog
Log File Name: DBELOG6
Size Of The Log File: 250
To File Name? /extra/lgn1
Rescue Log File(y/n)? y
Log file 'DBELOG6' with Sequence Number 12 was rescued.
|
|
