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,

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

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.

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

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.

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...

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.

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

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

I can tell you I see a lot of Exceptions with PostgreSQL latly too. Im my case there are funny bugs like database-functions that are called but never created and attempts to drop database-objects that do not exists.
Something seems to be seriously broken since Jira 4.4.

2011-12-09 17:26:44,852 http-443-6 ERROR lfstad-swo 1041x21277x2 gf0x9a 10.167.16.21,10.170.98.138 /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml [net.java.ao.sql] Exception executing SQL update <DROP FUNCTION jira_443.AO_60DB71_ISSUERANKING_CUSTOM_FIELD_ID_onupdate() CASCADE>
org.postgresql.util.PSQLException: FEHLER: Funktion jira_443.ao_60db71_issueranking_custom_field_id_onupdate() existiert nicht

Thanks Gum Shoes...if I'm going to go to the trouble to migrate, I might as well go to the best supported database. Do you have a lot of backend customizations or something? Is that why you don't migrate to PostgreSQL?

In my 5 years of experience with Atlassian products I have experienced a handful of similar 'oops it does not work right with Oracle' issues.
These issues always get resolved eventually but they are not confidence inspiring because it clearly shows that the products were not tested using Oracle.

Every time such an issue comes up I log it with support using my commercial account and ask if Oracle support is going away; every time the answer is no.
I suspect that the devs prefer postgresql (I think that is what Atlassian runs its own servers on) and that Oracle is just a pain to work with so it becomes the red-headed step child.

I'm wondering if the SQL Server, PostreSQL, and MySQL implementations have these kinds of problems? Or are these problems unique to Oracle? I'd be willing to migrate to a different database if it worked better out of the box...

We are also haveing a problem with this upgrade. Looks like the support folks are not talking to each other...

It kind of depends on the time you submit and the timezone/location of the person who can answer the question. Either way, you will probably get some follow up question or need to attach something for them (e.g., logs), which will delay it again for days. You might get some generic answer saying they are working on it with no set timeframe for resolution. If I had to guess a ballpark time, I would say sometime after the holidays...

David

I too have problems with Oracle sequence creation. I have contacted https://support.atlassian.com and have been waiting for a solution for two business days. Can anyone tell me the expected service level on support tickets of this nature? How long do you generally have to wait?

Hi Jason,

In certain circumstances users who upgraded to an affected version will need to perform some manual recovery. Could you please contact https://support.atlassian.com and they can help you?

Thanks,
Shaun

Upgraded to JIRA 4.4.4 and GH 5.8.4 and still seeing:

JiraImportTaskExecutionThread-1 ERROR anonymous 728x55x1 1ohi4pq 10.175.40.29 /secure/SetupImport.jspa [net.java.ao.sql] Exception executing SQL update <CREATE SEQUENCE "AO_60DB71_RAPIDVIEW_ID_SEQ" INCREMENT BY 1 START WITH 1 NOMAXVALUE MINVALUE 1>
java.sql.SQLException: ORA-00955: name is already used by an existing object

Please upgrade to JIRA 4.4.4 and GreenHopper 5.8.4 to fix this issue

Please note that this problem is actually related to the Active Objects plug in used by GreenHopper. As such it will affect the 5.8.x series of GreenHopper when running on Jira less than 4.4.4. We are still testing Jira 4.4.4 but it should be ready soon.

Thanks,
Shaun

Thanks Laurent, updated to reflect this.

You should update the issue as this bug also appear for GH 5.8.3 (just tested)

Looks like I got it up and running again now with a workaround I got from https://support.atlassian.com. Thanks!

(Some minor tweaks was still needed for the workaround to work...)

There is not a fixed time frame at the moment though we would be expecting within the next two weeks.

