Edit File - File Manager

Edit File: db_printlog.html

<html>
<head>
<title>Berkeley DB: db_printlog</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_printlog
</td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>db_printlog [-NrV] [-b start-LSN] [-e stop-LSN] [-h home] [-P password]</pre>
Description
<a name="2"></a>
The db_printlog utility is a debugging utility that dumps Berkeley DB
log files in a human-readable format.
The options are as follows:
 
-b<ul compact><li>Display log records starting at log sequence number (LSN) start-LSN;
start-LSN is specified as a file number, followed by a slash (/)
character, followed by an offset number, with no intervening whitespace.</ul>
-e<ul compact><li>Stop displaying log records at log sequence number (LSN) stop-LSN;
stop-LSN is specified as a file number, followed by a slash (/)
character, followed by an offset number, with no intervening whitespace.</ul>
-h<ul compact><li>Specify a home directory for the database environment; by
default, the current working directory is used.</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>
-r<ul compact><li>Read the log files in reverse order.</ul>
-V<ul compact><li>Write the library version number to the standard output, and exit.</ul>
 
For more information on the db_printlog output and using it to
debug applications, see <a href="../../db4-devel-4.7.25/ref/debug/printlog.html">Reviewing
Berkeley DB log files</a>.
The db_printlog 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_printlog should always be given the chance to
detach from the environment and exit gracefully. To cause db_printlog
to release all environment resources and exit cleanly, send it an
interrupt signal (SIGINT).
The db_printlog 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