TT6003: Lock request denied because of time-out

Trying to create cache group lead to the below error :-

java.sql.SQLException: [TimesTen][TimesTen ODBC Driver][TimesTen]TT6003: Lock request denied because of time-out
Details: Tran 143.23106 (pid 19946) wants Sn lock on rowid BMUFVUAAAAxogAALDp, table SUBSCRIBER. But tran 144.67398 (pid 19946) has it in Xn (request was Xn). Holder SQL (select ID,identifierType,identifiervalue,subscriberId,groupName,siid from subscriptionidentifie…) — file “tindex.c”, lineno 4277, procedure “sbTixNext()”

After check the Timesten parameter found the issue was with LockWait

Lockwait :- Allows an application to configure the lock wait interval for the connection.

LockWait may be set to any value between 0 and 1,000,000 inclusive to a precision of
tenths of a second. The default is 10 seconds.

Actual lock wait response time is imprecise and may be exceeded by up to one tenth of
a second, due to the scheduling of the agent that detects timeouts. This imprecision
does not apply to zero second timeouts, which are always reported immediately.


Osama …

Attempt to connect to a data store that has been manually unloaded from R AM

Timesten in-memory Database :-

ttisql DSN_NAME

ttIsql (c) 1996-2005, TimesTen, Inc. All rights reserved.
Type ? or “help” for help, type “exit” to quit ttIsql.
All commands must end with a semicolon character.
connect “DSN=DSN_NAME”;
707: Attempt to connect to a data store that has been manually unloaded from R

The command failed.

This should be easy to resolve. A TimesTen datastore (physical database), which is what a DSN points at, has a property called its ‘ramPolicy’ The default value for this is inUse which means that TimesTen will load the datastore into memory whenever it is being used.

Solution :

ttAdmin -ramload DSN_NAME

Reference :-
1- Oracle OTN Forum here


Osama ….