20 Monitoring Replication Lag
RDS uses Oracle GoldenGate to replicate application data from Retail applications to its ADW instance. The data is kept in sync with the source application as changes are made to the source. You can monitor the lag between source (application) and target (RDS) systems using the following GoldenGate heartbeat tables and views:
-
GGADMIN.GG_HEARTBEAT_SEED
-
GGADMIN.GG_HEARTBEAT
-
GGADMIN.GG_HEARTBEAT_HISTORY
-
GGADMIN.GG_LAG
-
GGADMIN.GG_LAG_HISTORY
Refer to Oracle GoldenGate Integrated Heartbeat for details on how to use these tables and views to assess replication lag. Note that GoldenGate heartbeat has already been enabled in RDS.
| Incoming Path | Product | Schema | Workspace |
|---|---|---|---|
|
BC_* ==> BCREP |
Brand Compliance Cloud Service |
BC_RDS_CUSTOM |
Yes |
|
CE_* ==> CEREP |
Customer Engagement Cloud Service |
CE_RDS_CUSTOM |
Yes |
|
I1_* ==> I1REP |
Retail Integration Cloud Service |
RICS_BDI |
No |
|
I2_* ==> I2REP |
Retail Integration Cloud Service |
RICS_RFI |
No |
|
I3_* ==> I3REP |
Retail Integration Cloud Service |
RICS_RIB_EXT1 |
No |
|
I4_* ==> I4REP |
Retail Integration Cloud Service |
RICS_RIB_LGF1 |
No |
|
I5_* ==> I5REP |
Retail Integration Cloud Service |
RICS_RIB_ROB1 |
No |
|
I6_* ==> I6REP |
Retail Integration Cloud Service |
RICS_RIB_RWMS1 |
No |
|
I7_* ==> I7REP |
Retail Integration Cloud Service |
RICS_RIB_SIM1 |
No |
|
I8_* ==> I8REP |
Retail Integration Cloud Service |
RICS_RIB_TAFR1 |
No |
|
I9_* ==> I9REP |
Retail Integration Cloud Service |
RICS_USM1 |
No |
|
IN_* ==> INREP |
Retail Integration Cloud Service |
XO_RDS_CUSTOM |
Yes |
|
MF_* ==> MFREP |
Merchandising Foundation Cloud Service |
MFCS_RDS_CUSTOM |
Yes |
|
OB_* ==> OBREP |
Order Broker Cloud Service |
OB_RDS_CUSTOM |
Yes |
|
OM_* ==> OMREP |
Order Administration Cloud Service |
OM_RDS_CUSTOM |
Yes |
|
SI_* ==> SIREP |
Store Inventory Operations Cloud Service |
SIOCS_RDS_CUSTOM |
Yes |
|
XO_* ==> XOREP |
Xstore Office Cloud Service |
XO_RDS_CUSTOM |
Yes |