Upgrade to 4.3.4 with Oracle

Question

I am trying to upgrade from JIRA 4.2.4 to 4.3.4 on tomcat 6 so that my LDAP authenticated users can integrate with Active Directory. I use an Oracle 10.2 database and have followed the instructions for upgrading to 4.3.4.

My problem is that my users do not get converted to Active Directory users. In the JIRA user browser they are all listed as "JIRA Internal Directory".

This is what I have tried:

* cp /usr/local/jira/4.2.4 /usr/local/jira/4.3.4
* backup database
* set jira.home in jira.properties
* build and deploy war

After that I realised that I needed the osuser.xml file for it to upgrade the LDAP-authenticated users to full AD users, so I stopped tomcat, replaced jira.home with a fresh copy from the old version, restored the database and started tomcat again. It seemed to do the upgrade again, except for the users (again).

There are definitely problems with the way that JIRA interacts with Oracle, and I think that might be some part of the problem (see my bug report at https://jira.atlassian.com/browse/JRA-25132).

Has anyone succeeded in upgrading using Oracle or perhaps have a comment that could help me transfer my users to Active Directory users?

Fabrice Porcher · Answer

How do you backup database ? and how to you restore the database ? schema or tables only ?

If you restore only tables, maybe the Crowd table CWD_* haven't be dropped

Drop all tables and restore again the JIRA 4.2.x data, look if you have CWD_* tables. You shoudln't

Then restart upgrade

Miles Jordan1 · Answer

My logs almost contain the same, but with a bit more that says:

2011-08-01 17:56:29,645 main INFO      [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Converting Users and Groups to new structure for Crowd Embedded.

2011-08-01 17:56:29,667 main WARN      [jira.upgrade.tasks.UpgradeTask_Build602] The crowd embedded tables already contain data.  No conversion will be performed.

I don't understand how the embedded directory can already have content if it's a new install. Is there anything from my old setup that could affect it? I've only ever had LDAP & an internal admin.

Fabrice Porcher · Answer

How was set your authentifcation in Jira 4.2.x ? Based on third party authentificator ? or based on native Jira with an customized OSUSER.XML ?

In the first case, you must create the OSUSER.XML which works with JIRA 4.2.x.

During the migration, you should have something like in log (catalina.out) :

2011-07-11 17:42:23,457 http-8080-1 INFO anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [jira.upgrade.tasks.UpgradeTask_Build601] LDAP directory detected in osuser.xml
2011-07-11 17:42:23,457 http-8080-1 INFO anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [jira.upgrade.tasks.UpgradeTask_Build601] Migrating a valid User Directory configuration found in osuser.xml
2011-07-11 17:42:23,497 http-8080-1 WARN anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [jira.upgrade.tasks.UpgradeTask_Build601] Added migrated directory to JIRA: 'JIRA delegating internal directory'.
2011-07-11 17:42:23,854 http-8080-1 INFO anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrate User Directory configuration' succeeded
2011-07-11 17:42:23,854 http-8080-1 INFO anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 601
2011-07-11 17:42:23,858 http-8080-1 INFO anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Converting Users and Groups to new structure for Crowd Embedded.
2011-07-11 17:44:53,536 http-8080-1 INFO anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Converting Users and Groups to new structure for Crowd Embedded.' succeeded
2011-07-11 17:44:53,536 http-8080-1 INFO anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 602
2011-07-11 17:44:53,543 http-8080-1 INFO anonymous 1033x6x1 1g2rsc9 10.80.110.9 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Synchronising remote user directories and reindexing all data in JIRA.

Then you shoudl have 2 user directory

an user directory named JIRA Delegated Authentication Directory with type Generic Directory Server which contains all users kwown in LDAP during the migration
    an user directory named JIRA Internal Directory with type Internal which contains the rest of the users.