Apply Queue spilling usually indicates that transactions are staying longer in memory.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Grid Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
|
Target Version |
Evaluation and Collection Frequency |
Upload Frequency |
Operator |
Default Warning Threshold |
Default Critical Threshold |
Consecutive Number of Occurrences Preceding Notification |
Alert Text |
|
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x |
Every 5 Minutes |
After Every Sample |
> |
60 |
80 |
1 |
Spilled messages for Apply process [%APPLY_NAME%] queue is %value% percent. |
For this metric you can set different warning and critical threshold values for each "Apply Name" object.
If warning or critical threshold values are currently set for any "Apply Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Apply Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Target database, gv$buffered_queues, gv$buffered_subscribers tables
Either increase Streams Pool size and/or increase Apply Parallelism to speed up Apply processing.
Related Topics
About Alerts
About the Metric Detail Page
Editing Thresholds
Understanding Line Charts
Copyright © 1996, 2009, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.