GoldenGate, Streams and Distributed Database (MOSC)

MOSC Banner

Incorrect Lag Info

in GoldenGate, Streams and Distributed Database (MOSC) Question

Hi,

I have a GoldenGate for MySQL (18.1) and GG for Big Data (19.1) running on the same EC2 server.

One extract running in GG for MySQL creates extract trail files and one replicat running in GG BDA reads the extract trail files and writes to AWS S3.

Heartbeat was set up and both GG_HEARTBEAT and GG_HEARTBEAT_HISOTRY info seem to generate correctly. One issue with the "LAG xxxx" command is that the result seems to be calculated using different time zones with 7 hours of difference (see below). Though the actual lag is 3 seconds the LAG command shows 7h3s. I think one (source/target) uses the time zone of PST and one uses UTC. Is there a way to correct that?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center