Why is a Delete taking a W table lock and causing TT6003 errors from other transactions?
Last updated on MARCH 02, 2016
Applies to:Oracle TimesTen In-Memory Database - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
A DELETE DML statement was seen to be taking a W table lock and thus causing lock contention with other transactions.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms