9.12.24 mark-next-changeset-ran

Marks the next change you apply as executed in your database.

Syntax

Liquibase|lb mark-next-changeset-ran|mancr {OPTIONS}

The mark-next-changeset-ran command is used when deploy errors occur due to Liquibase not being synchronized with changes made outside of Liquibase.

Options

Option	Description	Default
Required
-changelog-file|-chf	The root changelog file.	-
Optional
-database-changelog-table-name|-dactn	Name of table to use for tracking change history.	-
-debug|-de	Enable debug output.	-
-default-schema-name|-desn	The default schema name to use for the database connection.	-
-defaults-file|-def	Fully qualified path to the properties file you want to use. Example: -defaults-file/tmp/liquibase.properties	-
-liquibase-schema-name|-lbsn	Schema to use for Liquibase objects.	-
-liquibase-tablespace-name|-lbtn	Tablespace to use for Liquibase objects.	-
-log|-lo	Enable logging. Standard logging is INFO level (no debug flag). Debug logging is FINEST level (both log and debug flag).	-
-search-path|-sep	Complete list of locations to search for files such as changelog files. You can specify multiple paths by separating them with commas.	-
-secure-parsing|-scp	If true, remove functionality from file parsers that could be used insecurely. An example is disabling remote XML entity support.	True
-output-default-schema|-ouds	Controls whether names of objects in the default schema are fully qualified or not. If false, only objects outside the default schema are fully qualified.	False