Gecko [ 122.154.134.11 ]

Name	Size	Permission
asr.html	2.71 KB	-rw-r--r--
cxx.html	2.39 KB	-rw-r--r--
deadlock.html	1.63 KB	-rw-r--r--
disk.html	1.67 KB	-rw-r--r--
env.html	6.22 KB	-rw-r--r--
intro.html	1.63 KB	-rw-r--r--
java.html	2.21 KB	-rw-r--r--
lock.html	3.2 KB	-rw-r--r--
lock_id_free.html	1.77 KB	-rw-r--r--
log.html	4.19 KB	-rw-r--r--
mp.html	5.27 KB	-rw-r--r--
rpc.html	1.79 KB	-rw-r--r--
set_lk_max.html	1.88 KB	-rw-r--r--
toc.html	1.97 KB	-rw-r--r--
txn.html	3.26 KB	-rw-r--r--

Code Editor : asr.html

<html>
<head>
<title>Berkeley DB Reference Guide: Release 4.0: application-specific recovery</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><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></td>
<td align=right><a href="../upgrade.4.0/cxx.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.4.0/disk.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Release 4.0: application-specific recovery
If you have created your own logging and recovery routines, you may need
to upgrade them to the Berkeley DB 4.0 release.
First, you should regenerate your logging, print, read and the other
automatically generated routines, using the dist/gen_rec.awk tool
included in the Berkeley DB distribution.
Next, compare the template file code generated by the gen_rec.awk tool
against the code generated by the last release in which you built a
template file. Any changes in the templates should be incorporated into
the recovery routines you have written.
Third, if your recovery functions refer to <a href="../../api_c/env_set_app_dispatch.html#DB_TXN_FORWARD_ROLL">DB_TXN_FORWARD_ROLL</a>
(that is, your code checks for that particular operation code), you
should replace it with DB_REDO(op) which compares the operation code to
both <a href="../../api_c/env_set_app_dispatch.html#DB_TXN_FORWARD_ROLL">DB_TXN_FORWARD_ROLL</a> and <a href="../../api_c/env_set_app_dispatch.html#DB_TXN_APPLY">DB_TXN_APPLY</a>.
(<a href="../../api_c/env_set_app_dispatch.html#DB_TXN_APPLY">DB_TXN_APPLY</a> is a potential value for the operation code as of
the 4.0 release.)
Finally, if you have created your own logging and recovery routines, we
recommend you contact us and ask us to review those routines for you.
<table width="100%"><tr><td> </td><td align=right><a href="../upgrade.4.0/cxx.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.4.0/disk.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

${this.title}

Code Editor : asr.html