Last updated on SEPTEMBER 23, 2016
Applies to:TimesTen Data Server - Version 18.104.22.168.0 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.
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