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

GreenHopper failed to upgrade due to java.sql.SQLException: Function not supported

XMLWordPrintable

    • 5.08
    • Hide
      Atlassian Status as at December 13 2011

      Hi All,

      Please note that this problem is related to an issue with the Active Objects library/plugin that is shipped with Jira. This problem is fixed in Jira 4.4.4 which was released on the 13th of December 2012.

      Please note that in some cases affected users may require some manual corrections to their database. If you continue to have difficulties please contact https://support.atlassian.com for assistance.

      Thanks,
      Shaun Clowes

      Show
      Atlassian Status as at December 13 2011 Hi All, Please note that this problem is related to an issue with the Active Objects library/plugin that is shipped with Jira. This problem is fixed in Jira 4.4.4 which was released on the 13th of December 2012. Please note that in some cases affected users may require some manual corrections to their database. If you continue to have difficulties please contact https://support.atlassian.com for assistance. Thanks, Shaun Clowes

      When perform upgrade to GreenHopper 5.8.x in JIRA 4.4.3 using Oracle database, below error has been found:

      2011-10-21 13:46:33,248 http-8443-1 ERROR leon 826x334x1 1dxw16k 10.101.10.31 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [greenhopper.upgrade.task013.MigrateRankDataTaskImpl] Could not migrate ranks from old rank field customfield_10001 to new rank field customfield_10932
2011-10-21 13:46:33,248 http-8443-1 INFO leon 826x334x1 1dxw16k 10.101.10.31 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [greenhopper.upgrade.task013.MigrateRankDataTaskImpl] -- Undo class com.atlassian.greenhopper.upgrade.task013.MigrateRankDataTaskImpl

      And

      2011-10-21 13:46:33,810 http-8443-1 INFO leon 826x334x1 1dxw16k 10.101.10.31 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [greenhopper.upgrade.task013.ConvertOldRankFieldsToNumberTypeTask] -- Undo Done class com.atlassian.greenhopper.upgrade.task013.ConvertOldRankFieldsToNumberTypeTask
2011-10-21 13:46:33,826 http-8443-1 ERROR leon 826x334x1 1dxw16k 10.101.10.31 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [sal.core.upgrade.PluginUpgrader] Upgrade failed: null
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)

      end up with :

      Caused by: 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.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
	- minor version:2
	- major version:10
Driver:
	- name:Oracle JDBC driver
	- version:11.2.0.1.0

