In SQLcl 24.2, Liquibase Generate-schema Command Not Capturing ENABLED/DISABLED Status For Triggers
(Doc ID 3078800.1)
Last updated on MARCH 26, 2025
Applies to:
Oracle SQLcl - Version 24.2 and laterInformation in this document applies to any platform.
Symptoms
When using SQLcl versrion 24.2, generating objects with Liquibase results in the ENABLE / DISABLE clause for triggers being missing.
Specifically: Liquibase can be used to generate a schema from a source database in which a trigger is marked as DISABLED.
But when Liquibase is used to deploy that schema and trigger to a target database, that DISABLED trigger becomes ENABLED.
This problem was not present when using SQLcl version 23.3.
Specifically, in version 23.3, the 'ALTER TRIGGER "<SCHEMA>"."<TRIGGER>" DISABLE' command is included in the SQLcl Liquibase generated files.
But this line is missing when using SQLcl version 24.2.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |