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

Software Downloads

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

Documentation for v7.18

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

Notifications

Upgrade to Java 11 Coming Soon

v7.18 is the last release to ship with Java 8. Future versions will ship with and require 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.

Deprecation of the 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 (compression driver) was removed from our driver repository in versions 7.16 and higher.  The driver was previously available with versions 7.15 and lower.

Deprecation of the “Deployer” License

v7.18 will be the last release to support the Deployer license type. If you are using this type of license to use the Desktop Client, you will need to upgrade to an Admin license prior to installing future versions. To see which license you have installed, go to File → License Manager.

Notable Changes

DATAPUMP Optimization: DAT-9580

In Liquibase v7.18 the default backup method (BackupRestoreOracleDatapump) used by packager for Oracle databases is optimized. The code was modified to capture log output more efficiently. This may result in significant performance gains when backing up Oracle REFDBs containing a large number of objects.

Issues Addressed

Issue ID

Description

DAT-10517

DAT-10508

DAT-10708

Fixed the rollback issue that affected MSSQL storedlogic changes when rolling back to a previously deployed version.

DAT-10342

DAT-2731

Fixed the issue on Windows causing Packager to fail when committing files to DDB repo because the filename or extension was too long. Most often this occurred after a branch merge containing hundreds of files.

DAT-10290

Fixed the issue causing SqlPlus SP2-0341 errors to be ignored. This caused the deploy report to show success when there was an error running the script.

DAT-10281

Fixed the issue causing certain comments in SQL scripts to be evaluated by Rules when they should be ignored.

DAT-10238

Fixed the issue in the Liquibase Enterprise Desktop Client edit connection dialog that enabled the password field even when runtimeCredentials=true.

DAT-10191

Fixed the issue with Azure SQL DB while using active Directory Password Authentication with an untrusted certificate.

DAT-10131

DAT-10105

DAT-10247

DAT-10246

Fixed the packager pipeline and feature merge issues. If the checksum does not match anything previously packaged or if if the changeSet related to the file in the archive is not found at all, a warning notifies the user and packager continues processing.

DAT-9412

Fixed the issue that caused packager backups to fail when an Oracle database had transparent data encryption enabled.

DAT-9289

Fixed the packaging failure that occurred when using sql_direct to package a MSSQL procedure.

DAT-9244

Added the ability to log output from a SELECT statement executed using a DB2 JDBC connection by a sqlFile change type.

DAT-9120

Fixed the issue causing a prompt for username and password when clicking Test Connection while configured to use Integrated Security.

DAT-7830

Fixed the DMC deadlock issue that occurred when multiple deployments are simultaneously in progress to the same pipeline.

DAT-2588

GUI: In the Status Details tab, the user would sometimes need to scroll to see the buttons. This has been resolved.

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)

Liquibase Enterprise & Business Clients (Datical DB)

Item

Path

File

Software

COMMON/Datical_DB_Software/Datical_DB_7.18.7313

Choose the Linux or Windows installation file for your system

Liquibase Enterprise Documentation

COMMON/Datical_Documentation/Datical_DB_Documentation

datical_db_docs_7.18.pdf

Composite Installation Repository

COMMON/Datical_DB_Software/Datical_DB_7.18.7313

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


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

datical-service-unix-7_18_247-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_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