Liquibase Enterprise was formerly known as Datical DB.

Skip to end of metadata
  • Created by Former user, last modified by Former user on Oct 07, 2021
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 7 Current »

Table of Contents

 Expand for 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.

Credential Prompts Don’t Work After Enabling and Then Disabling Runtime Credentials

If you enable and then disable Runtime Credentials for a project that has stored credentials for
dbDefs, the credentials will be cleared from the project. Running an operation (Status, Forecast, Deploy, and others.) when the project is in this state will prompt you for credentials, but the operation will fail with an authentication error. To work around this, re-enter the missing credentials using the Edit Connection dialog in the GUI for each of the effected dbDefs. 

This issue is fixed in 7.12 (and higher).

Checksum Validation Errors With sqlFile Change Types

An issue was introduced in the 7.11 release that causes Changeset validation errors when a Changelog contains sqlFile changes. sqlFile changes are created in one of two ways:

  • When using the Deployment Packager, putting scripts in the sqlfile directory or in a directory where packagemethod=sqlfile is set in the metedata.properties files will create them

  • When using the Changeset Wizard, selecting the Execute a SQL script file using JDBC option (formerly called the Custom SQL External File option) will create them

This issue is fixed in 7.12 (and higher).

Documentation for v7.11

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

Liquibase Enterprise & Business Clients (Datical DB)

Item

Path

File

Software

COMMON/Datical_DB_Software/Datical_DB_7.11.6980

Choose the Linux or Windows installation file for your system

Liquibase Enterprise Documentation

COMMON/Datical_Documentation/Datical_DB_Documentation

datical_db_docs_v7.11.pdf

Composite Installation Repository

COMMON/Datical_DB_Software/Datical_DB_7.11.6980

DaticalDbCompositeRepo-7.11.6980.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.

 Getting started with the Deployment Monitoring Console

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

Software

COMMON/Datical_DMC_Software/Datical_DMC_7_10_214

datical-service-unix-7_10_214-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.

 Expand for DMC update instructions

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

Notable Changes

Memory Utilization of Scripts That Produce a High-volume Output

In release 7.11, we optimized memory utilization of SQL scripts that produce a high-volume output. From now on, if you process scripts with a native executor in Datical DB, you can run them without any memory errors related to high-volume outputs. The same reporting experience as in the earlier releases is maintained.

Issues Addressed

Liquibase Business & Enterprise Issues

Issue ID

Description

DAT-5702

Packager: Show the error/warning when unable to commit to SCM in packagerReport.html.

DAT-5824

CLI: Improve the wording of confusing line in the hammer checkDrivers output.

DAT-6068

Packager returns a successful restore status, even though the restore fails (Oracle).

DAT-6347

Optimize Memory Utilization of Extreme SQL Scripts (for scripts that produce a high-volume output with a native executor)

DAT-6441

GUI: After importing a project, closing by using File > Exit causes the failure upon restart.

DAT-6463

GUI: Cannot add a new dbDef step or view Schema Management if URL cannot be created for dbDef using the TNSNAMES/LDAP connection.
Using version 7.11, you can:

  • Add new dbDefs to your pipeline even if there is a connection error with one of your other TNSNAMES/LDAP dbDef connections.

  • View the Schema Management information and change schema settings in the Settings tab even if URL for the dbDef cannot be created.

DAT-6725

Azure MI : Datical DB fails to deploy a baseline generated snapshot.
In release 7.10, we discovered that a baseline changelog cannot be deployed (Azure SQL Managed Instance only). The reason is that Azure SQL Managed Instance automatically manages XTP filegroups and files for databases containing In-Memory OLTP objects. It means that the XTP filegroup exists on Azure SQL Managed Database right after creation and the attempted deployment fails because it already exists.
The issue is fixed in release 7.11.

DAT-6921

Runtime Credentials Switch is not working

  • No labels

Copyright © Liquibase 2012-2022 - Proprietary and Confidential