[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3467?page=c...
]
Maruthi S commented on HHH-3467:
--------------------------------
We use 10.1.0.2 version JDBC driver. I am wondering why Hibernate was not able to
understand on what SQL error occurs and its throwing a Generic constraint violation
exception. We tried with 10.2.0.3, the same issue is occuring.
Constraint Violation Exception while inserting clob data in multiple
iteration
------------------------------------------------------------------------------
Key: HHH-3467
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3467
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.4
Environment: Hibernate 3.2.4 ga , Oracle 10g
Reporter: Maruthi S
Original Estimate: 6 weeks
Remaining Estimate: 6 weeks
Following Exception occurs while inserting clob data into a table with high number of
iterations. The primary key violation mentioned in the exception is a sequence where it
can be never duplicated. As a temporary work around, when Constraint violation exception
occurs, I used JDBC connection to insert the data. Kindly treat this bug as a very
critical bug.
org.hibernate.event.def.AbstractFlushingEventListener - Could not synchronize database
state with session
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch
update
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:253)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:237)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141)
at
org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
at
org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
at
com.citi.cmb.gce.admin.db.daoimpl.InterfaceDaoImpl.insertInterfaceDetails(InterfaceDaoImpl.java:333)
at
com.citi.cmb.gce.admin.pojo.InterfaceService.insertInterfaceDetails(InterfaceService.java:118)
at com.citi.cmb.gce.admin.ejbs.InterfaceMDBBean.onMessage(InterfaceMDBBean.java:62)
at
com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1014)
at com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpointHandler.java:747)
at $Proxy8.onMessage(Unknown Source)
at
com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEndpoint(JmsJcaEndpointInvokerImpl.java:201)
at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDispatcher.java:768)
at
com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run(SibRaSingleProcessListener.java:584)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:419)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint
(ADMIN.INTERFACE_PK) violated
at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:367)
at
oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:8739)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteBatch(WSJdbcPreparedStatement.java:808)
at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeBatch(WSJdbcStatement.java:612)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira