]I: Incorrect number of compensations. iFileNextOffset is 296

[OritA]

Sometimes you may see in the Replicate log an informational message like the folllowing:  

SORTER_STORAGE  ]I:  Incorrect number of compensations. iFileNextOffset is 296, iReadPosition is 296, cNextRecordPart is 0.  (transaction_storage.c:4013)

When does this message displayed in the log?  

This informational messages (indicated by the capital i following the closing square bracket) is generated when a CDC task is working on a table and the source system has issued a rollback on the table or unit of work.
The rollback then begins to work backwards in the db log correcting the data.

Product: Replicate

[Datateam]

I don't understand, if the archiver logs only have committed operations, a rollback on a table shouldn't affect the CDC since unconfirmed operations are not part of the redos and archiver logs.

I'm not understanding something right

[Dana_Baldwin]

Hi @Datateam 

Transactions are written to the redo logs when they start, not when they are committed. Replicate reads these pending transactions. Whether or not they are applied to the target depends upon if they are committed or rolled back. For long running transactions, the commit or rollback may occur in a later redo/archived log.

Hope this helps!

Dana