Edit File - File Manager

Edit File: txn_prepare.html

<html>
<head>
<title>Berkeley DB: DB_TXN-&gt;prepare</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>
DB_TXN-&gt;prepare
</td>
<td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a>
<a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a></td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>
#include &lt;db.h&gt;

int
DB_TXN-&gt;prepare(DB_TXN *tid, u_int8_t gid[DB_XIDDATASIZE]);
</pre>
<hr size=1 noshade>
Description: DB_TXN-&gt;prepare
<a name="2"></a>
The DB_TXN-&gt;prepare method initiates the beginning of a two-phase commit.
In a distributed transaction environment, Berkeley DB can be used as a local
transaction manager. In this case, the distributed transaction manager
must send prepare messages to each local manager. The local
manager must then issue a DB_TXN-&gt;prepare and await its successful
return before responding to the distributed transaction manager. Only
after the distributed transaction manager receives successful responses
from all of its prepare messages should it issue any
commit messages.
In the case of nested transactions, preparing the parent causes all
unresolved children of the parent transaction to be committed. Child
transactions should never be explicitly prepared. Their fate will be
resolved along with their parent's during global recovery.
The DB_TXN-&gt;prepare method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 gid<ul compact><li>The gid parameter specifies the global transaction ID by which this
transaction will be known. This global transaction ID will be returned
in calls to <a href="../../db4-devel-4.7.25/api_c/txn_recover.html">DB_ENV-&gt;txn_recover</a>, telling the application which global
transactions must be resolved.</ul>
 
<hr size=1 noshade>
 Class
<a href="../../db4-devel-4.7.25/api_c/env_class.html">DB_ENV</a>, <a href="../../db4-devel-4.7.25/api_c/txn_class.html">DB_TXN</a>
 See Also
<a href="../../db4-devel-4.7.25/api_c/txn_list.html">Transaction Subsystem and Related Methods</a>
</tt>
<table width="100%"><tr><td> </td><td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a><a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager