Use the TRANSACTIONTIMEOUT parameter to prevent an uncommitted Replicat target transaction from holding locks on the target database and consuming its resources unnecessarily. You can change the value of this parameter so that Replicat can work within existing application timeouts and other database requirements on the target.

TRANSACTIONTIMEOUT limits the amount of time that Replicat can hold a target transaction open if it has not received the end-of-transaction record for the last source transaction in that transaction. By default, Replicat groups multiple source transactions into one target transaction to improve performance, but it will not commit a partial source transaction and will wait indefinitely for that last record. The Replicat parameter GROUPTRANSOPS controls the minimum size of a grouped target transaction.

The following events could last long enough to trigger TRANSACTIONTIMEOUT:

• Network problems prevent trail data from being delivered to the target system.

• Running out of disk space on any system, preventing trail data from being written.

• Extract abends or is terminated in the middle of writing records for a transaction.

• There is a source system failure, such as a power outage or system crash.

See TRANSACTIONTIMEOUT in Parameters and Functions Reference for Oracle GoldenGate for more information.