Why Do We Get Error "TT6002: Lock Request Denied Because Of Deadlock" When Our SQL Involves Unique Rows? (Doc ID 1507334.1)

Last updated on JUNE 15, 2016

Applies to:

Oracle TimesTen In-Memory Database - Version 11.2.2.4.0 to 11.2.2.4.5 [Release 11.2]
Oracle TimesTen In-Memory Database - Version 11.2.2.5.0 to 11.2.2.5.9 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on Jan 14, 2015***

Goal

 Question: Why do we get error "TT6002: Lock Request Denied Because Of Deadlock" when our SQL is mostly inserts and updates on unique rows? 

Solution

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