From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/am_upgrade.html | 81 ++++++++++++++++--------------- 1 file changed, 43 insertions(+), 38 deletions(-) (limited to 'docs/programmer_reference/am_upgrade.html') diff --git a/docs/programmer_reference/am_upgrade.html b/docs/programmer_reference/am_upgrade.html index 7366891f..9e08741f 100644 --- a/docs/programmer_reference/am_upgrade.html +++ b/docs/programmer_reference/am_upgrade.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +
Prev Chapter 3.  - Access Method Operations - Chapter 3.  Access Method Operations  Next
@@ -38,41 +36,47 @@
+

+ When upgrading to a new release of Berkeley DB, it may be + necessary to upgrade the on-disk format of already-created + database files. 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. To guard against + failure, the procedures outlined in the Upgrading Berkeley DB installations chapter of + the Berkeley DB Installation and Build Guide 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 offsite! +

- - When upgrading to a new release of Berkeley DB, it may be necessary to - upgrade the on-disk format of already-created database files. - 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. To guard - against failure, the procedures outlined in the Upgrading Berkeley DB installations chapter of the - Berkeley DB Installation and Build Guide 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 offsite! -

+ The actual database upgrade is done using the DB->upgrade() + method, or by dumping the database using the old version of + the Berkeley DB software and reloading it using the current + version. +

- The actual database upgrade is done using the DB->upgrade() method, or by - dumping the database using the old version of the Berkeley DB software - and reloading it using the current version.

-

After an - upgrade, Berkeley DB applications must be recompiled to use the new - Berkeley DB library before they can access an upgraded database. - 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. We do guarantee that any archived database may - be upgraded using a current Berkeley DB software release and the - DB->upgrade() 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. -

+ After an upgrade, Berkeley DB applications must be + recompiled to use the new Berkeley DB library before they can + access an upgraded database. 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. We do guarantee that any archived + database may be upgraded using a current Berkeley DB software + release and the DB->upgrade() 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. +

@@ -89,7 +93,8 @@ Home -  Database verification and salvage +  Database verification and + salvage
-- cgit v1.2.1