Applies to:
- Liquibase Enterprise (Datical DB)
Conditions:
- Liquibase Enterprise
- Expiring old License
- New License installed
Issue Summary:
When a Liquibase Enterprise (Datical DB) license is nearing the expiration date, a warning will appear either as a pop-up (in the GUI) or in the command line output (in the CLI). After the new license is installed, this warning should go away. However, there are times when the warning persists after the new license has been installed.
Error Message:
CLI:
WARNING! DaticalDB license will expire in X days. Please contact support@datical.com
GUI:
- A pop-up will appear with the following:
Potential Root Causes:
If a new license has been installed, but the warning still appears, the old license is most likely still in the datical directory.
Troubleshooting:
- Search for Liquibase Enterprise (Datical DB) .LIC files
- Linux: The license will be inside either the opt/app/datical/daticalDB/repl or opt/app/datical/daticalDB directory (the exact path may vary depending on the installation).
- Windows: The license will be inside either C:\Users\\DaticalDB\repl or C:\Users\\DaticalDB (the exact path may vary depending on the installation).
- Remove all Liquibase Enterprise (Datical DB) .LIC files, except for the current one
- Liquibase will only pick up the single license file and no longer show the warning
Some users see the new license, but CI/CD or other users do not
When running the hammer install license
command, a Java configuration XML file is updated with the new license, but this is done on a per-user basis.
This can result in a situation where some users see the new license, but either the CI/CD pipeline or other users don't.
There are two solutions for this.
- Have the user who is seeing the old license run the
hammer install license
command. - Wait for the license to expire before Liquibase automatically installs the new license.
- Please follow the next section for this solution.
Wait for the license to expire
If you are unable to run the hammer install license
command, the only option left is to ensure the new license file is available for Liquibase to automatically install once the old license expires.
We recommend the following to ensure that this process is as seamless as possible.
- If the environment variable, DATDB_LICENSE, has a value, remove the value.
- Note: this value can be set per pipeline, so you must ensure that this environment variable is empty in each pipeline.
- Place the new license file in the DATICAL_HOME/repl/enterprise-license folder
- Ensure that the old license file is NOT in the repl folder or the enterprise-license folder
Once the license expires, Liquibase Enterprise will automatically search for a license file in that directory, and if it is valid, it will install the license.
Comments
0 comments
Article is closed for comments.