http://download-uk.oracle.com/do ... 28322/troub_rep.htm
Is the Capture Process Paused for Flow Control?
If the capture process state is PAUSED FOR FLOW CONTROL, then the capture process is unable to enqueue logical change records (LCRs) either because of low memory or because propagations and apply processes are consuming messages at a slower rate than the capture process is creating them. This state indicates flow control that is used to reduce the spilling of captured LCRs when propagation or apply has fallen behind or is unavailable.
If a capture process is in this state, then check for the following issues:
An apply process is disabled or is performing slowly.
A propagation is disabled or is performing poorly.
There is not enough memory in the Streams pool.
You can query the V$STREAMS_APPLY_READER view to monitor the LCRs being received by the apply process. You can also query V$STREAMS_APPLY_SERVER view to determine whether all apply servers are applying LCRs and executing transactions.
Also, if the capture process does not use combined capture and apply, then you can query the PUBLISHER_STATE column in the V$BUFFERED_PUBLISHERS view to determine the exact reason why the capture process is paused for flow control.
To correct the problem, perform one or more of the following actions:
If any propagation or apply process is disabled, then enable the propagation or apply process.
If the apply reader is not receiving data fast enough, then try removing propagation and apply process rules or simplifying the rule conditions.
If there is not enough memory in the Streams pool at the capture process database, then try increasing the size of the Streams pool.
|
