Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Cloud Migration Assistant for Confluence link - Stack trace error?

Hello all,

We have recently upgraded our old version of Confluence from version 5.9 to 5.10 to enable us to use the Cloud Migration Assistant for Confluence (CMAC) to migrate our Confluence spaces to our new Cloud instance.

After installing the CMAC add-on and selecting the link in the Confluence Administration area, we get an error and large stack trace shown below, which seems to point to this error: "The database name component of the object qualifier must be the name of the current database"

Having Googled this issue there does not appear to be a direct solution related to CMAC, however some suggestions state this error may occur if the Confluence SQL database does not match the database name in the hibernate.connection.url  property in the confluence.cfg.xml file. We've checked and the database name is 'Confluencedatabase' in SQL and the hibernate.connection.url property is 'confluencedatabase' - the difference is case sensitivity of the database name.

Before we make any changes, has anyone experienced this error below with CMAC and could the case sensitivity between database names be the problem?

Many thanks.

--------

Oops - an error has occurred

logo System Error

A system error has occurred — our apologies!

For immediate troubleshooting, consult our knowledge base for a solution.

If you would like to receive support from Atlassian's support team, ask your Confluence administrator to create a support issue on Atlassian's support system with the following information:

  1. a description of your problem and what you were doing at the time it occurred
  2. a copy of the error and system information found below
  3. a copy of the application logs (if possible).

Your Confluence administrator can use the support request form to create a support ticket which will include this information.

We will respond as promptly as possible.
Thank you!

Return to site homepage…

Cause

org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getInitialState' in class com.atlassian.migration.agent.web.AppAction threw exception com.atlassian.util.concurrent.LazyReference$InitializationException: javax.persistence.PersistenceException: Failed to update database schema at /templates/app.vm[line 21, column 44]
    at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:223)

caused by: com.atlassian.util.concurrent.LazyReference$InitializationException: javax.persistence.PersistenceException: Failed to update database schema
    at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)

caused by: javax.persistence.PersistenceException: Failed to update database schema
    at com.atlassian.migration.agent.store.jpa.impl.LiquibaseSchemaUpgrader.upgrade(LiquibaseSchemaUpgrader.java:35)

caused by: liquibase.exception.MigrationFailedException: Migration failed for change set META-INF/db-changelog/5-attachment-migration-version.xml::5-attachment-migration-version-drop-index::MPT: Reason: META-INF/db-changelog/master.xml : Index Exists Precondition: MIG_ATTACH_SITE_PROGRESS_IDX on MIG_ATTACHMENT : The database name component of the object qualifier must be the name of the current database.
    at liquibase.changelog.ChangeSet.execute(ChangeSet.java:559)

caused by: liquibase.exception.PreconditionErrorException: Precondition Error
    at liquibase.precondition.core.IndexExistsPrecondition.check(IndexExistsPrecondition.java:123)

caused by: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLException: The database name component of the object qualifier must be the name of the current database.
    at liquibase.snapshot.jvm.ForeignKeySnapshotGenerator.addTo(ForeignKeySnapshotGenerator.java:110)

caused by: liquibase.exception.DatabaseException: java.sql.SQLException: The database name component of the object qualifier must be the name of the current database.
    at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:101)

caused by: java.sql.SQLException: The database name component of the object qualifier must be the name of the current database.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

 

<<snip>>

1 answer

1 accepted

0 votes
Answer accepted

We fixed this by editing the hibernate.connection.url  property in the confluence.cfg.xml file to ensure that the case matches that of the database.

Suggest an answer

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

What do you think is the most *delightful* Confluence feature? Comment for a prize!

- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...

462 views 24 9
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you