Liquibase Enterprise was formerly known as Datical DB.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

DATSoftware Downloads

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

Upgrade Notes

DMC Users

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

Notable Improvements

Certifications

Liquibase Enterprise added certifications for the following database versions:

  • Oracle 23c

Associated Tickets:

Enhancements

Blah

Blah Blah

Associated Tickets:

Desktop Client Updates, CLI Updates, and Issues Addressed

Issue ID

Description

DAT-15634

Added a new property internalRules.disabledDefaultRules for the daticaldb.properties which provides the ability to turn off Forecast Rules for ModifyDataType.

DAT-18096

Fixed an issue with the CLI showing an old license even though new license has been installed on the server. Licenses with 30 days or less remaining will now be replaced by any new license installation. See https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit/896566463?draftId=901611521&draftShareId=82e7539c-fd9d-410b-bd18-c5c77d7bc30f&. (update link once published)

DAT-18699

Increased the default Java Stack Size for CLI and GUI

SqlParser Issues Addressed

SqlParser issues apply to Oracle databases only.

Issue ID

Description

DAT-15854

Addressed an issue on the Forecast Report where the Table Impact Summary only reported the first drop of a multi-drop statement.

DAT-16944

Corrected an issue with multi-schema Oracle projects where DROP INDEX statements were failing with index does not exist errors when indexes referenced tables in another schema.

DMC Issues Addressed

Issue ID

Description

DAT-18536

Corrected an issue with sync operations for deleted pipelines where Packager operations had previously run on the deleted pipeline.

Error addressed was: ERROR: update or delete on table "dprj_environment" violates foreign key constraint "fk_dprj_packager_env_id" on table "dprj_deploy_packager"

This fix does not require a DMC update, but rather an update to the GUI or CLI to version 8.8.

Documentation for v8.8

Updated Documentation:

Documentation is available in the following locations:

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.8.XXX

Choose the Linux or Windows installation file for your system

Composite Installation Repository

Datical_DB_Software/Datical_DB_8.8.XXX

DaticalDBCompositeRepo-8.8.XXX.zip

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item

Path

File

Software

Datical_DMC_Software/Datical_DMC_8.8.XXX

datical-service-unix-8.8.XXX-master.sh

Liquibase Enterprise 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.

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

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

 

 Getting Started with the Deployment Monitoring Console

DMC Update Instructions

The process of updating the Deployment Monitoring Console to the latest version is similar to the installation process.

 Expand 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:

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

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.

  • No labels