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

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

Confluence space - Liquibase Enterprise Documentation Home - Starting with v6.7, this space will be updated each release.
PDFs for Datical DB and Datical Service on software.datical.com

Datical DB

Item	Path	File
Software	`COMMON/Datical_DB_Software/Datical_DB_6.7.6180`	Choose the Linux or Windows installation file for your system.
Documentation	`COMMON/Datical_Documentation/Datical_DB_Documentation`	`datical_db_docs_v6.7.pdf`
Composite Installation Repository	`COMMON/Datical_DB_Software/Datical_DB_6.7.6180`	`DaticalDbCompositeRepo-6.7.6180.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.7`	`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.7`

New Features

New Project Option: storedLogicValidityAction

You can now change the way failures in the stored logic validity check are handled. Currently a warning message is printed.

Starting with v6.7:

Use the Datical DB GUI to choose warn or fail in the storedLogicValidityAction option. If set to fail, the deployment halts and prints an error when the stored logic check returns errors.
Use the CLI to set invalidsAction to warn or fail.

Additional methods for setting this option will come in a future release.

See storedLogicValidityAction in Configuring Project Settings.

Version Numbers

Starting with this version (v6.7), we are returning to delivering releases using a sequential version numbering scheme.

Previously we experimented with a quarterly feature release scheme and produced maintenance releases for bug fixes between the feature releases.

Documentation on Confluence

Starting with this version (v6.7), we are returning to a single, centralized documentation space on Confluence. It is updated for every release.

If you stay on a release, you can get a PDF of the documentation for that release from software.datical.com.

Documentation Spaces for Individual Releases

See Customer Success Resources in the Releases with Doc Spaces section for a list of spaces available.

Issues Addressed

Fixes Provided in v6.7

(INTERNAL NOTE: Before release, "x" prefix means this fix was done in v6.6, which did not ship. The "x" will be removed before v6.7 ships)

ID	Description
xDAT-1924	SQL Parser: Quick Deploy still calls SQL Parser.
xDAT-2018	Doc + Test: Add documentation of hammer runRules to Datical CLI References page. See CLI Commands#runRules.
DAT-2116	Ignore version 0 change sets from status operations
xDAT-2122	In the deploy report, ID column is overwriting the Author column when sql filename is long
xDAT-2214	DOC + TEST: Work around instructions for when packager has forecast errors due to SQL Parser limitations. See "Debugging Procedures..." in Using SQL Parser.
DAT-2236	"Full Output" link in forecast report not working if forecast was successful
xDAT-2396	DOCUMENTATION ONLY: Provide instructions on how to add labels using the logical operators AND and OR in the dbDef settings See new instructions and examples: Datical Labels
xDAT-2509	Packager: Convert_sql should not run stored logic validity check
xDAT-2773	DOC + TEST :: Set NLS_LANG for Oracle Sqlplus Character Issues. See updates in Writing SQL Scripts for Datical DB.
xDAT-2801	DOC & TEST :: Configuration of Schema Name for Multi-Catalog. Always use fully-qualified object names in SQL scripts for multi-database projects. See updates: Multi-database Projects SQL Server Database Objects and Packaging
xDAT-2873	DOC & TEST: Update ALPHANUMERIC packagerOrderStrategy with a useful example (attached) See example in Choosing a Packaging Method.
xDAT-2946	Spaces in SQL file names fails to forecast and deploy in higher DbDefs
xDAT-2953	Implement Oracle Backup/Restore Using Datapump Packages. See Configuring Deployment Packager to Use the Oracle Datapump API for Backup and Restore.
xDAT-2963	DOC - GUI crashes / cannot access existing projects after installing new 2019.2.x GUI
xDAT-3018	Add new project property :: storedLogicValidityAction. See `storedLogicValidityAction` in Configuring Project Settings
DAT-3093	As a user, when I successfully package a valid cleanup change set, I get an error (only in my daticaldb.log) which is misleading and confusing
DAT-3111	DOCUMENTATION ONLY: As a user, I need to know how to increase RAM performance used by Datical on Windows OS
DAT-3227	DOC Infrastructure - move back to centralized doc space
DAT-3239	GUI: "Identifier" field in "Edit Connection" dialog is not properly reverting or saving data
DAT-3271	Liquibase checksum mismatch for Unique Constraint changes deployed prior to 2019.2.2 - See Known Issues, "Checksum Errors..."

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 Datical DB Version Requirements.

Datical v6.7 - Release Notes