My Oracle Support Banner

OptimisticLockException Updating Telephone Number in Bulk (Doc ID 2389107.1)

Last updated on JUNE 02, 2022

Applies to:

Oracle Communications Unified Inventory Management - Version 7.2.3 and later
Information in this document applies to any platform.


User first query the available telephone numbers and start updating all one by one.
1) Query 10K or 20K Telehone numbers with category(Char) as Normal.
2) Block all the telephone number using condition.

Observing below error :

2018-03-11 01:25:40,850 ERROR [] [[ACTIVE] ExecuteThread: '33' for queue: 'weblogic.kernel.Default (self-tuning)'] [TransactionManager] An error has occured flushing the user transaction.
javax.persistence.OptimisticLockException: Exception [EclipseLink-5011] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.OptimisticLockException
Exception Description: One or more objects cannot be updated because it has changed or been deleted since it was last read
  at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitToDatabase(
  at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithPreBuiltChangeSet(
  at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.writeChanges(
  at org.eclipse.persistence.internal.jpa.EntityManagerImpl.flush(
  at sun.reflect.GeneratedMethodAccessor1222.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(
  at java.lang.reflect.Method.invoke(
  at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.