How to Solve the Capture 'PAUSED FOR FLOW CONTROL' in Case of Long-Running Transactions
(Doc ID 1504856.1)
Last updated on DECEMBER 10, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.1 to 11.2]
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 Cloud Exadata Service - Version N/A and later
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.
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