Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version 2

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Software Downloads

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

Customer Notices for Upgrades

Warning

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.

Expand
titleOpenJDK 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


...

Warning

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_67.170.6410XXXXChoose the Linux or Windows installation file for your system. 
Datical DB DocumentationCOMMON/Datical_Documentation/Datical_DB_Documentationdatical_db_docs_v6v7.170.pdf
Composite Installation RepositoryCOMMON/Datical_DB_Software/Datical_DB_67.170.6410XXXXDaticalDbCompositeRepo-67.170.6410XXXX.zip

...

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.

...

  • 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 Spaces for Older Releases

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

Note
titleBEHAVIOR 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 procPrintHelloWorld

Code Block
languagesql
titleContents of procPrintHelloWorld.sql
CREATE OR REPLACE PROCEDURE procPrintHelloWorld
IS
BEGIN
  
  DBMS_OUTPUT.PUT_LINE('Hello VIDEO_TEST_World!');

END;
Code Block
languagexml
titleChange Produced by Packager
<createProcedure path="procedure/20190827160559730_procPrintHelloWorld.sql" procedureName="procPrintHelloWorld"/>

...

Drop a procedure called procPrintHelloWorld

...

Code Block
languagesql
titleContents of procPrintHelloWorld.sql
DROP PROCEDURE procPrintHelloWorld;
Code Block
languagexml
titleChange 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

...

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. 

...