1<!--$Id: db_verify.so,v 10.11 2006/10/05 01:06:08 bostic Exp $--> 2<!--Copyright (c) 1997,2008 Oracle. All rights reserved.--> 3<!--See the file LICENSE for redistribution information.--> 4<html> 5<head> 6<title>Berkeley DB: db_verify</title> 7<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> 8<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> 9</head> 10<body bgcolor=white> 11<table width="100%"><tr valign=top> 12<td> 13<b>db_verify</b> 14</td> 15</tr></table> 16<hr size=1 noshade> 17<tt> 18<b><pre>db_verify [<b>-NoqV</b>] [<b>-h home</b>] [<b>-P password</b>] file ...</pre></b> 19<b>Description</b> 20<a name="2"><!--meow--></a><a name="3"><!--meow--></a> 21<p>The db_verify utility verifies the structure of one or more 22files and the databases they contain.</p> 23<p>The options are as follows:</p> 24<br> 25<b>-h</b><ul compact><li>Specify a home directory for the database environment; by 26default, the current working directory is used.</ul> 27<b>-o</b><ul compact><li>Skip the database checks for btree and duplicate sort order and for 28hashing. 29<p>If the file being verified contains databases with non-default 30comparison or hashing configurations, calling the db_verify 31utility without the <b>-o</b> flag will usually return failure. The 32<b>-o</b> flag causes db_verify to ignore database sort or 33hash ordering and allows db_verify to be used on these files. 34To fully verify these files, verify them explicitly using the 35<a href="/api_c/db_verify.html">DB->verify</a> method, after configuring the correct comparison or hashing 36functions.</p></ul> 37<b>-N</b><ul compact><li>Do not acquire shared region mutexes while running. Other problems, 38such as potentially fatal errors in Berkeley DB, will be ignored as well. 39This option is intended only for debugging errors, and should not be 40used under any other circumstances.</ul> 41<b>-P</b><ul compact><li>Specify an environment password. Although Berkeley DB utilities overwrite 42password strings as soon as possible, be aware there may be a window of 43vulnerability on systems where unprivileged users can see command-line 44arguments or where utilities are not able to overwrite the memory 45containing the command-line arguments.</ul> 46<b>-q</b><ul compact><li>Suppress the printing of any error descriptions, simply exit success or 47failure.</ul> 48<b>-V</b><ul compact><li>Write the library version number to the standard output, and exit.</ul> 49<br> 50<p><b>The db_verify utility does not perform any locking, even in 51Berkeley DB environments that are configured with a locking subsystem. As 52such, it should only be used on files that are not being modified by 53another thread of control.</b></p> 54<p>The db_verify utility may be used with a Berkeley DB environment (as described for the 55<b>-h</b> option, the environment variable <b>DB_HOME</b>, or 56because the utility was run in a directory containing a Berkeley DB 57environment). In order to avoid environment corruption when using a 58Berkeley DB environment, db_verify should always be given the chance to 59detach from the environment and exit gracefully. To cause db_verify 60to release all environment resources and exit cleanly, send it an 61interrupt signal (SIGINT).</p> 62<p>The db_verify utility exits 0 on success, and >0 if an error occurs.</p> 63<br><b>Environment Variables</b> 64<br> 65<b>DB_HOME</b><ul compact><li>If the <b>-h</b> option is not specified and the environment variable 66DB_HOME is set, it is used as the path of the database home, as described 67in <a href="/api_c/env_open.html">DB_ENV->open</a>.</ul> 68<br> 69</tt> 70<p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> 71</body> 72</html> 73