db_log_verify [-cNvV] [-h home to verify] [-H temporary home] 
	[-P password] [-C cache size]
	[-b start lsn] [-e end lsn] [-s start time] [-z end time]
	[-d database file name] [-D database name]  

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


If the application(s) that use the environment make use of any of the following methods:


then in order for this utility to run correctly, you need a DB_CONFIG file which sets the proper paths using the add_data_dir, or set_lg_dir configuration parameters.

The options are as follows:

To specify a range of log records, you must provide either an lsn range or a time range. You can neither specify both nor specify an lsn and a time as a range.

If the log footprint is over several megabytes, specify a home directory and a big cache size for log verification internal use. Else, the process' private memory may be exhausted before the verification completes.

The db_log_verify utility does not perform the locking function, even in Berkeley DB environments that are configured with a locking subsystem. All errors are written to stderr, and all normal and verbose messages are written to stdout.

The db_log_verify utility can be used with a Berkeley DB environment (as described for the -h option, the environment variable DB_HOME). To avoid environment corruption when using a Berkeley DB environment, db_log_verify must be given the chance to detach from the environment and exit gracefully. For the db_log_verify utility to release all environment resources and exit, send an interrupt signal (SIGINT) to it.

The db_log_verify utility returns a non-zero error value on failure and 0 on success.

Environment Variables


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 the DbEnv::open() method.