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.
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.17
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.17.6410 | Choose the Linux or Windows installation file for your system. |
| Documentation | COMMON/Datical_Documentation/Datical_DB_Documentation | datical_db_docs_v6.17.pdf |
| Composite Installation Repository | COMMON/Datical_DB_Software/Datical_DB_6.1 | DaticalDbCompositeRepo-6.1 |
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.17 |
|
| Documentation | COMMON/Datical_Service_Documentation/ | DaticalServiceDocumentation_v6.17 |
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
Certification of Oracle 19c and Oracle 19c on Amazon RDS
Oracle 19c (direct installation and on Amazon RDS) has been fully tested and added to the platform configurations used in automated certification tests at Datical.
Generating Change Sets to Drop Stored Logic in the Deploy Packager
In previous releases, deleting a file from the SQL code repository that contained a stored logic object definition that had previously been packaged would result in a change set being added to the changelog.xml that dropped that object. To allow more precise control over when stored logic objects are dropped, this workflow has been changed.
BEHAVIOR CHANGE
As of Datical 6.17, deleting a stored logic file from the SQL code repository will no longer result in a drop of that object being added to the change log. File deletion will be noted in the log, but won't have any effect on the Datical Project.
To generate a change set to drop a stored logic object in version 6.17 and subsequent releases replace the object definition in the file with a valid drop SQL statement for that object. During the next execution of Deploy Packager for that project, the drop statement will be recognized and the appropriate change set created to drop the object in question.
Description of Change | SQL File Contents | Change Type Produced by Packager |
|---|---|---|
Create a procedure called | Contents of procPrintHelloWorld.sql CREATE OR REPLACE PROCEDURE procPrintHelloWorld
IS
BEGIN
DBMS_OUTPUT.PUT_LINE('Hello VIDEO_TEST_World!');
END;
| Change Produced by Packager <createProcedure path="procedure/20190827160559730_procPrintHelloWorld.sql" procedureName="procPrintHelloWorld"/> |
Drop a procedure called | Contents of procPrintHelloWorld.sql DROP PROCEDURE procPrintHelloWorld; | Change Produced by Packager <dropProcedure procedureName="procPrintHelloWorld"/> |
For more information see Writing SQL Scripts for Datical DB
Final Release of Datical Service with Docker & Kubernetes
We have updated the embedded Datical DB client and upgraded the following components of Datical Service to address vulnerabilities:
- Postgresql
- RabbitMQ
- Keycloak
- Groovy
6.17 marks the final release of Datical Service with Docker & Kubernetes. Datical will be release a new webapp for centralized status and reporting that is lighter weight and easier to manage in March 2020
Issues Addressed
| Issue ID | Description |
|---|---|
| DAT-3835 | Incorrect Packager log message "Found 1 TYPE statements in the SQL Script" when COMMENT contains "TYPE" |
| DAT-3677 | Packager: Provide Better Mechanism to Drop Stored Logic |
| DAT-3667 | DDB_USER and DDB_PASS environment variables do not work with "hammer groovy database_backup_restore.groovy" |
| DAT-3272 | TFS: Packager fails after a drop procedure or rename or revert procedure is attempted |
| DAT-2729 | Datical Eclipse GUI: missing data_dml option when creating Manifest file with the Datical DB GUI Manifest wizard |
| DAT-2608 | Hammer 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) | 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 Datical DB Version Requirements.