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'.

JIRA | David Björklund | 2 years ago
  1. 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'.
  2. 0

    [This commit|https://github.com/liquibase/liquibase/commit/8a2766a9a5b4882a20dd206ec181eab944ddcea2] broke Oracle 9 compatibility. This version of Oracle database doesn't provide any HISTOGRAM column on ALL_TAB_COLUMNS. Thus, I get the following exception : {code} java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:852) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1153) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1275) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1477) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:392) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at liquibase.snapshot.ResultSetCache$ResultSetExtractor.executeAndExtract(ResultSetCache.java:185) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData$3.oracleQuery(JdbcDatabaseSnapshot.java:333) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData$3.fastFetchQuery(JdbcDatabaseSnapshot.java:267) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.ResultSetCache$SingleResultSetExtractor.fastFetch(ResultSetCache.java:262) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:55) ~[liquibase-core-3.2.2.jar:na] ... 21 common frames omitted Wrapped by: liquibase.exception.DatabaseException: java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:77) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData.getColumns(JdbcDatabaseSnapshot.java:236) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.jvm.ColumnSnapshotGenerator.addTo(ColumnSnapshotGenerator.java:76) ~[liquibase-core-3.2.2.jar:na] ... 19 common frames omitted Wrapped by: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide at liquibase.snapshot.jvm.ColumnSnapshotGenerator.addTo(ColumnSnapshotGenerator.java:83) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:72) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:50) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:153) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.DatabaseSnapshot.init(DatabaseSnapshot.java:56) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:33) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:22) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:126) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:134) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.SnapshotGeneratorFactory.getDatabaseChangeLogTable(SnapshotGeneratorFactory.java:141) ~[liquibase-core-3.2.2.jar:na] at liquibase.changelog.StandardChangeLogHistoryService.init(StandardChangeLogHistoryService.java:81) ~[liquibase-core-3.2.2.jar:na] ... 9 common frames omitted Wrapped by: liquibase.exception.UnexpectedLiquibaseException: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide at liquibase.changelog.StandardChangeLogHistoryService.init(StandardChangeLogHistoryService.java:83) ~[liquibase-core-3.2.2.jar:na] at liquibase.Liquibase.checkLiquibaseTables(Liquibase.java:716) ~[liquibase-core-3.2.2.jar:na] at liquibase.Liquibase.update(Liquibase.java:189) ~[liquibase-core-3.2.2.jar:na] at liquibase.Liquibase.update(Liquibase.java:174) ~[liquibase-core-3.2.2.jar:na] at fr.harvest.big.database.BigBaseUpgrader.runChangeLog(BigBaseUpgrader.java:192) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.database.BigBaseUpgrader.doVersion(BigBaseUpgrader.java:172) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.database.BigBaseUpgrader.doUpgrade(BigBaseUpgrader.java:135) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.database.BigBaseUpgrader.upgrade(BigBaseUpgrader.java:104) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.database.BigBaseUpgrader.upgrade(BigBaseUpgrader.java:78) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.admin.BaseUpgrader$UpgraderThread.run(BaseUpgrader.java:52) [big-backend-2015.1.062.jar:2015.1.062] {code} Is there any workaround (unfortunately, some of our clients still have Oracle 9.02 databases) ?

    JIRA | 2 years ago | Laurent RICHARD
    liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide
  3. 0

    [This commit|https://github.com/liquibase/liquibase/commit/8a2766a9a5b4882a20dd206ec181eab944ddcea2] broke Oracle 9 compatibility. This version of Oracle database doesn't provide any HISTOGRAM column on ALL_TAB_COLUMNS. Thus, I get the following exception : {code} java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:852) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1153) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1275) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1477) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:392) ~[ojdbc6-11.2.0.2.0.jar:11.2.0.2.0] at liquibase.snapshot.ResultSetCache$ResultSetExtractor.executeAndExtract(ResultSetCache.java:185) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData$3.oracleQuery(JdbcDatabaseSnapshot.java:333) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData$3.fastFetchQuery(JdbcDatabaseSnapshot.java:267) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.ResultSetCache$SingleResultSetExtractor.fastFetch(ResultSetCache.java:262) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:55) ~[liquibase-core-3.2.2.jar:na] ... 21 common frames omitted Wrapped by: liquibase.exception.DatabaseException: java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:77) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData.getColumns(JdbcDatabaseSnapshot.java:236) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.jvm.ColumnSnapshotGenerator.addTo(ColumnSnapshotGenerator.java:76) ~[liquibase-core-3.2.2.jar:na] ... 19 common frames omitted Wrapped by: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide at liquibase.snapshot.jvm.ColumnSnapshotGenerator.addTo(ColumnSnapshotGenerator.java:83) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:72) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:50) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:153) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.DatabaseSnapshot.init(DatabaseSnapshot.java:56) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:33) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:22) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:126) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:134) ~[liquibase-core-3.2.2.jar:na] at liquibase.snapshot.SnapshotGeneratorFactory.getDatabaseChangeLogTable(SnapshotGeneratorFactory.java:141) ~[liquibase-core-3.2.2.jar:na] at liquibase.changelog.StandardChangeLogHistoryService.init(StandardChangeLogHistoryService.java:81) ~[liquibase-core-3.2.2.jar:na] ... 9 common frames omitted Wrapped by: liquibase.exception.UnexpectedLiquibaseException: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide at liquibase.changelog.StandardChangeLogHistoryService.init(StandardChangeLogHistoryService.java:83) ~[liquibase-core-3.2.2.jar:na] at liquibase.Liquibase.checkLiquibaseTables(Liquibase.java:716) ~[liquibase-core-3.2.2.jar:na] at liquibase.Liquibase.update(Liquibase.java:189) ~[liquibase-core-3.2.2.jar:na] at liquibase.Liquibase.update(Liquibase.java:174) ~[liquibase-core-3.2.2.jar:na] at fr.harvest.big.database.BigBaseUpgrader.runChangeLog(BigBaseUpgrader.java:192) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.database.BigBaseUpgrader.doVersion(BigBaseUpgrader.java:172) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.database.BigBaseUpgrader.doUpgrade(BigBaseUpgrader.java:135) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.database.BigBaseUpgrader.upgrade(BigBaseUpgrader.java:104) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.database.BigBaseUpgrader.upgrade(BigBaseUpgrader.java:78) [big-core-2015.1.062.jar:2015.1.062] at fr.harvest.big.admin.BaseUpgrader$UpgraderThread.run(BaseUpgrader.java:52) [big-backend-2015.1.062.jar:2015.1.062] {code} Is there any workaround (unfortunately, some of our clients still have Oracle 9.02 databases) ?

    JIRA | 2 years ago | Laurent RICHARD
    liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLSyntaxErrorException: ORA-00904: "HISTOGRAM" : identificateur non valide
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Key is too long with external MySQL container

    GitHub | 1 year ago | andrefreitas
    liquibase.exception.DatabaseException: Error executing SQL CREATE INDEX idx_label_key_value ON cattle.label(`key`, value): Specified key was too long; max key length is 767 bytes
  6. 0

    When using SpringLiquibase, the file names used for the databasechangelog can get rather long as it can use resource paths within jar files, e.g. {code}jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.project.name/WEB-INF/lib/some-library.jar!/database/scripts/00-project-database-liquibase.sql{code} When these paths exceed 200 characters, liquibase fails with the following stack trace: {code:java} liquibase.exception.DatabaseException: Error executing SQL INSERT INTO public.databasechangelog (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES ('1', 'jason', 'jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.semantico.journals.frontend/WEB-INF/lib/sipp2-locator-1.0-SNAPSHOT.jar!/database/scripts/00-locator-liquibase.sql', NOW(), 2, '7:b6b832985892bbec4f63b3e4ec0c949c', 'The ''sql'' tag allows you to specify whatever sql you want. It is useful for complex changes that aren''t supported through Liquibase''s automated refactoring tags and to work around bugs and limitations of Liquibase. The SQL contained in the sql tag...', '', 'EXECUTED', '3.0.0-SNP'): ERROR: value too long for type character varying(200) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:56) ~[liquibase-core-3.0.2.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:98) ~[liquibase-core-3.0.2.jar:na] at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:64) ~[liquibase-core-3.0.2.jar:na] at liquibase.database.AbstractJdbcDatabase.markChangeSetExecStatus(AbstractJdbcDatabase.java:1209) ~[liquibase-core-3.0.2.jar:na] at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:34) ~[liquibase-core-3.0.2.jar:na] at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58) ~[liquibase-core-3.0.2.jar:na] at liquibase.Liquibase.update(Liquibase.java:135) ~[liquibase-core-3.0.2.jar:na] at liquibase.integration.spring.SpringLiquibase.performUpdate(SpringLiquibase.java:285) ~[liquibase-core-3.0.2.jar:na] at liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:258) ~[liquibase-core-3.0.2.jar:na] [… spring setup truncated] {code} Suggested fix: update filename to 400 characters (merge request on the way).

    JIRA | 3 years ago | Toby Cole
    liquibase.exception.DatabaseException: Error executing SQL INSERT INTO public.databasechangelog (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES ('1', 'jason', 'jar:file:/Users/toby/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.semantico.journals.frontend/WEB-INF/lib/sipp2-locator-1.0-SNAPSHOT.jar!/database/scripts/00-locator-liquibase.sql', NOW(), 2, '7:b6b832985892bbec4f63b3e4ec0c949c', 'The ''sql'' tag allows you to specify whatever sql you want. It is useful for complex changes that aren''t supported through Liquibase''s automated refactoring tags and to work around bugs and limitations of Liquibase. The SQL contained in the sql tag...', '', 'EXECUTED', '3.0.0-SNP'): ERROR: value too long for type character varying(200)

    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

      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()
    2. Liquibase Core
      StandardChangeLogHistoryService.init
      1. liquibase.snapshot.jvm.ColumnSnapshotGenerator.snapshotObject(ColumnSnapshotGenerator.java:69)
      2. liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:60)
      3. liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:50)
      4. liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:163)
      5. liquibase.snapshot.DatabaseSnapshot.replaceObject(DatabaseSnapshot.java:241)
      6. liquibase.snapshot.DatabaseSnapshot.includeNestedObjects(DatabaseSnapshot.java:195)
      7. liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:177)
      8. liquibase.snapshot.DatabaseSnapshot.init(DatabaseSnapshot.java:60)
      9. liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:37)
      10. liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:25)
      11. liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:126)
      12. liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:134)
      13. liquibase.snapshot.SnapshotGeneratorFactory.getDatabaseChangeLogTable(SnapshotGeneratorFactory.java:141)
      14. liquibase.changelog.StandardChangeLogHistoryService.init(StandardChangeLogHistoryService.java:88)
      14 frames