You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are just in the stage ot test migrating selected products of our on premises Jira Software to a cloud instance of Jira Software. App Assesment went fine, as we will discontinue to use all our add-ons since they were mainly used in the contect of business projects for time tracking, contact data etc. So we will bring Jira "back to the roots" during the migration, therefore the selected migration.
However I am facing the problem with the migration assistant, that it cannot read projects from the local instance as it sends wrong SQL queries to the database. As usual the PostgreSQL Database is case-sensitive when query terms are placed in double quotes. As such, queries where the table project is used as
SELECT xyz FROM public."Project"
fail with unknown table errors from the dabase leading to corresponding SQL exceptions to be found in the atlassian-jira.log
Did anybody out there face the same problems and if yes, is there any solution / workaround that does NOT mean to switch the database system e.g. to MS-SQL just in order to prepare the migration?
Any help highly welcome
Hi @Marc Koppelaar ,
thanks for the hint but unfortunately not the cause. The schema tag is already present in the dbconfig, and besides some timeout and pool size values my file looks exactly as the one in the Kb article.
This is why I do not understand that the JCMA produces the erronous queries.