My Oracle Support Banner

GG_Lag_History Does Not Populate DIST PATH Info If Trail File Is Encrypted At The EXTRACT End And The Lag Values (DATA_PUMP_READ_LAG, REPLICAT_READ_LAG) (Doc ID 2979115.1)

Last updated on JANUARY 08, 2024

Applies to:

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

Symptoms

gg_lag_history does not populate DIST PATH info if trail file is encrypted at the EXTRACT end.

We have setup a GG replication using OGG 21c Microservice Architecture using OGG HUB. We were monitoring the lag using gg_heartbeat_history and it provided the lag at every step and also the names of the EXTRACT, DIST PATH and REPLICAT. We enabled encryption of the trail files (using ENCKEYS method) by adding the parameter "ENCRYPTTRAIL AES256, KEYNAME <>" to the extract paramater file and "DECRYPTTRAIL AES256, KEYNAME <>" to the replicat parameter file. After restarting the EXTRACT and REPLICAT, the replication is working fine but the gg_lag_history does not populate the name for the distribution path and the lag values (DATA_PUMP_READ_LAG, REPLICAT_READ_LAG).

> lag <REP_NAME>
No Extract groups exist.
LAG                 AGE                 FROM                TO                  PATH
4.08s               47.60s              DEMO              TESTXXX:PXXXXX   <EXT_NAME> ==> <REP_NAME> -- AFTER ENCRYPTION
2.84s               7727.59s            DEMO              TESTXXX:PXXXXX   <EXT_NAME> ==> XXXXXXXXXX:9021:XXXX ==> <REP_NAME> -- BEFORE ENCRYPTION
 
Missing Dist Path info:
 
SOURCE_HB_TS              EXTRACT   EXTRACT_LAG DATA_PUMP                    DATA_PUMP_READ_LAG REPLICAT  REPLICAT_READ_LAG REPLICAT_APPLY_LAGTOTAL_LAG
------------------------- --------- ----------- ---------------------------- ------------------ --------- ----------------- ------------------ ----------
23-AUG-23 07:30:30.011447 <EXT_NAME>     2.789139                                                 <REP_NAME>                                  .788163 4.704671
23-AUG-23 07:31:30.011593 <EXT_NAME>     1.744797                                                 <REP_NAME>                                  .529102 3.533219

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.