|
|
|
A wrapper DBEnvironment is a DBEnvironment
created to wrap around the log files orphaned after a hard crash
of a DBEnvironment. Wrapping log files means associating the files
with a wrapper DBEnvironment. After a DBEnvironment becomes inaccessible, its
log files are not associated with any DBEnvironment. These orphaned
log files are then also inaccessible.
Wrapper DBEnvironments are usually used with inaccessible audit
DBEnvironments, but they can be used to retrieve
the log files of any inaccessible DBEnvironment.
After you wrap the log files, you can then try to extract
audit information from the audit log records in the wrapped log
files with SQLAudit by partition number.
Access to wrapped log files avoids having a gap in the ongoing
record of audit information. The use of archive logging facilitates
wrapper DBEnvironment use, but nonarchive logging does not prevent
use of wrapper DBEnvironments.
To wrap log files, the orphaned log files marked Usable are first displayed and
selected. Then, it must be ensured that each log file is inactive. A
DBEnvironment is then created with the START DBE NEW statement and the
new DBEnvironment is converted to a wrapper
DBEnvironment with the SQLUtil WRAPDBE command.
 |
NOTE: Recovery of the database itself is a separate operation. It is
recommended that the log files be wrapped before recovery operations.
|
For detailed information on database recovery and wrapper DBEnvironments, refer
to the ALLBASE/SQL Database Administration Guide.
|
Complete PDF