If you get an exception similar to one of the following:
org.springframework.dao.DataIntegrityViolationException: (HibernateTemplate): data integrity violated by SQL ''; nested exception is java.sql.BatchUpdateException: Duplicate entry '1234' for key 1 at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.translate(SQLStateSQLExceptionTranslator.java:88) caused by: java.sql.BatchUpdateException: Duplicate entry '1234' for key 1 at com.mysql.jdbc.ServerPreparedStatement.executeBatch(ServerPreparedStatement.java:647) |
または
(HibernateTemplate): data integrity violated by SQL ''; nested exception is java.sql.BatchUpdateException: ORA-00001: unique constraint (CONFLUENCE.SYS_C0012345) violated |
This document will outline the steps to take to increasing logging on your system. This additional logging will help us work out the cause of this error.
To enable this additional logging:
confluence/WEB-INF/classes/log4j.properties and uncomment the following lines. The double ## lines are comments, leave them intact.
## log hibernate prepared statements/SQL queries (equivalent to setting 'hibernate.show_sql' to 'true') #log4j.logger.net.sf.hibernate.SQL=DEBUG, confluencelog #log4j.additivity.net.sf.hibernate.SQL=false ## log hibernate prepared statement parameter values #log4j.logger.net.sf.hibernate.type=DEBUG, confluencelog #log4j.additivity.net.sf.hibernate.type=false |
If you can not locate these lines in your |
CONFLUENCE.SYS_C0012345) refers to and add that information to your support ticket.confluence/WEB-INF/classes/log4j.properties again and remove the 4 lines you added in step 1 (the additional logging will impact performance and should be disabled once you have completed this procedure.Enable Hibernate Logging