public void verify(String file, String database, java.io.OutputStream outfile, int flags) throws DbException;
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 a file stream.
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:
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.DB_NOORDERCHK flag, and then individually verify the sort order and hashing function for each database in the file using the Db.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.DB_NOORDERCHK flag 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 database argument must be set to null except when the Db.DB_ORDERCHKONLY flag is set.
The Db.verify method throws an exception that encapsulates a non-zero error value on failure, and Db.DB_VERIFY_BAD if a database is corrupted. When the Db.DB_SALVAGE flag is specified, the Db.DB_VERIFY_BAD return means that all key/data pairs in the file may not have been successfully output.
The Db.verify method may fail and throw an exception encapsulating a non-zero error for the following conditions:
The Db.verify method may fail and throw an exception for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the Db.verify method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.
Copyright Sleepycat Software