Transaction State Changes; Valid Transaction State Transitions - Compaq AA-Q88CE-TE System Manager's Manual

Rtr
Table of Contents

Advertisement

4.1.2 Transaction State Changes

There are eight valid state changes allowed for the
Attempting to change transaction state to a state that is not allowed produces
an error message of
state to the specified state
changes.
Table 4–19 Valid Transaction State Transitions
Current State
SENDING
VOTED
COMMIT
EXCEPTION
PRI_DONE
Four typical situations are listed below where transaction state changes by the
system administrator are allowed.
1. State
The application server, after receiving a
calling
situation and cannot proceed. Aborting this transaction with the
TRANSACTION
will send the ABORT message to the router as well as the all participating
servers to abort this transaction in a consistent matter.
2. State
This is the case where a application server running on the backend may
have been separated from the rest of participating servers after casting the
VOTE for the transaction. The other servers may have already committed
the transaction but not ''forgotten'' it. As far as the application is concerned,
this global transaction is committed and all changes have been committed to
the underlying database on the different sites. However, the local transaction
record is still in VOTED state in the RTR journal. You can use the command
to manually commit the local transaction branch.
Note that this command is only applicable if there is no coordinating router
running, i.e., servers are separated from the rest of the RTR network. If this
is not the case, RTR rejects the command.
3. State
In a similar manner to the VOTED-to-COMMIT situation described above,
the server has been separated from the other participating servers and all
other participants aborted this transaction; use this command to manually
abort the local transaction branch.
Note that this command is only applicable if there is no coordinating router
running and servers are separated from the rest of the RTR network. If this
is not the case, RTR rejects the command.
4. State
%RTR-E-INVSTATCHANGE, Invalid to change from current
. The Table 6–19 table identifies the valid state
COMMIT
YES
YES
changed to state
SENDING
for a particular transaction, experiences a ''hung''
rtr_accept_tx( )
command is the only way to correct it. Internally, RTRACP
changed to state
VOTED
changed to state
VOTED
changed to state
COMMIT
Transaction Management
SET TRANSACTION
NEW STATE
ABORT
EXCEPTION
YES
YES
YES
.
ABORT
rtr_mt_msg_1
.
COMMIT
.
ABORT
.
DONE
Transaction Management 4–3
4.1 Overview
command.
DONE
YES
YES
YES
message and before
SET

Advertisement

Table of Contents
loading

This manual is also suitable for:

Reliable transaction router, version 3.2

Table of Contents

Save Article as PDF