Server Shadowing and Recovery
B.8 Application Considerations
•
Any physical reference to the transaction which is unique to the executing
server, e.g. Channel Id, system time, DB-key, etc., should not be passed back
to the client for future references within its subsequent messages, as this
could lead to inconsistent handling when a different server is involved in
shadow operations.
This consideration is also valid for recovery of non-shadowed servers.
B.9 Server States
The current state of a server can be examined as follows:
RTR> show server/full
Servers:
Process-id:
Channel:
State:
High Bound:
User Events:
Partition-Id:
Process-id:
Channel:
State:
High Bound:
User Events:
Partition-Id:
Figure B–2 gives an overview of the server state changes which appear in the
"State:" field
B–6 Server Shadowing and Recovery
13340
Facility:
131073
Flags:
active
Low Bound:
87 13
rcpnam:
0
RTR Events:
16777216
13340
Facility:
196610
Flags:
active
Low Bound:
0f'
rcpnam:
0
RTR Events:
16777217
RTR$DEFAULT_FACILITY
SRV
"RTR$DEFAULT_CHANNEL"
0
RTR$DEFAULT_FACILITY
SRV
88 13
"CHAN2"
0