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:

Log in to software.datical.com and go to COMMON/Java_JDK/OpenJDK
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
Close Datical DB if it's open, including Windows command line and Linux terminal sessions
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
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
Test the Datical DB GUI by launching the client to ensure it opens without issue
Test Datcial DB CLI by running 'hammer show version' from a terminal or or the Windows command line
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 v6.14

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

Confluence space - Liquibase Enterprise Documentation Home
PDFs for Datical DB and Datical Service on software.datical.com

Datical DB

Item	Path	File
Software	`COMMON/Datical_DB_Software/Datical_DB_6.14.6344`	Choose the Linux or Windows installation file for your system.
Documentation	`COMMON/Datical_Documentation/Datical_DB_Documentation`	`datical_db_docs_v6.14.pdf`
Composite Installation Repository	`COMMON/Datical_DB_Software/Datical_DB_6.14.6344`	`DaticalDbCompositeRepo-6.14.6344.zip`

Datical Service

NOTE: If you use Datical Service and also use the Internal Jenkins Client within Datical Service, note that you need to use the same version of Datical DB and Datical Service, such as Datical DB 6.9 and matching Datical Service 6.9. However, if you do NOT use the Internal Jenkins Client, you could run the current Datical DB 6.12 with Datical Service versions 5.8 or higher.

Item	Path	File
Software	`COMMON/Datical_Service_Software/Datical_Service_v6.9`	`datical-service-<version>.tar.part` - The main Datical Service files. `datical-jenkins-.part* -` (optional) Datical client used internally by Datical Service to run Datical operations. If you run operations from DMC (Forecast, Deploy), these files are required. `datical-service-preinstallcheck_<version>.sh` - Script to run a pre-installation check of your host environment and host resources to determine if the necessary resources are available for Datical Service. The script tells you if you need to make changes in its report. `datical-service-install.sh` - Script to run the installation.
Documentation	`COMMON/Datical_Service_Documentation/`	`DaticalServiceDocumentation_v6.9`

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

Notable In This Release

Fixed and Optimized Status Operations for General Performance Improvements

6.14 delivers bug fixes and performance optimizations for Status operations in the GUI & CLI. The performance issues with status affected many of our previous 2019.x and 6.x releases. We highly recommended that you update to 6.14 as a result.

Areas where you may notice improvements:

Status/Pipeline Status operations in the Datical DB UI
'status' & 'statusDetails' commands in the CLI
Complex operations which run status implicitly (CLI & GUI)
- All types of 'deploy' operations
- All types of 'rollback' operations
- Deploy Packager
- Convert SQL
- Change Log Sync

Issues Addressed

Issue ID	Description
DAT-4008	Part of GIT user password revealed in stdout when packager fails to perform final push to DDB repo with HTTPS url & special characters '%' or '{' are in password
DAT-3938	GUI: Deploy taking too long when the same dbDef is in multiple pipelines
DAT-3904	GUI: Status taking too long when multiple pipelines share the same dbDef
DAT-3830	Have the version be "INFO" level logging (instead of "DEBUG")
DAT-3803	Eclipse GUI: ClassCastException PlainPackageBinding cannot be cast to TypeBinding on WINDOWS
DAT-3733	Provide documentation for Datical CLI (hammer) silent install (UPDATED DOCUMENTATION) Using the CLI and the Composite Repository to install Liquibase Enterprise
DAT-3684	Oracle backup restore broken for single schema projects by unnecessary <schemas name=""/> node in datical.project files
DAT-3679	Generate SQL for Rollback Last Deploy Doesn't Work
DAT-3656	Command output from sqlcmd during deploy missing from daticaldb.log
DAT-3624	Better log and messaging when packager fails due to unsuccessful commit to SCM (near the end of packager)
DAT-3591	Passing --labels to hammer groovy deployPackager.groovy does not apply the labels to the changesets but does not throw error. Command needs labels without the --. (UPDATED DOCUMENTATION) CLI - Deployment Packager
DAT-3557	Generate rollback script in UI fails, when choosing Rollback Last Deploy
DAT-3176	GUI: New Deployment Plan: corrected hostname is not used for fetching schema list
DAT-2590	Packager: schemaName property in metadata.properties doesn't work if you put quotes around schema value
DAT-2586	Schema name in metadata.properties file is given case sensitive treatment
DAT-2195	Provide system requirements of how much memory is needed to package and deploy large DML scripts (UPDATED DOCUMENTATION) Recommendations for Working with Large DML Scripts

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)	Works	Does not work. Upgrade required.
Status run using new (2019.x/6.x)	Works	Works

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