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 running Datical DB version 6.9 or lower, please use the full install process for 7.5 (NOT an upgrade/update process).
If you are running Datical DB version 6.10 or higher, you can use whichever process you prefer for 7.5 (full install or upgrade/update).
Documentation for v7.6
Documentation for the base release is available in the following forms:
Confluence space - Datical Product Documentation Home
PDFs for Datical DB on software.datical.com
Datical DB
Item | Path | File |
|---|---|---|
Software |
| Choose the Linux or Windows installation file for your system. |
Datical DB Documentation |
|
|
Composite Installation Repository |
|
|
Datical Deployment Monitoring Console (DMC)
With the 7.0 release Datical 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.
Deployment Monitoring Console Software and Documentation
Datical DB and DMC Compatability
Each DMC release only works with certain releases of Datical DB. Consult the Datical DB and Deployment Monitoring Console Compatibility Matrix to ensure compatibility.
Item | Path | File |
|---|---|---|
Software | COMMON/Datical_DMC_Software/Datical_DMC_7.6.192 |
|
DMC Documentation |
|
Deployment Monitoring Console Update Instructions
To upgrade from version 6.17 or earlier of Datical Service, consult the DMC Upgrade Guide
The process to update the Deployment Monitoring Console from version 7.0 or later to the latest version is very similar to the installation process. Consult the instructions below.
New Features
Kerberos Support for Oracle Connections
Kerberos is an authentication protocol that works based on tickets to provide strong authentication for client/server applications by using secret-key cryptography. The Kerberos authentication protocol doesn’t store passwords locally or send them over the Internet. As a Datical DB user, you can use the Kerberos authentication with Oracle 12, Oracle 18, and Oracle 19 without having to present passwords or certificates to it.
All Datical DB operations that are available for Oracle databases support the Kerberos authentication in the GUI and CLI. For more information consult the documentation: Kerberos authentication for an Oracle database
Proxy User Support for Oracle Connections
An Oracle proxy connection allows you to connect to an Oracle database with one user account and operate with the access and privileges of a different account. It is typically used to share access to a common database account that has required privileges with other database users without sharing the privileged account’s password. For more information on using Oracle proxy connections consult the documentation: Oracle Proxy User Connections
Deployment Packager Environment Lock When Backup or Restore Fails
When the backup or restore phase fails during execution of deployPackager.groovy, the RefDB may be left in a partially updated or otherwise invalid state. Future executions of deployPackager.groovy may fail or produce inaccurate results because of the invalid state of the RefDB. To prevent this scenario, deployPackager.groovy will now add a lock file to the Datical Project when backup or restore fails that will direct deployPackager.groovy to exit immediately and alert the user that the RefDB may be in an invalid state on subsequent runs. Once the RefDB has been restored to a known good state, the lock file may be removed manually or by adding a command line parameter to deployPackager.groovy. For more information consult the documentation: Recovering from a Backup or Restore Failure
Other Notable Changes
DATA_DML Package Method Creates Changesets With Oracle SQL Parser Disabled by Default
Using Oracle SQL Parser for large DML scripts can result in performance issues during Forecast and Deploy operations. Because these scripts should only include data modifications and Oracle SQL Parser is designed to provide insight into DDL operations, Oracle SQL Parser provides little to no value to DML scripts. Starting with version 7.6, Oracle SQL Parser will be disabled for scripts Packaged using the DATA_DML package method. If you wish to re-enable Oracle SQL Parser for scripts Packaged using the DATA_DML package method, you may do so by setting disableSqlParser=false in the metadata.properties for that directory or sub-directory. For more information consult the documentation: Using the metadata.properties file
Issues Addressed
Datical DB Issues
Issue ID | Description |
|---|---|
DAT-4972 | Hammer runRules command doesn't handle commas in filenames |
DAT-4912 | project_creator.groovy blocks creating a project with one dbDef in a pipeline |
DAT-4910 | Using project_creator.groovy with "replace" option creates both <auditDB> and <dmcDB> nodes in datical.project file |
DAT-4840 | RegisterProjectWithDMCDB doesn't handle delayed credentials |
DAT-4839 | ValidateStoredLogic doesn't handle delayed credentials |
DAT-4837 | ForceSync doesn't handle delayed credentials for dmcDbDef |
DAT-4836 | ClearCheckSums doesn't handle delayed credentials for dmcDbDef |
DAT-4835 | Enabling runtime credentials doesn't remove password from dmcDbDef |
DAT-4641 | sqlplus.exe can't start -- MSVCR100.dll was not found |
Deployment Monitoring Console (DMC) Issues
Issue ID | Description |
|---|---|
DAT-4956 | Exclude Intermediate Packager-Related Reports From Reports List |
DAT-4671 | Dead link when I click "Full Output" in forecastReport.html/deployReport.html in DMC |
DAT-5014 | DMC: LTS Java Version 11 to satisfy vulnerability scans |
Known Issues & Planned Deprecation of Features
Oracle Accelerator JDBC Driver
Because of a change in deployment trends and continued improvement of the performance of Datical DB, the Oracle Accelerator JDBC Driver will be removed from our driver repository and no longer supported no later than .
Known Issues with oracle Accelerator
Issue ID | Description |
|---|---|
DAT-4808 | Packaging with manifest is failing with timeout if oracle accelerator is enabled |
DAT-4375 | GUI :: Datical Accelerator connection issue |
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).