I'm trying to upgrade our JIRA from 6.3.6 to 6.4.13, I have already run the upgrade in our test server, and everything is working good. But during I upgrade our production one, after the upgrade process is finished, the JIRA website is not able to access, and it says the indexing completed with 1 error. I followed the debugging process in https://confluence.atlassian.com/jirakb/indexing-failed-after-jira-application-upgrade-with-reindex-all-failed-error-429917142.html,
In cause 3: SELECT * FROM jiraissue WHERE assignee IN (SELECT user_name FROM cwd_user WHERE active = '0');
I got bunch of output, it has 83 rows, so I can't past it to here, but the output like below:
| NULL | 3 | 1 | 5 | 2013-09-07 00:44:01 | 2014-03-28 08:17:33 | NULL | 2014-03-28 08:17:33 | 0 | 1 | NULL | NULL | NULL | 16080 | NULL | NULL | NULL |
| 14834 | NULL | 627 | 10105 | pcapelluto | unassigned | pcapelluto | 2 | task_info: proper column sorting
In the solution 3 said: You may need to re create the accounts with the same username in the internal directory and then de-activating the new users within JIRA. There are 83 rows, I can't just update one by one user, and I can't confirm if this is the root cause? Could you please help?
SELECT DISTINCT au.lower_user_name FROM jiraissue ji INNER JOIN app_user au ON au.user_key = ji.assignee WHERE au.lower_user_name IN (SELECT lower_user_name FROM cwd_user WHERE active = '0');
If all else fails, you should contact support. These knowledge base articles are supposed to make it to where you can solve these problems without needing additional help, and if it isn't doing that job correctly, they need to know that the article is not good enough.
Follow-up: Our support team agreed that the information previously in "Cause 3" was not valid, so they have removed it. Please continue looking at the remaining potential causes if you like, and/or follow the link above to create a support ticket if you need their help.
I would suggest:
Our support team is likely to be in a better position to help you identify and correct problems with your database than I would be.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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