Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence 5.8.4: ORA-00955 and "java.lang.RuntimeException: names do not exist" error messages

Peter Schneider March 21, 2018

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.

 

 

1 answer

1 accepted

1 vote
Answer accepted
AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 21, 2018

Hi Peter,

I have seen the error: 

ORA-00955: name is already used by an existing object

when Confluence's db user has the ability to see other databases in Oracle, especially other Atlassian application databases with the same table names. I understand that:

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.

Please double check the user setup and other causes on: ORA-00955: Name is Already Used by an Existing Object and Database Setup for Oracle, especially:

Do not grant the user the select any table permission. That permission can cause problems with other schemas. 

I look forward to hearing how it goes.

Thanks,

Ann

Peter Schneider March 21, 2018

Hi Ann,

 

thanks for your reply. I have checked the items indicated.

 

- re: DB setup

The DB user confluence67 only has roles CONNECT and RESOURCE, and has system privileges CREATE TABLE, CREATE SEQUENCE, CREATE VIEW, CREATE TRIGGER and UNLIMITED TABLESPACE. He has no privilege SELECT ANY TABLE, in fact, none of the "...ANY..." privileges at all. Furthemore, there exist no private or public synonyms pointing to objects in the other schemas. Additionally, I locked the old schema account confluence58 and also set the old tablespace confluence58 OFFLINE. So the new confluence67 schema user is clearly confined to his own objects, only.

- re: cause 3, pre-existing sequence

In fact, after the import, confluence67 has all the sequences that confluence58 had. These ones:

 

  1  select object_name from dba_objects
  2  where owner = 'CONFLUENCE67'
  3  and object_type = 'SEQUENCE'
  4* order by 1

OBJECT_NAME
------------------------------
AO_187CCC_SIDEBAR_LINK_ID_SEQ
AO_21D670_WHITELIST1050971807
AO_26DB7F_ENTITIES_1253824155
AO_26DB7F_ENTITIES_746820745
AO_38321B_CUSTOM_CO518521787
AO_42E351_HEALTH_CH1455927005
AO_54C900_CONTENT_B2086059265
AO_54C900_C_TEMPLAT776456439
AO_54C900_SPACE_BLU760748750
AO_5F3884_FEATURE_D1494598703
AO_5FB9D7_AOHIP_CHA1011653610
AO_5FB9D7_AOHIP_CHA1544183047
AO_6384AB_DISCOVERED_ID_SEQ
AO_6384AB_FEATURE_M675681913
AO_7CDE43_EVENT_ID_SEQ
AO_7CDE43_FILTER_PARAM_ID_SEQ
AO_7CDE43_NOTIFICAT2124428477
AO_7CDE43_NOTIFICATION_ID_SEQ
AO_7CDE43_RECIPIENT_ID_SEQ
AO_7CDE43_SERVER_CONFIG_ID_SEQ
AO_7CDE43_SERVER_PARAM_ID_SEQ
AO_88263F_HEALTH_CH2055344827
AO_88263F_PROPERTIES_ID_SEQ
AO_88263F_READ_NOTI1693092892
AO_92296B_AORECENTL203488401
AO_9412A1_AONOTIFIC1763171329
AO_9412A1_AOTASK_ID_SEQ
AO_9412A1_AOUSER_ID_SEQ
AO_9412A1_USER_APP_LINK_ID_SEQ
AO_950DC3_TC_DISABL722054506
AO_950DC3_TC_EVENTS168946694
AO_950DC3_TC_EVENTS1717033857
AO_950DC3_TC_EVENTS_ID_SEQ
AO_950DC3_TC_JIRA_R455228544
AO_950DC3_TC_REMIND944137475
AO_950DC3_TC_SUBCAL25515726
AO_950DC3_TC_SUBCAL325214310
AO_950DC3_TC_SUBCAL529465434
AO_950DC3_TC_SUBCAL747808553
AO_A0B856_WEB_HOOK_625253910
AO_B1DBB9_ACCEPTANCE_ID_SEQ
AO_B1DBB9_BOUNTY_ID_SEQ
AO_B1DBB9_VOTE_ID_SEQ
AO_BAF3AA_AOINLINE_56962253
AO_DC98AE_AOHELP_TIP_ID_SEQ
SEQ_JOURNAL_ENTRY_ID

46 rows selected.

 

In the log, I do not see the error ORA-00955 around an SQL statement trying to create a sequence. Logs look like this, without even showing the offending SQL statement:

 

