Software Downloads

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

Customer Notices for Upgrades

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

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.9.6242`	Choose the Linux or Windows installation file for your system.
Documentation	`COMMON/Datical_Documentation/Datical_DB_Documentation`	`datical_db_docs_v6.9.pdf`
Composite Installation Repository	`COMMON/Datical_DB_Software/Datical_DB_6.9.6242`	`DaticalDbCompositeRepo-6.9.6242.zip`

Datical Service

If you use Datical Service, note that you need to use the same version of Datical DB and Datical Service. If you upgrade Datical DB, you need to upgrade Datical Service to the same version.

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

New Features

Deploy and Deploy Packager Overrides for the storedLogicValidityAction Project Setting

In 6.7 a new project setting (storedLogicValidityAction) was introduced that allows the user define whether a Deploy operation should treat deployments that result in new invalid stored logic objects as failed deployments. In this release an override for this project setting has been included for Deploy & Deploy Packager operations initiated from the CLI and the GUI. This override can be set in one of two ways:

In the "Deploy with Options" and "Deploy Packager" dialogs in the GUI, you can check or uncheck the option: Fail Deployments that produce new invalid object errors
When using the CLI to perform a deploy operation or run deployPackager.groovy, you can set the --invalidsAction option to one of the values below. NOTE: Option would be applied when Stored Logic Validity Check is not disabled.
- warn: Set to either warn (default), current behavior. New invalid stored logic will cause the Deploy to flag as deployment warning.
- fail: New invalid stored logic will cause a deployment to be marked as a failure.

For more information, consult the following pages:

Issues Addressed

Issue ID	Description
DAT-1948	Packager: Feature Merge Packager Reports Go To Wrong Directory
DAT-2459	Better error reporting when unable to find matching change set for developer workflow files (ignore, unignore, cleanup and replace)
DAT-3065	Eclipse GUI: Tracking Schema changes disappear when you mouse over the Tracking Schema field
DAT-3155 DAT-3201	Using project_creator.groovy and project_baseline.groovy force causes NullPointer Exception
DAT-3440	Update the Oracle Custom Backup & Restore Stub to Include DATAPUMP API Usage

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 (5.x)	Change deployed by new (2019.2+)
Status run using old	Works	Does not work. Upgrade required.
Status run using new	Works	Works

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