Gecko [ 122.154.134.11 ]

Name	Size	Permission
berkeley_db_svc.html	3.22 KB	-rw-r--r--
db_archive.html	5.46 KB	-rw-r--r--
db_checkpoint.html	4.47 KB	-rw-r--r--
db_codegen.html	9.31 KB	-rw-r--r--
db_deadlock.html	4.48 KB	-rw-r--r--
db_dump.html	7.08 KB	-rw-r--r--
db_hotbackup.html	7.69 KB	-rw-r--r--
db_load.html	10.15 KB	-rw-r--r--
db_printlog.html	3.51 KB	-rw-r--r--
db_recover.html	5.17 KB	-rw-r--r--
db_stat.html	5.93 KB	-rw-r--r--
db_upgrade.html	4.74 KB	-rw-r--r--
db_verify.html	3.72 KB	-rw-r--r--
index.html	2.31 KB	-rw-r--r--

Code Editor : db_archive.html

<html>
<head>
<title>Berkeley DB: db_archive</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<table width="100%"><tr valign=top>
<td>
db_archive
</td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>db_archive [-adlsVv] [-h home] [-P password]</pre>
Description
<a name="2"></a>
The db_archive utility writes the pathnames of log files that
are no longer in use (for example, no longer involved in 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.
The options are as follows:
 
-a<ul compact><li>Write all pathnames as absolute pathnames, instead of relative to the
database home directories.</ul>
-d<ul compact><li>Remove log files that are no longer needed; no filenames are written.
Automatic log file removal is likely to make catastrophic recovery
impossible.</ul>
-h<ul compact><li>Specify a home directory for the database environment; by
default, the current working directory is used.</ul>
-l<ul compact><li>Write out the pathnames of all the database log files, whether or not
they are involved in active transactions.</ul>
-P<ul compact><li>Specify an environment password. Although Berkeley DB utilities overwrite
password strings as soon as possible, be aware there may be a window of
vulnerability on systems where unprivileged users can see command-line
arguments or where utilities are not able to overwrite the memory
containing the command-line arguments.</ul>
-s<ul compact><li>Write the pathnames of all the database files that need to be archived
in order to recover the database from catastrophic failure. If any of
the database files have not been accessed during the lifetime of the
current log files, db_archive will not include them in this
output.
It is possible that some of the files to which the log refers have since
been deleted from the system. In this case, db_archive will
ignore them. When <a href="../../db4-utils-4.7.25/utility/db_recover.html">db_recover</a> is run, any files to which the
log refers that are not present during recovery are assumed to have been
deleted and will not be recovered.</ul>
-V<ul compact><li>Write the library version number to the standard output, and exit.</ul>
-v<ul compact><li>Run in verbose mode.</ul>
 
Log cursor handles (returned by the <a href="../../db4-devel-4.7.25/api_c/log_cursor.html">DB_ENV-&gt;log_cursor</a> method) may have open
file descriptors for log files in the database environment. Also, the
Berkeley DB interfaces to the database environment logging subsystem (for
example, <a href="../../db4-devel-4.7.25/api_c/log_put.html">DB_ENV-&gt;log_put</a> and <a href="../../db4-devel-4.7.25/api_c/txn_abort.html">DB_TXN-&gt;abort</a>) 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 db_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 db_archive utility uses a Berkeley DB environment (as described for the
-h option, the environment variable DB_HOME, or
because the utility was run in a directory containing a Berkeley DB
environment). In order to avoid environment corruption when using a
Berkeley DB environment, db_archive should always be given the chance to
detach from the environment and exit gracefully. To cause db_archive
to release all environment resources and exit cleanly, send it an
interrupt signal (SIGINT).
The <a href="../../db4-devel-4.7.25/api_c/log_archive.html">DB_ENV-&gt;log_archive</a> method is the underlying method used by the db_archive utility.
See the db_archive utility source code for an example of using <a href="../../db4-devel-4.7.25/api_c/log_archive.html">DB_ENV-&gt;log_archive</a>
in a IEEE/ANSI Std 1003.1 (POSIX) environment.
The db_archive utility exits 0 on success, and &gt;0 if an error occurs.
 Environment Variables
 
DB_HOME<ul compact><li>If the -h option is not specified and the environment variable
DB_HOME is set, it is used as the path of the database home, as described
in <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a>.</ul>
 
</tt>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

${this.title}

Code Editor : db_archive.html