release-locks
release-locks
removes the specific Liquibase lock record from the DATABASECHANGELOGLOCK table in the needed database.
Uses
release-locks
is typically used when there is an interruption with the Liquibase process during deployment resulting from the DATABASECHANGELOGLOCK table being in a locked state.
Syntax
To run the release-locks
command, specify the driver, classpath, and URL in the Liquibase properties file. You can also specify these properties in your command line.
Then run the release-locks
command:
liquibase release-locks --changelog-file=example-changelog.xml
Command parameters
CLI
Attributes | Definition | Requirement |
---|---|---|
|
The JDBC database connection URL. See Using JDBC URL in Liquibase. |
Required |
|
The root changelog |
Optional |
|
Name of the default catalog to use for the database connection |
Optional |
|
Name of the default schema to use for the database connection. If Note: In the properties file and Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set |
Optional |
|
The JDBC driver class |
Optional |
|
The JDBC driver properties file |
Optional |
|
Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. |
Optional |
|
Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. |
Optional |
Note: The username
and password
attributes are not required for connections and systems which use alternate means of authentication. Also, you can specify database credentials as part of the url
attribute.