Using the GoldenGate Hub with Timezone differences

Deploying a GoldenGate Hub with Timezone differences requires attention to detail.  I ran into this problem several months ago where the timezone of the Server Farm was US Central Time and the timezone of the database being extracted from was in Pacific time.  This issue is that whenever I would look at the Extract Lag the timezone difference would add two hours to the lag time:

GGSCI > info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING

EXTRACT     RUNNING     EXT01       02:00:02      00:00:05

EXTRACT     RUNNING     PMP01       00:00:00      00:00:08

This is not a real problem with the lag, rather than a timezone problem.  The solution to this problem is to add the following line to the extract parameter file:

SETENV (TZ=US/Pacific)

This simple changed provided for the proper feedback in the ggsci info all command.

GGSCI (ora1-ed.perftuning.com as ggadmin@gg01) 6> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

Previous: Performance of The GoldenGate Hub Architecture

When troubleshooting a GoldenGate Hub with timezone differences, be sure to follow these steps.

Remember to

MANAGER     RUNNING

EXTRACT     RUNNING     EXT01       00:00:03      00:00:05

EXTRACT     RUNNING     PMP01       00:00:00      00:00:08

Using the GoldenGate Server Farm is a great way to consolidate GoldenGate and offload overhead from the database servers.

By | 2018-05-18T16:39:34+00:00 April 17th, 2018|GoldenGate|Comments Off on Using the GoldenGate Hub with Timezone differences