My Oracle Support Banner

How to Ignore a Long-Running Transactions in Oracle Streams (Doc ID 1906221.1)

Last updated on OCTOBER 30, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.


Long-running transactions are open transactions with no activity (that is, no new Logical Change Records (LCRs), rollbacks, or commits) for an extended period (20 minutes).
A large transaction is an open transaction with a large number of LCRs.
In general, long-running transactions can cause a number of undesirable effects, including causing a source capture process to go into flow control, queue spilling at the source and the target,
apply spilling at the target, and unnecessary Streams pool memory consumption.
Ignoring a Long-Running Transaction should only be done as a last resort after consulting with Oracle Support since it will result in data that is not synchronized between source and target,
unless the transaction has been rolled back at the source. Streams can be stuck or processing slowly for many different reasons and trained analysis is needed to determine if the problem is
due to a particular long-running transaction or not.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Database Versions to 10.1.0.x
 Database Versions 10.2 and Above
 Database Versions and Above
 How to ignore transactions that have apply spilled messages

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.