Edit File - File Manager

Edit File: env_set_app_dispatch.html

<html>
<head>
<title>Berkeley DB: DB_ENV-&gt;set_app_dispatch</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_ENV-&gt;set_app_dispatch
</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_ENV-&gt;set_app_dispatch(DB_ENV *dbenv,
 int (*tx_recover)(DB_ENV *dbenv,
 DBT *log_rec, DB_LSN *lsn, db_recops op));
</pre>
<hr size=1 noshade>
Description: DB_ENV-&gt;set_app_dispatch
Declare a function to be called during transaction abort and recovery
to process application-specific log records.
The DB_ENV-&gt;set_app_dispatch method configures operations performed using the specified
<a href="../../db4-devel-4.7.25/api_c/env_class.html">DB_ENV</a> handle, not all operations performed on the underlying
database environment.
The DB_ENV-&gt;set_app_dispatch method may not be called after the <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a> method is
called.
If the database environment already exists when
<a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a> is called, the information specified to DB_ENV-&gt;set_app_dispatch
must be consistent with the existing environment or corruption can
occur.
The DB_ENV-&gt;set_app_dispatch method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 tx_recover<ul compact><li>The tx_recover parameter is the application's abort and recovery
function. The function takes four parameters:
 
dbenv<ul compact><li>The dbenv parameter is the enclosing database environment handle.</ul>
log_rec<ul compact><li>The log_rec parameter is a log record.</ul>
lsn<ul compact><li>The lsn parameter is a log sequence number.</ul>
op<ul compact><li>The op parameter is one of the following values:</ul>
 
<a name="DB_TXN_BACKWARD_ROLL">DB_TXN_BACKWARD_ROLL</a><ul compact><li>The log is being read backward to determine which transactions have been
committed and to abort those operations that were not; undo the operation
described by the log record.</ul>
<a name="DB_TXN_FORWARD_ROLL">DB_TXN_FORWARD_ROLL</a><ul compact><li>The log is being played forward; redo the operation described by the log
record.</ul>
<a name="DB_TXN_ABORT">DB_TXN_ABORT</a><ul compact><li>The log is being read backward during a transaction abort; undo the
operation described by the log record.</ul>
<a name="DB_TXN_APPLY">DB_TXN_APPLY</a><ul compact><li>The log is being applied on a replica site; redo the operation
described by the log record.</ul>
<a name="DB_TXN_PRINT">DB_TXN_PRINT</a><ul compact><li>The log is being printed for debugging purposes; print the contents of
this log record in the desired format.</ul>
 
The DB_TXN_FORWARD_ROLL and DB_TXN_APPLY operations
frequently imply the same actions, redoing changes that appear in the
log record, although if a recovery function is to be used on a
replication client where reads may be taking place concurrently with the
processing of incoming messages, DB_TXN_APPLY operations should
also perform appropriate locking. The macro DB_REDO(op) checks that the
operation is one of DB_TXN_FORWARD_ROLL or DB_TXN_APPLY,
and should be used in the recovery code to refer to the conditions under
which operations should be redone. Similarly, the macro DB_UNDO(op)
checks if the operation is one of DB_TXN_BACKWARD_ROLL or
DB_TXN_ABORT.
 
The function must return 0 on success and either errno or a
value outside of the Berkeley DB error name space on failure.</ul>
 
 Errors
The DB_ENV-&gt;set_app_dispatch method
may fail and return one of the following non-zero errors:
 
EINVAL<ul compact><li>If the method was called after <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a> was called; or if an
invalid flag value or parameter was specified.</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