As a test case I tried to import a 3.5.9 exported space into 3.5.17.
We had exported say SPACE1 from our production system and changed entities.xml according to
The import into our production 3.5.9 as say SPACE2 worked perfectly.
When I do the same with 3.5.17 (last 3.5.x) it fails with
Import failed. Check your server logs for more information.
Hibernate operation: could not insert: [com.atlassian.confluence.labels.Labelling#720969];
SQL ; Violation of PRIMARY KEY constraint 'PK__CONTENT___3214EC27FB627BCE'.
Cannot insert duplicate key in object 'dbo.CONTENT_LABEL'.
The duplicate key value is (720969).; nested exception is java.sql.SQLException:
Violation of PRIMARY KEY constraint 'PK__CONTENT___3214EC27FB627BCE'.
Cannot insert duplicate key in object 'dbo.CONTENT_LABEL'. The duplicate key value is (720969).
Back end is a SQL Server 2012.
Can you confirm whether you are using a case-sensitive collation scheme for your SQL Server database because this is the most common cause of issues such as this one? We recommend usingthe "SQL_Latin1_General_CP1_CS_AS" collation scheme, so if you are not using this scheme then please run the SQL below to convert the collation scheme of your database.
ALTER DATABASE <database_name> COLLATE SQL_Latin1_General_CP1_CS_AS
All the best,
This is really disturbing!
Just tried the import of the space on a 3.5.9 install (the exact version we are at) and it went without a hitch!
So apparently Confluence space import is NOT even compatible on a revision level!
Your understanding (documentation) of major and minor versions and revision levels is "interesting" too.
Some insight would be appreciated.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot