Software Downloads

Go to https://download.liquibase.com/ to download files.

Upgrade Notes

DMC Users

DMC users should be aware that Liquibase Enterprise 8.9 requires an upgrade of the DMC to version 8.6+ to ensure that the DMC Report Links continue to work as expected.

Enhancements

New Ephemeral Database property ephemeralCleanUpBeforeStart

This ephemeral database property is set in the deployPackager.properties to allow Liquibase to cleanup any existing ephemeral database or PDB found while performing Ephemeral Packaging. Existing databases can exist because of earlier failures or cancelations from an Ephemeral Packaging job. This property applies to Oracle, SqlServer, and Postgres Ephemeral Packaging.

Associated Tickets: DAT-17246

Desktop Client Updates, CLI Updates, and Issues Addressed

Issue ID	Description
DAT-17246	Added new Ephemeral Database property called `ephemeralCleanUpBeforeStart`. Setting this value to `true` will enable Liquibase to drop an existing ephemeral database or PDB in the event of a previously failed Packager Operation. This property is applicable for Oracle, SqlServer, and Postgres Ephemeral Packaging.
DAT-17821	Fixed an issue where the Deploy Report was missing a link to the .sql.log when using schema-level folders.
DAT-18899	Update the diffChangelog and snapshot commands so that a full view definition is included when using the --ddlExcludeList parameter. For Oracle databases only.
DAT-19138	Fixed an issue with Oracle RAC clusters and ephemeral packaging to include `instances=all` with the close and open commands when RAC cluster use is detected.
DAT-19253	Added flexibility in Oracle Ephemeral Packaging to include the ability to specify the following overrides in the deployPackager.properties: `oracleEphemeralCopySid` `oracleEphemeralCopyTnsName` If these properties are not specified, Liquibase will use the values from the dbDef and append an `_eph` suffix to the source. An additional override for Service Name can be specified in the deployPackager.properties with: `oracleEphemeralCopyServiceName` Default logic was changed for the handling of Service Name if an override is not provided. If this property is not specified, Liquibase will use the value from the dbDef and append an `_eph` suffix before a first dot. For example `datical.dev.com` will become `datical_eph.dev.com`. If a dot is not present in the value, the `_eph` suffix will be added to to the end of the source.

DMC Issues Addressed

Issue ID	Description
DAT-19015	Added optimizations to DMC Report Search to improve performance.

Documentation for v8.9

Updated Documentation:

Upgrading Liquibase Enterprise

Documentation is available in the following locations:

Liquibase Enterprise Documentation
Deployment Monitoring Console (DMC) Documentation
Specifically, these documents were created or updated:
- Hardware, Software, and Database Requirements
- https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit/896570147?draftId=898433287&draftShareId=b55ceaa1-0e40-44c5-8190-5d0a0d88279d& (Publish and switch to live link)
- https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit-v2/3623649281 (Publish and switch to live link)
- https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit-v2/3998023681 (Publish and switch to live link)
- https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit-v2/4062445569 (Publish and switch to live link)

Liquibase Enterprise & Business Clients (Desktop & CLI)

Find the latest downloads here: https://download.liquibase.com/

Item	Path	File
Software	Datical_DB_Software/Datical_DB_8.9.XXX	Choose the Linux or Windows installation file for your system
Composite Installation Repository	Datical_DB_Software/Datical_DB_8.9.XXX	DaticalDBCompositeRepo-8.9.XXX.zip

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item	Path	File
Software	Datical_DMC_Software/Datical_DMC_8.9.XXX	datical-service-unix-8.9.XXX-master.sh

Liquibase Enterprise includes a web-based Deployment Monitoring Console (DMC) that provides a centralized location to view pipeline status and report information for all your Liquibase Business & Enterprise projects.

Liquibase Enterprise & Business Clients (Datical DB) and DMC Compatibility

Each DMC release only works with certain releases of Liquibase Enterprise Desktop. To ensure compatibility, consult the Deployment Monitoring Console Compatibility Matrix.

Getting Started with the Deployment Monitoring Console

To get started with DMC, check out the following documentation resources:
- DMC Documentation Home
- DMC Install Configurations and System Requirements

DMC Update Instructions

Updating the Deployment Monitoring Console to the latest version is similar to the installation process.

Expand for DMC update instructions

Go to https://download.liquibase.com/ , download, and copy the datical-service-unix-<version>-master.sh, file to your existing DMC server.
Run the installer with the following command and enter your existing OS user as the admin user and admin group:

/home/datical> sudo bash /datical-service-unix-<version>-master.sh

Enter the directory of the previous DMC installation when prompted for an install location.

The installer will update your installation and restart affected DMC services. You can begin using the new version of the DMC immediately.

If you have manually changed the Java version used by DMC, you will need to restore DMC’s default version of Java (11.0.8) before any time that you upgrade DMC. Move or copy Java 11.0.8 from the /opt/datical/old_jre directory back to the /opt/datical/jre directory before starting your DMC upgrade. DMC expects Java version 11.0.8 to be in the /opt/datical/jre directory for the DMC upgrade process to be successful. After completing your DMC upgrade, you can change to a different 11.x java version again. For more information, see How to Change the Java version for DMC. This link is vital if you are using v7.18 or later.

Liquibase Enterprise 8.9 Release Notes