MD5SUM updating at every execution

daryldoak · September 14, 2022, 9:33pm

I did open a github issue. Thanks!

MD5SUM updating at every execution

opened 09:22PM - 12 Sep 22 UTC

DBOracle IntegrationCLI checksum cloudAWS ver4.14.0

## Environment **Liquibase Version**: Community 4.14 **Liquibase Integration & Version**: CLI **Liquibase Extension(s) & Version**: Oracle 4.14, Teradata 4.14, neo4j 4.14, netezza 4.14 (dbeaver extension) **Database Vendor & Version**: Oracle 12.1.0.2 **Operating System Type & Version**: Linux 5.4.0-1084-aws #91~18.04.1-Ubuntu SMP x86_64 GNU/Linux **Infrastructure Type/Provider**: AWS ## Description 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 ``` It's strange because it's not all of his changesets, only the changesets that contain PL/SQL (packages, 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: 1. Upgraded to 4.12 2. 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.

Topic		Replies	Views
MD5SUM value being updated every upate/update-sql General Discussion	1	216	August 16, 2023
Incorrect MD5SUM computing General Discussion	2	792	April 20, 2021
Calculation of checksum md5sum General Discussion	10	11813	November 24, 2009
Command Line ignoring MD5 Sum General Discussion	2	393	September 2, 2010
Is there an Update option to minimize reading DATABASECHANGELOG? General Discussion	6	1963	September 15, 2021

MD5SUM updating at every execution

Related topics