java.sql.SQLException: Functie wordt niet ondersteund.
	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.create(EntityManagedActiveObjects.java:79)
	at com.atlassian.activeobjects.osgi.DelegatingActiveObjects.create(DelegatingActiveObjects.java:58)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

      As far as we discovered, this only happened in Oracle Database.

            [JSWSERVER-3916] GreenHopper failed to upgrade due to java.sql.SQLException: Function not supported

            Bill Pribyl added a comment -

            Thanks guys, I think it's working now...and, as an oh-by-the-way, even if you do a fresh install of the plug-in, it doesn't actually build the AO_60DB71 database objects until a user first attempts to use a GH feature! Quite contrary to my expectations.

            Bill Pribyl added a comment - Thanks guys, I think it's working now...and, as an oh-by-the-way, even if you do a fresh install of the plug-in, it doesn't actually build the AO_60DB71 database objects until a user first attempts to use a GH feature! Quite contrary to my expectations.

            Jason Brison added a comment -

            We had to delete the related triggers as well. So Tables, sequences and triggers.

            Regards,

            Jason Scott Brison
            BB10 Development Support
            Software Support Specialist
            Software Tools and Systems – R&D
            Research In Motion, Limited
            Halifax, NS
             
            Visit http://go/sts for support details

            Jason Brison added a comment - We had to delete the related triggers as well. So Tables, sequences and triggers. Regards, Jason Scott Brison BB10 Development Support Software Support Specialist Software Tools and Systems – R&D Research In Motion, Limited Halifax, NS   Visit http://go/sts for support details

            Sean deBardelaben added a comment -

            Bill,

            Before we only needed to delete the tables to get a clean install. Now we need to (oracle 11) delete the Sequences in the database.
            AO_60DB71_COLUMN_ID_SEQ
            AO_60DB71_COLUMNSTATUS_ID_SEQ
            AO_60DB71_ISSUERANK1567494799
            AO_60DB71_ISSUERANKING_ID_SEQ
            AO_60DB71_QUICKFILTER_ID_SEQ
            AO_60DB71_RAPIDVIEW_ID_SEQ
            AO_60DB71_SPRINT_ID_SEQ
            AO_60DB71_STATSFIELD_ID_SEQ
            AO_60DB71_SWIMLANE_ID_SEQ

            Sean deBardelaben added a comment - Bill, Before we only needed to delete the tables to get a clean install. Now we need to (oracle 11) delete the Sequences in the database. AO_60DB71_COLUMN_ID_SEQ AO_60DB71_COLUMNSTATUS_ID_SEQ AO_60DB71_ISSUERANK1567494799 AO_60DB71_ISSUERANKING_ID_SEQ AO_60DB71_QUICKFILTER_ID_SEQ AO_60DB71_RAPIDVIEW_ID_SEQ AO_60DB71_SPRINT_ID_SEQ AO_60DB71_STATSFIELD_ID_SEQ AO_60DB71_SWIMLANE_ID_SEQ

            Bill Pribyl added a comment -

            Support has had me try a lot of things, but nothing seems to work in my installation. At this point my Greenhopper is non functional. Does anyone in the user community know how to completely uninstall and reinstall Greenhopper from scratch? Running the uninstall and deleting the database objects does not seem to be enough.

            Bill Pribyl added a comment - Support has had me try a lot of things, but nothing seems to work in my installation. At this point my Greenhopper is non functional. Does anyone in the user community know how to completely uninstall and reinstall Greenhopper from scratch? Running the uninstall and deleting the database objects does not seem to be enough.

            Shaun Clowes (Inactive) added a comment -

            Hi All,

            Bill Pribyl: Could you please follow up with support? They should be able to help you resolve this without a downgrade.

            All: It's important to note that not all 'java.sql.SQLException' problems are equal. We are seeing a different error with some customers that is being actively worked on. If you are not receiving and exception with "Function Not Supported" you may be experiencing either: problems with left over data from a previous problematic version of AO or a new error that we need to track separately. In either case please be sure to work the issue through with Support.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi All, Bill Pribyl: Could you please follow up with support? They should be able to help you resolve this without a downgrade. All: It's important to note that not all 'java.sql.SQLException' problems are equal. We are seeing a different error with some customers that is being actively worked on. If you are not receiving and exception with "Function Not Supported" you may be experiencing either: problems with left over data from a previous problematic version of AO or a new error that we need to track separately. In either case please be sure to work the issue through with Support. Thanks, Shaun

            Gisela S Nogueira added a comment - - edited

            I´m with the same issue, but I use PostGree, I already update to Jira 4.4.4 and GreenHopper 5.8.4 but didn´t work.

            Gisela S Nogueira added a comment - - edited I´m with the same issue, but I use PostGree, I already update to Jira 4.4.4 and GreenHopper 5.8.4 but didn´t work.

            Sean deBardelaben added a comment -

            I was told last night that the development team needed the our data to reproduce the problem. I attached an clean anonymous copy of the zip we are using for upgrade testing which I assume was delivered to the greenhopper developers. I've not heard back yet...

            Sean deBardelaben added a comment - I was told last night that the development team needed the our data to reproduce the problem. I attached an clean anonymous copy of the zip we are using for upgrade testing which I assume was delivered to the greenhopper developers. I've not heard back yet...

            Gum Shoes added a comment -

            I don't migrate to postgresql because the multinational corp that I work at is, like many large corporations, an 'Oracle first' shop.
            I have done no DB customizations.

            Gum Shoes added a comment - I don't migrate to postgresql because the multinational corp that I work at is, like many large corporations, an 'Oracle first' shop. I have done no DB customizations.

            Gleb Budko added a comment -

            2 Bill Pribyl. No problem with MySQL at all. I tested upgrade on test server which runs MySQL. Then it failed on Oracle

            Gleb Budko added a comment - 2 Bill Pribyl. No problem with MySQL at all. I tested upgrade on test server which runs MySQL. Then it failed on Oracle

            Bill Pribyl added a comment -

            By the way, I did receive an answer back from my support ticket...they told me to downgrade Greenhopper to 5.7.4...

            Given all the investigation we've performed over this issue, and some other similar tickets that came to our attention, we believe that the cause of these problems can be related to the latest Greenhopper versions.

            I suggest you to downgrade to GreenHopper 5.7.4 for the time being until we sorted out the root cause for this problem.

            To do that:

            1. Backup JIRA
            2. Shutdown JIRA
            3. Backup JIRA database
            4. Remove GreenHopper plugin from JIRA_HOME/plugins/installed-plugin directory.
            5. Start JIRA

            Bill Pribyl added a comment - By the way, I did receive an answer back from my support ticket...they told me to downgrade Greenhopper to 5.7.4... Given all the investigation we've performed over this issue, and some other similar tickets that came to our attention, we believe that the cause of these problems can be related to the latest Greenhopper versions. I suggest you to downgrade to GreenHopper 5.7.4 for the time being until we sorted out the root cause for this problem. To do that: 1. Backup JIRA 2. Shutdown JIRA 3. Backup JIRA database 4. Remove GreenHopper plugin from JIRA_HOME/plugins/installed-plugin directory. 5. Start JIRA

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

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 1m
                  1m
                  Remaining:
                  Remaining Estimate - 1m
                  1m
                  Logged:
                  Time Spent - Not Specified
                  Not Specified