UpgradeTask_Build633 Oracle 11g takes more than 5 hours to finish each customfield

Question

Hello, I am upgrading JIRA from 4.0.1 to 6.0.6.

WAR installation, Linux OS, Oracle 11g, Connected 4.0.1 data to 6.0.6 compiled code(which is called In-Place DB upgrade I believe).

UpgradeTask_Build633 is taking hell lot of time to finish single custom field. To finish each custom field it takes more than 5 or 6 hours. Insane! I know that this task migrates Custom field values for Select and MultiSelect types to store the id of the option rather than the value.

I am wondering whu does this take so much time. Any clue on what might be causing this huge delay?

PS: There is a solution mention here for MS-SQL:  https://confluence.atlassian.com/pages/viewpage.action?pageId=264045011

Also it complains that no option was found for custom field but there are option values configured. Take a look at the log. Just note the time difference between each custom field.

2013-09-24 18:08:33,881 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] Updating custom field 'Affected Languages', 1 of 31

2013-09-24 23:11:45,342 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] Updating custom field 'App Server Type', 2 of 31

2013-09-24 23:13:09,988 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:14:05,093 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:14:31,176 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:14:35,163 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:15:38,173 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:15:46,977 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:15:58,337 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:18:13,802 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:19:03,240 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:22:47,822 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:23:25,442 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' Field value 'null'. Value cleared.

2013-09-24 23:23:45,201 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] No option found for Custom field 'App Server Type' ... more than 10 times.

2013-09-25 10:04:41,402 localhost-startStop-1 INFO      [jira.upgrade.tasks.UpgradeTask_Build633] Updating custom field 'Application Server OS Type', 3 of 31

Hanumesh Jojode · Answer

I can only go with upgrading JIRA manually. Since our DB is huge we can't go with XML export and import. Only way out is to connect extracted WAR for 6.0.6 along with our customizations to the database.

I don't know why this particular upgrade task is taking so much time. It' been two days and it has just finished 4 custom fields.

Zul NS [Atlassian] · Answer

May I know if you are performing in-place database upgrade? Are you upgrading from 4.0.1 directly to 6.x? We recommend to upgrade from 4.0.1 to 4.4.5 first, then only 6.x.