head 1.4; access; symbols RPM_4_1:1.1.1.2 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.4 date 2003.08.24.12.43.13; author rse; state dead; branches; next 1.3; 1.3 date 2003.08.24.12.33.49; author rse; state Exp; branches; next 1.2; 1.2 date 2003.08.24.12.25.46; author rse; state dead; branches; next 1.1; 1.1 date 2001.07.23.20.45.37; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.37; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.10; author rse; state Exp; branches; next ; desc @@ 1.4 log @Resolve: RPM 4.1 -> RPM 4.1.1 @ text @
DbEnv.set_tx_recover |
![]() ![]() |
import com.sleepycat.db.*;public interface DbTxnRecover { public abstract int tx_recover(DbEnv dbenv, Dbt log_rec, DbLsn lsn, int op); } public class DbEnv { public void set_tx_recover(DbTxnRecover tx_recover) throws DbException; ... }
Set the application's method to be called during transaction abort and recovery. This method must return 0 on success and either errno or a value outside of the Berkeley DB error name space on failure. It takes four arguments:
The Db.DB_TXN_FORWARD_ROLL and Db.DB_TXN_APPLY operations frequently imply the same actions, redoing changes that appear in the log record. The macro DB_REDO(op) checks that the operation is one of Db.DB_TXN_FORWARD_ROLL or Db.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.DB_TXN_BACKWARD_ROLL or Db.DB_TXN_ABORT.
The DbEnv.set_tx_recover interface may be used only to configure Berkeley DB before the DbEnv.open interface is called.
The DbEnv.set_tx_recover method throws an exception that encapsulates a non-zero error value on failure.
The DbEnv.set_tx_recover method may fail and throw an exception encapsulating a non-zero error for the following conditions:
Called after DbEnv.open was called.
The DbEnv.set_tx_recover method may fail and throw an exception for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the DbEnv.set_tx_recover method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.
![]() ![]() |
Copyright Sleepycat Software
@
1.3
log
@Resolve: RPM 4.0.5 -> RPM 4.1
@
text
@@
1.2
log
@Resolve: RPM 4.0.4 -> RPM 4.0.5
@
text
@d1 1
a1 1
d17 1
a17 1
d26 2
a27 2
public abstract int
tx_recover(DbEnv dbenv, Dbt log_rec, DbLsn lsn, int op);
d31 3
a33 3
public void set_tx_recover(DbTxnRecover tx_recover)
throws DbException;
...
d54 2
d58 7
d92 1
d97 1
a97 1
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
d17 1
a17 1
d26 2
a27 2
public abstract int
tx_recover(DbEnv dbenv, Dbt log_rec, DbLsn lsn, int op);
d31 3
a33 3
public void set_tx_recover(DbTxnRecover tx_recover)
throws DbException;
...
a53 2
The Db.DB_TXN_FORWARD_ROLL and Db.DB_TXN_APPLY operations
frequently imply the same actions, redoing changes that appear in the
log record. The macro DB_REDO(op) checks that the operation is one of
Db.DB_TXN_FORWARD_ROLL or Db.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.DB_TXN_BACKWARD_ROLL or Db.DB_TXN_ABORT.
a82 1
DbTxn.set_timeout
d87 1
a87 1
@