- Reference
- Version ยท 6.0.2
- Change Automation Reference
oracle-fail-options
Last updated: November 17, 2026
--oracle-fail-options is a global parameter that controls whether Oracle compiler warnings and errors stop a deployment of stored logic, such as a procedure, package, or trigger. The default value is none, so the compiler output is shown and the deployment continues.
Uses
When you deploy stored logic to Oracle and its code does not compile, Oracle still creates the object and marks it INVALID. The statement itself succeeds, so Liquibase sees only a driver warning, not a failure. By default, Liquibase shows the compiler output, records the changeset as deployed, and finishes the command with exit code 0.
Set --oracle-fail-options to have that compiler output stop the deployment instead. It accepts these values:
none(default): Liquibase shows the compiler output and continues the deployment.errors: Liquibase stops when Oracle reports a compilation error. Code that does not compile produces an error, so this is the value that catches it.warnings: Liquibase stops when Oracle reports a compilation warning. It does not stop on an error, so it does not catch code that fails to compile.all: Liquibase stops on any compilation warning or error.
The values are not case sensitive, and Liquibase also accepts error and warning. A value Liquibase does not recognize is treated as none, so a misspelled value never stops a deployment.
The check covers packages, package bodies, types, type bodies, procedures, functions, triggers, views, Java sources, and Java classes.
When the check stops a changeset, the command exits with code 1 and reports LB-EXE-0006 along with the compiler output. Liquibase does not record the changeset in the DATABASECHANGELOG table, so the next deployment runs it again. The INVALID object stays in the database. If your corrected changeset uses CREATE OR REPLACE, it replaces the object. If it uses CREATE without OR REPLACE, drop the INVALID object before you rerun the changeset.
If you also set --rollback-on-error to true and the changeset has its own <rollback> block, Liquibase runs that block when the check stops the changeset, so the object is removed if the block drops it.
Note: Most pipelines want errors. Oracle also reports advisory warnings, such as an omitted AUTHID clause or unreachable code, on objects that compile VALID. Liquibase does not print those advisories during a normal run, but warnings and all stop the deployment on them.
The check applies to every command that deploys changesets, such as update, update-count, update-to-tag, update-one-changeset, and update-testing-rollback. This parameter covers changesets that Liquibase runs over its JDBC connection, which is the default. A changeset with runWith:sqlplus uses --sqlplus-fail-options instead. Commands such as update-sql only generate SQL and never run it, so the parameter has no effect on them.
The compiler output appears on the console only while --sql-show-sql-warnings is true, which is its default. Setting it to false hides the output but does not change what --oracle-fail-options stops on.
Example: oracle-fail-options
liquibase --oracle-fail-options=errors update --changelog-file=example-changelog.xml
Syntax
You can set this parameter in the following ways:
Option | Syntax |
Liquibase properties file (defaults file) |
|
Global flow file argument |
|
Global CLI parameter |
|
JVM system property (JAVA_OPTS environment variable) | Unix:
Windows:
|
Liquibase environment variable |
|