WRAPDBE

Associates a new DBEnvironment with the log files of an inaccessible DBEnvironment. It wraps the new DBEnvironment around orphaned log files.

Scope

SQLUtil Only

SQLUtil Syntax

>> WRAPDBE WrapperDBEnvironment Name: WrapperDBEnvironmentName Maintenance Word: MaintenanceWord Wrapper Mode (log) (opt): Log Enter Log File Name(s) Separated by a Blank? (RETURN to finish): LogFileName1 Enter Log File Name(s) Separated by a Blank? (RETURN to finish): Convert to Wrapper DBEnvironment (y/n)? { Y [es] N [o]}

Parameters

DBEnvironmentName: is the name of a Wrapper DBEnvironment. Must be the name of an empty DBEnvironment previously created to wrap around the log files.
MaintenanceWord: is the Maintenance Word. Must be the Maintenance Word of the DBEnvironment.
Wrapper Mode: is the mode. Log is the default and only mode presently allowed.
LogFileName1: physical name of a log file that is to be wrapped.
Convert to Wrapper DBEnvironment: converts the empty DBEnvironment to a wrapper DBEnvironment or gives you the opportunity to exit this command without wrapping a DBEnvironment around the orphaned log file(s).

Description

This command wraps a DBEnvironment around log files orphaned after a hard crash of a DBEnvironment.
The DBEnvironment can be empty or it can have tables on which updates have been performed.
No updates can be made to the DBEnvironment after it has been converted to a wrapper DBEnvironment with this command. Any updates must be performed before this command is issued.
The log files around which the DBEnvironment is to be wrapped must be valid and must be marked as usable log files before this command is used. Refer to the section of this manual that describes wrapper DBEnvironment use.
The log files entered should constitute a correct log file sequence list with no sequence numbers missing. If the DBEnvironment that crashed has dual log files, then log file names can be taken from either of the dual log files, as long as they constitute a proper sequence. The proper list of log files must be determined before using the WRAPDBE command.
The DBEnvironment to be wrapped around the orphaned log files must be created before the WRAPDBE command is used. The DBEnvironment is created with the START DBE NEW statement. Refer to the "Setting up a Wrapper DBEnvironment" section of the "Backup and Recovery" SECT of this manual.
WRAPDBE prompts for the names of files around which the WrapperDBE is to be wrapped. WRAPDBE does not accept more than one file name on a single line.
Any log files associated with the wrapper DBEnvironment before it is converted are removed. Only the wrapped log files are associated with the DBEnvironment after the WRAPDBE command is executed.

For more information, refer to the "Backup and Recovery" SECT.

Authorization

You must be the superuser (HP-UX) or system administrator (MPE/iX) or DBECreator of the original inaccessible DBEnvironment to use this command.

Example

   >> WRAPDBE

   DBEnvironment Name:  WRAPDBE1

   Maintenance Word:   Return 

   Wrapper Mode (log) (opt): log

   Enter Log File Name Separated by a Blank? (RETURN to finish):    LGN1

   Enter Log File Name Separated by a Blank? (RETURN to finish):

   Convert to Wrapper DBEnvironment (y/n)? y