# Liquibase rollback-sql not producing SQL statements **URL:** \ **Category:** Uncategorized\ **Created:** [April 20, 2023, 7:02pm UTC](https://forum.liquibase.org/t/liquibase-rollback-sql-not-producing-sql-statements/8119 "2023-04-20T19:02:09Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![bwmann89](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@bwmann89](https://forum.liquibase.org/u/bwmann89)\ **Post date:** [April 20, 2023, 7:02pm UTC](https://forum.liquibase.org/t/liquibase-rollback-sql-not-producing-sql-statements/8119/1 "2023-04-20T19:02:09Z")
I’m attempting to run the following liquibase rollback-sql statement in order to produce the required SQL or DDL in order to reverse my changes in Snowflake. I am also using the Liquibase docker container in Jenkins. Version is 4.19. The following are the changes I’d like reversed in DATBASECHANGELOG. These were new changes put into the database through Liquibase update. | 33\_123 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:35.5 | 1557 | EXECUTED | 8:424fde792016cfcb3ecb2d9fb57e8c71 | sql | | | 4.21.1 | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 33\_124 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:36.4 | 1558 | EXECUTED | 8:8ddc3bf0aebdefe58671127a6c718488 | sql | | | 4.21.1 | | 33\_125 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:37.6 | 1559 | EXECUTED | 8:23b9130739ed5d02247d7875b1d1fc15 | sql | | | 4.21.1 | | 33\_126 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:38.6 | 1560 | EXECUTED | 8:1233f73bdf5fa7c3ee483cfab949cb6a | sql | | | 4.21.1 | | 33\_127 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:40.0 | 1561 | EXECUTED | 8:38edfdeb3ebf5553fa1b634ee3147298 | sql | | | 4.21.1 | | 33\_128 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:40.9 | 1562 | EXECUTED | 8:254fcf5eb5815dc6dc0cc1cb902ec0a1 | sql | | | 4.21.1 | | 33\_129 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:42.2 | 1563 | EXECUTED | 8:14819e9d1c3039df029bddd500e5bf22 | sql | | | 4.21.1 | | 33\_130 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:43.5 | 1564 | EXECUTED | 8:7ae5229343b5c1898dacf9ba058e95c8 | sql | | | 4.21.1 | | 33\_131 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:44.4 | 1565 | EXECUTED | 8:be3d0a4ea996d171535754a93995c448 | sql | | | 4.21.1 | | 33\_132 | M11X | ./…/com/idrc/impl/CMS\_FCT\_CLM\_IMPL/CMS\_FCT\_CLM\_IMPL-changelog.sql | 00:45.5 | 1566 | EXECUTED | 8:5883f780e28185fd54edad61ce7373ee | sql | | | 4.21.1 | | 39\_123 | M11X | ./…/com/idrc/impl/CMS\_VIEW\_CLM\_IMPL/CMS\_VIEW\_CLM\_IMPL-changelog.sql | 00:46.7 | 1567 | EXECUTED | 8:b51b27d8ac8a05d0d7654efd6b6b9f34 | sql | | | 4.21.1 | | 39\_124 | M11X | ./…/com/idrc/impl/CMS\_VIEW\_CLM\_IMPL/CMS\_VIEW\_CLM\_IMPL-changelog.sql | 00:48.1 | 1568 | EXECUTED | 8:f0a88ad3f640344b12782f6c5c8d3b8d | sql | | | 4.21.1 | | 39\_125 | M11X | ./…/com/idrc/impl/CMS\_VIEW\_CLM\_IMPL/CMS\_VIEW\_CLM\_IMPL-changelog.sql | 00:49.2 | 1569 | EXECUTED | 8:6fc037ab17138b1388e7a17e95457e82 | sql | | | 4.21.1 | | 39\_126 | M11X | ./…/com/idrc/impl/CMS\_VIEW\_CLM\_IMPL/CMS\_VIEW\_CLM\_IMPL-changelog.sql | 00:52.7 | 1570 | EXECUTED | 8:6535b8e1fa2181df678782a03d45e892 | sql | | | 4.21.1 | | 39\_127 | M11X | ./…/com/idrc/impl/CMS\_VIEW\_CLM\_IMPL/CMS\_VIEW\_CLM\_IMPL-changelog.sql | 00:53.8 | 1571 | EXECUTED | 8:c7b2868ebabc03169990c5c71e0e86d2 | sql | | IDRS\_2513 | 4.21.1 | I can confirm that the --rollback statements are present in the 2 changelog files as well, but they do not get produced using the rollback-sql command. ---
**Author:** ![PJatLiquibase](https://avatars.discourse-cdn.com/v4/letter/p/d26b3c/32.png) [@PJatLiquibase](https://forum.liquibase.org/u/PJatLiquibase)\ **Post date:** [April 20, 2023, 7:40pm UTC](https://forum.liquibase.org/t/liquibase-rollback-sql-not-producing-sql-statements/8119/2 "2023-04-20T19:40:59Z")
Hi @bwmann89, In order to help troubleshoot this, I think we need a few more details. What are you actually seeing? Do you get any error messages? Do you get nothing back? Do you get some but not all of the rollback statements? `-PJ` ---
**Author:** ![bwmann89](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@bwmann89](https://forum.liquibase.org/u/bwmann89)\ **Post date:** [April 20, 2023, 7:51pm UTC](https://forum.liquibase.org/t/liquibase-rollback-sql-not-producing-sql-statements/8119/3 "2023-04-20T19:51:49Z")
Hi @PJatLiquibase thanks for replying. I’m not seeing any errors, but just lock and unlock statements. In my pipeline, I’m running the following: liquibase --username=$LIQUIBASE\_TST\_USER --password=$LIQUIBASE\_TST\_PASS --url=“jdbc:snowflake://cms-idritlab.privatelink.snowflakecomputing.com/?&warehouse=IDRC\_NP\_DEVOPS\_WH\_BATCH&db=IDRC\_TST&schema=LB\_CHANGELOG\_TST” --changeLogFile=db.change-master.xml rollback-sql --tag=“initial-deployment” \> …/…/scripts/rollback-sql.sql Following this I read in this file, …/…/scripts/rollback-sql.sql, and it only shows the following, instead of all of the rollback statements I specified for each changeset. alter session set jdbc\_query\_result\_format = ‘JSON’; – Lock Database UPDATE LB\_CHANGELOG\_IMPL.DATABASECHANGELOGLOCK SET LOCKED = TRUE, LOCKEDBY = ‘idrc-poc-liquibase-deployment-itlab-527-m9v86-m0f13-47hsj (100.85.159.190)’, LOCKGRANTED = current\_timestamp::timestamp\_ntz WHERE ID = 1 AND LOCKED = FALSE; alter session set jdbc\_query\_result\_format = ‘JSON’; alter session set jdbc\_query\_result\_format = ‘JSON’; – \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* – Rollback to ‘initial-deployment’ Script – \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* – Change Log: db.change-master.xml – Ran at: 4/20/23, 6:38 PM – Against: IDRC\_IMPL\_LB\_SVC@jdbc:snowflake://cms-idritlab.privatelink.snowflakecomputing.com:443/ – Liquibase version: 4.21.1 – \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* – Release Database Lock alter session set jdbc\_query\_result\_format = ‘JSON’; UPDATE LB\_CHANGELOG\_IMPL.DATABASECHANGELOGLOCK SET LOCKED = FALSE, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1; alter session set jdbc\_query\_result\_format = ‘JSON’; Thanks, Braz ---
**Author:** ![bwmann89](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@bwmann89](https://forum.liquibase.org/u/bwmann89)\ **Post date:** [April 21, 2023, 7:15pm UTC](https://forum.liquibase.org/t/liquibase-rollback-sql-not-producing-sql-statements/8119/4 "2023-04-21T19:15:16Z")
Some additional strange behavior I’m seeing: Regular rollback does not work either, and whenever I run a ‘liquibase update’, it’s trying to execute the changesets again… it’s like Liquibase doesn’t recognize that these changes are in place already, and in the designated table for DATABASECHANGELOG. Is there a reason why this could be?