-
Bug
-
Resolution: Fixed
-
Low
-
None
-
5.6.5
-
javaVersion = 1.8.0_74
javaVendor = Oracle CorporationoperatingSystem = Linux 3.10.0-327.10.1.el7.x86_64
Database:
- name:Oracle
- version:Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options - minor version:1
- major version:12
Driver: - name:Oracle JDBC driver
- version:12.1.0.2.0
javaVersion = 1.8.0_74 javaVendor = Oracle Corporation operatingSystem = Linux 3.10.0-327.10.1.el7.x86_64 Database: name:Oracle version:Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options minor version:1 major version:12 Driver: name:Oracle JDBC driver version:12.1.0.2.0
During the migration of Confluence from a server to another server I faced the following errors, and managed to resolve them dropping a table and a sequence.
Migration process applied
- export full XML backup from source installation + data directory
- install confluence on new server
- import source backup in new confluence using normal import tool
Error / Issue description
- After migrating, no plugin would not update (the "update" box is shown and either the progress bar would get stuck or finish correctly, but after a full Confluence stop/start it would show that the plugin is still in the same version).
- In the log, I identified 2 oracle errors : ORA-01400 (regarding the table) and ORA-00955 (regarding the sequence associated to this table).
- The table identified by ORA-01400 was empty.
Solution applied
- Look in the logs and identify the Table and it's Sequence (look for ORA-00955 error for the Sequence number) .
- Stop confluence
- Drop the culprit table & sequence :
select * from AO_6384AB_FEATURE_METADATA_AO DROP TABLE AO_6384AB_FEATURE_METADATA_AO; DROP SEQUENCE AO_6384AB_FEATURE_M675681913; COMMIT;
- Start confluence
- Check :
- if logs still show the same error
- if Confluence filled correctly the table after the restart
- if plugins update correctly
Error logs
ERROR : ORA-01400
The culprit table is empty and needs to be reconstructed.
2016-03-02 11:25:07,717 ERROR [localhost-startStop-1] [atlassian.event.internal.AsynchronousAbleEventDispatcher] run There was an exception thrown trying to dispatch event [com.atlassian.config.lifecycle.events.ApplicationStartedEvent@407a742d] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.confluence.plugins.featurediscovery.PluginModuleEventListener.onApplicationStart(com.atlassian.config.lifecycle.events.ApplicationStartedEvent), listener=com.atlassian.confluence.plugins.featurediscovery.PluginModuleEventListener@1cc7b1ba}]
java.lang.RuntimeException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:Oracle
- version:Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
- minor version:1
- major version:12
Driver:
- name:Oracle JDBC driver
- version:12.1.0.2.0
java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("CONFPROD"."AO_6384AB_FEATURE_METADATA_AO"."ID")
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:54)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:48)
at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:107)
at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:160)
at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:79)
at com.atlassian.confluence.event.TimingEventPublisher.publish(TimingEventPublisher.java:73)
at com.atlassian.config.lifecycle.DefaultLifecycleManager.startUp(DefaultLifecycleManager.java:43)
at com.atlassian.config.lifecycle.LifecycleServletContextListener.contextInitialized(LifecycleServletContextListener.java:17)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4973)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5467)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
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:
And the sequence error :
2016-03-03 09:50:30,209 ERROR [active-objects-init-system tenant-0] [net.java.ao.sql] handleUpdateError Exception executing SQL update <CREATE SEQUENCE "AO_6384AB_FEATURE_M675681913" INCREMENT BY 1 START WITH 1 NOMAXVALUE MINVALUE 1> java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object
References
this solution was inspired by the following 2 pages :
- https://confluence.atlassian.com/confkb/unable-to-install-add-ons-in-upm-due-to-duplicate-key-value-in-ao_6384ab_feature_metadata-table-741999240.html
==> confirmed that I could "safely" delete this table.
- https://confluence.atlassian.com/confkb/comments-and-likes-fail-with-internal-server-error-319390100.html
==> confirmed that I could "safely" delete this table, and shown that the "Sequence" also needed to be dropped.
[CONFSERVER-40983] ORA-01400 and/or ORA-00955 : problem with Confluence plugins tables during migration
Hello Minh Tran,
as explained in the ticket, we managed to bypass this issue, so I raised it for informative purpose so that I or someone else facing it again could use the trick.
There is probably an underlying bug somewhere, but that's not on my side anymore 
Thanks for your answers.
Dear corentin.mehat404000523,
Thanks for raising this issue. I believe this is something that our support team will be able to help you with.
Could I ask that you create a support ticket on https://support.atlassian.com?
Once you've done this one of our support engineers will be in touch to work with you in resolving this problem.
Regards,
Minh Tran
Confluence Bugmaster
Atlassian
This is still an issue. We are using Oracle 12c, Java 1.8.0_66, Ubuntu 14.04 LTS and migrating from 5.6.4 to 5.10.3. We are receiving error like the one in this issue. Also my only path to upgrade was to migrate using the XML backup. The restore of the backup corrupted the wiki metadata. Hundreds of record were listed with Anonymoous authors or last updates by Anonymous. The fix is to manually update onthe database and restart Confluence. Not only is this a slow process but changing data records directly in the DB is not usually a recommended practice by Atlassian. I have added comments to https://jira.atlassian.com/browse/CONF-34177 on the corruption issue but it appears Atlassian has let it sit for a number of years.