"TimesTen Error: 10011; Data store is currently not being managed"
445523Aug 6 2007 — edited Sep 23 2009We have been intermittently (but frequently) encountering an issue when we attempt to manually unload a datastore and then destroy it.
I'm posting this looking for suggestions on how to resolve/avoid this issue.
First the following is executed:
ttAdmin -ramPolicy manual -ramUnload -wait MYDSN
The following error occurs:
ttAdmin: TimesTen Error: 10011; Data store is currently not being managed
All future attempts to execute the above command sometime result in the same error and sometimes they execute without error.
Next, if we try to destroy the datastore with the following command:
ttDestroy -force -wait /opt/home/myid/datastore/MYDSN
The follow error occurs:
Failed to destroy data store: TT0839: Cannot access data store because it is in use. A data store may be considered to be in use due to its RAM Policy setting, even though there are no active connections to it. -- file "db.c", lineno 20890, procedure "sbDbDestroy"
Retrying...
Retrying...
Retrying...
Retrying...
Retrying...
Retrying...
Retrying...
ttstatus displays the following information:
------------------------------------------------------------------------
Data store /opt/home/myid/datastore/MYDSN
There are 6 connections to the data store
Data store is in shared mode
Shared Memory KEY 0x0c01791c ID 198705158
Type PID Context Connection Name ConnID
Subdaemon 25158 0x00000000005506e0 Worker 2042
Subdaemon 25158 0x00000000005dcd70 Flusher 2043
Subdaemon 25158 0x000000000062e4a0 Checkpoint 2044
Subdaemon 25158 0x000000000065f7c0 Aging 2045
Subdaemon 25158 0x0000000000690ae0 HistGC 2046
Subdaemon 25158 0x00000000006c1e00 Monitor 2047
RAM residence policy: Manual
Data store is manually loaded into RAM
Replication policy : Manual
Cache agent policy : Manual
------------------------------------------------------------------------
We are running TimesTen 7.0.2 for 64 bits on Linux Red Hat ES 4.0.