liquibase.exception.MigrationFailedException

Migration failed for change set releases/1614/atg/dynct1/drop_view_v_a.xml::1614::venkatrama.kamaraj: Reason: src/main/resources/changeLog.xml : liquibase.precondition.core.ViewExistsPrecondition@59d4cd39 : Empty result set, expected one row

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web12

  • via Unknown by Bhvani Prasad Atluri,
  • via Unknown by Bhvani Prasad Atluri,
  • via Unknown by Rafael Chaves,
  • Stack trace

    • liquibase.exception.MigrationFailedException: Migration failed for change set releases/1614/atg/dynct1/drop_view_v_a.xml::1614::venkatrama.kamaraj: Reason: src/main/resources/changeLog.xml : liquibase.precondition.core.ViewExistsPrecondition@59d4cd39 : Empty result set, expected one row at liquibase.changelog.ChangeSet.execute(ChangeSet.java:513) at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:51) at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:73) at liquibase.Liquibase.update(Liquibase.java:212) at liquibase.Liquibase.update(Liquibase.java:192) at liquibase.Liquibase.update(Liquibase.java:327) at liquibase.Liquibase.updateTestingRollback(Liquibase.java:1069) at liquibase.Liquibase.updateTestingRollback(Liquibase.java:1061) at liquibase.integration.commandline.Main.doMigration(Main.java:1167) at liquibase.integration.commandline.Main.run(Main.java:180) at liquibase.integration.commandline.Main.main(Main.java:99) Caused by: liquibase.exception.PreconditionErrorException: Precondition Error at liquibase.precondition.core.ViewExistsPrecondition.check(ViewExistsPrecondition.java:66) at liquibase.precondition.core.AndPrecondition.check(AndPrecondition.java:43) at liquibase.precondition.core.PreconditionContainer.check(PreconditionContainer.java:202) at liquibase.changelog.ChangeSet.execute(ChangeSet.java:470) ... 10 more Caused by: liquibase.exception.DatabaseException: Error getting jdbc:oracle:thin:@localhost:1541:OV1ATG view with liquibase.statement.core.GetViewDefinitionStatement@421e361 at liquibase.snapshot.jvm.ViewSnapshotGenerator.snapshotObject(ViewSnapshotGenerator.java:100) at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:60) at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:50) at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:63) at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:50) at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:194) at liquibase.snapshot.DatabaseSnapshot.init(DatabaseSnapshot.java:70) at liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:44) at liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:21) at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:150) at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:158) at liquibase.snapshot.SnapshotGeneratorFactory.has(SnapshotGeneratorFactory.java:108) at liquibase.precondition.core.ViewExistsPrecondition.check(ViewExistsPrecondition.java:60) ... 13 more Caused by: liquibase.exception.DatabaseException: Expected single row from liquibase.statement.core.GetViewDefinitionStatement@658c5a19 but got 0 at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:140) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:151) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:146) at liquibase.database.AbstractJdbcDatabase.getViewDefinition(AbstractJdbcDatabase.java:867) at liquibase.snapshot.jvm.ViewSnapshotGenerator.snapshotObject(ViewSnapshotGenerator.java:75) ... 25 more Caused by: liquibase.exception.DatabaseException: Empty result set, expected one row at liquibase.util.JdbcUtils.requiredSingleResult(JdbcUtils.java:141) at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:138) ... 29 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.