1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>db_verify</title>
<link rel="stylesheet" href="apiReference.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
<link rel="start" href="index.html" title="Berkeley DB C API Reference" />
<link rel="up" href="utilities.html" title="Appendix A. Berkeley DB Command Line Utilities" />
<link rel="prev" href="db_upgrade.html" title="db_upgrade" />
<link rel="next" href="sqlite3.html" title="sqlite3" />
</head>
<body>
<div xmlns="" class="navheader">
<div class="libver">
<p>Library Version 12.1.6.1</p>
</div>
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">db_verify</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="db_upgrade.html">Prev</a> </td>
<th width="60%" align="center">Appendix A.
Berkeley DB Command Line Utilities
</th>
<td width="20%" align="right"> <a accesskey="n" href="sqlite3.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="db_verify"></a>db_verify</h2>
</div>
</div>
</div>
<pre class="programlisting">db_verify [-mNoqV] [-b blob_dir] [-h home] [-P password] name ... </pre>
<p>
The <span class="command"><strong>db_verify</strong></span> utility verifies the structure of one or more files and
the databases they contain. If '-m' option is specified, it verifies one or more named
in-memory databases.
</p>
<p>
The options are as follows:
</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>
<span class="bold"><strong>-b</strong></span>
</p>
<p>
Specify the directory where BLOB data is stored. By default, if using a
database environment, the BLOB data is placed in a subdirectory within the
environment, otherwise, it is placed in a directory local to the current
working directory.
</p>
</li>
<li>
<p>
<span class="bold"><strong>-h</strong></span>
</p>
<p>
Specify a home directory for the database environment; by default, the
current working directory is used.
</p>
</li>
<li>
<p>
<span class="bold"><strong>-m</strong></span>
</p>
<p>
Verify the named in-memory databases.
</p>
</li>
<li>
<p>
<span class="bold"><strong>-o</strong></span>
</p>
<p>
Skip the database checks for btree and duplicate sort order and for
hashing.
</p>
<p>
If the file being verified contains databases with non-default
comparison or hashing configurations, calling the <span class="command"><strong>db_verify</strong></span> utility
without the <span class="bold"><strong>-o</strong></span> flag will usually
return failure. The <span class="bold"><strong>-o</strong></span> flag causes
<span class="command"><strong>db_verify</strong></span> to ignore database sort or hash ordering and allows
<span class="command"><strong>db_verify</strong></span> to be used on these files. To fully verify these files,
verify them explicitly using the <a class="xref" href="dbverify.html" title="DB->verify()">DB->verify()</a>
method, after configuring the correct comparison or hashing functions.
</p>
</li>
<li>
<p>
<span class="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, will be ignored as
well. This option is intended only for debugging errors, and should
not be used under any other circumstances.
</p>
</li>
<li>
<p>
<span class="bold"><strong>-P</strong></span>
</p>
<p>
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.
</p>
</li>
<li>
<p>
<span class="bold"><strong>-q</strong></span>
</p>
<p>
Suppress the printing of any error descriptions, simply exit success
or failure.
</p>
</li>
<li>
<p>
<span class="bold"><strong>-V</strong></span>
</p>
<p>
Write the library version number to the standard output, and exit.
</p>
</li>
</ul>
</div>
<p>
<span class="bold"><strong>The <span class="command"><strong>db_verify</strong></span> 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.</strong></span>
</p>
<p>
The <span class="command"><strong>db_verify</strong></span> utility may be used with a Berkeley DB environment (as
described for the <span class="bold"><strong>-h</strong></span> option, the
environment variable <span class="bold"><strong>DB_HOME</strong></span>, 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, <span class="command"><strong>db_verify</strong></span> should always be given the chance
to detach from the environment and exit gracefully. To cause
<span class="command"><strong>db_verify</strong></span> to release all environment resources and exit cleanly, send
it an interrupt signal (SIGINT).
</p>
<p>
The <span class="command"><strong>db_verify</strong></span> utility exits 0 on success, and >0 if an error
occurs.
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="idp5361000"></a>Environment Variables</h3>
</div>
</div>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a id="idp5378376"></a>DB_HOME</h4>
</div>
</div>
</div>
<p>
If the <span class="bold"><strong>-h</strong></span> 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 the
<a class="xref" href="envopen.html" title="DB_ENV->open()">DB_ENV->open()</a>
method.
</p>
</div>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="db_upgrade.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="utilities.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="sqlite3.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">db_upgrade </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> sqlite3</td>
</tr>
</table>
</div>
</body>
</html>
|
