How To Recover From Stuck Streams Data Flow
(Doc ID 730742.1)
Last updated on APRIL 09, 2020
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 9.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
When Streams components(QUEUE,CAPTURE,APPLY,PROP) gets aborted/disabled and if you are not able to recover from the situation, this article can be used. The note just creates the new set of streams components and starts the replication(without exp/imp) from the place, where we stuck.
This cannot be used for all types of streams error. The cause of the error needs to be identified.
For example, if streams component is stuck due to long running transaction, this note will not be helpful. Because, when we create the new setup, still we will hit the same long running transaction. So, in this case, first the long running transaction should be skipped.
Hence, before we use this note, we should do the initial analysis of the problem and understand the problem.
For example, we hit the following error for one customer:
Errors in file <path>/<SID>_c002_18485.trc:
ORA-00600: internal error code, arguments: , , , , , , , 
ORA-00448: normal completion of background process
Stop/start capture did not resolve the issue.
Using the steps mentioned in below note, we were able to recover from the situation
The advantage of this note over general drop/recreate streams is, we skip the exp/imp.
Hence the setup is Quick.
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