GoldenGate, Streams and Distributed Database (MOSC)

MOSC Banner

EAGER_SIZE OGG Integrated Replicat

edited Aug 17, 2018 5:00AM in GoldenGate, Streams and Distributed Database (MOSC) 3 commentsAnswered

According to Oracle Doc.

EAGER_SIZE: Sets a threshold for the size of a transaction (in number of LCRs) after which Oracle GoldenGate starts applying data before the commit record is received. The default for Oracle GoldenGate is 9500 or 15100 depending on GG version.

This is a little confusing to me.  Why not just make eager_size to 1,  and if replicat sees a LCR, just apply it and never wait to see the commit record?

I read the following article and I summarized the result  and  it is confusing too.  It seems you have to make EAGER_SIZE > max(transaction_size) to take advantage. Can someone shed more light? Thanks.

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