mirror of
https://github.com/MariaDB/server.git
synced 2025-11-09 11:41:36 +03:00
51 lines
3.3 KiB
HTML
51 lines
3.3 KiB
HTML
<!--$Id: upgrade.so,v 10.14 2000/12/21 18:37:08 bostic Exp $-->
|
|
<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.-->
|
|
<!--All rights reserved.-->
|
|
<html>
|
|
<head>
|
|
<title>Berkeley DB Reference Guide: Upgrading databases</title>
|
|
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
|
|
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
|
|
</head>
|
|
<body bgcolor=white>
|
|
<a name="2"><!--meow--></a>
|
|
<table><tr valign=top>
|
|
<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Access Method Operations</dl></h3></td>
|
|
<td width="1%"><a href="../../ref/am/opensub.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/am/get.html"><img src="../../images/next.gif" alt="Next"></a>
|
|
</td></tr></table>
|
|
<p>
|
|
<h1 align=center>Upgrading databases</h1>
|
|
<p>When upgrading to a new release of Berkeley DB, it may be necessary to upgrade
|
|
the on-disk format of already-created database files. <b>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. To
|
|
guard against failure, the procedures outlined in
|
|
<a href="../../ref/upgrade/process.html">Upgrading Berkeley DB installations</a>
|
|
should be carefully followed. If you are not performing catastrophic
|
|
archival as part of your application upgrade process, you should at
|
|
least copy your database to archival media, verify that your archival
|
|
media is error-free and readable, and that copies of your backups are
|
|
stored off-site!
|
|
<p>The actual database upgrade is done using the <a href="../../api_c/db_upgrade.html">DB->upgrade</a>
|
|
method, or by dumping the database using the old version of the Berkeley DB
|
|
software and reloading it using the current version.
|
|
<p>After an upgrade, Berkeley DB applications must be recompiled to use the new
|
|
Berkeley DB library before they can access an upgraded database.
|
|
<b>There is no guarantee that applications compiled against
|
|
previous releases of Berkeley DB will work correctly with an upgraded database
|
|
format. Nor is there any guarantee that applications compiled against
|
|
newer releases of Berkeley DB will work correctly with the previous database
|
|
format.</b> We do guarantee that any archived database may be upgraded
|
|
using a current Berkeley DB software release and the <a href="../../api_c/db_upgrade.html">DB->upgrade</a>
|
|
method, and there is no need to step-wise upgrade the database using
|
|
intermediate releases of Berkeley DB. Sites should consider archiving
|
|
appropriate copies of their application or application sources if they
|
|
may need to access archived databases without first upgrading them.
|
|
<table><tr><td><br></td><td width="1%"><a href="../../ref/am/opensub.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/am/get.html"><img src="../../images/next.gif" alt="Next"></a>
|
|
</td></tr></table>
|
|
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>
|
|
</body>
|
|
</html>
|