Edit File - File Manager

Edit File: repinit.html

<html>
<head>
<title>Berkeley DB Reference Guide: Release 4.2: Replication</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.2/lockng.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.2/nosync.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Release 4.2: Replication
Replication initialization
In the Berkeley DB 4.2 release, replication environments must be specifically
initialized by any process that will ever do anything other than open
databases in read-only mode (that is, any process which might call any
of the Berkeley DB replication interfaces or modify databases). This
initialization is done when the replication database environment handle
is opened, by specifying the <a href="../../api_c/env_open.html#DB_INIT_REP">DB_INIT_REP</a> flag to the
<a href="../../api_c/env_open.html">DB_ENV-&gt;open</a> method.
Database methods and replication clients
All of the <a href="../../api_c/db_class.html">DB</a> object methods may now return
<a href="../../api_c/db_put.html#DB_REP_HANDLE_DEAD">DB_REP_HANDLE_DEAD</a> when a replication client changes masters.
When this happens the <a href="../../api_c/db_class.html">DB</a> handle is no longer able to be used and
the application must close the handle using the <a href="../../api_c/db_close.html">DB-&gt;close</a> method and
open a new handle. This new return value is returned when a client
unrolls a transaction in order to synchronize with the new master.
Otherwise, if the application was permitted to use the original handle,
it's possible the handle might attempt to access nonexistent resources.
<a href="../../api_c/rep_message.html">DB_ENV-&gt;rep_process_message</a>
The <a href="../../api_c/rep_message.html">DB_ENV-&gt;rep_process_message</a> method has new return values and an log sequence
number (LSN) associated with those return values. The new argument is
ret_lsnp, which is the returned LSN when the
<a href="../../api_c/rep_message.html">DB_ENV-&gt;rep_process_message</a> method returns <a href="../../api_c/rep_message.html#DB_REP_ISPERM">DB_REP_ISPERM</a> or
<a href="../../api_c/rep_message.html#DB_REP_NOTPERM">DB_REP_NOTPERM</a>. See <a href="../../ref/rep/trans.html">Transactional guarantees</a> for more information.
<table width="100%"><tr><td> </td><td align=right><a href="../upgrade.4.2/lockng.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.2/nosync.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager