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

JIRA | Gerd Behrmann | 7 months ago
  1. 0

    After upgrading from 3.3.2 to 3.5.0, the following changeset got a new checksum: <changeSet id="4" author="behrmann"> <comment>Refresh list of valid request states</comment> <loadUpdateData tableName="srmjobstate" primaryKey="id" file="/org/dcache/srm/request/sql/srmjobstate-214.csv"/> <rollback/> </changeSet> After upgrade we now receive a validation error: ERROR - 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 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]

    JIRA | 7 months ago | Gerd Behrmann
    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
  2. 0

    After upgrading from 3.3.2 to 3.5.0, the following changeset got a new checksum: <changeSet id="4" author="behrmann"> <comment>Refresh list of valid request states</comment> <loadUpdateData tableName="srmjobstate" primaryKey="id" file="/org/dcache/srm/request/sql/srmjobstate-214.csv"/> <rollback/> </changeSet> After upgrade we now receive a validation error: ERROR - 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 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]

    JIRA | 7 months ago | Gerd Behrmann
    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
  3. 0

    How can I force Liquibase to recalculate checksums without re-running the statements?

    Stack Overflow | 2 years ago
    liquibase.exception.ValidationFailedException: Validation Failed: 3 change sets check sum db.changelog-1.0.xml::1357593229391-25::rob (generated) is now: 7:5cfe9ecd779a71b6287ef2360a6979bf db.changelog-7.0.xml::create-address-email-index::davea is now: 7:da0132e30ebd6a1bc52d9a39bb8c56d7 db.changelog-7.0.xml::add-myproject-event-object-id-col::davea is now: 7:2eab5d784647ce33ef3488aa8c383443
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    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?

    JIRA | 7 years ago | Ben Middleton
    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)
  6. 0

    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

    JIRA | 1 year ago | Sandeep
    liquibase.exception.ValidationFailedException: Validation Failed: 1 change sets check sum changelogA.xml::01::author is now: 7:8b6dc55517d1034abcd7fbf893003f11

    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.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()
    2. Liquibase Core
      Main.main
      1. liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:266)[liquibase-core-3.5.0.jar:na]
      2. liquibase.Liquibase.update(Liquibase.java:210)[liquibase-core-3.5.0.jar:na]
      3. liquibase.Liquibase.update(Liquibase.java:192)[liquibase-core-3.5.0.jar:na]
      4. liquibase.integration.commandline.Main.doMigration(Main.java:1126)[liquibase-core-3.5.0.jar:na]
      5. liquibase.integration.commandline.Main.run(Main.java:184)[liquibase-core-3.5.0.jar:na]
      6. liquibase.integration.commandline.Main.main(Main.java:103)[liquibase-core-3.5.0.jar:na]
      6 frames