How to Solve the Capture 'PAUSED FOR FLOW CONTROL' in Case of Long-Running Transactions
Last updated on FEBRUARY 08, 2017
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.1 to 11.2]
Information in this document applies to any platform.
In certain cases where customer needs to accelerate the process of messages to avoid waiting for the transaction to complete.
As large transactions are causing spilling performance problem seems to come because a "Full Table Scan" on SYS.STREAMS$_APPLY_SPILL_MSGS_PART.
Therefore, you can help the customer to create a temporary index on SYS.STREAMS$_APPLY_SPILL_MSGS_PART, then dropped it after transaction applied.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms