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 3.2: DB_INCOMPLETE</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_3_2_toc.html" title="Chapter��35.��Upgrading Berkeley DB 3.1 applications to Berkeley DB 3.2" /> 11 <link rel="prev" href="upgrade_3_2_renumber.html" title="Release 3.2: Logically renumbering records" /> 12 <link rel="next" href="upgrade_3_2_tx_recover.html" title="Release 3.2: DB_ENV->set_tx_recover" /> 13 </head> 14 <body> 15 <div class="navheader"> 16 <table width="100%" summary="Navigation header"> 17 <tr> 18 <th colspan="3" align="center">Release 3.2: DB_INCOMPLETE</th> 19 </tr> 20 <tr> 21 <td width="20%" align="left"><a accesskey="p" href="upgrade_3_2_renumber.html">Prev</a>��</td> 22 <th width="60%" align="center">Chapter��35.��Upgrading Berkeley DB 3.1 applications to Berkeley DB 3.2</th> 23 <td width="20%" align="right">��<a accesskey="n" href="upgrade_3_2_tx_recover.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_3_2_incomplete"></a>Release 3.2: DB_INCOMPLETE</h2> 33 </div> 34 </div> 35 </div> 36 <p> 37 There are a number of functions that flush pages from the Berkeley DB shared memory buffer pool 38 to disk. Most of those functions can potentially fail because a page that needs to be flushed 39 is not currently available. However, this is not a hard failure and is rarely cause for 40 concern. In the Berkeley DB 3.2 release, the C++ API (if that API is configured to throw 41 exceptions) and the Java API have been changed so that this failure does not throw an exception, 42 but rather returns a non-zero error code of <code class="literal">DB_INCOMPLETE</code>. 43</p> 44 <p> 45 The following C++ methods will return <code class="literal">DB_INCOMPLETE</code> rather than throw 46 an exception: 47 <a href="../api_reference/CXX/dbclose.html" class="olink">Db::close</a>, 48 <a href="../api_reference/CXX/dbsync.html" class="olink">Db::sync</a>, 49 <a href="../api_reference/CXX/mempsync.html" class="olink">DbEnv::memp_sync</a>, 50 <a href="../api_reference/CXX/txncheckpoint.html" class="olink">DbEnv::txn_checkpoint</a>, 51 and <a href="../api_reference/CXX/mempfsync.html" class="olink">DbMpoolFile::memp_fsync</a>. 52</p> 53 <p> 54 The following Java methods are now declared "public int" rather than "public void", and will 55 return <code class="literal">Db.DB_INCOMPLETE</code> rather than throw an exception: 56 <code class="methodname">Db.close()</code>, <code class="methodname">Db.sync()</code>, and 57 <code class="methodname">DbEnv.checkpoint()</code>. 58</p> 59 <p> 60 It is likely that the only change required by any application will be those currently checking 61 for a <code class="literal">DB_INCOMPLETE</code> return that has been encapsulated in an exception. 62</p> 63 </div> 64 <div class="navfooter"> 65 <hr /> 66 <table width="100%" summary="Navigation footer"> 67 <tr> 68 <td width="40%" align="left"><a accesskey="p" href="upgrade_3_2_renumber.html">Prev</a>��</td> 69 <td width="20%" align="center"> 70 <a accesskey="u" href="upgrade_3_2_toc.html">Up</a> 71 </td> 72 <td width="40%" align="right">��<a accesskey="n" href="upgrade_3_2_tx_recover.html">Next</a></td> 73 </tr> 74 <tr> 75 <td width="40%" align="left" valign="top">Release 3.2: Logically renumbering records��</td> 76 <td width="20%" align="center"> 77 <a accesskey="h" href="index.html">Home</a> 78 </td> 79 <td width="40%" align="right" valign="top">��Release 3.2: DB_ENV->set_tx_recover</td> 80 </tr> 81 </table> 82 </div> 83 </body> 84</html> 85