We are in the process of upgrading our Atlassian applications:
- Jira 6.4.7 to 7.8.0
- Confluence 5.8.4 to 6.7.2
- Fisheye 3.8.1 to 4.5.2
All reside in an Oracle 11.2.0.4 database, in users/schemas jira64, confluence58 and fisheye38, respectively. In the past, we have performed upgrades by exporting/importing with Oracle Data Pump into a new schema dedicated to that release, and this has worked well.
For this upgrade we have created schemas jira78, confluence67 and fisheye45, exported/imported from the older (current in use) version schemas, changed DB connect setup for the applications. As the schema data is identical, the expectation was that all apps work in their new schemas, and to be able to then perform the upgrade. The still existing old schemas would then be a fallback, if anything should go wrong.
Now, Jira and Fisheye work without problem in the new schema, however Confluence is having problems. The Space directory navigation menus don't work any more, and the team calendar is not displayed anymore. The confluence log file exhibits two kinds of error stack traces (lots of them):
First,
2018-03-20 12:50:00,076 ERROR [team-calendars-worker-4] [extra.calendar3.util.DefaultAsynchronousTaskExecutor] call Exception happens on task execution:
java.lang.RuntimeException: names do not exist: (AO_950DC3_TC_EVENTS, )
although this AO table exists in the DB, and second,
2018-03-20 13:22:34,538 ERROR [scheduler_Worker-10] [org.quartz.core.JobRunShell] run Job pluginSchedulerJobGroup.com.atlassian.support.healthcheck.scheduler.HealthCheckSchedulerImpl:job threw an unhandled Exception:
com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.support.healthcheck.support-healthcheck-plugin]
at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:105)
at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:92)
at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:42)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:Oracle
- version:Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
- minor version:2
- major version:11
Driver:
- name:Oracle JDBC driver
- version:11.2.0.4.0
java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object
I can attach or send full log, if necessary (it's too long to post it here)
Now if old Confluence 5.8 is not even running properly in the new schema confluence67 designated for the upgrade, I see no sense in continuing with the upgrade process. What might be the reason for this error messages? What can be done? I thought that it should be completely transparent to the application inside which schema it runs.
New schemas are exact copies of the old ones, all DB privileges, roles, default roles and object count after the import are exactly the same.
