Liquibase Enterprise was formerly known as Datical DB.

Liquibase Enterprise v7.12 - Release Notes

Table of Contents

Software Downloads

Go to https://software.datical.com to download files. See details for the release below. 

Known Issues

Missing SSH Preferences in Liquibase Enterprise GUI

After upgrading Datical DB to later versions, you might have issues with the SSH feature being unavailable to generate the SSH key via the Eclipse GUI. To return SSH in Preferences, follow these steps:

  1. In the Datical DB GUI, select Help > Install New Software.

  2. In the Work with field of the Install dialog box, enter https://download.eclipse.org/releases/2018-12.

  3. Select Git integration for Eclipse, and then select Next to install it.

  4. Open Preferences. You should see SSH2 under Network Connections.

Documentation for v7.12

Documentation for the base release is available in the following forms:

Liquibase Enterprise & Business Clients (Datical DB)

Item

Path

File

Item

Path

File

Software

COMMON/Datical_DB_Software/Datical_DB_7.12.7036

Choose the Linux or Windows installation file for your system

Liquibase Enterprise Documentation

COMMON/Datical_Documentation/Datical_DB_Documentation

datical_db_docs_v7.12.pdf

Composite Installation Repository

COMMON/Datical_DB_Software/Datical_DB_7.12.7036

DaticalDbCompositeRepo-7.12.7036.zip

Liquibase Deployment Monitoring Console (DMC)

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.

To get started with DMC, check out the following documentation resources:

Deployment Monitoring Console Software and Documentation

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

Each DMC release only works with certain releases of Liquibase Enterprise & Business Clients (Datical DB). Consult the Datical DB and Deployment Monitoring Console Compatibility Matrix to ensure compatibility.

Item

Path

File

Item

Path

File

Software

COMMON/Datical_DMC_Software/Datical_DMC_7.12.216

datical-service-unix-7_12_216-master.sh

DMC Documentation

Online @ dmc.datical.com

<N/A>

Deployment Monitoring Console Update Instructions

The process of updating the Deployment Monitoring Console from version 7.0 or later to the latest version is similar to the installation process.

  1. Go to software.datical.com, download and copy the datical-service-unix-7_12_216-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-7_12_216-master.sh

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

Notable Changes

Oracle SQL Parser usability improvements

In release 7.12, we improved the Oracle SQL Parser usability, which allows you to benefit from forecast capabilities for Oracle SQL scripts packaged through the DIRECT package method. The main fixes include constraints and indexes. See the following table with the issues addressed for more details.

Issue ID

Description

Issue ID

Description

DAT-4118

SQL Parser: a nested create index statement in the unique constraint for create table breaks the parser.

DAT-4581

SQL Parser unable to forecast the unique index and primary key when scripted within the CREATE TABLE command. In release 7.12, we fixed the following:

  • The issue with the generation of the create index change related to a primary key constraint:

    • The column tag generated incorrectly for multiple columns

  • The issue with the generation of the create index change related to unique constraints:

    • The column tag generated incorrectly for multiple columns

    • The tableName attribute missed for the generated create index change

DAT-5171

SQL Parser: duplicate index forecast errors if script drops an index and then creates an index. SQL Parser does not model the drop of the index, which results in duplicate index error. 

DAT-5943

SQL Parser: the forecast fails when packaging a CREATE MATERIALIZED VIEW script that contains the clause USING INDEX TABLESPACE.

DAT-6779

SQL Parser adds an incorrect SELECT statement with scripts that are altering partitions.

DAT-7013

SQL Parser: parentheses and semicolon symbols ); in a create table ddl script lead to the creation of a tag changeset.

Issues Addressed

Liquibase Business & Enterprise Issues

Issue ID

Description

Issue ID

Description

DAT-5850

Alignment and line ending deviation between the sql_direct and procedure folders. Procedures packaged through the sql_direct folder have alignment issues. From now on, the script can be formatted and aligned similarly regardless of the packaging folder.

DAT-6529

A false forecast rule failure when more than one script is packaged.

DAT-6766

Packager missed scripts that were merged and reverted in git. The packager logic has been enhanced to check for all the needed files.

DAT-6813

Liquibase Enterprise support for Db2 LUW 11.5.

DAT-6827

The stored logic versioning does not work as expected as it cannot be reverted by copying an older version from the SCM. When Packager runs, it cannot package a new version of the updated script. From now on, you can check a copy of the previous version of the code and get a new versioned changeset created for it.

DAT-6922

GUI: Unable to run operations after enabling and then disabling runtime credentials.

DAT-7062

The issue with calculating checksum for sqlFile after the DaticalDB upgrade. In release 7.11, we discovered that a changelog which contains sqlFile Change Types causes checksum validation errors. The issue is fixed in release 7.12.

DAT-7222

Azure MI: connection retry logic is broken due to updates in Azure PITR (point in time restore). The issue is fixed in release 7.12. When using Azure MI, you need to grant the appropriate permissions: GRANT VIEW SERVER STATE TO [#{dbusername}]. See Roles and Permissions for Datical DB and Azure SQL Managed Instance.

Deployment Monitoring Console (DMC) Issues

Issue ID

Description

Issue ID

Description

DAT-6850

DMC sequences can get out-of-sync and cause an error: the insert or update on the table dprj_deploy_packager violates a foreign key constraint. The error makes projects unusable or does not allow the creation of projects. Packager reports cannot be uploaded to projects. The issue is fixed in release 7.12.

DAT-6858

The DMC foreign key constraint issue: Packager results should be warning/success (not error/failure)

DAT-6869

The DMC project auto-registration causing foreign key constraint violations.

If your project includes the DMCDB connection information but it was not registered with the DMCDB, you need to run the registerprojectwithdmcdb command from the CLI. Alternatively, open the project in the Datical DB GUI and register the project from the DMC Database section of the Settings tab.

 

Copyright © Liquibase 2012-2022 - Proprietary and Confidential