2018-03-20 21:22:34,543 ERROR [scheduler_Worker-4] [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

    at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:54)
    at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory$1.doInTransaction(AbstractActiveObjectsFactory.java:91)
    at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory$1.doInTransaction(AbstractActiveObjectsFactory.java:85)
    at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25)
    at com.atlassian.sal.spring.component.SpringHostContextAccessor$1.doInTransaction(SpringHostContextAccessor.java:88)
    at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
    at com.atlassian.sal.spring.component.SpringHostContextAccessor.doInTransaction(SpringHostContextAccessor.java:82)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:134)
    at com.sun.proxy.$Proxy220.doInTransaction(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154)
    at com.sun.proxy.$Proxy220.doInTransaction(Unknown Source)
    at com.atlassian.sal.core.transaction.HostContextTransactionTemplate.execute(HostContextTransactionTemplate.java:21)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58)
    at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:56)
    at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:39)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.osgi.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:59)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at com.sun.proxy.$Proxy1158.execute(Unknown Source)
    at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory.create(AbstractActiveObjectsFactory.java:84)
    at com.atlassian.activeobjects.internal.DelegatingActiveObjectsFactory.create(DelegatingActiveObjectsFactory.java:40)
    at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:99)
    ... 6 more
Caused by: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object

    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
    at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
    at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
    at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:195)
    at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1036)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
    at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1845)
    at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1810)
    at oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:294)
    at com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:64)
    at net.java.ao.DatabaseProvider.executeUpdate(DatabaseProvider.java:2391)
    at net.java.ao.DatabaseProvider.executeUpdateForAction(DatabaseProvider.java:2461)
    at net.java.ao.DatabaseProvider.executeUpdatesForActions(DatabaseProvider.java:2424)
    at net.java.ao.schema.SchemaGenerator.migrate(SchemaGenerator.java:99)
    at net.java.ao.EntityManager.migrate(EntityManager.java:132)
    at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:50)
    ... 49 more

Peter Schneider March 21, 2018

Hi Ann,

thanks for your reply.

-re: DB setup:

New schema confluence67 only has roles CONNECT and RESOURCE, and system privileges CREATE TABLE, CREATE TRIGGER, CREATE SEQUENCE, CREATE VIEW and UNLIMITED TABLESPACE. None of the "...ANY..." privileges whatsoever, of course no SELECT ANY TABLE privilege. Also, there exist no public or private synonyms pointing to other Atlassian application schema objects, and additionally I locked the old confluence58 schema account and set the confluence58 tablespace offline. So confluence67 is clearly confined to his own objects, only.

-re: Sequences

After import, confluece67 has the same sequences as confluence58 had. These ones:

 

  1  select object_name from db
  2  where owner = 'CONFLUENCE6
  3  and object_type = 'SEQUENC
  4* order by 1

OBJECT_NAME
------------------------------
AO_187CCC_SIDEBAR_LINK_ID_SEQ
AO_21D670_WHITELIST1050971807
AO_26DB7F_ENTITIES_1253824155
AO_26DB7F_ENTITIES_746820745
AO_38321B_CUSTOM_CO518521787
AO_42E351_HEALTH_CH1455927005
AO_54C900_CONTENT_B2086059265
AO_54C900_C_TEMPLAT776456439
AO_54C900_SPACE_BLU760748750
AO_5F3884_FEATURE_D1494598703
AO_5FB9D7_AOHIP_CHA1011653610
AO_5FB9D7_AOHIP_CHA1544183047
AO_6384AB_DISCOVERED_ID_SEQ
AO_6384AB_FEATURE_M675681913
AO_7CDE43_EVENT_ID_SEQ
AO_7CDE43_FILTER_PARAM_ID_SEQ
AO_7CDE43_NOTIFICAT2124428477
AO_7CDE43_NOTIFICATION_ID_SEQ
AO_7CDE43_RECIPIENT_ID_SEQ
AO_7CDE43_SERVER_CONFIG_ID_SEQ
AO_7CDE43_SERVER_PARAM_ID_SEQ
AO_88263F_HEALTH_CH2055344827
AO_88263F_PROPERTIES_ID_SEQ
AO_88263F_READ_NOTI1693092892
AO_92296B_AORECENTL203488401
AO_9412A1_AONOTIFIC1763171329
AO_9412A1_AOTASK_ID_SEQ
AO_9412A1_AOUSER_ID_SEQ
AO_9412A1_USER_APP_LINK_ID_SEQ
AO_950DC3_TC_DISABL722054506
AO_950DC3_TC_EVENTS168946694
AO_950DC3_TC_EVENTS1717033857
AO_950DC3_TC_EVENTS_ID_SEQ
AO_950DC3_TC_JIRA_R455228544
AO_950DC3_TC_REMIND944137475
AO_950DC3_TC_SUBCAL25515726
AO_950DC3_TC_SUBCAL325214310
AO_950DC3_TC_SUBCAL529465434
AO_950DC3_TC_SUBCAL747808553
AO_A0B856_WEB_HOOK_625253910
AO_B1DBB9_ACCEPTANCE_ID_SEQ
AO_B1DBB9_BOUNTY_ID_SEQ
AO_B1DBB9_VOTE_ID_SEQ
AO_BAF3AA_AOINLINE_56962253
AO_DC98AE_AOHELP_TIP_ID_SEQ
SEQ_JOURNAL_ENTRY_ID

