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 6 Next »

Software Downloads

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

Notable Improvements

Certifications

Liquibase Enterprise added certifications for the following database versions

  • Postgres 16 Community, Amazon RDS, Amazon Aurora

Associated Tickets: DAT-17376

Enhancements

Link from the Status screen to the corresponding Report in DMC

The Status screen has been updated with a link to the corresponding Report in DMC so that users are able to navigate easily to the SQL and other content for the change.

Associated Tickets: DAT-16723

 New link to move from Status screen to corresponding Report with SQL and other content
image-20240315-170030.png

Desktop Client and CLI Updates and Issues Addressed

Issue ID

Description

DAT-16703

The autoGenSQL truncates scripts if over 500+ lines.

DAT-16707

CheckProjectSchema.drl does not work with runtime credentials.

DAT-16749

ALTER PROCEDURE gets modified when packageMethod=storedlogic which causes it to be invalid.

DAT-16763

Changed behavior so that the Deploy Report shows a success if the Deploy portion of a Full Deploy is successful. Report will show a success even if the Change Simulation of the Full Deploy shows a warning or error.

DAT-17466

Certify RHEL 9 for DaticalDB.

DAT-17427

Changed behavior when multiple -replace and -cleanup files are added for a SQL script. Previously, the SQLRules were skipped for these additional -replace and -cleanup files. Now SQLRules are applied for all versions of -replace and -cleanup files.

DAT-17477

Postgres 13 ‘OR REPLACE’ is not supported and should not be added during packager.

DAT-17735

Provide additional information in the log when psql times out during a deployment

DAT-17742

Illegal char <“> when filename has UTF-8 characters and no [core] in git config

DMC Issues Addressed

Issue ID

Description

DAT-16723

Added link on the Status screen of the DMC that directs users to the corresponding Report for the changeset. This link allows uses to find and view the SQL that is associated with the changeset.

DAT-17466

Certified RHEL 9 support for DMC.

DAT-17478

Corrected an issue caused by removing environments with existing deployments in the DMC.

DAT-17487

Upgraded the embedded database shipped with DMC Demo Mode to PostgreSQL 15.

Documentation for v8.7

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

Choose the Linux or Windows installation file for your system

Composite Installation Repository

Datical_DB_Software/<version>

DaticalDBCompositeRepo-<version>.zip

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item

Path

File

Software

Datical_DMC_Software/<version>

datical-service-unix-<version>-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