GoldenGate, Streams and Distributed Database (MOSC)

MOSC Banner

OGG Extract Abended due to Journal Sequence Number is out of order, without JSN being reset.

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

Our Linux machine has a Journal Sequence Number problem in Oracle Golden Gate. We have now seen this problem for two of our extract groups, during two separate occasions. The data is coming in from the same DB2 but two different servers. Suddenly, we see that the extract is abandoned and cannot be restarted again. We checked the logs and saw the following error:

2023-11-25T16:12:05.654+0100 INFO  OGG-01513 Oracle GoldenGate Capture for DB2 for i, lf04_cd0.prm: Positioning to 

                   Journal        Receiver        Timestamp (UTC)     Sequence Number

                   JRN/JRN    |    JRN/JRNRCV1233|Nov 23 2023 23:06:05.365824|00000000022374278842.

2023-11-25T16:17:19.737+0100 ERROR  OGG-06613 Oracle GoldenGate Capture for DB2 for i, lf04_cd0.prm: Journal Sequence Number out of order in single journal Extract.

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