GG_LAG View In In-Built Heartbeat Functionality Does Not Show Complete Incoming/outgoing Path With Multiple Data Pumps

(Doc ID 2312899.1)

Last updated on OCTOBER 02, 2017

Applies to:

Oracle GoldenGate - Version 12.2.0.1.0 and later
Information in this document applies to any platform.

Symptoms

When two data pumps are used in the following flow:

extract -> pump1 -> pump2 -> replicat

The GG_LAG view implemented by using the heatbeat feature does not show a full path. For example, when the following extract/pumps/replicat running on the same host as:

IEUSER1 (integrated extract to extract user1 schema) -> ptest1 (pump 1) -> ptest2 (pump 2) -> rtest (integrated replicat to apply to user2 schema), we got the following result from gg_lag:

SQL> exec print_table('select * from ggs.gg_lag');
LOCAL_DATABASE : OGGP
CURRENT_LOCAL_TS : 10-MAR-16 01.28.58.506810 AM
REMOTE_DATABASE : OGGP
INCOMING_HEARTBEAT_AGE : 50.493204
INCOMING_PATH : IEUSER1 ==> PTEST1, ==> RTEST
INCOMING_LAG : 7.834574
OUTGOING_HEARTBEAT_AGE :
OUTGOING_PATH :
OUTGOING_LAG :
-----------------
LOCAL_DATABASE : OGGP
CURRENT_LOCAL_TS : 10-MAR-16 01.28.58.506810 AM
REMOTE_DATABASE : OGGP
INCOMING_HEARTBEAT_AGE : 110.491634
INCOMING_PATH : IEUSER1 ==> PTEST1, ==> RTEST
INCOMING_LAG : 5.766506
OUTGOING_HEARTBEAT_AGE : 170.4978
OUTGOING_PATH : IEUSER1 ==> PTEST1, ==> RTEST
OUTGOING_LAG : 5.705843


We should get only one record, with IEUSER1 ==> PTEST1, PTEST2 ==> RTEST as the incoming/outgoing path. But instead, we got 2 records, and the paths are incomplete.

in GG_HEARTBEAT table, which supplies data to the GG_LAG view, there is only one record. So two issues:

1) 2 records from the view when only one record in the underlying table
2) incomplete paths

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms