1I&Berkeley DB: db_recover[P

db_recover





(db_recover [-cv] [-h home]




Description



CThe db_recover utility must be run after an unexpected application,MBerkeley DB, or system failure to restore the database to a consistent state.DAll committed transactions are guaranteed to appear after db_recoverDhas run, and all uncommitted transactions will be completely undone.

The options are as follows:

-

-c
Failure was catastrophic.>

-h
Specify a home directory for the database.(

-v
Run in verbose mode.


IIn the case of catastrophic failure, an archival copy, or snapshotNof all database files must be restored along with all of the log files written*since the database file snapshot was made.L(If disk space is a problem, log files may be referenced by symbolic links).<For further information on creating a database snapshot, see@Archival Procedures.3For further information on performing recovery, see@Recovery Procedures.

KIf the failure was not catastrophic, the files present on the system at the3time of failure are sufficient to perform recovery.

>If log files are missing, db_recover will identify the missingDlog file(s) and fail, in which case the missing log files need to be&restored and recovery performed again.

OThe db_recover utility attaches to one or more of the Berkeley DB shared memoryHregions. In order to avoid region corruption, it should always be givenJthe chance to detach and exit gracefully. To cause db_recover to clean up<after itself and exit, send it an interrupt signal (SIGINT).

EThe db_recover utility exits 0 on success, and >0 if an error occurs.



Environment Variables





DB_HOME
EIf the -h option is not specified and the environment variableIDB_HOME is set, it is used as the path of the database home, as described8in db_appinit.




See Also

4db_archive,:db_checkpoint,6db_deadlock,.db_dump,.db_load, db_recover,and.db_stat.
ÿÿ