Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-2602

Import fails with unique constraint violation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • None
    • 1.3.1
    • None

    • Confluence Standalone
      AS: Tomcat 4.1.30
      DB: Oracle 10g

      We've tried to export our Confluence site from version 1.2.3 and import it into a clean 1.3.1 installation. The import fails with unique constraint violation.

      The constraint SYS_C0016204 is the primary key constraint of CONTENT.CONTENTID.

      18.1.2005 9:36:30 net.sf.hibernate.JDBCException <init>
      SEVERE: could not insert: com.atlassian.confluence.user.PersonalInformation#3961
      java.sql.BatchUpdateException: ORA-00001: unique constraint (CONFLUENCE.SYS_C0016204) violated
      at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:367)
      at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:8739)
      at org.apache.commons.dbcp.DelegatingPreparedStatement.executeBatch(DelegatingPreparedStatement.java:231)
      at net.sf.hibernate.impl.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:54)
      at net.sf.hibernate.impl.BatchingBatcher.addToBatch(BatchingBatcher.java:34)
      at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:468)
      at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:442)
      at net.sf.hibernate.impl.ScheduledInsertion.execute(ScheduledInsertion.java:29)
      at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2418)
      at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2371)
      at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2240)
      at com.atlassian.confluence.importexport.impl.BackupImporter.doUpgrades(BackupImporter.java:142)
      at com.atlassian.confluence.importexport.impl.BackupImporter.doImport(BackupImporter.java:87)
      at com.atlassian.confluence.importexport.DefaultImportExportMana18.1.2005 9:36:30 net.sf.hibernate.JDBCException <init>
      ...
      18.1.2005 9:36:30 net.sf.hibernate.impl.SessionImpl execute
      SEVERE: Could not synchronize database state with session
      net.sf.hibernate.JDBCException: could not insert: com.atlassian.confluence.user.PersonalInformation#3961
      at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:478)
      at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:442)
      at net.sf.hibernate.impl.ScheduledInsertion.execute(ScheduledInsertion.java:29)
      at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2418)
      at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2371)
      at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2240)
      at com.atlassian.confluence.importexport.impl.BackupImporter.doUpgrades(BackupImporter.java:142)
      at com.atlassian.confluence.importexport.impl.BackupImporter.doImport(BackupImporter.java:87)
      at com.atlassian.confluence.importexport.DefaultImportExportManager.importAs(DefaultImportExportManager.java:48)
      ...

        1. LobSelector.class
          1 kB

            [CONFSERVER-2602] Import fails with unique constraint violation

            Jarno Peltoniemi added a comment -

            We're doing fine with the updated LobSelector class. No objections from us.

            Jarno Peltoniemi added a comment - We're doing fine with the updated LobSelector class. No objections from us.

            Nick Faiz [OLD] (Inactive) added a comment -

            Anyone have any objections if I close this issue?

            I think we've verified that this problem can occur on 10G drivers with higher volumes of data.

            Cheers,
            Nick

            Nick Faiz [OLD] (Inactive) added a comment - Anyone have any objections if I close this issue? I think we've verified that this problem can occur on 10G drivers with higher volumes of data. Cheers, Nick

            Jarno Peltoniemi added a comment -

            The upgraded Confluence broke up after restart. It was related to CONF-2355. Removing the incompatible macro plugin fixed the issue and all the other issues we had encountered on the administration pages.

            Regards,
            Jarno

            Jarno Peltoniemi added a comment - The upgraded Confluence broke up after restart. It was related to CONF-2355 . Removing the incompatible macro plugin fixed the issue and all the other issues we had encountered on the administration pages. Regards, Jarno

            Jarno Peltoniemi added a comment -

            We've succesfully upgraded our production system to 1.3.2 using the patched LobSelector.class. We ran into CONF-2656 and patched the affected class ourselves. All major functionality seems to work fine, but we've encountered some problems on administration pages. I'll file separate issues on those.

            Thanks,
            Jarno

            Jarno Peltoniemi added a comment - We've succesfully upgraded our production system to 1.3.2 using the patched LobSelector.class. We ran into CONF-2656 and patched the affected class ourselves. All major functionality seems to work fine, but we've encountered some problems on administration pages. I'll file separate issues on those. Thanks, Jarno

            Nick Faiz [OLD] (Inactive) added a comment -

            Jamo,
            Glad that it worked on your test system. Yes, please let us know how it goes and if run into any difficulties.

            Cheers,
            Nick

            Nick Faiz [OLD] (Inactive) added a comment - Jamo, Glad that it worked on your test system. Yes, please let us know how it goes and if run into any difficulties. Cheers, Nick

            Nick Faiz [OLD] (Inactive) added a comment -

            Richard,
            If you're seeing integrity constraints where there should be none, we recommend that you use the 9i Drivers with Oracle 9i, alongside the LobSelector patch.

            If you have any further questions please email confluence-support@atlassian.com .

            Cheers,
            Nick

            Nick Faiz [OLD] (Inactive) added a comment - Richard, If you're seeing integrity constraints where there should be none, we recommend that you use the 9i Drivers with Oracle 9i, alongside the LobSelector patch. If you have any further questions please email confluence-support@atlassian.com . Cheers, Nick

            Jarno Peltoniemi added a comment -

            Hi!

            I replaced the LobSelector class with the one you provided. Otherwise, the environment stayed the same. Using Oracle 10g DB, Oracle 10g jdbc drivers and a standalone Confluence the import went just fine!

            I'll provide more information after the production update.

            Thanks,
            Jarno

            Jarno Peltoniemi added a comment - Hi! I replaced the LobSelector class with the one you provided. Otherwise, the environment stayed the same. Using Oracle 10g DB, Oracle 10g jdbc drivers and a standalone Confluence the import went just fine! I'll provide more information after the production update. Thanks, Jarno

            Richard THIBAULT added a comment -

            OK it means that I can stay using Oracle 10g on Oracle 9i ?

            Richard THIBAULT added a comment - OK it means that I can stay using Oracle 10g on Oracle 9i ?

            Nick Faiz [OLD] (Inactive) added a comment -

            Hi Jamo,
            Any progress made following the suggestions we made above?

            Cheers,
            Nick

            Nick Faiz [OLD] (Inactive) added a comment - Hi Jamo, Any progress made following the suggestions we made above? Cheers, Nick

            Nick Faiz [OLD] (Inactive) added a comment -

            Hi Richard,
            We'd like you to use the 9i drivers with Oracle 8i, and use the LobSelector class in attachment - this is a work around for the Clob problem. It doesn't require the SetBigStringTryClob parameter.

            The integrity constraint error message can be encountered for other reasons, which are legitimate, than the problem we've currently encountered using the 10g drivers. However, we've only encountered it using the 10g drivers so we suggest the 9i drivers and LobSelector work around, which fixes things.

            In the meantime, we're working on diagnosing the 10g prob - see CONF-2640

            It might be helpful to open a separate support issue on http://support.atlassian.com - you could send us the export which is problematic and we could test it ourselves.

            Let us know if you run into any problems.

            Cheers,
            Nick

            Nick Faiz [OLD] (Inactive) added a comment - Hi Richard, We'd like you to use the 9i drivers with Oracle 8i, and use the LobSelector class in attachment - this is a work around for the Clob problem. It doesn't require the SetBigStringTryClob parameter. The integrity constraint error message can be encountered for other reasons, which are legitimate, than the problem we've currently encountered using the 10g drivers. However, we've only encountered it using the 10g drivers so we suggest the 9i drivers and LobSelector work around, which fixes things. In the meantime, we're working on diagnosing the 10g prob - see CONF-2640 It might be helpful to open a separate support issue on http://support.atlassian.com - you could send us the export which is problematic and we could test it ourselves. Let us know if you run into any problems. Cheers, Nick

              Unassigned Unassigned
              760f629e6819 Jarno Peltoniemi
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: