GoldenGate, Streams and Distributed Database (MOSC)

MOSC Banner

commit_timestamp$ and CSCN$ not in order in CDC on 11.2.0.4 RAC database

edited Jul 20, 2016 5:01AM in GoldenGate, Streams and Distributed Database (MOSC) 1 commentAnswered

Hi all,

We have interesting problem with asynchronous CDC in our workplace in Australia.

It seems that for some reason data in CDC tables is not logically consistent when it comes to TIMESTAMP$ and COMMIT_TIMESTAMP values compared to CSCN$ (transaction SCN number). We have 1 insert transaction and 4 transactions which updates the same records for 4 times and transaction 4 is committed AFTER transaction 5 even-though it started BEFORE transaction 5 for about 7 seconds. Please note bellow. All the updates transactions are happening on ONE unique record with C=11554 and I=16253013.

Column LASTEUPDATETIME is column on the table update by our application and first 5 columns bellow are system columns on CDC tables generated by Oracle package DBMS_CDC_PUBLISH.CREATE_CHANGE_TABLE

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