releaseLocks command
releaseLocks releases all locks on the DATABASECHANGELOGLOCK table from the specified database.
Uses
releaseLocks is typically used when there was an interruption with the Liquibase process during deployment resulting from the DATABASECHANGELOGLOCK table being in a locked state.
Running the releaseLocks command
To run the releaseLocks command, you need to specify your URL and user authentication information in your liquibase.properties file. You can also specify these properties in your command line.
Then run the releaseLocks command:
liquibase -–changeLogFile=mainchangelog.xml releaseLocksNote: Enter the name of the changelog you want to use in place of mainchangelog.xml. You can also add the changeLogFile to your liquibase.properties file
releaseLocks global attributes
| Attributes | Definition | Requirement |
|---|---|---|
--changeLogFile
|
The root changelog | Required |
--username
|
The database username | Required |
--password
|
The database password | Required |
--url
|
The JDBC database connection | Required |
Output
When successful, the releaseLocks command produces the following output:
Liquibase Pro 3.9.0 by Datical licensed to Liquibase Pro Customer until Tue Sep 22 19:00:00 CDT 2020
Successfully released all database change log locks for 'HR_DEV@jdbc:oracle:thin:@support.datical.net:1521:ORCL'
Liquibase command 'releaseLocks' was executed successfully.