Confluence Cloud Migration Assistant version 2.4.2 on a Confluence server (or DC) instance that uses MSSQL Server as database can flood the application logs and might lead to an instance crash
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Confluence Cloud Migration Assistant version 2.4.2 on a Confluence Server (or DC) instance that uses MSSQL Server as database causes the app to flood the logs with DB schema error entries.
Environment
Confluence 7.0.2
Migration Cloud Plugin 2.4.2
Database Name: Microsoft SQL Server Database Version: 14.00.1000
Database Driver Name: com.microsoft.sqlserver.jdbc.SQLServerDriver Database Driver Version: 6.3.0.0
Diagnosis
The following log entries are observed:
2019-12-13 09:34:13,801 ERROR [Caesium-1-3] [migration.agent.queue.QueueBroker] error An error occurred when getting the next batch for consumer type: CONFLUENCE_EXPORT. Message: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: wrong column type encountered in column [USER_KEY] in table [`AO_92296B_AORECENTLY_VIEWED`]; found [nvarchar (Types#NVARCHAR)], but expecting [varchar(255) (Types#VARCHAR)]
com.atlassian.util.concurrent.LazyReference$InitializationException: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: wrong column type encountered in column [USER_KEY] in table [`AO_92296B_AORECENTLY_VIEWED`]; found [nvarchar (Types#NVARCHAR)], but expecting [varchar(255) (Types#VARCHAR)]
Cause
Confluence Cloud Migration Assistance on version 2.4.2 on a server (or DC) instance doesn't work well with MSSQL databases.
Solution
Either upgrade the Confluence Cloud Migration Assistant to version 2.4.3 and upwards or disable it.