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.

...

2

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

Datical DB

ItemPathFile
SoftwareCOMMON/Datical_DB_Software/Datical_DB_7.02.6465XXXXChoose the Linux or Windows installation file for your system. 
Datical DB DocumentationCOMMON/Datical_Documentation/Datical_DB_Documentationdatical_db_docs_v7.02.pdf
Composite Installation RepositoryCOMMON/Datical_DB_Software/Datical_DB_7.02.6465DaticalDbCompositeRepo-7.02.6465XXXX.zip

Datical Deployment Monitoring Console (DMC)

ItemPathFile
SoftwareCOMMON/Datical_DMC_Software/Datical_DMC_7.02.90XXdatical-service-unix-7_02_90XX-master.sh
DMC DocumentationOnline @ dmc.datical.com<N/A>

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

...

Recent Additions to the Datical DB Product Line

Deployment Monitoring Console (DMC) 

With the 7.0 release Datical is offering included a new, lightweight web-based Deployment Monitoring Console (DMC) that provides status and reporting information for all of your Datical projects through a browser.  The new DMC is a simpler replacement for Datical Service that is much easier to install, manage and use. 

...

The new Deployment Monitoring Console was built to get you up and running fast.  Hardware requirements have been greatly simplified to reduce the time it takes to requisition a suitable system and reduce the overall operational costs of the solution. The new installer workflow is simpler and more intuitive.  Upgrading to new versions beyond 7.0 will be as easy as running the new installer on the system where the previous version is installed. 

Controlled Access to Database Deployment Information

The new DMC still uses Keycloak to manage user authentication and authorization.  This allows you to integrate the DMC with your existing LDAP solution in order to simplify user management and control what data individual users have access to. 

Centralized Operational Reports and Status Details for All of Your Projects, Pipelines and Databases

The DMC provides several views into your organization's database deployment data so that you can quickly understand where your database changes have been deployed and where they haven't. It also acts as the central repository for Datical's detailed operational reports.  Users can now easily self service requests about database status and deployment outcomes as easily as they can log into their email or banking website.

To get started with DMC check out the following documentation resources:

Issues Addressed

Datical DB Issues

Issue IDDescription
DAT-4302Update Postgres Setup instructions to address RDS issue with "REASSIGN OWNED BY" Postgres EDB and PostgreSQL Setup4429Delayed Credentials not working for DMC with hammer commands
DAT-4120Custom Forecast Rules run 2x for each changeset4390Packager: Remove BOM from Sql_Direct scripts
DAT-41034390Packager: Remove Environment Type field from Datical DB GUIBOM from Sql_Direct scripts
DAT-4079Forecast Report is misleading for changes packaged using SQL_DIRECT
DAT-3619Property substitution fails when labels values are used (Improved logging and recommendations to avoid this scenario) Setting Properties in the Project Changelog#UsingPropertiesforSchemaNames
DAT-2404Example scripts for Oracle Roles and Permissions should not use "$DaticalUser" Roles and Permissions for Datical DB on Oracle Database4416daticaldb.log file shows dbdef passwords in plain text when using NewDbDef / project_creator.groovy script to create project
DAT-4337Packager: Remove BOM from All Packaging Scripts
DAT-4277

Handle Rollback Last Deploy Precondition for Multi-Catalog

DAT-4168

CX :: DiffChangeLog (with append option) fails for addFileGroup changeset and with reverse substitution enabled

DAT-4150

Reduced Required Privileges for Backup and Restore with DB2 LUW Roles and Permissions for Datical DB on DB2 LUW

DAT-4148Incorrect status message after Deploy with rule violation warning and deployThreshold="stopOnWarn"

Deployment Monitoring Console (DMC) Issues

Issue IDDescription
PD-515More detailed documentation provided for creating and configuring an external Postgresql DMCDB. DMC Production Mode Instructions 
DAT-4429Delayed Credentials not working for DMC with hammer commands
DAT-4306Installation: Validate external database content before install
DAT-4284Filtering columns reset columns width
DAT-4268Installation: Validate external database version during installation
DAT-4187Reports page is not updated if click project name on the breadcrumb
DAT-4172

DMC uninstall/reinstall in production mode fails. Database has orphaned connections.

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. 

...