Delete Query Fails With 'OptimisticLockException' if JDBC Batching Is Enabled
Last updated on AUGUST 02, 2016
Applies to:Oracle TopLink - Version 184.108.40.206 to 220.127.116.11 [Release 12c]
Information in this document applies to any platform.
***Checked for relevance 09-FEB-2015***
You are experiencing an 'OptimisticLockException' when JDBC batching is enabled against an Oracle 18.104.22.168 database using TopLink 22.214.171.124/ Eclipselink 2.3.2, as shown in the example error trace below:
and redeploying to 126.96.36.199 FMw WebLogic Server.
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