Uncommitted DML And Database Lock On Recursive Validation Error

(Doc ID 1613723.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle JDeveloper - Version to [Release Oracle11g]
Information in this document applies to any platform.


An ADF application using ADF BC and doing changes to other entities in the prepareForDml or doDML methods hold on to a database lock in case entity-level validation fails. Upon failing only the failing entity object is being rolled back and not the update of the other entity object thus causing a session with a pending change to hold a lock on the record on the database.

Suppose you have following code on your DepartmentImpl class:


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