java.lang.reflect.InvocationTargetException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Unable to use changelogSchemaName/changelogCatalogName configuration parameters on Oracle DB. h3. Steps to reproduce: Testplan 1. # Configure Liquibase against Oracle DB instance, user A; # Set changelogSchemaName to B; # Launch update procedure; # Note that DATABASECHAGELOG* tables are created in A schema. Testplan 2. # Configure Liquibase against Oracle DB instance, user A; # Set changelogCatalogName to B; # Launch update procedure; # Note that DATABASECHAGELOG* tables are created in A schema. Testplan 3. # Perform steps outlined in Testplan 2. # Launch Liquibase again with the same configuration. # Notice an exception similar to this: {code} Error setting up or running Liquibase: liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE <changelogCatalogName>.DATABASECHANGELOGLOCK (ID NUMBER(10) NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): ORA-00955: name is already used by an existing object at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Error setting up or running Liquibase: liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE <changelogCatalogName>.DATABASECHANGELOGLOCK (ID NUMBER(10) NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): ORA-00955: name is already used by an existing object at org.liquibase.maven.plugins.AbstractLiquibaseMojo.execute(AbstractLiquibaseMojo.java:371) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: liquibase.exception.LockException: liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE <changelogCatalogName>.DATABASECHANGELOGLOCK (ID NUMBER(10) NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): ORA-00955: name is already used by an existing object at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:214) at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:153) at liquibase.Liquibase.update(Liquibase.java:182) at liquibase.Liquibase.update(Liquibase.java:174) at org.liquibase.maven.plugins.LiquibaseUpdate.doUpdate(LiquibaseUpdate.java:31) at org.liquibase.maven.plugins.AbstractLiquibaseUpdateMojo.performLiquibaseTask(AbstractLiquibaseUpdateMojo.java:24) at org.liquibase.maven.plugins.AbstractLiquibaseMojo.execute(AbstractLiquibaseMojo.java:367) ... 21 more Caused by: liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE <changelogCatalogName>.DATABASECHANGELOGLOCK (ID NUMBER(10) NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): ORA-00955: name is already used by an existing object at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:62) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:122) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:112) at liquibase.lockservice.StandardLockService.init(StandardLockService.java:88) at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:187) ... 27 more Caused by: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:30) at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:931) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1150) at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1792) at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1745) at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:334) at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:310) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:55) ... 31 more {code} h2. Code analysis showed that: h3. Oracle does not support schemas "in Liquibase's opinion". I.e. {{liquibase.database.core.OracleDatabase.supportsSchemas()}} always return {{false}}, hence {{liquibase.database.AbstractJdbcDatabase.getDefaultSchemaName()}} always return default catalog (usually <jdbc_connection_username>). h3. Code, which creates DATABASECHANGELOG/DATABASECHANGELOGLOCK tables also affected. {{liquibase.sqlgenerator.core.CreateDatabaseChangeLogLockTableGenerator.generateSql(CreateDatabaseChangeLogLockTableStatement, Database, SqlGeneratorChain)}} will create an SQL statement containing catalog only, whereas schema (set to <changelogSchemaName>) ignored by {{liquibase.database.AbstractJdbcDatabase.escapeObjectName(String, String, String, Class<? extends DatabaseObject>)}}. The same issue with {{liquibase.sqlgenerator.core.CreateDatabaseChangeLogTableGenerator.generateSql(CreateDatabaseChangeLogTableStatement, Database, SqlGeneratorChain)}}. h3. Note on DB metadata check when <changelogCatalogName> is set. In {{liquibase.snapshot.SnapshotGeneratorFactory.hasDatabaseChangeLogLockTable(Database)}} DATABASECHANGELOGLOCK table object recieves catalog = <changelogCatalogName>, schemaName = <jdbc_connection_username> (see note about {{AbstractJdbcDatabase.getDefaultSchemaName()}} above) upon creation. DB metadata loading code - {{liquibase.snapshot.JdbcDatabaseSnapshot.CachingDatabaseMetaData.getTables(String, String, String, String[])}} - called prior to the existance check, recieves catalogName = null, schemaName = <changelogCatalogName>, but eventually calls {{CatalogAndSchema catalogAndSchema = new CatalogAndSchema(catalogName, schemaName).customize(database);}}(JdbcDatabaseSnapshot.java:356, fastFetchQuery() method). customize(Database) method, in turn, calls {{liquibase.CatalogAndSchema.standardize(Database)}}, which nullifyes schema name: {code:title=CatalogAndSchema.java|borderStyle=solid} if (accordingTo.supportsSchemas()) { if (schemaName != null && schemaName.equalsIgnoreCase(accordingTo.getDefaultSchemaName())) { schemaName = null; } } else { schemaName = null; } {code} This effectively eliminates configured <changelogCatalogName> value and resets it to default schema (usually <jdbc_connection_username>). {{queryOracle(CatalogAndSchema, String)}} that called furhter creates a query of the form: {code:SQL} SELECT null as TABLE_CAT, a.OWNER as TABLE_SCHEM, a.TABLE_NAME as TABLE_NAME, 'TABLE' as TABLE_TYPE, c.COMMENTS as REMARKS from ALL_TABLES a join ALL_TAB_COMMENTS c on a.TABLE_NAME=c.table_name and a.owner=c.owner WHERE a.OWNER='<jdbc_connection_username>' AND a.TABLE_NAME not in (select mv.name from all_registered_mviews mv where mv.owner='<jdbc_connection_username>') {code} which will return information about tables from <jdbc_connection_username> schema only; table snapshot will retain this info and, hence, the DATABASECHANGELOGLOCK table object passed to {{liquibase.snapshot.SnapshotGeneratorFactory.has(DatabaseObject, Database)}} by {{liquibase.snapshot.SnapshotGeneratorFactory.hasDatabaseChangeLogLockTable(Database)}} will not be matched because schema names differ. Liquibase will decide that this table does not exist (even if it is not the case, and it existis within the default schema) and attempt to recreate a lock table.
    via by Alexander Kiselyov,
  • Unable to use changelogSchemaName/changelogCatalogName configuration parameters on Oracle DB. h3. Steps to reproduce: Testplan 1. # Configure Liquibase against Oracle DB instance, user A; # Set changelogSchemaName to B; # Launch update procedure; # Note that DATABASECHAGELOG* tables are created in A schema. Testplan 2. # Configure Liquibase against Oracle DB instance, user A; # Set changelogCatalogName to B; # Launch update procedure; # Note that DATABASECHAGELOG* tables are created in A schema. Testplan 3. # Perform steps outlined in Testplan 2. # Launch Liquibase again with the same configuration. # Notice an exception similar to this: {code} Error setting up or running Liquibase: liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE <changelogCatalogName>.DATABASECHANGELOGLOCK (ID NUMBER(10) NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): ORA-00955: name is already used by an existing object at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Error setting up or running Liquibase: liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE <changelogCatalogName>.DATABASECHANGELOGLOCK (ID NUMBER(10) NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): ORA-00955: name is already used by an existing object at org.liquibase.maven.plugins.AbstractLiquibaseMojo.execute(AbstractLiquibaseMojo.java:371) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: liquibase.exception.LockException: liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE <changelogCatalogName>.DATABASECHANGELOGLOCK (ID NUMBER(10) NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): ORA-00955: name is already used by an existing object at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:214) at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:153) at liquibase.Liquibase.update(Liquibase.java:182) at liquibase.Liquibase.update(Liquibase.java:174) at org.liquibase.maven.plugins.LiquibaseUpdate.doUpdate(LiquibaseUpdate.java:31) at org.liquibase.maven.plugins.AbstractLiquibaseUpdateMojo.performLiquibaseTask(AbstractLiquibaseUpdateMojo.java:24) at org.liquibase.maven.plugins.AbstractLiquibaseMojo.execute(AbstractLiquibaseMojo.java:367) ... 21 more Caused by: liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE <changelogCatalogName>.DATABASECHANGELOGLOCK (ID NUMBER(10) NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): ORA-00955: name is already used by an existing object at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:62) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:122) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:112) at liquibase.lockservice.StandardLockService.init(StandardLockService.java:88) at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:187) ... 27 more Caused by: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:30) at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:931) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1150) at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1792) at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1745) at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:334) at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:310) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:55) ... 31 more {code} h2. Code analysis showed that: h3. Oracle does not support schemas "in Liquibase's opinion". I.e. {{liquibase.database.core.OracleDatabase.supportsSchemas()}} always return {{false}}, hence {{liquibase.database.AbstractJdbcDatabase.getDefaultSchemaName()}} always return default catalog (usually <jdbc_connection_username>). h3. Code, which creates DATABASECHANGELOG/DATABASECHANGELOGLOCK tables also affected. {{liquibase.sqlgenerator.core.CreateDatabaseChangeLogLockTableGenerator.generateSql(CreateDatabaseChangeLogLockTableStatement, Database, SqlGeneratorChain)}} will create an SQL statement containing catalog only, whereas schema (set to <changelogSchemaName>) ignored by {{liquibase.database.AbstractJdbcDatabase.escapeObjectName(String, String, String, Class<? extends DatabaseObject>)}}. The same issue with {{liquibase.sqlgenerator.core.CreateDatabaseChangeLogTableGenerator.generateSql(CreateDatabaseChangeLogTableStatement, Database, SqlGeneratorChain)}}. h3. Note on DB metadata check when <changelogCatalogName> is set. In {{liquibase.snapshot.SnapshotGeneratorFactory.hasDatabaseChangeLogLockTable(Database)}} DATABASECHANGELOGLOCK table object recieves catalog = <changelogCatalogName>, schemaName = <jdbc_connection_username> (see note about {{AbstractJdbcDatabase.getDefaultSchemaName()}} above) upon creation. DB metadata loading code - {{liquibase.snapshot.JdbcDatabaseSnapshot.CachingDatabaseMetaData.getTables(String, String, String, String[])}} - called prior to the existance check, recieves catalogName = null, schemaName = <changelogCatalogName>, but eventually calls {{CatalogAndSchema catalogAndSchema = new CatalogAndSchema(catalogName, schemaName).customize(database);}}(JdbcDatabaseSnapshot.java:356, fastFetchQuery() method). customize(Database) method, in turn, calls {{liquibase.CatalogAndSchema.standardize(Database)}}, which nullifyes schema name: {code:title=CatalogAndSchema.java|borderStyle=solid} if (accordingTo.supportsSchemas()) { if (schemaName != null && schemaName.equalsIgnoreCase(accordingTo.getDefaultSchemaName())) { schemaName = null; } } else { schemaName = null; } {code} This effectively eliminates configured <changelogCatalogName> value and resets it to default schema (usually <jdbc_connection_username>). {{queryOracle(CatalogAndSchema, String)}} that called furhter creates a query of the form: {code:SQL} SELECT null as TABLE_CAT, a.OWNER as TABLE_SCHEM, a.TABLE_NAME as TABLE_NAME, 'TABLE' as TABLE_TYPE, c.COMMENTS as REMARKS from ALL_TABLES a join ALL_TAB_COMMENTS c on a.TABLE_NAME=c.table_name and a.owner=c.owner WHERE a.OWNER='<jdbc_connection_username>' AND a.TABLE_NAME not in (select mv.name from all_registered_mviews mv where mv.owner='<jdbc_connection_username>') {code} which will return information about tables from <jdbc_connection_username> schema only; table snapshot will retain this info and, hence, the DATABASECHANGELOGLOCK table object passed to {{liquibase.snapshot.SnapshotGeneratorFactory.has(DatabaseObject, Database)}} by {{liquibase.snapshot.SnapshotGeneratorFactory.hasDatabaseChangeLogLockTable(Database)}} will not be matched because schema names differ. Liquibase will decide that this table does not exist (even if it is not the case, and it existis within the default schema) and attempt to recreate a lock table.
    via by Alexander Kiselyov,
  • jpaProperties.put("javax.persistence.schema-generation.database.action", "none"); Since 5.2.3, hibernate ignore this "none" value and try to create tables. Hibernate 5.2.3 find my jpa property and drop and create database schema if i set "drop-and-create" value. jpaProperties.put("javax.persistence.schema-generation.database.action", "drop-and-create"); *Logs / hibernate 5.2.3 :* 2017-04-17 16:51:10.780 INFO 6267 --- [ main] org.hibernate.Version : HHH000412: Hibernate Core {5.2.3.Final} 2017-04-17 16:51:10.780 INFO 6267 --- [ main] org.hibernate.cfg.Environment : HHH000206: hibernate.properties not found 2017-04-17 16:51:10.781 INFO 6267 --- [ main] org.hibernate.cfg.Environment : HHH000021: Bytecode provider name : javassist 2017-04-17 16:51:10.809 INFO 6267 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.0.1.Final} 2017-04-17 16:51:36.283 INFO 6267 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect Hibernate: create table Civilite (id number(10,0) not null, libelleCourt varchar2(255 char) not null, libelleLong varchar2(255 char) not null, primary key (id)) 2017-04-17 16:51:36.783 WARN 6267 --- [ main] o.h.t.s.i.ExceptionHandlerLoggedImpl : GenerationTarget encountered exception accepting command : Error executing DDL via JDBC Statement org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL via JDBC Statement at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:67) ~[hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlString(AbstractSchemaMigrator.java:524) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlStrings(AbstractSchemaMigrator.java:470) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.createTable(AbstractSchemaMigrator.java:273) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.tool.schema.internal.GroupedSchemaMigratorImpl.performTablesMigration(GroupedSchemaMigratorImpl.java:71) ~[hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.performMigration(AbstractSchemaMigrator.java:203) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration(AbstractSchemaMigrator.java:110) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:177) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:66) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:309) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:493) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:878) [hibernate-core-5.2.3.Final.jar:5.2.3.Final] at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:60) [spring-orm-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:353) [spring-orm-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:370) [spring-orm-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:359) [spring-orm-4.3.7.RELEASE.jar:4.3.7.RELEASE] at com.renaissance.referentiel.config.ReferentielPersistenceConfig.entityManagerFactory1(ReferentielPersistenceConfig.java:111) [classes/:na] at com.renaissance.referentiel.config.ReferentielPersistenceConfig$$EnhancerBySpringCGLIB$$6de1023e.CGLIB$entityManagerFactory1$1(<generated>) [classes/:na] at com.renaissance.referentiel.config.ReferentielPersistenceConfig$$EnhancerBySpringCGLIB$$6de1023e$$FastClassBySpringCGLIB$$8c219831.invoke(<generated>) [classes/:na] at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) [spring-core-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) [spring-context-4.3.7.RELEASE.jar:4.3.7.RELEASE] at com.renaissance.referentiel.config.ReferentielPersistenceConfig$$EnhancerBySpringCGLIB$$6de1023e.entityManagerFactory1(<generated>) [classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_102] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_102] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_102] at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_102] at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1173) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1067) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) [spring-beans-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:866) [spring-context-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:542) [spring-context-4.3.7.RELEASE.jar:4.3.7.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:737) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:370) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:314) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1162) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1151) [spring-boot-1.5.2.RELEASE.jar:1.5.2.RELEASE] at com.renaissance.referentiel.config.ReferentielPersistenceConfig.main(ReferentielPersistenceConfig.java:130) [classes/:na] Caused by: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:195) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1036) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1916) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1878) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.4.0] at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:54) ~[hibernate-core-5.2.3.Final.jar:5.2.3.Final] ... 44 common frames omitted *Success logs hibernate 5.2.2 :* 2017-04-17 17:23:23.903 INFO 6394 --- [ main] org.hibernate.Version : HHH000412: Hibernate Core {5.2.2.Final} 2017-04-17 17:23:23.904 INFO 6394 --- [ main] org.hibernate.cfg.Environment : HHH000206: hibernate.properties not found 2017-04-17 17:23:23.907 INFO 6394 --- [ main] org.hibernate.cfg.Environment : HHH000021: Bytecode provider name : javassist 2017-04-17 17:23:23.946 INFO 6394 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.0.1.Final} 2017-04-17 17:23:49.548 INFO 6394 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect 2017-04-17 17:23:50.129 INFO 6394 --- [ main] o.h.h.i.QueryTranslatorFactoryInitiator : HHH000397: Using ASTQueryTranslatorFactory 2017-04-17 17:23:50.209 INFO 6394 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'PERSISTENCE_UNIT_REFERENTIEL'
    via by jyl1999,
  • OER with problems
    via by 875617,
  • Hibernate - Unable to execute command
    via Stack Overflow by Maven Maverick
    ,
  • OAM 11g Setup issues!!
    via by User21776251,
    • java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at oracle.sysman.assistants.rcu.backend.action.ActionThread.run(JavaAction.java:510) at java.lang.Thread.run(Thread.java:662) Caused by: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91) at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:183) at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:942) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222) at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1770) at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1739) at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:299) at oracle.ias.version.SchemaVersion.createRegistryTable(SchemaVersion.java:883) at oracle.ias.version.SchemaVersionUtil.utilCreateRegistryTable(SchemaVersionUtil.java:203) ... 6 more

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    540 more bugmates