Why is Assertion failed: lrhdrp->blkSerialNum == logc->xactReplKeyCnt[lrhdrp->xact.xcb seen on a replicated TimesTen datastore?

(Doc ID 1643655.1)

Last updated on NOVEMBER 08, 2017

Applies to:

Oracle TimesTen In-Memory Database - Version 11.2.2.2.0 to 11.2.2.6.3 [Release 11.2]
Information in this document applies to any platform.

Goal

 To explain what causes Assertion Failure like below that were encountered by replication or during database recovery:

2014-03-07 22:38:55.64 Err : : 23322: 12450/0x7fec4c0008c0: XXX:type=141 hdr.idmap=[932303739:2:306093693+216]:425683.-1 xcb=42.32137272:2, logc-xcbCounter=32137272beginseen=1 cntExp=2 seenCnt=1
2014-03-07 22:38:55.67 Err : : 23322: 12450/0x7fec4c0008c0: Assertion failed: lrhdrp->blkSerialNum == logc->xactReplKeyCnt[lrhdrp->xact.xcb] [logmgr.c:/st_timesten_11.2.2.6/1:sbLogCursorAdvanceReplXLA:5359] PID 12450 (timestenrepd) CONN 161 (TRANSMITTER(M):140683694917376) 2014-03-07 22:38:55.656
2014-03-07 22:38:55.71 Err : : 23322: 12450/0x7fec4c0008c0: Data store marked invalid [logmgr.c:/st_timesten_11.2.2.6/1:sbLogCursorAdvanceReplXLA:5359] PID 12450 (timestenrepd) CONN 161 (TRANSMITTER(M):140683694917376) Context 0x7fec4c0008c0

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms