liquibase.bteq.maxerror
Last updated: June 9, 2026
liquibase.bteq.maxerror is an Integer parameter that sets the BTEQ error severity threshold for SQL statement execution. Default: 1 (strictest).
Uses
Liquibase emits .SET MAXERROR {value} as the first directive in every generated BTEQ script. BTEQ uses this threshold to decide whether to stop execution after a SQL statement produces an error or warning. Lower values are stricter; higher values tolerate more warning conditions.
Valid values follow the Teradata BTEQ severity scale:
Value | Behavior |
|---|---|
| Stop on any error or warning (strictest) |
| Ignore syntax warnings, stop on errors |
| Ignore conversion warnings, stop on errors |
| Stop on errors only, ignore all warnings |
Note: liquibase.bteq.maxerror applies to SQL statement execution only. Login errors and database selection failures use separate .IF ERRORCODE checks in the generated script and are not affected by this setting.
Set liquibase.bteq.maxerror when:
Tolerating expected warnings: Your Teradata environment produces warnings that should not halt execution (for example, implicit data type conversions).
Strict production deployments: The default of
1is appropriate for most production use, stopping immediately on any problem.
Syntax
Option | Syntax |
|---|---|
Liquibase properties file |
|
Environment variable |
|