Details
-
Bug
-
Resolution: Fixed
-
Medium
-
2.5.4, 2.8
-
None
-
Sybase, or other database using case sensitive database column names.
Description
A customer reported that the following error is generated when attempting to perform a site restore:
2007-07-10 09:53:32,111 ERROR [Importing data task] [atlassian.confluence.setup.DefaultHibernateConfigurator] createAdditionalDatabaseIndexes Error creating additional indexes. - url: /admin/restore-local-file.action | userName: breton | action: restore-local-file com.sybase.jdbc3.jdbc.SybSQLException: Column name 'ENTITY_ID' does not exist in target table. at com.sybase.jdbc3.tds.Tds.a(Unknown Source) at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.executeLoop(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.execute(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.execute(Unknown Source) at com.mchange.v2.c3p0.impl.NewProxyStatement.execute(NewProxyStatement.java:899)
Attachments
Issue Links
- relates to
-
CONFSERVER-11331 OSUser entity migration fails due to case differences in database columns
- Closed