My Oracle Support Banner

How to Solve the Capture 'PAUSED FOR FLOW CONTROL' in Case of Long-Running Transactions (Doc ID 1504856.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.4 [Release 11.1 to 11.2]
Information in this document applies to any platform.

Goal

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.

Solution

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
Goal
Solution
References

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