Gecko [ 122.154.134.11 ]

Name	Size	Permission
berkeley_db_svc.html	3.22 KB	-rw-r--r--
db_archive.html	5.46 KB	-rw-r--r--
db_checkpoint.html	4.47 KB	-rw-r--r--
db_codegen.html	9.31 KB	-rw-r--r--
db_deadlock.html	4.48 KB	-rw-r--r--
db_dump.html	7.08 KB	-rw-r--r--
db_hotbackup.html	7.69 KB	-rw-r--r--
db_load.html	10.15 KB	-rw-r--r--
db_printlog.html	3.51 KB	-rw-r--r--
db_recover.html	5.17 KB	-rw-r--r--
db_stat.html	5.93 KB	-rw-r--r--
db_upgrade.html	4.74 KB	-rw-r--r--
db_verify.html	3.72 KB	-rw-r--r--
index.html	2.31 KB	-rw-r--r--

Code Editor : db_upgrade.html

<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>
db_upgrade
</td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>db_upgrade [-NsVv] [-h home] [-P password] file ...</pre>
Description
<a name="2"></a><a name="3"></a>
The db_upgrade utility upgrades the Berkeley DB version of one or more
files and the databases they contain to the current release version.
The options are as follows:
 
-h<ul compact><li>Specify a home directory for the database environment; by
default, the current working directory is used.</ul>
-N<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>
-P<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>
-s<ul compact><li>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 specify 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 corruption.
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 -s flag
is correctly specified. Otherwise, the file cannot be upgraded using
db_upgrade, and must be upgraded manually using the
<a href="../../db4-utils-4.7.25/utility/db_dump.html">db_dump</a> and <a href="../../db4-utils-4.7.25/utility/db_load.html">db_load</a> utilities.</ul>
-V<ul compact><li>Write the library version number to the standard output, and exit.</ul>
-v<ul compact><li>Run in verbose mode, displaying a message for each successful upgrade.</ul>
 
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 procedure
runs out of disk space, the databases may be left in an inconsistent and
unrecoverable state. See <a href="../../db4-devel-4.7.25/ref/am/upgrade.html">Upgrading
databases</a> for more information.
The db_upgrade 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_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).
The db_upgrade utility exits 0 on success, and &gt;0 if an error occurs.
 Environment Variables
 
DB_HOME<ul compact><li>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 <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a>.</ul>
 
</tt>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

${this.title}

Code Editor : db_upgrade.html