1DB_VERIFY(1)                 BerkeleyDB Utilities                 DB_VERIFY(1)
2
3
4

NAME

6       db_verify -  Verify the database structure
7

SYNOPSIS

9       db_verify [-NoqV] [-h home] [-P password] file ...
10

DESCRIPTION

12       The  db_verify  utility verifies the structure of one or more files and
13       the databases they contain.
14

OPTIONS

16       -h home
17              Specify a  home  directory  for  the  database  environment;  by
18              default, the current working directory is used.
19
20       -o     Skip  the database checks for btree and duplicate sort order and
21              for hashing.
22
23              If the file being verified contains databases  with  non-default
24              comparison  or  hashing  configurations,  calling  the db_verify
25              utility without the -o flag will usually return failure.  The -o
26              flag  causes  db_verify to ignore database sort or hash ordering
27              and allows db_verify to be used on these files.  To fully verify
28              these files, verify them explicitly using the DB->verify method,
29              after configuring the correct comparison or hashing functions.
30
31       -N     Do not acquire shared region mutexes while running.  Other prob‐
32              lems,  such  as potentially fatal errors in Berkeley DB, will be
33              ignored as well.  This option is  intended  only  for  debugging
34              errors, and should not be used under any other circumstances.
35
36       -P password
37              Specify an environment password.  Although Berkeley DB utilities
38              overwrite password strings as soon as possible, be  aware  there
39              may  be  a window of vulnerability on systems where unprivileged
40              users can see command-line arguments or where utilities are  not
41              able  to  overwrite the memory containing the command-line argu‐
42              ments.
43
44       -q     Suppress the printing of any  error  descriptions,  simply  exit
45              success or failure.
46
47       -V     Write  the  library  version  number to the standard output, and
48              exit.
49
50       The db_verify utility does not perform any locking, even in Berkeley DB
51       environments that are configured with a locking subsystem.  As such, it
52       should only be used on files that are not  being  modified  by  another
53       thread of control.
54
55       The  db_verify  utility  may be used with a Berkeley DB environment (as
56       described for the -h  option,  the  environment  variable  DB_HOME,  or
57       because  the  utility  was  run in a directory containing a Berkeley DB
58       environment).  In order to avoid environment corruption  when  using  a
59       Berkeley DB environment, db_verify should always be given the chance to
60       detach from the environment and exit gracefully.  To cause db_verify to
61       release  all  environment resources and exit cleanly, send it an inter‐
62       rupt signal (SIGINT).
63

EXIT STATUS

65       The db_verify utility exits 0 on success, and >0 if an error occurs.
66

ENVIRONMENT

68       DB_HOME
69              If the -h option is not specified and the  environment  variable
70              DB_HOME  is set, it is used as the path of the database home, as
71              described in DB_ENV->open.
72

SEE ALSO

74       db_archive(1)  db_checkpoint(1)   db_deadlock(1)   db_dump(1)   db_hot‐
75       backup(1)   db_log_verify(1)  db_load(1)  db_printlog(1)  db_recover(1)
76       db_replicate(1) db_stat(1) db_tuner(1) db_upgrade(1)
77
78
79
80BerkeleyDB 5.3.28              06 December 2016                   DB_VERIFY(1)