Versions Compared

Old Version 4

changes.mady.by.user Amy Smith

Saved on

compared with

New Version Current

changes.mady.by.user Amber Williams

Saved on

Key

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

...

Tip

Packager Access

Packager process now checks for read/write access to the database and SQL repos prior to packaging any files.

Associated Tickets: DAT-13122

Tip

enableRollbackOnError property improvement

The enableRollbackOnError property that was available for SQLPlus is also now available to EdbPlus and ClpPlus native tools. Learn more about the details at the link below.

Using the metadata.properties file

Associated Tickets: DAT-10947, DAT-14784

Desktop Client and CLI Updates and Issues Addressed

Issue ID

Description

DAT-15265

If Java 8 or above, including 11 Temurine, is present on a Windows 10 machine while installing Liquibase Enterprise, Liquibase will install successfully as expected. A “Liquibase Enterprise Installer requires java 8 or higher.” dialog will no longer appear.

DAT-14959

SSH options are available to users by default.

DAT-15347

StoredLogic is validated as expected on DB2 LUW when there is a null value for ERRORMESSAGE column in the SYSCAT.INVALIDOBJECTS table.

DAT-15260

The Packager report displays SQL Rule violations for all applicable scripts when multiple scripts fail validation. This is fully resolved by DAT-11434

DAT-14750

The project_creator.groovy script no longer adds unnecessary comments and release labels to the datical.project file.

DAT-14749

The project_creator.groovy file no longer errors when enable DdlLockTimeout and ddlLockTimeoutValue's are specified. The project_creator.groovy file properly adds the attributes to the datical.project file as expected.

DAT-14677

The Unable to determine the URL for database error no longer appears when configuring TNS

files

files with double quotes.

DAT-14131

Liquibase Enterprise no longer has performance issues when running the internal MigrateLabelData changeset.

DAT-13014

Comments at the end of files are ignored and no longer cause database exception errors for DB2 LUW and Oracle.

DAT-12937

Scripts packaged in data_dml and sql_direct folders via CLPPlus no longer save their .sql.log files to the DDB repository root directory. They are saved in the Reports directory for the Deploy Report. This directory does not save to the repo because it is located in the .gitignore file by default.

DAT-9729

A SqlParser error related to addPrimaryKey and schemaName substitution with multiSchema projects is resolved. The forIndexSchemaName is present in the parsed output from SqlParser.

DMC Issues Addressed

Issue ID

Description

DAT-15382

The DMC Heapdump Actuator endpoint is no longer exposed.

Please refer to the guide below for further information:
https://support.liquibase.com/knowledge/steps-to-resolve-exposure-of-credentials-and-confidential-information-in-deployment-monitoring-console

Info

An upgrade to DMC 8.4 will remove the need to resolve exposure of this endpoint using the manual steps provided.

DAT-15286

The DMC no longer truncates SQL scripts and output so errors can be seen successfully in the final deployment report tab.

DAT-7842

The Date Ran data is updated each time the AutoPermission (and AutoSynonym) rule is executed as expected.

DAT-13154

The troubleshooting command no longer throws an Out of memory error for Centos 8 unless the RAM falls below the 6 GB minimum.

Documentation for v8.4

Documentation is available in the following locations:

...

Info

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

Item

Path

File

Software

Datical_DB_Software/Datical_DB_8.4.66

Choose the Linux or Windows installation file for your system

Composite Installation Repository

Datical_DB_Software/Datical_DB_8.4.66

DaticalDbCompositeRepo

DaticalDBCompositeRepo-8.4.66.zip

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item

Path

File

Software

Datical_DMC_Software/Datical_DMC_8.4.366

datical-service-unix-8_4_366-master.sh

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

...

Expand
titleExpand for DMC update instructions

  1. Go to https://download.liquibase.com/ , download and copy the datical-service-unix-8_14_317366-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-8_14_317366-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 prior to 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 your DMC upgrade is complete, 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 especially important if you are using v7.18 or later.

...