Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,559,471
Community Members
 
Community Events
184
Community Groups

Can not start Migration Assistant

Edited
Paul Brannigan
Paul Brannigan Jul 13, 2022

Environment:

Confluence Data Center 6.0.2

Looking to migrate to cloud

Installed Migration assistant Version: 3.0.6

Click on "Migration Assistant" link

Result:

Oops - an error occured....

.... Stack Trace ....

Key text:

Caused by: java.sql.SQLException: The database name component of the object qualifier must be the name of the current database.

 

This is very similar to reported issue found at:

https://community.atlassian.com/t5/Confluence-questions/Cloud-Migration-Assistant-for-Confluence-link-Stack-trace-error/qaq-p/1179130

and also

https://confluence.atlassian.com/bitbucketserverkb/bitbucket-server-fails-to-connect-to-sql-server-the-database-name-component-of-the-object-qualifier-must-be-the-name-of-the-current-database-952624350.html

My database is named correctly (case sensitive) in

hibernate.connection.url property in the confluence.cfg.xml file

 

I do not have a <home-directory>/shared/bitbucket.properties file.

 

IF this is really a Microsoft SQL Database name mis - match, are there other configuration files I can check that may have the "database name" string?

 

 

Answer
Watch
Like Be the first to like this
97 views

1 answer

0 votes
Sylvain Dhonneur
Sylvain Dhonneur Feb 01, 2023

Did you ever figure out this one? I am on the same situation...

View More Comments
Shannon S
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 06, 2023

Hi Sylvain,

If you're still having trouble, can you raise a ticket with our Migration Support Team? We can look with you and find out the reason for the error.

Take care,

Shannon | Atlassian Community Support

Like
Reply

Suggest an answer

Log in or Sign up to answer
Confluence
Confluence
DEPLOYMENT TYPE
SERVER
VERSION
6.0.2
TAGS
AUG Leaders

Atlassian Community Events

See all events