I have a customer who has a large number of changesets that get the MD5SUM updated in databasechangelog at the start of every deployment, even though the changesets have not been modified and the changesets are not actually executed. The Liquibase output looks like this:
[2022-09-02 15:46:24] INFO [liquibase.executor] UPDATE TST4CIS.DATABASECHANGELOG SET MD5SUM = '8:cf74d98bf9923254d88d77efba90e1ec' WHERE ID = 'ads_cisd015.pks' AND AUTHOR = 'xxx' AND FILENAME = 'Packages/db-changelog-1.xml'
[2022-09-02 15:46:24] INFO [liquibase.executor] 1 row(s) affected
[2022-09-02 15:46:24] INFO [liquibase.executor] UPDATE TST4CIS.DATABASECHANGELOG SET MD5SUM = '8:a1d70adee4b5b830d4b5ab103c371548' WHERE ID = 'ads_cisd109.pks' AND AUTHOR = 'xxx' AND FILENAME = 'Packages/db-changelog-1.xml'
[2022-09-02 15:46:24] INFO [liquibase.executor] 1 row(s) affected
[2022-09-02 15:46:24] INFO [liquibase.executor] UPDATE TST4CIS.DATABASECHANGELOG SET MD5SUM = '8:859cb9b9b4174f5322329ee434232c55' WHERE ID = 'bobfixtca.pkb' AND AUTHOR = 'xxx' AND FILENAME = 'Packages/db-changelog-1.xml'
[2022-09-02 15:46:24] INFO [liquibase.executor] 1 row(s) affected
Database: Oracle
Liquibase: 4.12 and 4.14
Liquibase CLI
It’s strange because it’s not all of his changesets, only the changesets that contain PL/SQL (pacakges, procedures, trigggers, etc) , executed via sqlFile, and the files have .pkb, .pks, .prc, and .sql extensions.
This seems to have started after two changes we made:
Upgraded to 4.12
Added sql-log-level=INFO
This is only occurring with this one customer (we have 100s) so I’m assuming it’s something about his changelogs that is causing this, but I don’t see anything obvious.
