man > db_verify(1)

man perldoc info pydoc3 ri search

📛 NAME

db5.3_verify — Verifies the structure databases

🚀 Quick Reference

Use Case	Command	Description
🔍 Verify database file(s) in current directory	db5.3_verify file.db	Verifies structure of one or more database files
📂 Verify with custom home directory	db5.3_verify -h /path/to/home file.db	Specify database environment home directory
⏭️ Skip sort/hash order checks	db5.3_verify -o file.db	Ignore non-default comparison/hashing configurations
🔇 Suppress error output	db5.3_verify -q file.db	Only return exit status, no error messages
🔓 Use environment password	db5.3_verify -P password file.db	Specify password for encrypted environment
📋 Show version	db5.3_verify -V	Print library version and exit
🔧 Debug mode (no mutex locks)	db5.3_verify -N file.db	Skip mutex acquisition — debugging only

📖 SYNOPSIS

db5.3_verify [-NoqV] [-h home] [-P password] file ...

📝 DESCRIPTION

The db5.3_verify utility verifies the structure of one or more files and the databases they contain.

⚙️ OPTIONS

📂 -h — Specify home directory

Specify a home directory for the database environment; by default, the current working directory is used.

⏭️ -o — Skip sort/hash order checks

Skip the database checks for btree and duplicate sort order and for hashing.

If the file being verified contains databases with non-default comparison or hashing configurations, calling the db5.3_verify utility without the -o flag will usually return failure. The -o flag causes db5.3_verify to ignore database sort or hash ordering and allows db5.3_verify to be used on these files. To fully verify these files, verify them explicitly using the DB->verify method, after configuring the correct comparison or hashing functions.

🔧 -N — No mutex locks (debug only)

Do not acquire shared region mutexes while running. Other problems, such as potentially fatal errors in Berkeley DB, will be ignored as well. This option is intended only for debugging errors, and should not be used under any other circumstances.

🔑 -P — Environment password

Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments.

🔇 -q — Quiet mode

Suppress the printing of any error descriptions, simply exit success or failure.

📋 -V — Show version

Write the library version number to the standard output, and exit.

⚠️ Important Notes

The db5.3_verify utility 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 db5.3_verify utility may be used with a Berkeley DB environment (as described for the -h option, the environment variable DB_HOME, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.3_verify should always be given the chance to detach from the environment and exit gracefully. To cause db5.3_verify to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT).

The db5.3_verify utility exits 0 on success, and >0 if an error occurs.

🌍 ENVIRONMENT

📁 DB_HOME

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 DB_ENV->open.

👤 AUTHORS

Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_verify from Sleepycat, by Thijs Kinkhorst <thijs AT kinkhorst.com>, for the Debian system (but may be used by others).

28 January 2005 — DB5.3_VERIFY(1)

📛 NAME 🚀 Quick Reference 📖 SYNOPSIS 📝 DESCRIPTION ⚙️ OPTIONS 🌍 ENVIRONMENT 👤 AUTHORS