Why is there a 15 Minute Delay For AWT Transactions to reach Oracle after a network break?
Last updated on MARCH 02, 2016
Applies to:TimesTen Data Server - Version 11.2.1 and later
Information in this document applies to any platform.
***Checked for relevance on 18-NOV-2013***
A customer found that after removing the network cable that allowed communication between Active and Standby replication agents, there was also a 15 minute delay for AWT transactions to be fully applied to the Oracle database. Since the AWT transactions were being propagated through the Active to Oracle, the question was why interrupting communications on the Standby should affect this at all.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms