Applies to:
- Liquibase Enterprise (Datical)
Conditions:
- Using Liquibase Enterprise with DMC
Issue Summary:
When registering a Liquibase Enterprise project with DMC using the registerProjectWithDMCDB command, an error about a type_id being null occurs. Subsequent runs of this command result in the same error but also state that the project is already registered.
If you try and search DMC for this project, it does not appear.
Error Message:
Sync is UnSuccessful:ERROR: null value in column "type_id" violates not-null constraint
Root Cause:
Prior to Liquibase Enterprise v7.0, there was an "environment" type attribute that was able to be added to the dbDef in the datical.project file. The acceptable values were:
- "" (or blank)
- Dev
- QA
- Stage
- Production
After v7.0, the option for this environment type was removed from the GUI. However, it is still eligible to be in the datical.project file for backward compatibility.
DMC expects the environment type to be one of those 5 values, and if it is set to anything else, the type_id error will occur.
Resolution:
- If you are on Enterprise version 7.0 or higher, you can remove the environment attribute from the datical.project file. If you are on a version older than 7.0 or you do not want to remove the environment attribute, you may set the environment attribute to one of the five accepted values listed above.
- Rerun the registerProjectWithDMCDB command
- Note that there will still be an error that the project is already registered.
- The project will successfully sync and is visible in DMC
Related Article(s):
N/A
Comments
0 comments
Article is closed for comments.