NAME
dbupgrade - Upgrade files and databases to the current release ver‐ sion. SYNOPSIS
dbupgrade [-NsVv] [-h home] [-P password] file ... DESCRIPTION The dbupgrade utility upgrades the Berkeley DB version of one or more files and the databases they contain to the current release version. OPTIONS
-h home Specify a home directory for the database environment; by default, the current working directory is used.
-N Do not acquire shared region mutexes while running. Other prob‐ lems, 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 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 argu‐ ments.
-s This flag is only meaningful when upgrading databases from releases before the Berkeley DB 3.1 release. As part of the upgrade from the Berkeley DB 3.0 release to the
3.1 release, the on-disk format of duplicate data items changed. To correctly upgrade the format requires that applications spec‐ ify whether duplicate data items in the database are sorted or
not. Specifying the -s flag means that the duplicates are sorted; otherwise, they are assumed to be unsorted. Incorrectly specifying the value of this flag may lead to database corrup‐ tion. Because the dbupgrade utility upgrades a physical file (includ‐ ing all the databases it contains), it is not possible to use dbupgrade to upgrade files where some of the databases it includes have sorted duplicate data items, and some of the data‐ bases it includes have unsorted duplicate data items. If the file does not have more than a single database, if the databases do not support duplicate data items, or if all the databases that support duplicate data items support the same style of duplicates (either sorted or unsorted), dbupgrade will work
correctly as long as the -s flag is correctly specified. Other‐ wise, the file cannot be upgraded using dbupgrade, and must be upgraded manually using the dbdump and dbload utilities.
-V Write the library version number to the standard output, and exit.
-v Run in verbose mode, displaying a message for each successful upgrade. It is important to realize that Berkeley DB database upgrades are done in place, and so are potentially destructive. This means that if the system crashes during the upgrade procedure, or if the upgrade proce‐ dure runs out of disk space, the databases may be left in an inconsis‐ tent and unrecoverable state. The dbupgrade utility may be used with a Berkeley DB environment (as
described for the -h option, the environment variable DBHOME, 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, dbupgrade should always be given the chance to detach from the environment and exit gracefully. To cause dbupgrade to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). EXIT STATUS The dbupgrade utility exits 0 on success, and >0 if an error occurs. ENVIRONMENT DBHOME
If the -h option is not specified and the environment variable DBHOME is set, it is used as the path of the database home, as
described in DBENV->open. SEE ALSO dbarchive(1) dbcheckpoint(1) dbdeadlock(1) dbdump(1) dbhot‐ backup(1) dblogverify(1) dbload(1) dbprintlog(1) dbrecover(1) dbreplicate(1) dbstat(1) dbtuner(1) dbverify(1) BerkeleyDB 5.3.21 06 December 2016 DBUPGRADE(1)