liquibase.exception.DatabaseException: Error executing SQL select user_name(): Incorrect syntax near the keyword 'select'.

JIRA | Consultant Leon | 5 months ago
  1. 0

    This method uses a Call statement, which is not supported for sybase when executing select user_name() , Sybase requires a prepared statement to be used here. Call statement should only be used to call a stored procedure, not to run a regular 'select' This page put me on the right track: https://sourceforge.net/p/jtds/discussion/104389/thread/102edfcd/ protected String getConnectionSchemaName() { if (connection == null || connection instanceof OfflineConnection) { return null; } try { String currentSchemaStatement = getConnectionSchemaNameCallStatement(); return ExecutorService.getInstance().getExecutor(this). queryForObject(new RawCallStatement(currentSchemaStatement), String.class); } catch (Exception e) { LogFactory.getLogger().info("Error getting default schema", e); } return null; } I just ran this in the debugger and arrived at line: public Object query(final SqlStatement sql, final ResultSetExtractor rse, final List<SqlVisitor> sqlVisitors) throws DatabaseException { if (sql instanceof CallableSqlStatement) { return execute(new QueryCallableStatementCallback(sql, rse), sqlVisitors); } return execute(new QueryStatementCallback(sql, rse, sqlVisitors), sqlVisitors); } As it's instanceof CallableSqlStatement it executes the QueryCallableStatementCallback which throws exception as per below. When I evaluate the execute QueryStatementCallback it succeeds and returns 'dbo' as expected! Error getting default schema {liquibase:133} liquibase.exception.DatabaseException: Error executing SQL select user_name(): Incorrect syntax near the keyword 'select'. at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:88) at liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:117) at liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:128) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:136) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:151) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:146) at liquibase.database.AbstractJdbcDatabase.getConnectionSchemaName(AbstractJdbcDatabase.java:324) at liquibase.database.AbstractJdbcDatabase.getDefaultSchemaName(AbstractJdbcDatabase.java:305) at liquibase.database.AbstractJdbcDatabase.toString(AbstractJdbcDatabase.java:881) at liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:117) at liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:128) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:136) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:151) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:146) at liquibase.database.AbstractJdbcDatabase.getConnectionSchemaName(AbstractJdbcDatabase.java:324) at liquibase.database.AbstractJdbcDatabase.getDefaultSchemaName(AbstractJdbcDatabase.java:305) at liquibase.changelog.ChangeLogParameters.<init>(ChangeLogParameters.java:54) at liquibase.Liquibase.<init>(Liquibase.java:104)

    JIRA | 5 months ago | Consultant Leon
    liquibase.exception.DatabaseException: Error executing SQL select user_name(): Incorrect syntax near the keyword 'select'.
  2. 0

    When running update in version 3.3.0+ there is an exception: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: Error executing SQL SELECT CAST(value as varchar(max)) as REMARKS FROM sys.extended_properties WHERE name='MS_Description' AND major_id = OBJECT_ID('DATABASECHANGELOG') AND minor_id = COLUMNPROPERTY(major_id, 'ID', 'ColumnId'): Line 2: Incorrect syntax near 'max'. at liquibase.snapshot.jvm.ColumnSnapshotGenerator.snapshotObject(ColumnSnapshotGenerator.java:69) at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:60) at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:50) at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:163) at liquibase.snapshot.DatabaseSnapshot.replaceObject(DatabaseSnapshot.java:241) at liquibase.snapshot.DatabaseSnapshot.includeNestedObjects(DatabaseSnapshot.java:195) at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:177) at liquibase.snapshot.DatabaseSnapshot.init(DatabaseSnapshot.java:60) at liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:37) at liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:25) at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:126) at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:134) at liquibase.snapshot.SnapshotGeneratorFactory.getDatabaseChangeLogTable(SnapshotGeneratorFactory.java:141) at liquibase.changelog.StandardChangeLogHistoryService.init(StandardChangeLogHistoryService.java:88) The update proccess will not continue after this. It is the hardcoded SQL in ColumnSnapshotGenerator for mssql instances of db that is the issue. MS SQL 2000 does not support the usage of 'max' when specifying size of data type. Also the table/view sys.extended_properties does not exist. See CORE-2191 for same issue of non-existent table/view.

    JIRA | 2 years ago | David Björklund
    liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: Error executing SQL SELECT CAST(value as varchar(max)) as REMARKS FROM sys.extended_properties WHERE name='MS_Description' AND major_id = OBJECT_ID('DATABASECHANGELOG') AND minor_id = COLUMNPROPERTY(major_id, 'ID', 'ColumnId'): Line 2: Incorrect syntax near 'max'.
  3. 0

    I have a Liquibase 2.x style change set with the following configuration: {code} <renameColumn tableName="my_table" oldColumnName="my_column_old" newColumnName="my_column_new" columnDataType="text"/> {code} This change set worked properly against MySQL using Liquibase 2.x. Running this change set against a MySQL database using Liquibase 3.x, I encounter the following error: {code} [INFO] ChangeSet schema/my.changelog.xml::my-changeset::jduke ran successfully in 32ms [ERROR] Change Set my.changelog.xml::my-changeset::jduke failed. Error: Error executing SQL ALTER TABLE my_database.my_table CHANGE my_column_old my_column_new clob: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'clob' at line 1 liquibase.exception.DatabaseException: Error executing SQL ALTER TABLE my_database.my_table CHANGE my_column_old my_column_new clob: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'clob' at line 1 at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:56) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:98) at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.java:1341) at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1325) at liquibase.changelog.ChangeSet.execute(ChangeSet.java:343) at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:28) at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58) at liquibase.Liquibase.update(Liquibase.java:135) {code} It seems that Liquibase is incorrectly mapping the 'text' data type to 'clob', when it should be using 'text' for MySQL, as it did in 2.x. I have verified I am using a MySQLDatabase object. Is this a bug, or am I missing something?

    JIRA | 3 years ago | Jason Duke
    liquibase.exception.DatabaseException: Error executing SQL ALTER TABLE my_database.my_table CHANGE my_column_old my_column_new clob: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'clob' at line 1
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    During a deployment of 2.5.0 at Sinclair, the SSP deployment failed with the following error in the log {noformat} Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in ServletContext resource [/WEB-INF/spring/app-config.xml]: Invocation of init method failed; nested exception is liquibase.exception.MigrationFailedException: Migration failed for change set org/jasig/ssp/database/changesets/000130.xml::create mv directory_person view and pop msql::jim.stanley: Reason: liquibase.exception.DatabaseException: Error executing SQL SELECT * INTO dbo.mv_directory_person FROM dbo.v_directory_person;: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.: Caused By: Error executing SQL SELECT * INTO dbo.mv_directory_person FROM dbo.v_directory_person;: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.: Caused By: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1512) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:296) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:293) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:286) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:912) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:855) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:770) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:489) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] ... 65 common frames omitted Caused by: liquibase.exception.MigrationFailedException: Migration failed for change set org/jasig/ssp/database/changesets/000130.xml::create mv directory_person view and pop msql::jim.stanley: Reason: liquibase.exception.DatabaseException: Error executing SQL SELECT * INTO dbo.mv_directory_person FROM dbo.v_directory_person;: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.: Caused By: Error executing SQL SELECT * INTO dbo.mv_directory_person FROM dbo.v_directory_person;: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.: Caused By: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. at liquibase.changelog.ChangeSet.execute(ChangeSet.java:347) ~[liquibase-core-2.0.3.jar:na] at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:27) ~[liquibase-core-2.0.3.jar:na] at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58) ~[liquibase-core-2.0.3.jar:na] at liquibase.Liquibase.update(Liquibase.java:113) ~[liquibase-core-2.0.3.jar:na] at liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:244) ~[liquibase-core-2.0.3.jar:na] at org.jasig.ssp.util.liquibase.ExtendedSpringLiquibase.afterPropertiesSet(ExtendedSpringLiquibase.java:67) ~[ExtendedSpringLiquibase.class:na] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1571) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1509) ~[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE] ... 77 common frames omitted Caused by: liquibase.exception.DatabaseException: Error executing SQL SELECT * INTO dbo.mv_directory_person FROM dbo.v_directory_person;: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:62) ~[liquibase-core-2.0.3.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:104) ~[liquibase-core-2.0.3.jar:na] at liquibase.database.AbstractDatabase.execute(AbstractDatabase.java:1075) ~[liquibase-core-2.0.3.jar:na] at liquibase.database.AbstractDatabase.executeStatements(AbstractDatabase.java:1059) ~[liquibase-core-2.0.3.jar:na] at liquibase.changelog.ChangeSet.execute(ChangeSet.java:317) ~[liquibase-core-2.0.3.jar:na] ... 84 common frames omitted Caused by: java.sql.SQLException: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368) ~[jtds-1.2.4.jar:1.2.4] at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820) ~[jtds-1.2.4.jar:1.2.4] at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258) ~[jtds-1.2.4.jar:1.2.4] at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632) ~[jtds-1.2.4.jar:1.2.4] at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584) ~[jtds-1.2.4.jar:1.2.4] at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546) ~[jtds-1.2.4.jar:1.2.4] at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723) ~[jtds-1.2.4.jar:1.2.4] at net.sourceforge.jtds.jdbc.JtdsStatement.execute(JtdsStatement.java:1160) ~[jtds-1.2.4.jar:1.2.4] at liquibase.executor.jvm.JdbcExecutor$1ExecuteStatementCallback.doInStatement(JdbcExecutor.java:92) ~[liquibase-core-2.0.3.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:55) ~[liquibase-core-2.0.3.jar:na] ... 88 common frames omitted {noformat}

    Apereo Issues | 2 years ago | Jason Elwood
    liquibase.exception.DatabaseException: Error executing SQL SELECT * INTO dbo.mv_directory_person FROM dbo.v_directory_person;: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.: Caused By: Error executing SQL SELECT * INTO dbo.mv_directory_person FROM dbo.v_directory_person;: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.: Caused By: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
  6. 0

    This XML no longer works (is "condition" now treated as a keyword and quoted???): <update tableName="mytablename"> <column name="condition" valueNumeric="7"/> <where>condition = 52</where> </update> Error: Error executing SQL UPDATE bingo_jackpot_condition_map SET "condition" = 7 WHERE condition = 52: "condition" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=3.52.95 liquibase.exception.DatabaseException: Error executing SQL UPDATE bingo_jackpot_condition_map SET "condition" = 7 WHERE condition = 52: "condition" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=3.52.95 at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:61) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:106) at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.java:1189) at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1172) at liquibase.changelog.ChangeSet.execute(ChangeSet.java:352) at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:40) at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:64) at liquibase.Liquibase.update(Liquibase.java:202) at liquibase.Liquibase.update(Liquibase.java:181) 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:377) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) 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:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: com.ibm.db2.jcc.a.nn: "condition" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=3.52.95 at com.ibm.db2.jcc.a.ad.a(ad.java:666) at com.ibm.db2.jcc.a.ad.a(ad.java:60) at com.ibm.db2.jcc.a.ad.a(ad.java:127) at com.ibm.db2.jcc.a.rl.c(rl.java:2424) at com.ibm.db2.jcc.a.rl.d(rl.java:2401) at com.ibm.db2.jcc.a.rl.b(rl.java:1842) at com.ibm.db2.jcc.t4.db.h(db.java:219) at com.ibm.db2.jcc.t4.db.b(db.java:45) at com.ibm.db2.jcc.t4.t.b(t.java:38) at com.ibm.db2.jcc.t4.sb.g(sb.java:120) at com.ibm.db2.jcc.a.rl.X(rl.java:1837) at com.ibm.db2.jcc.a.rl.a(rl.java:2777) at com.ibm.db2.jcc.a.rl.e(rl.java:946) at com.ibm.db2.jcc.a.rl.execute(rl.java:930) at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:294) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:54) ... 32 more

    JIRA | 3 years ago | Alex Colins
    liquibase.exception.DatabaseException: Error executing SQL UPDATE bingo_jackpot_condition_map SET "condition" = 7 WHERE condition = 52: "condition" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=3.52.95

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. liquibase.exception.DatabaseException

      Error executing SQL select user_name(): Incorrect syntax near the keyword 'select'.

      at liquibase.executor.jvm.JdbcExecutor.execute()
    2. Liquibase Core
      Liquibase.<init>
      1. liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:88)
      2. liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:117)
      3. liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:128)
      4. liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:136)
      5. liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:151)
      6. liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:146)
      7. liquibase.database.AbstractJdbcDatabase.getConnectionSchemaName(AbstractJdbcDatabase.java:324)
      8. liquibase.database.AbstractJdbcDatabase.getDefaultSchemaName(AbstractJdbcDatabase.java:305)
      9. liquibase.database.AbstractJdbcDatabase.toString(AbstractJdbcDatabase.java:881)
      10. liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:117)
      11. liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:128)
      12. liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:136)
      13. liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:151)
      14. liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:146)
      15. liquibase.database.AbstractJdbcDatabase.getConnectionSchemaName(AbstractJdbcDatabase.java:324)
      16. liquibase.database.AbstractJdbcDatabase.getDefaultSchemaName(AbstractJdbcDatabase.java:305)
      17. liquibase.changelog.ChangeLogParameters.<init>(ChangeLogParameters.java:54)
      18. liquibase.Liquibase.<init>(Liquibase.java:104)
      18 frames