Alter table set pages can lead to invalidation if table is replicated

(Doc ID 2349988.1)

Last updated on APRIL 16, 2018

Applies to:

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


TimesTen replication is being used.

While replication is occurring, user alters the page count of hash table index on a replicated table.  Shortly after the hash index pages change, TimesTen database invalidated with one of these two following reason found in message log or inval file:

Assertion failed: (((sbBlkHdr_p)(fp))->sane == ((sbBlkSane_t)0xCAFE)) [blk.c:/st_timesten_11.2.2.8/4:sbBlkDirFreeListUnlink:3122]


Invalidating data store: <path to datastore> Reason: Assertion failed: (((ha)->nodet) == ((sbNodeTag_t) 14)) [hash.c:/st_timesten_11.2.2.8/2:sbHaLookup:1910] PID 12976 (timestenrepd)


The above invalidation, the line number of the files (3122 and 1910) are from system running, line number might differ slightly in older versions of TimesTen.




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