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

Software Downloads

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

Customer Notices for Upgrades

Starting with the 6.10 release, Datical DB will run in the OpenJDK runtime instead of the Oracle Java runtime. If you are installing release 6.10 or greater of Datical DB from scratch in it's own folder, the installer will provide the new OpenJDK runtime. There are no additional steps for you to take.  This is the recommended course of action.

If you are updating an older version of Datical DB (6.9 or earlier) using the Datical software update site or the composite repo, you will need to replace the old Oracle Java runtime with the OpenJDK runtime.  For instructions expand the link below.

 OpenJDK Update - Manual Instructions

Datical DB now runs on OpenJDK

Starting with the 6.10 release, Datical DB will bundle OpenJDK instead of the Oracle Java Runtime.  The decision to migrate was prompted by a change in Oracle's licensing that would have impeded our ability to provide security patches to the Java distribution in our frequent releases.

NOTE: Datical will only install the new Java distribution as part of a fresh install of the product.  If you prefer to update an existing installation using Datical's update site or the composite repo follow the steps below to manually replace the Oracle Java Runtime with OpenJDK:

  1. Log in to software.datical.com and go to COMMON/Java_JDK/OpenJDK
  2. Download the archive for your client platform
    1. Linux: OpenJDK8U-jre_x64_linux_hotspot_8u222b10.tar.gz
    2. Windows: OpenJDK8U-jre_x64_windows_hotspot_8u222b10.zip
  3. Close Datical DB if it's open, including Windows command line and Linux terminal sessions
  4. Rename the root folder of the current JRE in the Datical installation
    1. BEFORE: <DDB_INSTALL_ROOT>/jre
    2. AFTER:    <DDB_INSTALL_ROOT>/oracle.jre
  5. Extract the JRE archive downloaded in step 2 to the Datical DB Install root
    1. Extracting the archive should create a new directory that will need to be renamed 
      1. Extracted directory name: <DDB_INSTALL_ROOT>/jdk8u222-b10-jre
      2. Rename directory to: <DDB_INSTALL_ROOT>/jre
  6. Test the Datical DB GUI by launching the client to ensure it opens without issue
  7. Test Datcial DB CLI by running 'hammer show version' from a terminal or or the Windows command line
  8. At this point you may delete <DDB_INSTALL_ROOT>/oracle.jre at your leisure


If you are upgrading from version 5.12 or earlier, see Customer Notices for Upgrades from 5.12 or Earlier to v2019.x or Later for important information before you install or upgrade. 

Installation for the Datical DB GUI client requires special attention. 

Documentation for v7.0

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

Datical DB

ItemPathFile
SoftwareCOMMON/Datical_DB_Software/Datical_DB_7.0.XXXXChoose the Linux or Windows installation file for your system. 
Datical DB DocumentationCOMMON/Datical_Documentation/Datical_DB_Documentationdatical_db_docs_v7.0.pdf
Composite Installation RepositoryCOMMON/Datical_DB_Software/Datical_DB_7.0.XXXXDaticalDbCompositeRepo-7.0.XXXX.zip

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

New Features

Issues Addressed

Issue IDDescription
DAT-3835Incorrect Packager log message "Found 1 TYPE statements in the SQL Script" when COMMENT contains "TYPE"
DAT-3677Packager: Provide Better Mechanism to Drop Stored Logic
DAT-3667DDB_USER and DDB_PASS environment variables do not work with "hammer groovy database_backup_restore.groovy"
DAT-3272TFS: Packager fails after a drop procedure or rename or revert procedure is attempted
DAT-2729Datical Eclipse GUI: missing data_dml option when creating Manifest file with the Datical DB GUI Manifest wizard
DAT-2608Hammer forecast or deploy output shows "unable to determine pipeline" when --pipeline is not used

Known Issues

Checksum Errors when Performing Status on Deployed AddUniqueConstraints Changes

If you deploy AddUniqueConstraint changes using Datical DB v6.7 or later AND you deploy changes using an older version of Datical DB, you get errors during Status operations. The error is reported when the status command performs checksum validation. Checksum creation was changed in version 2019.2. 

Starting in v6.7, the Status operation accepts "old" checksums. However, if you attempt a Status operation using an old client, it reports an error on changes deployed by a new client.  

  • Old - before version 2019.2
  • New - version 2019.2 or later

Change deployed by old (4.x/5.x)Change deployed by new (2019.x/6.x))
Status run using old (4.x/5.x)WorksDoes not work. Upgrade required.
Status run using new (2019.x/6.x)WorksWorks

Datical now notes version matching for clients working on the same release pipeline. See Datical DB Version Requirements. 


  • No labels

Copyright © Liquibase 2012-2022 - Proprietary and Confidential