liquibase.exception.ValidationFailedException

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.

  • Hi, I'm running a recent 2.0-rc2-SNAPSHOT, but am seeing the following error when creating the sequence: <changeSet author="63DA9B42-9C60-71BE-E1D0-325D11415173" id="Ben Middleton"> <createSequence sequenceName="SEQ_COREOBJECTID" startValue="-100" incrementBy="-1" ordered="true"/> </changeSet> LiquiBase Update Failed: Validation Failed: 1 changes have validation failures ordered is not allowed on oracle, install/seq/coreobjectid.xml::Ben Middleton::63DA9B42-9C60-71BE-E1D0-325D11415173::(Checksum: 2: 0dca6cbdbb4ac0028ab2b348ed40c311) INFO 04/05/10 19:32:liquibase: Validation Failed: 1 changes have validation failures ordered is not allowed on oracle, install/seq/coreobjectid.xml::Ben Middleton::63DA9B42-9C60-71BE-E1D0-325D11415173::(Checksum: 2: 0dca6cbdbb4ac0028ab2b348ed40c311) liquibase.exception.ValidationFailedException: Validation Failed: 1 changes have validation failures ordered is not allowed on oracle, install/seq/coreobjectid.xml::Ben Middleton::63DA9B42-9C60-71BE-E1D0-325D11415173::(Checksum: 2: 0dca6cbdbb4ac0028ab2b348ed40c311) at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:132) at liquibase.Liquibase.update(Liquibase.java:97) at liquibase.integration.commandline.Main.doMigration(Main.java:670) at liquibase.integration.commandline.Main.main(Main.java:105) I am running against an Oracle 10R2 DB using the ojdbc5.jar. Oracle does support the ORDER attribute on CREATE SEQUENCE. i.e. the following is valid: CREATE SEQUENCE seq_coreobjectid INCREMENT BY -1 START WITH -100 NOCACHE ORDER; Presumably this is a bug?
    via by Ben Middleton,
  • Hi, I am using Liquibase 3.4.0 to release changes to my Oracle 11g database on Linux Red Hat. I am using XML formatted changelogs and in particular my changesets are using the runAlways="true" attribute. I released changelogA.xml with changeset 01 using the runAlways="true" attribute to my database for the very first time. No problem there. I then made corrections to the same changelogA.xml file. I.e. I modified changeset 01 in changelogA.xml, which still had runAlways="true" set. I now attempted to re-release changelogA.xml to the same database. This fails with an invalid checksum error. {code:java} INFO 8/28/15 6:16 PM: liquibase: Successfully released change log lock Unexpected error running Liquibase: Validation Failed: 1 change sets check sum changelogA.xml::01::author is now: 7:8b6dc55517d1034abcd7fbf893003f11 SEVERE 8/28/15 6:16 PM: liquibase: Validation Failed: 1 change sets check sum changelogA.xml::01::author is now: 7:8b6dc55517d1034abcd7fbf893003f11 liquibase.exception.ValidationFailedException: Validation Failed: 1 change sets check sum changelogA.xml::01::author is now: 7:8b6dc55517d1034abcd7fbf893003f11 at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:206) at liquibase.Liquibase.update(Liquibase.java:204) at liquibase.Liquibase.update(Liquibase.java:188) at liquibase.integration.commandline.Main.doMigration(Main.java:1096) at liquibase.integration.commandline.Main.run(Main.java:180) at liquibase.integration.commandline.Main.main(Main.java:99) {code} runAlways="true" should override the validation of the checksum behaviour surely? runOnChange="true" seems to be working PERFECTLY in the SAME manner as already described above. A bug surely with runAlways="true"? Regards, sand33p
    via by Sandeep,
  • Hi, I am using Liquibase 3.4.0 to release changes to my Oracle 11g database on Linux Red Hat. I am using XML formatted changelogs and in particular my changesets are using the runAlways="true" attribute. I released changelogA.xml with changeset 01 using the runAlways="true" attribute to my database for the very first time. No problem there. I then made corrections to the same changelogA.xml file. I.e. I modified changeset 01 in changelogA.xml, which still had runAlways="true" set. I now attempted to re-release changelogA.xml to the same database. This fails with an invalid checksum error. {code:java} INFO 8/28/15 6:16 PM: liquibase: Successfully released change log lock Unexpected error running Liquibase: Validation Failed: 1 change sets check sum changelogA.xml::01::author is now: 7:8b6dc55517d1034abcd7fbf893003f11 SEVERE 8/28/15 6:16 PM: liquibase: Validation Failed: 1 change sets check sum changelogA.xml::01::author is now: 7:8b6dc55517d1034abcd7fbf893003f11 liquibase.exception.ValidationFailedException: Validation Failed: 1 change sets check sum changelogA.xml::01::author is now: 7:8b6dc55517d1034abcd7fbf893003f11 at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:206) at liquibase.Liquibase.update(Liquibase.java:204) at liquibase.Liquibase.update(Liquibase.java:188) at liquibase.integration.commandline.Main.doMigration(Main.java:1096) at liquibase.integration.commandline.Main.run(Main.java:180) at liquibase.integration.commandline.Main.main(Main.java:99) {code} runAlways="true" should override the validation of the checksum behaviour surely? runOnChange="true" seems to be working PERFECTLY in the SAME manner as already described above. A bug surely with runAlways="true"? Regards, sand33p
    via by Sandeep,
  • Hi, I'm running a recent 2.0-rc2-SNAPSHOT, but am seeing the following error when creating the sequence: <changeSet author="63DA9B42-9C60-71BE-E1D0-325D11415173" id="Ben Middleton"> <createSequence sequenceName="SEQ_COREOBJECTID" startValue="-100" incrementBy="-1" ordered="true"/> </changeSet> LiquiBase Update Failed: Validation Failed: 1 changes have validation failures ordered is not allowed on oracle, install/seq/coreobjectid.xml::Ben Middleton::63DA9B42-9C60-71BE-E1D0-325D11415173::(Checksum: 2: 0dca6cbdbb4ac0028ab2b348ed40c311) INFO 04/05/10 19:32:liquibase: Validation Failed: 1 changes have validation failures ordered is not allowed on oracle, install/seq/coreobjectid.xml::Ben Middleton::63DA9B42-9C60-71BE-E1D0-325D11415173::(Checksum: 2: 0dca6cbdbb4ac0028ab2b348ed40c311) liquibase.exception.ValidationFailedException: Validation Failed: 1 changes have validation failures ordered is not allowed on oracle, install/seq/coreobjectid.xml::Ben Middleton::63DA9B42-9C60-71BE-E1D0-325D11415173::(Checksum: 2: 0dca6cbdbb4ac0028ab2b348ed40c311) at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:132) at liquibase.Liquibase.update(Liquibase.java:97) at liquibase.integration.commandline.Main.doMigration(Main.java:670) at liquibase.integration.commandline.Main.main(Main.java:105) I am running against an Oracle 10R2 DB using the ojdbc5.jar. Oracle does support the ORDER attribute on CREATE SEQUENCE. i.e. the following is valid: CREATE SEQUENCE seq_coreobjectid INCREMENT BY -1 START WITH -100 NOCACHE ORDER; Presumably this is a bug?
    via by Ben Middleton,
  • GitHub comment 1690#176138473
    via GitHub by ruan0011
    ,
    • liquibase.exception.ValidationFailedException: Validation Failed: 1 change sets check sum org/dcache/srm/request/sql/srm.changelog-2.14.xml::4::behrmann was: 7:0e1c15013e23f1df41d4035279a1e832 but is now: 7:9ecabc0f8b7f5c3223df370147657ccc at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:266)[liquibase-core-3.5.0.jar:na] at liquibase.Liquibase.update(Liquibase.java:210)[liquibase-core-3.5.0.jar:na] at liquibase.Liquibase.update(Liquibase.java:192)[liquibase-core-3.5.0.jar:na] at liquibase.integration.commandline.Main.doMigration(Main.java:1126)[liquibase-core-3.5.0.jar:na] at liquibase.integration.commandline.Main.run(Main.java:184)[liquibase-core-3.5.0.jar:na] at liquibase.integration.commandline.Main.main(Main.java:103)[liquibase-core-3.5.0.jar:na]

    Users with the same issue

    Luka
    1 times, last one,
    aidoan
    3 times, last one,
    tvrmsmith
    2 times, last one,
    batwalrus76
    3 times, last one,
    jpvee
    2 times, last one,
    2 more bugmates