What is the expected release of 4.4.4 (that would dictate whether it's worth the "technical time" to do this or just wait for the upgrade).

Hi All,

We now have a workaround fix process for this problem that affected users may wish to apply (before the release of Jira 4.4.4 which will include this fix).

The workaround is somewhat technical so we would prefer customers contact Support for details so they are available for additional assistance if needed. Please log an issue with https://support.atlassian.com

Thanks,
Shaun

Any updates on this issue? Any workarounds?

Hi. I just ran into this after upgrading Jira to 4.4.3 and Greenhopper 5.8.3

Should I revert back to 4.4.1 until they release this fix into the wild?

I am also interested in the status on this.

Dear All, I am new to this but i am having the same problem described above i would like to know when we can expect the fix to be rolled out.

Thank You
Rabih

Good to hear you have a fix. Yes, adequate testing this time would be appreciated.

Hi All,

We have developed a fix for this problem but it will require a Jira update. We are working on ensuring we get adequate test coverage for the fix before we roll it in to a new version of Jira. We will update this ticket again when more data is available.

Thanks,
Shaun

Hello,

Checking in on any updates on the workaround for this.

David

Hi All,

Just an update... we are still analyzing this problem and it looks to be a complex issue to resolve. We will likely need to release a new version of Jira and GH to resolve it. We will have more information next week and hope to provide a workaround at that time.

Thanks,
Shaun

The affected version for this ticket should change to incluse 5.8.2. Right now it says just 5.8.1.

Note that one of the other java modules had a customfield called Rank, so that was an issue for greenhopper. I suggest calling the customfield for greenhopper 5.8.2 RapidRank instead of Rank.

I set the Default ID values to be 0 and the rapid view create box pops up and allows me to start creating a rapid view. However, it gest to Select Kanaban and stops. There is something else I need to set a default value for I am sure. Anyway, I think this is the issue (no values in AO+60DB71* tables makes it all fail. Either add initial rows to the tables (not sure what to put in them) to get it going or set the default values as appropriate and let it add the first row.

Note that setting AO_60DB71_ISSUERANKING No NULL allowed the upgrade to complete, but ranking does not work after. All the AO_60DB71* tables are empty. We do have projects actively using Greenhopper prior to the upgrade to 5.8.2. Does one of the rules expect a value and increments the ID or something by 1? This will not work if there is no data (i.e., cannot increment NULL by 1).

Sorry for the confusion, there was a hole in our workflow which meant anyone could transition an issue from Selected to Resolve. This has now been fixed. We are still working on this issue.

I tried to upgrade on test server which uses MySQL. All works great. GH does many things during upgrade.
During upgrade GH creates new Rank field of Global Ranking type and migrate rank data in it. Then it renames old rank to Rank (old). Then searches in filters and dashboards for old Rank field (10002) and replace it with new one.

Not sure if this is something you want to try, but I connected to the database and found AO_60DB71_ISSUERANKING table and set the turned off the No NULL setting. This allowed the upgrade to complete. I suspect what is going on is there is a couple tables (this being one of them) that has this constraint, but the old greenhopper data has nothing to fill in for these tables. What I am saying here is merely speculation, and it may be way off. Anyway, allowing NULL did allow the upgrade to complete.

An anonymous user marked this ticket as "Won't Fix", so I don't think it's a statement on Atlassian's part that Oracle support is going away (we can pretty much assume that's not the case).

However, I do I hope Atlassian has a fix very soon since our Jira instance is now left in a half-upgraded state. This ticket's been open for a week now with little or no recourse for those of us with busted Jira instances now.

I want to emphatically echo the above comments. If the GreenHopper folks cannot at least offer a workaround for this issue, my company will begin to look for alternative tools. Oracle DB support is an absolute requirement. Very disappointing if this is not addressed.

Losing Oracle support would be devastating to our company as that is the database we support and bringing in another would be a major support issue.

I also don't understand why this is 'won't fix'.
JIRA is sold as supporting Oracle and GreenHopper is sold as a JIRA plugin so it must then also work with Oracle.
I know that over the years various Atlassian products have had similar issues with Oracle but they have always been resolved; if Oracle support is going away just say so.

Michael,

I see the status of Won't Fix for getting Jira 4.4.3, Oracle, and Greenhopper 5.8.2 working. We need this to work to upgrade to 4.4.3. What can we do to get this fixed? Why was the status set as Won't Fix?

Why is the resolution set to Won't Fix? We cannot use Jira 4.4.3 with Oracle and Greenhopper 5.8.2 if this is not fixed.

Something wrong with JIRA settings on this site. Anonymous user can resolve issues.

I see the same issue with Oracle with 4.4.3 and Greenhopper 5.8.2. Is this because they separated out the database stuff now into the dbconfig.xml and Greenhopper is not understanding where to find shcema stuff? Is there any status on this?

Same here with Oracle. All works well with MySQL.

See https://studio.atlassian.com/browse/AO-204