Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-3904

Greenhopper 5.8 doesn't work well with Oracle database due to ORA-01400

XMLWordPrintable

      When try to upgrade to GreenHopper 5.8.1 in JIRA 4.4.3 using Oracle database, below error has been found:

      2011-10-20 10:19:10,374 http-8080-78 INFO jamesg 619x398x1 1dw7b1w 172.16.20.141,127.0.0.1 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [com.atlassian.greenhopper.upgrade] Starting upgrade task (buildNumber=12) : Migrate labs ranking data to multi-rank-field implementation
2011-10-20 10:19:38,678 http-8080-78 INFO jamesg 619x398x1 1dw7b1w 172.16.20.141,127.0.0.1 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [atlassian.greenhopper.upgrade.GhUpgradeTask012Dao] migrating labs rank data to new ranking table
2011-10-20 10:19:38,923 http-8080-78 ERROR jamesg 619x398x1 1dw7b1w 172.16.20.141,127.0.0.1 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [sal.core.upgrade.PluginUpgrader] Upgrade failed: There was a SQL exception thrown by the Active Objects library:
Database:
	- name:Oracle
	- version:Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
	- minor version:2
	- major version:10
Driver:
	- name:Oracle JDBC driver
	- version:11.2.0.1.0

java.sql.SQLException: ORA-01400: cannot insert NULL into ("JIRA_4_4"."AO_60DB71_ISSUERANKING"."ID")

com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
	- name:Oracle
	- version:Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
	- minor version:2
	- major version:10
Driver:
	- name:Oracle JDBC driver
	- version:11.2.0.1.0

