Export from 5.0.3 will not import into 5.5.6 Error

I have upgraded 3.5.17 to 5.0.3 successfully.  I have XML exported a space in 5.0.3 and attempted to import into 5.5.6 and get the error "Backups made prior to Confluence 4.0 (build 3047) can not be restored. This backups build number was missing." 

I want to export and import the spaces individually to help weed out the unused wiki's.  Any thoughts?

3 answers

This widget could not be displayed.

Hi,

You cannot import a backup from version 5.0.3 into Confluence version 5.5.6. 

https://confluence.atlassian.com/display/DOC/Restoring+a+Site

You should try to upgrade your 5.0.3 to 5.5.6 as suggested on the mentioned page: 

  • XML backups should not be used to upgrade Confluence. Upgrade Confluence by following: Upgrading Confluence.
This widget could not be displayed.

I have.  Several times with the same results.  See below.

 

Doing a manual upgrade, when I connect to the server after upgrade the browser shows:

 

Type

Description

Exception

Level

Time

startup

This installation of Confluence has failed one or more bootstrap configuration checks. Please check the logs for details.

Your server id is: BK5F-JT1Y-SCYD-RU7J

Database collation is incorrect, it must be set to 'SQL_Latin1_General_CP1_CS_AS'. Please see https://confluence.atlassian.com/x/pQXFIw

fatal

2015-01-27 17:27:45

 

So I looked up the error and did a roll back and before launching confluence I connected to the DB server and ran:

 

ALTER DATABASE confluence3515 SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

ALTER DATABASE confluence3515 COLLATE SQL_Latin1_General_CP1_CS_AS;

ALTER DATABASE confluence3515 SET MULTI_USER;

 

So now the SQL studio shows the correct collation.

 

So I tried it again.  And got a read committed snapshot error.  So I rolled back again and ran the above steps and these steps:

ALTER DATABASE confluence3515

   SET READ_COMMITTED_SNAPSHOT ON

   WITH ROLLBACK IMMEDIATE;

 

Now the read_committed_snapshot is on (1)

 

So I tried again.

 

And very consistently get the errors below.  Thoughts? 

 

2015-01-27 18:16:01,388 ERROR [localhost-startStop-1] [atlassian.confluence.upgrade.UpgradeLauncherServletContextListener] contextInitialized Upgrade failed, application will not start: Upgrade task com.atlassian.confluence.upgrade.upgradetask.ReferencedUsersUserMappingUpgradeTask@1fc4ac4 failed during the SCHEMA_UPGRADE phase due to: Unable to complete user mapping creation.

com.atlassian.confluence.upgrade.UpgradeException: Upgrade task com.atlassian.confluence.upgrade.upgradetask.ReferencedUsersUserMappingUpgradeTask@1fc4ac4 failed during the SCHEMA_UPGRADE phase due to: Unable to complete user mapping creation.

                at com.atlassian.confluence.upgrade.AbstractUpgradeManager.executeUpgradeStep(AbstractUpgradeManager.java:273)

                at com.atlassian.confluence.upgrade.AbstractUpgradeManager.runSchemaUpgradeTasks(AbstractUpgradeManager.java:217)

                at com.atlassian.confluence.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:167)

                at com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListener.contextInitialized(UpgradeLauncherServletContextListener.java:51)

                at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4973)

                at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5467)

                at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

                at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)

                at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)

                at java.util.concurrent.FutureTask.run(FutureTask.java:262)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

                at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.RuntimeException: Unable to complete user mapping creation.

                at com.atlassian.confluence.upgrade.upgradetask.AbstractUserMappingUpgradeTask.doUpgrade(AbstractUserMappingUpgradeTask.java:72)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                at java.lang.reflect.Method.invoke(Method.java:606)

                at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)

                at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)

                at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)

                at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)

                at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

                at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)

                at com.sun.proxy.$Proxy29.doUpgrade(Unknown Source)

                at com.atlassian.confluence.upgrade.AbstractUpgradeManager$UpgradeStep$3.execute(AbstractUpgradeManager.java:761)

                at com.atlassian.confluence.upgrade.AbstractUpgradeManager.executeUpgradeTask(AbstractUpgradeManager.java:293)

                at com.atlassian.confluence.upgrade.AbstractUpgradeManager.executeUpgradeStep(AbstractUpgradeManager.java:264)

                ... 12 more

Caused by: org.springframework.dao.TransientDataAccessResourceException: StatementCallback; SQL [select distinct t.CREATOR from LINKS t left outer join user_mapping um1 on t.CREATOR = um1.user_key left outer join user_mapping um2 on t.CREATOR = um2.lower_username where um1.user_key is null and um2.user_key is null]; Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CS_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.; nested exception is java.sql.SQLException: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CS_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

                at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:106)

                at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:72)

                at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)

                at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)

                at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:407)

                at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:458)

                at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:462)

                at com.atlassian.confluence.upgrade.upgradetask.ReferencedUsersUserMappingUpgradeTask.getUsernamesMissingMapping(ReferencedUsersUserMappingUpgradeTask.java:64)

                at com.atlassian.confluence.upgrade.upgradetask.AbstractUserMappingUpgradeTask.doUpgrade(AbstractUserMappingUpgradeTask.java:46)

                ... 26 more

Caused by: java.sql.SQLException: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CS_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

                at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

                at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)

                at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)

                at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631)

                at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)

                at net.sourceforge.jtds.jdbc.JtdsStatement.executeQuery(JtdsStatement.java:1301)

                at com.mchange.v2.c3p0.impl.NewProxyStatement.executeQuery(NewProxyStatement.java:35)

                at org.springframework.jdbc.core.JdbcTemplate$1QueryStatementCallback.doInStatement(JdbcTemplate.java:443)

                at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:396)

                ... 30 more

2015-01-27 18:16:01,404 ERROR [localhost-startStop-1] [atlassian.confluence.upgrade.UpgradeLauncherServletContextListener] contextInitialized 1 errors were encountered during upgrade:

2015-01-27 18:16:01,404 ERROR [localhost-startStop-1] [atlassian.confluence.upgrade.UpgradeLauncherServletContextListener] contextInitialized 1: Unable to complete user mapping creation.

2015-01-27 18:16:01,404 WARN [localhost-startStop-1] [atlassian.confluence.plugin.PluginFrameworkContextListener] contextInitialized Not starting full plugin system due to upgrade or licensing errors

2015-01-27 18:16:02,184 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve

 

This widget could not be displayed.

The issue you are having is because the major numbers of the Confluence versions do not match.

"Wait ... what?" (I hear you cry ...) "I'm trying to export from 5.x and import to 5.y - surely these are both the same major number (5)?"

Nope ... according to Restoring a Space:

"Confluence only supports compatibility for space import and export when executed within the same major version of Confluence. (This issue is logged as CONF-26111.)

Clarifying our terminology: By major version, we mean the version defined in the first two sections of the release number. For example, Confluence 2.2 and Confluence 2.3 are different major versions. Confluence 2.2.1 and Confluence 2.2.6 are the same major version."

What this means that they refer to the "5" part of 5.0.3 as I have no idea (super-version, ultra-version, mega-version?!).

So what you'll need to do is to perform an export/import from your existing 5.0.3 instance into another 5.0.3 instance, and then upgrade that 5.0.3 instance to whatever version you're looking to get to.

sad

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

473 views 6 6
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you