DB_VERIFY(1)

💖 DB_VERIFY — the verify-the-database-structure utility, from BerkeleyDB Utilities 💖

okay bestie, sit down, hydrate, because we're doing db_verify from the BerkeleyDB Utilities fam and it's actually so useful. it verifies the database structure. that's the whole vibe. 🦋

---

✨ NAME ✨

db_verify — verify the database structure 🔍

---

🌸 SYNOPSIS 🌸

db_verify [-NoqV] [-h home] [-P password] file ...

---

🎀 DESCRIPTION 🎀

so like, the db_verify utility verifies the structure of one or more files and the databases they contain. plural files. plural databases. it's thorough like that. 💅

---

👑 OPTIONS 👑

• -h home — tell it where the home directory for the database environment lives. if you don't say anything, it just uses the current working directory. default behavior, iconic. 🏠
• -o — skip the database checks for btree and duplicate sort order, and for hashing. ngl this one needs a sec to explain, so:

if the file you're verifying has databases with non-default comparison or hashing configurations, running db_verify without the -o flag will usually return failure. like, it will be dramatic about it. the -o flag makes db_verify ignore database sort or hash ordering, which lets you actually use db_verify on those files.

but bestie, heads up: to fully verify these files, verify them explicitly using the DB->verify method, after configuring the correct comparison or hashing functions. -o is the shortcut, not the whole story. 💀

• -N — do not acquire shared region mutexes while running. also, other problems — like 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. fr fr. do not make this your personality.

• -P password — specify an environment password.

okay so real talk: 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. so like… be mindful. 🙈

• -q — suppress the printing of any error descriptions. it simply exits success or failure. no notes, no drama, just vibes and an exit code. 🤐
• -V — write the library version number to the standard output, and exit. cute little version check moment. ⭐

---

🧚 the important behavior stuff 🧚

the db_verify utility does not perform any locking, even in Berkeley DB environments that are configured with a locking subsystem. the way that it just does not lock, at all. so as such, it should only be used on files that are not being modified by another thread of control. periodt. 🫶

the db_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, db_verify should always be given the chance to detach from the environment and exit gracefully. so to cause db_verify to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). yeah, SIGINT is the polite exit here, not the rude one. 😭

---

💜 EXIT STATUS 💜

the db_verify utility exits 0 on success, and >0 if an error occurs. simple. clean. iconic. ✨

---

🌈 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. 💖

---

🔥 SEE ALSO 🔥

• db_archive(1)
• db_checkpoint(1)
• db_deadlock(1)
• db_dump(1)
• db_hotbackup(1)
• db_log_verify(1)
• db_load(1)
• db_printlog(1)
• db_recover(1)
• db_replicate(1)
• db_stat(1)
• db_tuner(1)
• db_upgrade(1)

the whole friend group, honestly. go say hi. 🦋

---

and that's the page, bestie! this one's from BerkeleyDB 5.3.28, dated 06 December 2016. go verify something responsibly, don't use -N unless you're debugging, and remember to let it detach gracefully. mwah. 💅🎀✨