dba_apply_progress
SELECT APPLY_NAME,
(APPLY_TIME - APPLIED_MESSAGE_CREATE_TIME)*86400
"Latency in Seconds",
TO_CHAR(APPLIED_MESSAGE_CREATE_TIME,'HH24:MI:SS
MM/DD/YY')
"Event Creation",
TO_CHAR(APPLY_TIME,'HH24:MI:SS MM/DD/YY')
"Apply Time",
APPLIED_MESSAGE_NUMBER
FROM DBA_APPLY_PROGRESS
/
dba_apply_table_columns
This view displays information about the
destination table object columns for all tables in the database.
Some useful columns include:
-
The COMPARE_OLD_ON_DELETE column indicates
whether to compare the old value of the column on deletes for
YES or not for NO.
-
The COMPARE_OLD_ON_UPDATE column indicates
whether to compare the old value of the column on updates for
YES or not for NO.
This view is populated when conflict
resolution methods are configured. A query of this view helps to
understand the conflict resolution defined.
Apply-related useful queries
Capture to Dequeue Latency for an Event
To find out the latency for the last
dequeued event, some of the fields in the dynamic
v$streams_apply_reader view can be used. For the captured
events, the latency is the amount of time between when the event
was created at a source database and when the event was dequeued
by the Apply process. In the case of user-enqueued events, the
latency represents the amount of time between when the event
enqueued at the local database and when the event was dequeued
by the Apply process. The goal should be to reduce the latency.
Reduced latency indicates that transactional activity is
progressing well at the destination database.
