-
Suggestion
-
Resolution: Answered
-
None
-
None
-
10
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Different databases have different settings for case sensitivity. The case sensitivity of the database is usually set through the collation that it uses.
The default embedded database (HSQL) in Confluence is a CASE SENSITIVE database. When you attempt to migrate this data to an external database that is set up with a case insensitive collation, you may experience problems.
You may encounter this error for example:
The data import process reported the duplicate error on the wrong object:
Import failed. (HibernateTemplate): data integrity violated by SQL ''; nested exception is java.sql.BatchUpdateException: Duplicate entry 'OSUser_user-11-confluence.prefs.email.notify' for key 1
or
2007-02-21 15:02:03,676 ERROR [sf.hibernate.util.JDBCExceptionReporter] logExceptions Violation of PRIMARY KEY constraint 'PK_OS_PROPERTYENTRY_619B8048'. Cannot insert duplicate key in object 'OS_PROPERTYENTRY'.
2007-02-21 15:02:03,692 ERROR [confluence.importexport.impl.ReverseDatabinder] endElement net.sf.hibernate.exception.ConstraintViolationException: could not insert: [bucket.user.propertyset.BucketPropertySetItem#bucket.user.propertyset.BucketPropertySetItem@d88630dc]
net.sf.hibernate.exception.ConstraintViolationException: could not insert: [bucket.user.propertyset.BucketPropertySetItem#bucket.user.propertyset.BucketPropertySetItem@d88630dc]
at net.sf.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:62)
at net.sf.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
- relates to
-
CONFCLOUD-7917 Support migration from a case-sensitive database (including HSQL) to a case-insensitive database
- Closed
[CONFSERVER-7917] Support migration from a case-sensitive database (including HSQL) to a case-insensitive database
Workflow | Original: JAC Suggestion Workflow 4 [ 3578869 ] | New: JAC Suggestion Workflow 3 [ 4337478 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3178509 ] | New: JAC Suggestion Workflow 4 [ 3578869 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3037631 ] | New: JAC Suggestion Workflow 2 [ 3178509 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2532834 ] | New: JAC Suggestion Workflow [ 3037631 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2290854 ] | New: Confluence Workflow - Public Facing v4 [ 2532834 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2185196 ] | New: Confluence Workflow - Public Facing v3 [ 2290854 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1914586 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2185196 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1756147 ] | New: Confluence Workflow - Public Facing v3 [ 1914586 ] |
Description |
Original:
Different databases have different settings for case sensitivity. The case sensitivity of the database is usually set through the collation that it uses.
The default embedded database (HSQL) in Confluence is a CASE SENSITIVE database. When you attempt to migrate this data to an external database that is set up with a case insensitive collation, you may experience problems. You may encounter this error for example: The data import process reported the duplicate error on the wrong object: Import failed. (HibernateTemplate): data integrity violated by SQL ''; nested exception is java.sql.BatchUpdateException: Duplicate entry 'OSUser_user-11-confluence.prefs.email.notify' for key 1 or 2007-02-21 15:02:03,676 ERROR [sf.hibernate.util.JDBCExceptionReporter] logExceptions Violation of PRIMARY KEY constraint 'PK__OS_PROPERTYENTRY__619B8048'. Cannot insert duplicate key in object 'OS_PROPERTYENTRY'. 2007-02-21 15:02:03,692 ERROR [confluence.importexport.impl.ReverseDatabinder] endElement net.sf.hibernate.exception.ConstraintViolationException: could not insert: [bucket.user.propertyset.BucketPropertySetItem#bucket.user.propertyset.BucketPropertySetItem@d88630dc] net.sf.hibernate.exception.ConstraintViolationException: could not insert: [bucket.user.propertyset.BucketPropertySetItem#bucket.user.propertyset.BucketPropertySetItem@d88630dc] at net.sf.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:62) at net.sf.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-7917]. {panel} Different databases have different settings for case sensitivity. The case sensitivity of the database is usually set through the collation that it uses. The default embedded database (HSQL) in Confluence is a CASE SENSITIVE database. When you attempt to migrate this data to an external database that is set up with a case insensitive collation, you may experience problems. You may encounter this error for example: The data import process reported the duplicate error on the wrong object: Import failed. (HibernateTemplate): data integrity violated by SQL ''; nested exception is java.sql.BatchUpdateException: Duplicate entry 'OSUser_user-11-confluence.prefs.email.notify' for key 1 or 2007-02-21 15:02:03,676 ERROR [sf.hibernate.util.JDBCExceptionReporter] logExceptions Violation of PRIMARY KEY constraint 'PK__OS_PROPERTYENTRY__619B8048'. Cannot insert duplicate key in object 'OS_PROPERTYENTRY'. 2007-02-21 15:02:03,692 ERROR [confluence.importexport.impl.ReverseDatabinder] endElement net.sf.hibernate.exception.ConstraintViolationException: could not insert: [bucket.user.propertyset.BucketPropertySetItem#bucket.user.propertyset.BucketPropertySetItem@d88630dc] net.sf.hibernate.exception.ConstraintViolationException: could not insert: [bucket.user.propertyset.BucketPropertySetItem#bucket.user.propertyset.BucketPropertySetItem@d88630dc] at net.sf.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:62) at net.sf.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) |
Link |
New:
This issue relates to |