GoldenGate, Streams and Distributed Database (MOSC)

MOSC Banner

Goldengate Replicat Lag - how to identify if there is trail file or other contention

in GoldenGate, Streams and Distributed Database (MOSC) 1 commentAnswered

Goldengate 19.1

Site-site, like for like replication between two identical Oracle 19.12 databases.

Source:

One Integrated Extract capturing changes for schemas A, B, C, D

One Pump process propagating those trails to the target site

Target:

Two separate Replicats

R1 - Non-integrated. Applies changes for schemas A, B , C

R2 - Integrated. Applies changes for schema D

Nothing fancy in the param files, just straight mappings A.* to A.* , etc

R1 shows no issues. R2 is experiencing constant issues with significant lag.

By observation we see this...

When R2 is experiencing lag it appears to be "stuck" at a particular RBA in the file and rba doesn't advance until 2 or 3 checkpoints have happened. When we investigate we find that the record it is "stuck" on is for a change to one of the A, B or C schemas. Shouldn't it just skip those?

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