Child pages
  • Upgrade to GreenHopper 5.8.x using Rapid Board gives Oracle Error ORA-01400: cannot insert NULL into ("JIRA44"."AO_60DB71_RAPIDVIEW"."ID")
Skip to end of metadata
Go to start of metadata

The license could not be verified: License Certificate has expired! Administrators, please check your license details here.


When upgrading to GreenHopper v5.8.x (previous version of JIRA Agile). When trying to use the Rapid Board the screen displays a database server error. The tomcat logs will show the following Oracle error:

	- name:Oracle
	- version:Oracle Database 10g Enterprise Edition Release - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
	- minor version:2
	- major version:10
	- name:Oracle JDBC driver
	- version:

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


This error is from the following issue  GHS-3904 - Getting issue details... STATUS  and caused by a lack of database privileges for the Oracle database user. In this case, while GreenHopper has been upgrading the database user has not had privelages to create the GreenHopper sequence AO_60DB71_ISSUERANKING_ID_seq, although it has created the table AO_60DB71_ISSUERANKING, so when GreenHopper calls on the sequence it fails.


Please read all steps for the full picture. 

Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.

The following is the procedure when an upgrade from JIRA 4.4.x breaks GreenHopper/JIRA:

  1. Stop JIRA.
  2. Immediately roll back your JIRA upgrade Rolling Back a JIRA Upgrade
  3. Restore your JIRA 4.4.x database
  4. Drop all AO_60DB71_ tables
  5. Make sure that the database user has CREATE SEQUENCES and CREATE TRIGGER permissions, as per this guide.
  6. Upgrade JIRA again
    (info) Once restarted, JIRA should recreate the appropriate tables correctly including all triggers and sequences that were not created the first time around and this issue should be resolved.
The reason for the full roll back is because JIRA also uses AO tables now since JIRA 5.x and these likely have not been created correctly.

If it is found that the upgrade tasks have been run already and this in fact does not fix the problem, you have most likely run into a different problem. Please gather as much relevant information on your case as possible and feel free to contact the given channels.