Assertion failed: (!(((sbHBHdr_p) bufp)->flags & (((sbHBFlag_t) 0x1)|((sbHBFlag_t) 0x2)))) [heap.c:/st_timesten_11.2.2.8/4:sbLCBHpCoalesce:9731] (Doc ID 2112365.1)

Last updated on SEPTEMBER 22, 2016

Applies to:

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

Symptoms

TimesTen database invalidated with the following assertion:

Reason: Assertion failed: (!(((sbHBHdr_p) bufp)->flags & (((sbHBFlag_t) 0x1)|((sbHBFlag_t) 0x2)))) [heap.c:/st_timesten_11.2.2.8/4:sbLCBHpCoalesce:9731] PID 6049 (timestensubd) CONN 1071 (Manager) 2016-01-12 17:36:51.188

the stack trace of the relevant thread from .inval file was this:

#0 0x000000318546878d in _IO_proc_close@@GLIBC_2.2.5 () from /lib64/libc.so.6
#1 0x0000003185472a43 in _IO_new_file_close_it () from /lib64/libc.so.6
#2 0x00000031854667f8 in fclose@@GLIBC_2.2.5 () from /lib64/libc.so.6
#3 0x00007fee6d47aa45 in sbUtStackTrace () from /opt/TimesTen/SPC/lib/libtten.so
#4 0x00007fee6d46cb5a in sbDbInvalidSet () from /opt/TimesTen/SPC/lib/libtten.so
#5 0x00007fee6d46ccd4 in sbBailOutFn () from /opt/TimesTen/SPC/lib/libtten.so
#6 0x00007fee6d47cc2a in sbUtAssertion () from /opt/TimesTen/SPC/lib/libtten.so
#7 0x00007fee6da630d5 in sbLCBHpCoalesce () from /opt/TimesTen/SPC/lib/libtten.so
#8 0x00007fee6d4678ed in sbDbRedo () from /opt/TimesTen/SPC/lib/libtten.so
#9 0x00007fee6d4663e9 in sbDbRecover () from /opt/TimesTen/SPC/lib/libtten.so
#10 0x00007fee6cd9291d in sbDbConnect () from /opt/TimesTen/SPC/lib/libtten.so
#11 0x00007fee6cd8f53d in sb_dbConnect () from /opt/TimesTen/SPC/lib/libtten.so
#12 0x000000000040d144 in do_manage ()
#13 0x0000000000407c94 in daHandler ()
#14 0x00000000004155e4 in handlerThread ()
#15 0x00000031858079d1 in start_thread () from /lib64/libpthread.so.0
#16 0x00000031854e8b6d in clone () from /lib64/libc.so.6

 

Other users may see this invalidation:

Data store marked invalid [heap.c:/main/83:sbLCBHpCoalesce:10428] PID 25284 (timestensubd) CONN 2047 (Manager) Context 0xb946f0

Stack trace was same functions and files as above.

Reloading the database kept running into the same assertion and invalidating, so the database will not recover itself from this condition.

Cause

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