Golden Gate Replication Issue DASPRD Is Not Updated From SAAS Layer for Over 3 Hours
(Doc ID 2943118.1)
Last updated on APRIL 21, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Goal
GG replication issue, DASPRD is not updated from SAAS layer
Seeing there is no replication happened from SAAS to DAS layer, the client checked with DBA and found that lag apply is fine from their end. However, it’s been over 3 hours since the last message was created on oracle side.
+-----------------------+---------------------------------------------------------------------------------------------------+
| Replicat Name | OGG$REPPRD |
| Apply Lag | 00:00:31 |
| Last Message Dequeued | 04/03/2023 01:31:29 - 03:19:28 since last dequeue. |
| Last Message Created | 04/03/2023 01:27:58 - 03:22:59 since last message was created @ Oracle. |
| | - 00:03:31 between when the last message was created and being dequeued. |
| Current System Time | 04/03/2023 04:50:57 |
+-----------------------+---------------------------------------------------------------------------------------------------+
| If there is an Apply Lag of greater than 30 minutes, please escalate to DBA. |
| If there is a significant difference between Last Message Dequeued and Last Message Created, please escalate to DBA. |
| If the Last Message Created date is more than 2 hours old, contact Oracle to determine if there is a delay on their side. |
+---------------------------------------------------------------------------------------------------------------------------+
Please check and fix the issue as all our reporting jobs affected as they pick data from DASPRD tables.
Solution
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
Goal |
Solution |
References |