Versions Compared

Version Old Version 11 New Version Current
Changes made by

Amy Smith

Amy Smith

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Software Downloads

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

...

Note

DMC Users

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

Enhancements

Tip

New Ephemeral Database property ephemeralCleanUpBeforeStart

This ephemeral database property is set in the deployPackager.properties to allow and allows Liquibase to cleanup clean up 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, SqlServerSQLServer, and Postgres Ephemeral Packaging.

Associated Tickets: DAT-17246

...

Issue ID

Description

DAT-17246

Added A new Ephemeral Database property called ephemeralCleanUpBeforeStart is available. Setting this value to true will enable Liquibase to drop an existing ephemeral database or PDB in the event case of a previously failed Packager Operation. This property is applicable for applies to Oracle, SqlServerSQLServer, 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

Made updates to the diffChangelog and snapshot commands so that to include 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 You can override for a Service Name can be specified by specifying in the deployPackager.properties with:

  • oracleEphemeralCopyServiceName

The Default logic was changed for the handling of is updated to handle 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.comwill become datical_eph.dev.com. If a dot is not present absent in the value, the _eph suffix will be added to to the end of the source.

DMC Issues Addressed

...

Liquibase Enterprise & Business Clients (Desktop & CLI)

...

Item

Path

File

Software

Datical_DB_Software/Datical_DB_8.9.XXX449

Choose the Linux or Windows installation file for your system

Composite Installation Repository

Datical_DB_Software/Datical_DB_8.9.XXX449

DaticalDBCompositeRepo-8.9.XXX449.zip

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item

Path

File

Software

Datical_DMC_Software/Datical_DMC_8.9.XXX460

datical-service-unix-8.9.XXX460-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.

...

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

...

Expand
titleExpand for DMC update instructions

  1. Go to https://download.liquibase.com/ , download, and copy the datical-service-unix-<version>-master.sh, file to your existing DMC server.

  2. Run the installer with the following command and enter your existing OS user as the admin user and admin group:

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

  1. 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.

Info

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.

...