Liquibase Enterprise was formerly known as Datical DB.

Liquibase Enterprise v7.7 - Release Notes

Owned by Former user (Deleted)
Last updated: Nov 17, 2022 by Roderick Bowser
4 min read

Software Downloads

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

Customer Notices for Upgrades

In recent releases Liquibase Enterprise and Liquibase Business has introduced newer versions of third party utilities to improve performance and maintain security

  • Starting with the 6.10 release, Liquibase Enterprise will run in the OpenJDK runtime instead of the Oracle Java runtime

  • Starting with the 7.6 release, Liquibase Enterprise will run Oracle Instant Client 12.2

Please use the full install process for the desktop client GUI when upgrading from Liquibase Enterprise or Business 7.5 or earlier to Liquibase Enterprise or Business 7.7 (NOT an upgrade/update process):

  • If you are running version 7.5 or lower, please use the full install process for the desktop client GUI with 7.7 (NOT an upgrade/update process).

  • If you are running version 7.6, you can use whichever process you prefer for the desktop client GUI with 7.7 (full install or upgrade/update).

Documentation for v7.7

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

Choose the Linux or Windows installation file for your system. 

Liquibase Enterprise Documentation

COMMON/Datical_Documentation/Datical_DB_Documentation

datical_db_docs_v7.7.pdf

Composite Installation Repository

COMMON/Datical_DB_Software/Datical_DB_7.7.6783

DaticalDbCompositeRepo-7.7.6783.zip

Liquibase Deployment Monitoring Console (DMC)

With the 7.0 release Liquibase included a new, lightweight web-based Deployment Monitoring Console (DMC) that provides status and reporting information for all of your Liquibase Business & Enterprise projects through a browser.  The new DMC is a simpler replacement for Datical Service that is much easier to install, manage and use. 

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 Compatability

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

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

DMC Documentation

Online @ dmc.datical.com

<N/A>

Deployment Monitoring Console Update Instructions

To upgrade from version 6.17 or earlier of Datical Service, consult the DMC Upgrade Guide

The process to update the Deployment Monitoring Console from version 7.0 or later to the latest version is very similar to the installation process. Consult the instructions below.

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

     

  3. When prompted for an install location, enter the directory of the previous DMC installation

  4. The installer will update your installation and restart effected DMC services.  You can begin using the new version of the DMC immediately.

New Features

Mark Deployment as Failed When Stored Logic Correction Attempt Is Unsuccessful

We have extended the cases that result in a deployment being marked as a failure when the “Fail Deployments that produce new invalid object errors.“ In previous releases, we treated the case of an object being invalid before and after a Deploy operation as a warning regardless of whether a new version of the object was included in the Deployment. This case will now be treated as a Deployment failure. Consult the table below for scenarios and their expected outcomes.

Object Status Before Deploy

Deploy Operation

Object Status After Deploy

Deploy Outcome

Object Status Before Deploy

Deploy Operation

Object Status After Deploy

Deploy Outcome

Invalid

New version of the object is deployed

Invalid

Fail

Invalid

No change to the object

Invalid

Warn

Invalid

New version of the object is deployed

Valid

Pass

DMC DB Password Obscured for Non-Administrator Accounts When DMC is Installed in DEMO Mode

In previous versions, the DMC DB password was readable by any logged in account on the Client Connect page when the DMC was installed in DEMO Mode. In 7.7 and later versions, only Administrator accounts will be able to view this password in DEMO mode by default. Instructions to enable display of the password to non-administrator accounts can be found in the DMC Documentation.

Recent Notable Changes

(Enterprise & Business 7.6) DATA_DML Package Method Creates Changesets With Oracle SQL Parser Disabled by Default

Using Oracle SQL Parser for large DML scripts can result in performance issues during Forecast and Deploy operations. Because these scripts should only include data modifications and Oracle SQL Parser is designed to provide insight into DDL operations, Oracle SQL Parser provides little to no value to DML scripts. Starting with version 7.6, Oracle SQL Parser will be disabled for scripts Packaged using the DATA_DML package method. If you wish to re-enable Oracle SQL Parser for scripts Packaged using the DATA_DML package method, you may do so by setting disableSqlParser=false in the metadata.properties for that directory or sub-directory.

For more information consult the documentation: https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/896570155

Issues Addressed

Liquibase Business & Enterprise Issues

Issue ID

Description

Issue ID

Description

DAT-5336

SqlServer procedures and views that reference column names ending in 'go' are truncating the column name resulting in errors

DAT-5228

UTF-8-BOM file results in Packager error "Unable to detect character encoding for script"

DAT-5146

Metadata-variables substitution doesn't work with CONVERT

DAT-5049

Packager: metadata.properties errors if schema property includes a period

DAT-4970

Checksum error when using Cleanup/Replace and Merge to another Branch

DAT-4846

CLI: hammer newDbDef stores credentials unexpectedly when creating delayed credential dbDefs

DAT-4722

Packager: Next run blocked by uncommitted delete of .sql.tmp file in Resources folder

DAT-4623

Packager: CREATE OR REPLACE FORCE VIEW fails as: "Unknown filetype - unknown_storedlogic."

DAT-4301

With storedLogicValidityAction=fail, I package a script which updates an existing storedLogic; initially in INVALID state and after deployment is still INVALID, I want the deploy operation to fail

DAT-317

Enhancement Request: Move "Change Log Properties Used" section up higher in Forecast and Deploy html reports

Deployment Monitoring Console (DMC) Issues

Issue ID

Description

Issue ID

Description

DAT-4957

DMC - Customer does not want Client Connect information showing for non-SysAdmin users

Known Issues & Planned Deprecation of Features

Oracle Accelerator JDBC Driver

Because of a change in deployment trends and continued improvement of the performance of Datical DB, the Oracle Accelerator JDBC Driver will be removed from our driver repository and no longer supported no later than Feb 19, 2021 .

Known Issues with Oracle Accelerator

Issue ID

Description

Issue ID

Description

DAT-4808

Packaging with manifest is failing with timeout if oracle accelerator is enabled

DAT-4375

GUI :: Datical Accelerator connection issue

 

Documentation Spaces for Older Releases

See Customer Success Resources in the Releases with Doc Spaces section for a list of spaces available for older releases (prior to 6.7). 

Copyright © Liquibase 2012-2022 - Proprietary and Confidential