Specify the cache size (in megabytes) of the temporary database environment internally used during the log verification.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-b</strong></span>
</p>
<p>
Specify the starting log record (by lsn) to verify.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-c</strong></span>
</p>
<p>
Specify whether to continue the verification after an error is detected.
If not specified, the verification stops when the first error is detected.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-D</strong></span>
</p>
<p>
Specify a database name. Only log records related to this database are verified.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-d</strong></span>
</p>
<p>
Specify a database file name. Only log records related this database file are verified.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-e</strong></span>
</p>
<p>
Specify the ending log record by lsn.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-h</strong></span>
</p>
<p>
Specify a home directory of the database environment whose log is to be verified.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-H</strong></span>
</p>
<p>
Specify a home directory for this utility to create a temporarily database
environment to store runtime data during the verification.
</p>
<p>
It is an error to specify the same directory as the -h option. If this directory is not specified, all
temporary databases created during the verification will be in-memory, which is not
a problem if the log files to verify are not huge.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-N</strong></span>
</p>
<p>
Do not acquire shared region mutexes while running. Other problems,
such as potentially fatal errors in Berkeley DB, are ignored as
well. This option is intended only for debugging errors, and should
not be used under any other circumstances.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-P</strong></span>
</p>
<p>
Specify an environment password. Although Berkeley DB utilities
overwrite password strings as soon as possible, 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.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-s</strong></span>
</p>
<p>
Specify the starting log record by time. The time range specified is not precise because the lsn of the most recent time point is used as the starting lsn.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-V</strong></span>
</p>
<p>
Write the library version number to the standard output and exit.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-v</strong></span>
</p>
<p>
Enable verbose mode to display verbose output during the verification process.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-z</strong></span>
</p>
<p>
Specify the ending log record by time. The time range specified is not precise because the lsn of the most recent time point is used as the ending lsn.
</p>
</li>
</ul>
</div>
<p>
To specify a range of log records, you must provide
either an lsn range or a time range. You can neither specify both nor specify an lsn and a time as a range.
</p>
<p>
If the log footprint is over several megabytes, specify a home
directory and a big cache size for log verification internal use. Else, the process'
private memory may be exhausted before the verification completes.</p>
<p>
The <spanclass="command"><strong>db_log_verify</strong></span> utility does not perform the
locking function, even in Berkeley DB environments that are configured with a
locking subsystem. All errors are written to stderr, and all normal and verbose messages
are written to stdout.
</p>
<p>
The <spanclass="command"><strong>db_log_verify</strong></span> utility can be used with a Berkeley DB environment (as
described for the <spanclass="bold"><strong>-h</strong></span> option, the
