db4.3_archive(1)
NAME
- db4.3_archive - Find unused log files for archiving pur
- poses
SYNOPSIS
db4.3_archive [-adlsVv] [-h home] [-P password]
DESCRIPTION
Arrayin active transactions), to the standard output, one pathname per
line. These log files should be written to backup media to provide for recovery in the case of catastrophic failure (which also
requires a snapshot of the database files), but they may then be
deleted from the system to reclaim disk space.
OPTIONS
- Arraydatabase environment. Also, the Berkeley DB interfaces to the
database environment logging subsystem (for example,
DB_ENV->log_put and DB_TXN->abort) may allocate log cursors and
have open file descriptors for log files as well. On operating
systems where filesystem related system calls (for example, rename and unlink on Windows/NT) can fail if a process has an open
file descriptor for the affected file, attempting to move or remove the log files listed by db4.3_archive may fail. All Berkeley DB internal use of log cursors operates on active log files
only and furthermore, is short-lived in nature. So, an application seeing such a failure should be restructured to close any
open log cursors it may have, and otherwise to retry the operation until it succeeds. (Although the latter is not likely to be
necessary; it is hard to imagine a reason to move or rename a log
file in which transactions are being logged or aborted.)
The db4.3_archive utility uses a Berkeley DB environment - (as described for the -h option, the environment variable
DB_HOME
- Arraysource code for an example of using DB_ENV->log_archive in a
IEEE/ANSI Std 1003.1 (POSIX) environment.
The db4.3_archive utility exits 0 on success, and >0 if an - error occurs.
ENVIRONMENT
Arraydatabase home, as described in DB_ENV->open.
AUTHORS
- ArrayThijs Kinkhorst <thijs@kinkhorst.com>, for the Debian system (but
may be used by others).
28 January 2005