1<?xml version="1.0" encoding="UTF-8" standalone="no"?> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3<html xmlns="http://www.w3.org/1999/xhtml"> 4 <head> 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 6 <title>Release 4.0: application-specific recovery</title> 7 <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> 8 <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> 9 <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" /> 10 <link rel="up" href="upgrade_4_0_toc.html" title="Chapter 37. Upgrading Berkeley DB 3.3 applications to Berkeley DB 4.0" /> 11 <link rel="prev" href="upgrade_4_0_cxx.html" title="Release 4.0: C++ ostream objects" /> 12 <link rel="next" href="upgrade_4_0_disk.html" title="Release 4.0: Upgrade Requirements" /> 13 </head> 14 <body> 15 <div class="navheader"> 16 <table width="100%" summary="Navigation header"> 17 <tr> 18 <th colspan="3" align="center">Release 4.0: application-specific recovery</th> 19 </tr> 20 <tr> 21 <td width="20%" align="left"><a accesskey="p" href="upgrade_4_0_cxx.html">Prev</a> </td> 22 <th width="60%" align="center">Chapter 37. Upgrading Berkeley DB 3.3 applications to Berkeley DB 4.0</th> 23 <td width="20%" align="right"> <a accesskey="n" href="upgrade_4_0_disk.html">Next</a></td> 24 </tr> 25 </table> 26 <hr /> 27 </div> 28 <div class="sect1" lang="en" xml:lang="en"> 29 <div class="titlepage"> 30 <div> 31 <div> 32 <h2 class="title" style="clear: both"><a id="upgrade_4_0_asr"></a>Release 4.0: application-specific recovery</h2> 33 </div> 34 </div> 35 </div> 36 <p>If you have created your own logging and recovery routines, you may need 37to upgrade them to the Berkeley DB 4.0 release.</p> 38 <p>First, you should regenerate your logging, print, read and the other 39automatically generated routines, using the dist/gen_rec.awk tool 40included in the Berkeley DB distribution.</p> 41 <p>Next, compare the template file code generated by the gen_rec.awk tool 42against the code generated by the last release in which you built a 43template file. Any changes in the templates should be incorporated into 44the recovery routines you have written.</p> 45 <p>Third, if your recovery functions refer to <a href="../api_reference/C/envset_app_dispatch.html#set_app_dispatch_DB_TXN_FORWARD_ROLL" class="olink">DB_TXN_FORWARD_ROLL</a> 46(that is, your code checks for that particular operation code), you 47should replace it with DB_REDO(op) which compares the operation code to 48both <a href="../api_reference/C/envset_app_dispatch.html#set_app_dispatch_DB_TXN_FORWARD_ROLL" class="olink">DB_TXN_FORWARD_ROLL</a> and <a href="../api_reference/C/envset_app_dispatch.html#set_app_dispatch_DB_TXN_APPLY" class="olink">DB_TXN_APPLY</a>. 49(<a href="../api_reference/C/envset_app_dispatch.html#set_app_dispatch_DB_TXN_APPLY" class="olink">DB_TXN_APPLY</a> is a potential value for the operation code as of 50the 4.0 release.)</p> 51 <p>Finally, if you have created your own logging and recovery routines, we 52recommend you contact us and ask us to review those routines for you.</p> 53 </div> 54 <div class="navfooter"> 55 <hr /> 56 <table width="100%" summary="Navigation footer"> 57 <tr> 58 <td width="40%" align="left"><a accesskey="p" href="upgrade_4_0_cxx.html">Prev</a> </td> 59 <td width="20%" align="center"> 60 <a accesskey="u" href="upgrade_4_0_toc.html">Up</a> 61 </td> 62 <td width="40%" align="right"> <a accesskey="n" href="upgrade_4_0_disk.html">Next</a></td> 63 </tr> 64 <tr> 65 <td width="40%" align="left" valign="top">Release 4.0: C++ ostream objects </td> 66 <td width="20%" align="center"> 67 <a accesskey="h" href="index.html">Home</a> 68 </td> 69 <td width="40%" align="right" valign="top"> Release 4.0: Upgrade Requirements</td> 70 </tr> 71 </table> 72 </div> 73 </body> 74</html> 75