java.sql.SQLException: ORA-01400: cannot insert NULL into ("JIRA_4_4"."AO_60DB71_ISSUERANKING"."ID")

	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.create(EntityManagedActiveObjects.java:79)
	at com.atlassian.activeobjects.osgi.DelegatingActiveObjects.create(DelegatingActiveObjects.java:58)

      Due to this, Greenhopper upgrade process has halted.

          Form Name

            [JSWSERVER-3904] Greenhopper 5.8 doesn't work well with Oracle database due to ORA-01400

            Michael Andreacchio added a comment -

            Hi Edwin,

            I've commented in your Support Issue on the procedure to fix this in your case: https://support.atlassian.com/browse/GHS-3660
            Other customers experiencing this please log the problem in https://support.atlassian.com/ and a support engineer will step you through.

            Cheers,

            Michael

            Michael Andreacchio added a comment - Hi Edwin, I've commented in your Support Issue on the procedure to fix this in your case: https://support.atlassian.com/browse/GHS-3660 Other customers experiencing this please log the problem in https://support.atlassian.com/ and a support engineer will step you through. Cheers, Michael

            Edwin Stol added a comment -

            Shaun,

            My issue (support.atlassian.com, GHS-3660) was already 'resolved' (i had to revert to GH 5.7.4 and take my losses concerning the 'Rank' field values, those were lost). If the solution is to extend the rights of the Oracle user, we will proceed with upgrading those rights, and retry our upgrade.

            Regards,

            Edwin

            Edwin Stol added a comment - Shaun, My issue (support.atlassian.com, GHS-3660 ) was already 'resolved' (i had to revert to GH 5.7.4 and take my losses concerning the 'Rank' field values, those were lost). If the solution is to extend the rights of the Oracle user, we will proceed with upgrading those rights, and retry our upgrade. Regards, Edwin

            Shaun Clowes (Inactive) added a comment -

            Hi Edwin,

            I've searched for your support issues and can't seem to find them. If you wanted to email me personally we can search for your specific problem and help you out.

            As noted in this ticket:

            • This problem is to do with the Active Objects component of JIRA, it is not directly related to GreenHopper (except that GreenHopper uses AO)
            • The problem (ORA-01400) is caused by permissions in Oracle. It's discussed at a support page, http://confluence.atlassian.com/pages/viewpage.action?pageId=273875298
            • Unfortunately, no future version of GreenHopper can fix this problem magically, though we are discussing having JIRA 5.0 provide an explicit warning if the required Oracle permissions do not exist

            I'm going to close this issue as we have determined the cause, updated the documentation for the required permissions and planned to address warning users in product in JIRA 5.0. That said, support can help you with this problem if you are experiencing it (this ticket contains a number of notes visible only to support that describe exactly how they can help).

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi Edwin, I've searched for your support issues and can't seem to find them. If you wanted to email me personally we can search for your specific problem and help you out. As noted in this ticket: This problem is to do with the Active Objects component of JIRA, it is not directly related to GreenHopper (except that GreenHopper uses AO) The problem (ORA-01400) is caused by permissions in Oracle. It's discussed at a support page, http://confluence.atlassian.com/pages/viewpage.action?pageId=273875298 Unfortunately, no future version of GreenHopper can fix this problem magically, though we are discussing having JIRA 5.0 provide an explicit warning if the required Oracle permissions do not exist I'm going to close this issue as we have determined the cause, updated the documentation for the required permissions and planned to address warning users in product in JIRA 5.0. That said, support can help you with this problem if you are experiencing it (this ticket contains a number of notes visible only to support that describe exactly how they can help). Thanks, Shaun

            Matthew Gorton added a comment -

            Just to confirm that we have now been able to upgrade to GH 5.8.5 on Jira 4.4.4

            During our initial upgrade the Oracle user did not have sufficient privileges to create sequences. It appears that when the GH upgrade process added the sequences, the resulting db errors were ignored and as a result Rapdidview did not work. After we granted the additional permissions to the db account and repeated the upgrade on a fresh copy of our Jira install, Rapidview worked successfully.

            Good luck Edwin...

            Cheers
            <matthew

            Matthew Gorton added a comment - Just to confirm that we have now been able to upgrade to GH 5.8.5 on Jira 4.4.4 During our initial upgrade the Oracle user did not have sufficient privileges to create sequences. It appears that when the GH upgrade process added the sequences, the resulting db errors were ignored and as a result Rapdidview did not work. After we granted the additional permissions to the db account and repeated the upgrade on a fresh copy of our Jira install, Rapidview worked successfully. Good luck Edwin... Cheers <matthew

            Edwin Stol added a comment -

            So, Greenhopper 5.8.6 is released, but no solution for this problem.
            I raised a support request already to 'fix' this issue, but i'm still stuck on Greenhopper 5.7.4.
            So, i ask again, what's the ETA on the fix for this problem? Is it scheduled/being actively worked on at least?

            Cheers,

            Edwin

            Edwin Stol added a comment - So, Greenhopper 5.8.6 is released, but no solution for this problem. I raised a support request already to 'fix' this issue, but i'm still stuck on Greenhopper 5.7.4. So, i ask again, what's the ETA on the fix for this problem? Is it scheduled/being actively worked on at least? Cheers, Edwin

            Michael Andreacchio added a comment -

            Customers facing this problem are recommended to go to this page: http://confluence.atlassian.com/pages/viewpage.action?pageId=273875298

            Please send in a support request to https://support.atlassian.com concerning this issue for advice on how to fix.

            Cheers,

            Michael
            Atlassian Support

            Michael Andreacchio added a comment - Customers facing this problem are recommended to go to this page: http://confluence.atlassian.com/pages/viewpage.action?pageId=273875298 Please send in a support request to https://support.atlassian.com concerning this issue for advice on how to fix. Cheers, Michael Atlassian Support

            Matthew Gorton added a comment -

            So what is the recommended path forward to use this key feature ingh against 4.4.4 with an Oracle database?

            In the latest greenhopper the rapid board screen is the default entry point to the product and it gives a server error. Not good. I need to get to jira 4.4.4 to resolve unrelated ldap issues but I am blocked by this gh issue. I also have third party integrations that are going to delay any move to 5.0.

            Can you confirm that this will be addressed in 4.4.4?

            Matthew Gorton added a comment - So what is the recommended path forward to use this key feature ingh against 4.4.4 with an Oracle database? In the latest greenhopper the rapid board screen is the default entry point to the product and it gives a server error. Not good. I need to get to jira 4.4.4 to resolve unrelated ldap issues but I am blocked by this gh issue. I also have third party integrations that are going to delay any move to 5.0. Can you confirm that this will be addressed in 4.4.4?

            Shaun Clowes (Inactive) added a comment -

            Apologies Edwin, that comment was meant to be internal.

            As I've stated before, please do not wait for JIRA 5 and GreenHopper 5.9, if you are experiencing problems they will not be automatically resolved by a future upgrade. We apologise for all of the inconvenience over these issues but we want to help everyone get back up and running as soon as possible.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Apologies Edwin, that comment was meant to be internal. As I've stated before, please do not wait for JIRA 5 and GreenHopper 5.9, if you are experiencing problems they will not be automatically resolved by a future upgrade. We apologise for all of the inconvenience over these issues but we want to help everyone get back up and running as soon as possible. Thanks, Shaun

            Edwin Stol added a comment -

            Shaun,

            I do not think we can access the extranet. (i get a Log In page, with no possibilities to register)

            The 'solution' proposed in AO-285 can hardly be called a solution, more of an work-around. It only 'solves' the problem upon installing GH 5.8.4, you'd still need to rollback to 5.7.4.
            I do not know what the ETA on JIRA 5/GH 6 is, but i hope it's soon..

            Edwin Stol added a comment - Shaun, I do not think we can access the extranet. (i get a Log In page, with no possibilities to register) The 'solution' proposed in AO-285 can hardly be called a solution, more of an work-around. It only 'solves' the problem upon installing GH 5.8.4, you'd still need to rollback to 5.7.4. I do not know what the ETA on JIRA 5/GH 6 is, but i hope it's soon..

            Edwin Stol added a comment - - edited

            Same problem on Jira v4.4.4#664-r167664 with GH 5.8.4 and Oracle 10g.

            This problem is blocking our progress, since we really need the Rapid Board for our new Jira architecture.

            Edwin Stol added a comment - - edited Same problem on Jira v4.4.4#664-r167664 with GH 5.8.4 and Oracle 10g. This problem is blocking our progress, since we really need the Rapid Board for our new Jira architecture.

              Unassigned Unassigned
              vkgan Gan VoonKiat
              Affected customers:
              14 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: