int DB->verify(DB *db, const char *file, const char *database, FILE *outfile, u_int32_t flags);
The DB->verify method verifies the integrity of all databases in the file specified by the file argument, and optionally outputs the databases' key/data pairs to the file stream specified by the outfile argument.
The flags value must be set to 0 or the following value:
Because the key/data pairs are output in page order as opposed to the sort order used by db_dump, using DB->verify to dump key/data pairs normally produces less than optimal loads for Btree databases.
In addition, the following flags may be set by bitwise inclusively OR'ing them into the flags parameter:
Note: different systems may have different notions about what characters are considered printing characters, and databases dumped in this manner may be less portable to external systems.
The DB->verify method normally verifies that btree keys and duplicate items are correctly sorted, and hash keys are correctly hashed. If the file being verified contains multiple databases using differing sorting or hashing algorithms, some of them must necessarily fail database verification because only one sort order or hash function can be specified before DB->verify is called. To verify files with multiple databases having differing sorting orders or hashing functions, first perform verification of the file as a whole by using the DB_NOORDERCHK flag, and then individually verify the sort order and hashing function for each database in the file using the DB_ORDERCHKONLY flag.
When this flag is specified, a database argument should also be specified, indicating the database in the physical file which is to be checked. This flag is only safe to use on databases that have already successfully been verified using DB->verify with the DB_NOORDERCHK flag set.
The database argument must be set to NULL except when the DB_ORDERCHKONLY flag is set.
The DB->verify method 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.
The DB->verify interface may not be called after the DB->open interface is called.
The DB->verify method returns a non-zero error value on failure, 0 on success, and DB_VERIFY_BAD if a database is corrupted. When the DB_SALVAGE flag is specified, the DB_VERIFY_BAD return means that all key/data pairs in the file may not have been successfully output.
The DB->verify method is the underlying interface used by the db_verify utility. See the db_verify utility source code for an example of using DB->verify in a IEEE/ANSI Std 1003.1 (POSIX) environment.
DB->verify is affected by any database directory specified using the DB_ENV->set_data_dir method, or by setting the "set_data_dir" string in the environment's DB_CONFIG file.
The DB->verify method may fail and return a non-zero error for the following conditions:
DB->verify was called after DB->open.
The DB->verify method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB->verify method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
Copyright Sleepycat Software