My Oracle Support Banner

TimesTen: TT6003 Lock Timeout Encountered When Blocking Session Is Read-Only Query (Doc ID 1549241.1)

Last updated on AUGUST 03, 2018

Applies to:

TimesTen Data Server - Version and later
Information in this document applies to any platform.


A customer reported receiving a TT6003 error indicating that a DML transaction had timed out waiting on 1 or more locks necessary to complete a transaction. However, the error messages returned from TimesTen indicate that the session blocking the transaction was executing a read-only query:

These messages show  transaction 48.440382926  unable to get a lock on a specific table because transaction 147.119302663 is holding an S (shared table) lock on that table. A shared table lock should not be able to block a DML transaction since shared table locks result from read-only queries and a read-only query  should not be able to block an update being executed concurrently against the same objects by a different session. 


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.