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

Software Downloads

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

Notifications

Upgrade Instructions For This Release

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

Installation still requires a minimum of Java 8 to be installed on the operating system beforehand.

Coming Soon: Revamped 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.

All relevant content from the existing Liquibase Enterprise Documentation in Confluence and DMC Documentation sites will be migrated.

Notable Changes

Java JRE & Eclipse Upgrades

Liquibase Enterprise 8.0 and forward ships with and requires a Java 11 runtime environment. Previous versions used Java 8.

If your installation uses a different JRE than the one bundled with Liquibase Enterprise, you will need to update to Java 11 prior to running Liquibase Enterprise 8.0.

Also in version 8.0 we have upgraded the underlying Eclipse framework to the latest version. This enables us to use the latest libraries and maintain defenses against security vulnerabilities.

See the Notifications section for upgrade instructions.

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 Security Enhancements

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

For Postgres :: Allow custom psql arguments to be used in <appdba:psql> change types.

DAT-8757

For Oracle :: Fixed the forecast failure occurring with Auto-Synonym changesets in limited forecast mode. The workaround of switching to full forecast mode is no longer necessary.

DAT-11251

For Azure SQL Database :: Accommodate dashes in database names that caused failure during backup / restore.

DAT-10518

Rollback :: Fixed issue where stored logic was not being included in generated SQL when using the --gensql option on the rollback command.

DAT-11139

For Oracle :: Fixed issue with backup/restore on Oracle 11g databases when using BackupRestoreOracleDatapump.

DAT-10663

For Oracle :: Fixed issue in forecast with sql parser enabled when using indexes on materialized views.

DAT-10142

For Oracle :: Fixed issue in forecast with sql parser enabled to allow reserved keyword PERIOD as a valid column name.

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)

Documentation for v8.0

Documentation is available in the following locations:

Liquibase Enterprise Desktop & CLI Client

Item

Path

File

Software

COMMON/Datical_DB_Software/Datical_DB_8.0.7416

Choose the Linux or Windows installation file for your system

Composite Installation Repository

COMMON/Datical_DB_Software/Datical_DB_8.0.7416

DaticalDbCompositeRepo-7.18.7416.zip

Liquibase Deployment Monitoring Console (DMC)

Item

Path

File

Software

COMMON/Datical_DMC_Software/Datical_DMC_8.0.267

datical-service-unix-8_0_267-master.sh

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 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 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-8_0_267-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-8_0_267-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