MAN page from CentOS 8 libdb-utils-5.3.28-36.el8.x86_64.rpm

DB_UPGRADE

Section: BerkeleyDB Utilities (1)
Updated: 06 December 2016
Index

NAME

db_upgrade - Upgrade files and databases to the current release version.

SYNOPSIS

db_upgrade[-NsVv] [-h home] [-P password] file ...

DESCRIPTION

The db_upgrade utility upgrades the Berkeley DB version of one or more filesand the databases they contain to the current release version.

OPTIONS

-h home

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

-N

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 beused under any other circumstances.

-P password

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

-s

This flag is only meaningful when upgrading databases from releasesbefore 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 upgradethe format requires that applications specify whether duplicate dataitems in the database are sorted or not. Specifying the -sflag means that the duplicates are sorted; otherwise, they are assumedto be unsorted. Incorrectly specifying the value of this flag may leadto database corruption.

Because the db_upgrade utility upgrades a physical file(including all the databases it contains), it is not possible to usedb_upgrade to upgrade files where some of the databases itincludes have sorted duplicate data items, and some of the databases itincludes have unsorted duplicate data items. If the file does not havemore than a single database, if the databases do not support duplicatedata items, or if all the databases that support duplicate data itemssupport the same style of duplicates (either sorted or unsorted),db_upgrade will work correctly as long as the -s flagis correctly specified. Otherwise, the file cannot be upgraded usingdb_upgrade, and must be upgraded manually using thedb_dump and db_load 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 donein place, and so are potentially destructive. This means that if thesystem crashes during the upgrade procedure, or if the upgrade procedureruns out of disk space, the databases may be left in an inconsistent andunrecoverable state.

The db_upgrade utility may be used with a Berkeley DB environment (as described for the-h option, the environment variable DB_HOME, orbecause the utility was run in a directory containing a Berkeley DBenvironment). In order to avoid environment corruption when using aBerkeley DB environment, db_upgrade should always be given the chance todetach from the environment and exit gracefully. To cause db_upgradeto release all environment resources and exit cleanly, send it aninterrupt signal (SIGINT).

EXIT STATUS

The db_upgrade utility exits 0 on success, and >0 if an error occurs.

ENVIRONMENT

DB_HOME: If the -h option is not specified and the environment variableDB_HOME is set, it is used as the path of the database home, as describedin DB_ENV->open.

This document was created byman2html,using the manual pages.