What happened when you tried? Did it fail? I’m still not clear what your error is.
The reason that you get that error message is that some changesets have been deployed to a database. At the time they were deployed, Liquibase calculated a checksum for each changeset. If you then run update again, Liquibase checks two things - whether each changeset in the changelog has been deployed before or not, which is does by comparing the changeset id, author, and path that in in the changelog to the entries in the DATABASECHANGELOG table. Liquibase also calculates a checksum for each changeset in the changelog again, and then compares that checksum to any that are in the DATABASECHANGELOG table. If they are different, that is an error.
Typically, this should only happen if the changeset has actually been changed between the first deploy and the second deploy. If you are certain that the changeset has NOT changed, then you can work around the problem by manually clearing the checksum column from that row, and Liquibase will just update the checksum - it won’t try to re-apply the changeset, but will just re-calculate the checksum.
There are also cases where the checksum algorithm has changed - this has happened a few times in the lifetime history of Liquibase. The number with the colon preceeding the checksum is the version of the checksum algorithm. In your first post, the partial message you included showed a version of 7.
If you have recently updated the version of Liquibase you are using, that could be the issue. In that case, you can use the Liquibase clearChecksums command after you have verified that the changelog hasn’t been altered from what it should be, and then re-run the update command, and Liquibase will update the checksums as described above.
Again, without a full description of what you did, and the full output of the errors, it is difficult to help more.
Principal Software Engineer
Datical, Inc. http://www.datical.com/