You may also want to look at the HADR Peer Window feature, which can
help ensure that transactions do not commit on the primary without
replication to the standby, for a configurable period of time. This
is useful where there is a high desire for consistency at failover,
and esp. where failover is automated. Note that this choice for
consistency does trade off against availability, as when the HADR pair
is disconnected, the primary (in SYNC or NEARSYNC modes) cannot commit
transactions during Peer state, nor in the new Disconnected Peer state
that comes with the Peer Window feature.
Some intro material here:
http://publib.boulder.ibm.com/infoce.../c0051997.html
Regards,
- Steve P.
--
Steve Pearson, DB2 for Linux, UNIX, and Windows, IBM Software Group
"Portland" Development Team, IBM Beaverton Lab, Beaverton, OR, USA