46 rows selected.

 

To further demonstrate that both schemas are identical after import:

 

  1  select owner, object_type, status, count(*)
  2  from dba_objects
  3  where owner like 'CONFLUENCE%'
  4  group by owner, object_type, status
  5* order by 1, 2

OWNER                OBJECT_TYPE         STATUS    COUNT(*)
-------------------- ------------------- ------- ----------
CONFLUENCE58         INDEX               VALID          392
CONFLUENCE58         LOB                 VALID           53
CONFLUENCE58         SEQUENCE            VALID           46
CONFLUENCE58         TABLE               VALID          108
CONFLUENCE58         TRIGGER             VALID           45
CONFLUENCE58         VIEW                VALID            1
CONFLUENCE67         INDEX               VALID          392
CONFLUENCE67         LOB                 VALID           53
CONFLUENCE67         SEQUENCE            VALID           46
CONFLUENCE67         TABLE               VALID          108
CONFLUENCE67         TRIGGER             VALID           45
CONFLUENCE67         VIEW                VALID            1

12 rows selected.


 

In the logs, I do not see the ORA-00955 error message around or near an SQL statement trying to create a sequence. In fact, the offending SQL is not visible at all. Log entries look like this:

 

2018-03-20 21:22:34,543 ERROR [scheduler_Worker-4] [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

    at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:54)
    at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory$1.doInTransaction(AbstractActiveObjectsFactory.java:91)
    at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory$1.doInTransaction(AbstractActiveObjectsFactory.java:85)
    at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25)
    at com.atlassian.sal.spring.component.SpringHostContextAccessor$1.doInTransaction(SpringHostContextAccessor.java:88)
    at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
    at com.atlassian.sal.spring.component.SpringHostContextAccessor.doInTransaction(SpringHostContextAccessor.java:82)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:134)
    at com.sun.proxy.$Proxy220.doInTransaction(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154)
    at com.sun.proxy.$Proxy220.doInTransaction(Unknown Source)
    at com.atlassian.sal.core.transaction.HostContextTransactionTemplate.execute(HostContextTransactionTemplate.java:21)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58)
    at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:56)
    at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:39)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.osgi.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:59)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at com.sun.proxy.$Proxy1158.execute(Unknown Source)
    at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory.create(AbstractActiveObjectsFactory.java:84)
    at com.atlassian.activeobjects.internal.DelegatingActiveObjectsFactory.create(DelegatingActiveObjectsFactory.java:40)
    at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:99)
    ... 6 more
Caused by: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object

    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
    at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
    at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
    at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:195)
    at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1036)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
    at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1845)
    at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1810)
    at oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:294)
    at com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:64)
    at net.java.ao.DatabaseProvider.executeUpdate(DatabaseProvider.java:2391)
    at net.java.ao.DatabaseProvider.executeUpdateForAction(DatabaseProvider.java:2461)
    at net.java.ao.DatabaseProvider.executeUpdatesForActions(DatabaseProvider.java:2424)
    at net.java.ao.schema.SchemaGenerator.migrate(SchemaGenerator.java:99)
    at net.java.ao.EntityManager.migrate(EntityManager.java:132)
    at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:50)
    ... 49 more
AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 21, 2018

Hi Peter,

I created a support request for you so we could take a closer look. Please watch for an email from our support portal.

Once the issue is resolved we can update this thread to let the Community know the root cause.

Thanks,

Ann

Peter Schneider March 23, 2018

The issue is resolved. After importing the DB schema data into the new schema, a view ALL_OBJECTS was created in the new schema which still queried against the old schema. I changed the view query to use the new schema, and then everything worked fine again.

 

Thanks

Peter

Daniel Alonso
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 3, 2019

Hey Peter, I'm facing the same issue, where exactly did you change the query? Did that view was created automatically?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events