db_log_verify(1)

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

NAME

6       db_log_verify - Verify log files of a database environment
7

SYNOPSIS

9       db_log_verify [-cNvV] [-h home-to-verify] [-H temporary-home] [-P pass‐
10       word] [-C cache-size] [-b start-lsn] [-e end-lsn] [-s  start-time]  [-z
11       end-time] [-d database-filename] [-D database-name]
12

DESCRIPTION

14       The db_log_verify utility verifies the log files of a specific database
15       environment.  This utility verifies a specific range of log records, or
16       changed log records of a specific database.
17

OPTIONS

19       -C cache-size
20              Specify  the cache size (in megabytes) of the temporary database
21              environment internally used during the log verification.
22
23       -b start-lsn
24              Specify the starting log record (by lsn) to verify.
25
26       -c     Specify whether to continue the verification after an  error  is
27              detected.   If  not  specified,  the verification stops when the
28              first error is detected.
29
30       -D database-name
31              Specify a database name. Only log records related to this  data‐
32              base are verified.
33
34       -d database-filename
35              Specify  a  database  file  name.  Only log records related this
36              database file are verified.
37
38       -e end-lsn
39              Specify the ending log record by lsn.
40
41       -h home-to-verify
42              Specify a home directory of the database environment  whose  log
43              is to be verified.
44
45       -H temporary-home
46              Specify  a home directory for this utility to create a temporar‐
47              ily database environment to store runtime data during the  veri‐
48              fication.
49
50              It  is  an error to specify the same directory as the -h option.
51              If this directory is not specified, all temporary databases cre‐
52              ated  during  the verification will be in-memory, which is not a
53              problem if the log files to verify are not huge.
54
55       -N     Do not acquire shared region mutexes while running. Other  prob‐
56              lems,  such  as  potentially  fatal  errors  in Berkeley DB, are
57              ignored as well. This option  is  intended  only  for  debugging
58              errors, and should not be used under any other circumstances.
59
60       -P password
61              Specify  an environment password. Although Berkeley DB utilities
62              overwrite password strings as soon as possible, there may  be  a
63              window  of vulnerability on systems where unprivileged users can
64              see command-line arguments or where utilities are  not  able  to
65              overwrite the memory containing the command-line arguments.
66
67       -s start-time
68              Specify  the  starting log record by time. The time range speci‐
69              fied is not precise because the lsn  of  the  most  recent  time
70              point is used as the starting lsn.
71
72       -V     Write  the  library  version  number  to the standard output and
73              exit.
74
75       -v     Enable verbose mode to display verbose output during the verifi‐
76              cation process.
77
78       -z end-time
79              Specify  the ending log record by time. The time range specified
80              is not precise because the lsn of the most recent time point  is
81              used as the ending lsn.
82
83       To specify a range of log records, you must provide either an lsn range
84       or a time range.  You can neither specify both nor specify an lsn and a
85       time as a range.
86
87       If  the  log footprint is over several megabytes, specify a home direc‐
88       tory and a big cache size for log verification internal use. Else,  the
89       process'  private  memory may be exhausted before the verification com‐
90       pletes.
91
92       The db_log_verify utility does not perform the locking  function,  even
93       in  Berkeley DB environments that are configured with a locking subsys‐
94       tem.  All errors are written to stderr, and all normal and verbose mes‐
95       sages are written to stdout.
96
97       The  db_log_verify utility uses a Berkeley DB environment (as described
98       for the -h option, the environment variable  DB_HOME,  or  because  the
99       utility  was  run in a directory containing a Berkeley DB environment).
100       In order to avoid environment corruption when using a Berkeley DB envi‐
101       ronment, db_log_verify should always be given the chance to detach from
102       the environment and exit gracefully.  To cause db_log_verify to release
103       all environment resources and exit cleanly, send it an interrupt signal
104       (SIGINT).
105

EXIT STATUS

107       The db_log_verify utility exits 0  on  success,  and  >0  if  an  error
108       occurs.
109

ENVIRONMENT

111       DB_HOME
112              If  the  -h option is not specified and the environment variable
113              DB_HOME is set, it is used as the path of the database home,  as
114              described in DB_ENV->open.
115

NOTES

117       If  the  application(s)  that  use  the  environment  make  use  of the
118       DB_ENV->set_lg_dir method, then in order for this utility to  run  cor‐
119       rectly, you need a DB_CONFIG file which sets the proper paths using the
120       set_lg_dir configuration parameter.
121