Hi,
I'm upgrading Confluence from 5.6.6 to 6.2.0. After upgrade while starting app.. I'm seeing below exception in logs., Could someone please help me.. i'm stuck right now.
2017-12-22 20:01:42,672 WARN [localhost-startStop-1] [jdbc.connections.internal.ConnectionProviderInitiator] instantiateC3p0Provider HHH000022: c3p0 properties were encountered, but the c3p0 provider class was not found on the classpath; these properties are going to be ignored.
2017-12-22 20:01:42,678 WARN [localhost-startStop-1] [hibernate.orm.connections.pooling] configure HHH10001002: Using Hibernate built-in connection pool (not for production use!)
2017-12-22 20:01:48,166 ERROR [localhost-startStop-1] [atlassian.confluence.plugin.PluginFrameworkContextListener] error Upgrade failed, application will not start: com.atlassian.config.ConfigurationException: Cannot update schema
com.atlassian.confluence.upgrade.UpgradeException: com.atlassian.config.ConfigurationException: Cannot update schema
at com.atlassian.confluence.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:133)
at com.atlassian.confluence.plugin.PluginFrameworkContextListener.launchUpgrades(PluginFrameworkContextListener.java:118)
at com.atlassian.confluence.plugin.PluginFrameworkContextListener.contextInitialized(PluginFrameworkContextListener.java:77)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
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.config.ConfigurationException: Cannot update schema
at bucket.core.persistence.hibernate.schema.SchemaHelper.validateSchemaUpdateIfNeeded(SchemaHelper.java:174)
at com.atlassian.confluence.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:119)
... 11 more
Caused by: org.hibernate.tool.schema.extract.spi.SchemaExtractionException: More than one table found in namespace (, ) : cwd_app_dir_group_mapping
at org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl.processGetTableResults(InformationExtractorJdbcDatabaseMetaDataImpl.java:371)
at org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl.getTable(InformationExtractorJdbcDatabaseMetaDataImpl.java:277)
at org.hibernate.tool.schema.internal.exec.ImprovedDatabaseInformationImpl.getTableInformation(ImprovedDatabaseInformationImpl.java:110)
at org.hibernate.tool.schema.internal.SchemaMigratorImpl.performMigration(SchemaMigratorImpl.java:251)
at org.hibernate.tool.schema.internal.SchemaMigratorImpl.doMigration(SchemaMigratorImpl.java:136)
at com.atlassian.confluence.impl.hibernate.ConfluenceHibernateSchemaManagementTool$3.doMigration(ConfluenceHibernateSchemaManagementTool.java:105)
at org.hibernate.tool.schema.internal.SchemaMigratorImpl.doMigration(SchemaMigratorImpl.java:109)
Hi Srikanth,
I understand an upgrade from Confluence 5.6.6 to Confluence 6.2 failed with the following error:
2017-12-22 20:01:48,166 ERROR [localhost-startStop-1] [atlassian.confluence.plugin.PluginFrameworkContextListener] error Upgrade failed, application will not start: com.atlassian.config.ConfigurationException: Cannot update schema
Caused by: org.hibernate.tool.schema.extract.spi.SchemaExtractionException: More than one table found in namespace (, ) : cwd_app_dir_group_mapping
(The WARN level errors you included are benign per c3p0 Class not Found on the Classpath and its Properties are Ignored)
If you are using an Oracle database, that error can be caused by the Oracle user having the select any table permission, or if the local all objects view is not set up as in this article: Step 3. Set up your Oracle user with schema-creation privileges
If you are not using an Oracle database, please let me know what database you are using. If the Oracle user was already set up as in the article I linked, please let me know that as well.
Thanks,
Ann
Hey, Found it later.. was using ojdbc6 .. after replacing with 8 it went through.. thanks for rly!
Sri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.