Edit File - File Manager

Edit File: db_verify.html

<html>
<head>
<title>Berkeley DB: db_verify</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_verify
</td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>db_verify [-NoqV] [-h home] [-P password] file ...</pre>
Description
<a name="2"></a><a name="3"></a>
The db_verify utility verifies the structure of one or more
files and the databases they contain.
The options are as follows:
 
-h<ul compact><li>Specify a home directory for the database environment; by
default, the current working directory is used.</ul>
-o<ul compact><li>Skip the database checks for btree and duplicate sort order and for
hashing.
If the file being verified contains databases with non-default
comparison or hashing configurations, calling the db_verify
utility without the -o flag will usually return failure. The
-o flag causes db_verify to ignore database sort or
hash ordering and allows db_verify to be used on these files.
To fully verify these files, verify them explicitly using the
<a href="../../db4-devel-4.7.25/api_c/db_verify.html">DB-&gt;verify</a> method, after configuring the correct comparison or hashing
functions.</ul>
-N<ul compact><li>Do not acquire shared region mutexes while running. Other problems,
such as potentially fatal errors in Berkeley DB, will be ignored as well.
This option is intended only for debugging errors, and should not be
used under any other circumstances.</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>
-q<ul compact><li>Suppress the printing of any error descriptions, simply exit success or
failure.</ul>
-V<ul compact><li>Write the library version number to the standard output, and exit.</ul>
 
The db_verify utility does not perform any locking, even in
Berkeley DB environments that are configured with a locking subsystem. As
such, it should only be used on files that are not being modified by
another thread of control.
The db_verify utility may be used with 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_verify should always be given the chance to
detach from the environment and exit gracefully. To cause db_verify
to release all environment resources and exit cleanly, send it an
interrupt signal (SIGINT).
The db_verify 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>

Back to File Manager