I'm trying to understand how/if "indoubt transaction record" ("XA prepare log record" in KC ref. link), could ALWAYS survive db2 restart or forced HADR takeover.
This would be a trivial question, if the XAPrepare record is always flushed to disk first, before the XAPrepare call is considered completed (similar to normal COMMIT), which should probably be true considering DB2 supports XA (otherwise "XAResource # recover()" might not be able to return a complete list of Xid).... But i haven't been able to find much reference on this topic, and hope our experts could share some insight :)
Assuming XAPrepare log record always flushed to disk first, it implies (NEAR)SYNC HADR 2PC needs two round trip between primary and standby.... hmmmmm
Btw, we use LUW V10.5FP8, in a single node env.
Thanks for your input!
Rui Chen[Organization Members] @ Jul 02, 2018 - 11:38 AM (America/Eastern)
Rui Chen[Organization Members] @ Jul 02, 2018 - 03:30 PM (America/Eastern)