1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
<!--$Id: incomplete.so,v 1.9 2004/08/15 03:22:57 bostic Exp $-->
<!--Copyright 1997-2004 by Sleepycat Software, Inc.-->
<!--All rights reserved.-->
<!--See the file LICENSE for redistribution information.-->
<html>
<head>
<title>Berkeley DB Reference Guide: Release 3.2: DB_INCOMPLETE</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><h3><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></h3></td>
<td align=right><a href="../upgrade.3.2/renumber.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.3.2/tx_recover.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p>
<h3 align=center>Release 3.2: DB_INCOMPLETE</h3>
<p>There are a number of functions that flush pages from the Berkeley DB shared
memory buffer pool to disk. Most of those functions can potentially
fail because a page that needs to be flushed is not currently available.
However, this is not a hard failure and is rarely cause for concern.
In the Berkeley DB 3.2 release, the C++ API (if that API is configured to
throw exceptions) and the Java API have been changed so that this
failure does not throw an exception, but rather returns a non-zero error
code of DB_INCOMPLETE.</p>
<p>The following C++ methods will return DB_INCOMPLETE rather than throw
an exception: <a href="../../api_cxx/db_close.html">Db::close</a>, <a href="../../api_cxx/db_sync.html">Db::sync</a>, DbEnv::memp_sync,
DbEnv::txn_checkpoint, DbMpoolFile::memp_fsync.</p>
<p>The following Java methods are now declared "public int" rather than
"public void", and will return Db.DB_INCOMPLETE rather than throw an
exception: Db.close, Db.sync, and DbEnv.checkpoint.</p>
<p>It is likely that the only change required by any application will be
those currently checking for a DB_INCOMPLETE return that has
been encapsulated in an exception.</p>
<table width="100%"><tr><td><br></td><td align=right><a href="../upgrade.3.2/renumber.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.3.2/tx_recover.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p><font size=1><a href="../../sleepycat/legal.html">Copyright (c) 1996-2004</a> <a href="http://www.sleepycat.com">Sleepycat Software, Inc.</a> - All rights reserved.</font>
</body>
</html>
|
