<!--$Id: db_upgrade.so,v 1.10 2006/10/05 01:06:08 bostic Exp $--> <!--Copyright (c) 1997,2008 Oracle. All rights reserved.--> <!--See the file LICENSE for redistribution information.--> <html> <head> <title>Berkeley DB: db_upgrade</title> <meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> <meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> </head> <body bgcolor=white> <table width="100%"><tr valign=top> <td> <b>db_upgrade</b> </td> </tr></table> <hr size=1 noshade> <tt> <b><pre>db_upgrade [<b>-NsVv</b>] [<b>-h home</b>] [<b>-P password</b>] file ...</pre></b> <b>Description</b> <a name="2"><!--meow--></a><a name="3"><!--meow--></a> <p>The db_upgrade utility upgrades the Berkeley DB version of one or more files and the databases they contain to the current release version.</p> <p>The options are as follows:</p> <br> <b>-h</b><ul compact><li>Specify a home directory for the database environment; by default, the current working directory is used.</ul> <b>-N</b><ul compact><li>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.</ul> <b>-P</b><ul compact><li>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.</ul> <b>-s</b><ul compact><li>This flag is only meaningful when upgrading databases from releases before the Berkeley DB 3.1 release. <p>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 specify whether duplicate data items in the database are sorted or not. Specifying the <b>-s</b> 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 corruption.</p> <p>Because the db_upgrade utility upgrades a physical file (including all the databases it contains), it is not possible to use db_upgrade to upgrade files where some of the databases it includes have sorted duplicate data items, and some of the databases 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), db_upgrade will work correctly as long as the <b>-s</b> flag is correctly specified. Otherwise, the file cannot be upgraded using db_upgrade, and must be upgraded manually using the <a href="../utility/db_dump.html">db_dump</a> and <a href="../utility/db_load.html">db_load</a> utilities.</p></ul> <b>-V</b><ul compact><li>Write the library version number to the standard output, and exit.</ul> <b>-v</b><ul compact><li>Run in verbose mode, displaying a message for each successful upgrade.</ul> <br> <p><b>It is important to realize that Berkeley DB database upgrades are done in place, and so are potentially destructive.</b> This means that if the system crashes during the upgrade procedure, or if the upgrade procedure runs out of disk space, the databases may be left in an inconsistent and unrecoverable state. See <a href="../ref/am/upgrade.html">Upgrading databases</a> for more information.</p> <p>The db_upgrade utility may be used with a Berkeley DB environment (as described for the <b>-h</b> option, the environment variable <b>DB_HOME</b>, 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_upgrade should always be given the chance to detach from the environment and exit gracefully. To cause db_upgrade to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT).</p> <p>The db_upgrade utility exits 0 on success, and >0 if an error occurs.</p> <br><b>Environment Variables</b> <br> <b>DB_HOME</b><ul compact><li>If the <b>-h</b> 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 <a href="../api_c/env_open.html">DB_ENV->open</a>.</ul> <br> </tt> <p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> </body> </html>