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

Version 1 Next »

Software Downloads

Go to https://software.datical.com to download files.

Notifications

Coming Soon: New Location for Liquibase Enterprise Docs!

All Liquibase Enterprise Documentation will be available on docs.liquibase.com within the coming weeks! This new format will allow users to quickly find the documentation that caters directly to their user persona.

Notable Changes

The upgrade to Java 11 is here!

Liquibase Enterprise v8.0 and forward ships with and requires Java 11. If your installation uses a different JRE than the one bundled with Liquibase Enterprise, you will need to update this to Java 11 prior to installing future versions.

Upgrade Instructions

A fresh install is required for Liquibase Enterprise 8.0 to function successfully. Upgrading from 7.18 to 8.0 is using the Install New Software feature is not recommended. If installing to the same location, you will need to first uninstall the previous installation.

EDBPlus Upgraded to Java 11 Compatible Version

EDBPlus v14 is available in Liquibase Enterprise 8.0. This version is compatible with Java 11. EnterpriseDB customers should select this option during installation.

DMC Libraries Updated

Several dependent libraries used in DMC are upgraded. This resolves many recent vulnerabilities that were detected using vulnerability scanning software.

Rebrand from DaticalDB to Liquibase Enterprise

Liquibase Enterprise v8.0 is rebranded in most places to remove the previous Datical branding. This phase of rebranding is primarily cosmetic, while future releases may also rebrand filenames and the default workspace location. Users will be notified in advance of any functional changes.

DMC Issues Addressed

Issue ID

Description

DAT-10192

Fixed unique constraint violation that kept users from registering new projects in DMC that had the same DbDef names and Pipeline names as other projects.

DAT-10857
DAT-10856
DAT-10855
DAT-10854

Fixed DMC security vulnerabilities associated with SSL Strength, Cookie attributes, Content Security Policy Header, and the Browser Cache directive.

Other Issues Addressed

Issue ID

Description

DAT-9160

DAT-

DAT-

Fixed the issue that prevented psql change types from handling custom arguments. Psql change types can pass custom arguments successfully.

DAT-8884

Fixed the out of memory issue that occurred when packager ran with too large SQL files.

DAT-9507

DAT-9289

Fixed the SqlServer eror that occurred when statements existed prior to CREATE OR ALTER PROCEDURE.

DAT-8757

Fixed the forecast failure that occurred when Limited Forecast did not include autoSynonymForObjects changeset schemas in profiles.

DAT-11251

Fixed the Azure SQL Database packaging issue that caused packaging to fail.

DAT-10520

Fixed the --onlysql rollback option so users can produce a SQL script for rollback as intended.

DAT-10518

Fixed the storedlogic rollback issue that did not provide a generated SQL when --gensql, --onlysql, or --genrollbacksql were ran. These commands work as expected.

DAT-11139

Fixed the Oracle DATAPUMP issue so the optimization backup and restore method for packaging successfully works on Oracle 11g databases.

Known Issues

Stored Logic State

In release 7.13 and later, we discovered that existing stored logic was in an UNKNOWN state on a Deploy report, which caused deployment to fail. We have reviewed desired behavior and will implement a storedLogicValidityAction to warn, not error, when pre-existing objects that are not part of the deployment show changes from Valid to Invalid. (DAT-9156)

Limited Forecast does not include autoSynonymForObjects changeset schemas in profiling

In release 7.13 and later, if you use Limited Forecast in Oracle multi-schema projects with auto synonyms, you might get errors about the schema targeted by an auto synonym change being for a schema that cannot be managed, even though that schema is included in the project definition. If you encounter such errors with version 7.18, use Full Forecast instead of Limited Forecast. (DAT-8757)

Missing SSH Preferences in Liquibase Enterprise & Business 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, paste in this link: https://download.eclipse.org/releases/2018-12 then hit enter.

  3. Expand open the Collaboration category.

  4. Enable the checkbox to select Git integration for Eclipse, and then select Next to install it.

  5. When it finishes installing, you will be prompted to restart.

  6. Open File > Preferences > General > Network Connections. You should now have a new SSH2 option under Network Connections.

Liquibase Enterprise & Business cannot pick up SQLPATH environment variable on Windows

In release 7.6 and later, we updated the version of instantclient, which provides SQLPLUS 12.2.0.1.0. This version of SQLPLUS contains a bug: SQL PLUS 12.2 NOT OBSERVING SQLPATH IN REGISTRY OR ENV VARIABLE FOR LOGIN.SQL. As a workaround, use SQLPLUS 12.1 on Windows. (DAT-7598)

Documentation for v8.0

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

Choose the Linux or Windows installation file for your system

Composite Installation Repository

COMMON/Datical_DB_Software/Datical_DB_7.18.7336

DaticalDbCompositeRepo-7.18.7336.zip

Liquibase Deployment Monitoring Console (DMC)

Item

Path

File

Software

COMMON/Datical_DMC_Software/Datical_DMC_7.18.247

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

DMC Documentation

Online @ dmc.datical.com

<N/A>

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.

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.

 Getting Started with the Deployment Monitoring Console

DMC 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_18_247-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_18_247-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

Copyright © Liquibase 2012-2022 - Proprietary and Confidential