 |
|
Oracle Tips by Burleson |
Oracle Streams
Chapter 7 -
Monitoring and Troubleshooting Oracle Streams
Capture to Dequeue Latency for an Event
SELECT APPLY_NAME,
(APPLY_TIME-APPLIED_MESSAGE_CREATE_TIME) * 86400 "Latency in
Seconds", APPLIED_MESSAGE_NUMBER
FROM DBA_APPLY_PROGRESS
/
Even though the above specified views are both
dependable, the following differences between these two queries
exist:
The Apply process should be enabled when the
query is run on the v$streams_apply_coordinator view. The
Apply process can be either enabled or disabled when the query is
run on the dba_apply_progress view.
The query on the v$streams_apply_coordinator
view may show the latency for a more recent transaction than the
query on the dba_apply_progress view.
Display Error Transaction Details
Even though a query of the dba_apply_error
view provides the list of Apply errors, the event itself needs to be
queried in order to fully understand the details of the event and
error details. Without the full details, it may not possible to
pinpoint the problem.
This section contains the PL/SQL code for three
procedures that help inquire about the event details. These
procedures are not mutually exclusive. They compliment each other
in the search for event details.
The above text is
an excerpt from:
Oracle Streams
High Speed Replication and Data
Sharing
ISBN 0-9745993-5-2
by Madhu Tumma
|
Download your Oracle scripts now:
www.oracle-script.com
The
definitive Oracle Script collection for every Oracle professional DBA
|
|
