Last updated on FEBRUARY 27, 2016
Applies to:Oracle TimesTen In-Memory Database - Version 18.104.22.168.6 and later
Information in this document applies to any platform.
***Checked for relevance on 11-NOV-2013***
***Checked for relevance on 04-Nov-2015***
Ram policy changed to "inUse" and Rep policy changed to "manual" after db invalidation due to assertion.
Here are some sample entries from the support log (ttmesg.log) demonstrating the same issue:
As part of the assertion, the db was invalidated. When that happened, the old db image remained in memory until all the connections (stale connections) are disconnected.
A new connection to the db will try to load a new instance of the db into memory based on the checkpoint and transaction log files on disk. When it tried to do that, it ran into the following error:
15:03:33.42 Err : : 18723: -- OS reports not enough memory available
15:03:33.43 Err : : 18725: Err 836: TT0836: Cannot create data store shared-memory segment, error 12 -- file "db.c", lineno 9698, procedure "sbDbConnect"
The above errors indicates that there was not enough memory to load the datastore. It was due to the fact that old db image was still around while it tried to load the new db image. This system didn't have enough memory on the system to have two copies of the db in memory at the same time. Therefore, got the not enough memory available error.
The following entries indicate the policy changes:
15:03:33.44 Warn: : 18723: Setting RAM policy to inUse for data store /opt/bpc/is/TimesTen/bpckansparc5724/datastore/bpckansparc5724 due to failure to start manager
15:03:33.44 Warn: : 18723: Setting replication policy to manual for data store /opt/bpc/is/TimesTen/bpckansparc5724/datastore/bpckansparc5724 due to failure to start manager
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms