Orphaned Entries in V$STREAMS_TRANSACTION.
(Doc ID 1340222.1)
Last updated on MARCH 19, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle 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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- Orphaned entries reported in v$streams_transaction.
- V$streams_transaction will show all open transactions being captured, which means transactions where capture has not yet found a 'commit' or 'rollback' at the redo / archived logs, not actually active transactions as seen on v$session / v$process. Therefore even a database bounce will not clean some of these transactions.
- Besides the open transactions as defined above, we might also see orphaned entries on these objects, which means that the transaction was actually applied fine, but there were not cleaned up properly.
- So there will not be corresponding entry of txn from v$streams_transaction in v$transaction.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |