Unable to run multiple sql queries

Hi All,
I am unable to run multiple sql queries.
We have created a Jenkins pipeline for Liquibase, in which we are putting our code in bitbucket. We are pulling the below sql from there as shown below.
CREATE TABLE JOHN(ENAME VARCHAR(10) NOT NULL, JOB VARCHAR(9) NOT NULL, SAL DECIMAL(7, 2), COMM DECIMAL(7, 2))
When I trigger the pipeline in Jenkins I am able to create a table and it’s verified in sql developer. But when we have more than one sql in bitbucket and I trigger the pipeline it’s failing with below error
Unexpected error running Liquibase: Validation Failed:
1 change sets check sum
create.sql::raw::includeAll was: 8:39897ea371fae624d82a88669060934c but is now: 8:1c719c70c1bc339697c54ccb85c41458

For more information, please use the --logLevel flag
[2021-02-15 18:57:51] SEVERE [liquibase.integration] Unexpected error running Liquibase: Validation Failed:
1 change sets check sum
create.sql::raw::includeAll was: 8:39897ea371fae624d82a88669060934c but is now: 8:1c719c70c1bc339697c54ccb85c41458

liquibase.exception.ValidationFailedException: Validation Failed:
1 change sets check sum
create.sql::raw::includeAll was: 8:39897ea371fae624d82a88669060934c but is now: 8:1c719c70c1bc339697c54ccb85c41458

Also sometimes the error is invalid sql query when more than 1 query exist

Hi @nitesh ,

The error root cause, from a Liquibase point of view is this: a changeset that was once executed and later modified, then re-executed, will fail with those output errors. This is because of a checksum mechanism that Liquibase has in place to make sure that changesets are “locked” in their initial setup (this is the default behavior, can be overridden of course).
If you need the same changeset (same combination of id, author and filename) to be executed multiple times you need to modify the changeset and specify the tag: runAlways - true (changeset | Liquibase Docs).
Of course, the logic in the changeset itself must be compatible with re-runability (i.e if you have a sql type changeset that creates a table, add logic to check if the table already exists or not etc).

If the issue is not resolved and it’s possible, can you also add the entire changelog to the thread (would help understanding the big picture)?

Hope this helps,
Eduard

Hi Eduard,
Thanks for your quick reply. I am attaching changelog here. Please suggest your inputs. I am getting same error. Is there any way we can resolve this.

<?xml version="1.0" encoding="UTF-8"?>

runAlways - true

@nitesh , not sure if you attached the changelog (or added inside the comment itself) as I am unable to find it.
Can you (re)check please?

Thanks,
Eduard