| 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.
|
...
| 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:
- Confluence space - DDOC
- PDFs for Datical DB and Datical Service on software.datical.com
- Deployment Monitoring Console (DMC) Documentation Site
Datical DB
| Item | Path | File |
|---|---|---|
| Software | COMMON/Datical_DB_Software/Datical_DB_7.02.64656528 | Choose the Linux or Windows installation file for your system. |
| Datical DB Documentation | COMMON/Datical_Documentation/Datical_DB_Documentation | datical_db_docs_v7.02.pdf |
| Composite Installation Repository | COMMON/Datical_DB_Software/Datical_DB_7.02 | DaticalDbCompositeRepo- |
Datical Deployment Monitoring Console (DMC)
| Item | Path | File |
|---|---|---|
| Software | COMMON/Datical_DMC_Software/Datical_DMC_7.02.90137 | datical-service-unix-7_02_90137-master.sh |
| DMC Documentation | Online @ 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.
Simplified Installation, Configuration and Upgrade
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:
- DMC Documentation Home
- DMC Upgrade Guide
- DMC Install Configurations and System RequirementsUninstalling Datical Service (Versions 5.6 - 6.17)
- /wiki/spaces/CEDH/pages/1087734181
Issues Addressed
Datical DB Issues
| Issue ID | Description |
|---|---|
| DAT-4429 | Delayed Credentials not working for DMC with hammer commands |
| DAT-4302 | Update Postgres Setup instructions to address RDS issue with "REASSIGN OWNED BY" Postgres EDB and PostgreSQL Setup |
| DAT-4120 | Custom Forecast Rules run 2x for each changeset |
| DAT-4103 | Remove Environment Type field from Datical DB GUI |
| DAT-4079 | Forecast Report is misleading for changes packaged using SQL_DIRECT |
| DAT-3619 | Property substitution fails when labels values are used (Improved logging and recommendations to avoid this scenario) Setting Properties in the Project Changelog#UsingPropertiesforSchemaNames |
| DAT-2404 | Example scripts for Oracle Roles and Permissions should not use "$DaticalUser" Roles and Permissions for Datical DB on Oracle Database |
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
...
| 4416 | daticaldb.log file shows dbdef passwords in plain text when using NewDbDef / project_creator.groovy script to create project |
| DAT-4390 | Packager: Remove BOM from Sql_Direct scripts |
| DAT-4337 | Packager: 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 Liquibase Enterprise on DB2 LUW |
| DAT-4148 | Incorrect status message after Deploy with rule violation warning and deployThreshold="stopOnWarn" |
| DAT-2696 | Have releaseLocks use hammer installed drivers (instead of needing properties files for driver path): CLI Commands#releaseLocks |
| DAT-2837 | --log=path does not work (use --report instead): Command Options |
| DAT-2131 | Convert SQL: accept and use author agreement |
| DAT-2129 | Deploy Packager: Author Should Be Consistent Across Changesets |
Deployment Monitoring Console (DMC) Issues
| Issue ID | Description |
|---|---|
| PD-515 | More detailed documentation provided for creating and configuring an external Postgresql DMCDB. DMC Production Mode Instructions |
| DAT-4429 | Delayed Credentials not working for DMC with hammer commands |
| DAT-4306 | Installation: Allow fresh DMC install to use a previously populated DMCDB |
| DAT-4284 | Filtering columns reset columns width |
| DAT-4268 | Installation: Validate external database version during installation |
| DAT-4243 | Create datical-control command to update configuration of the DMCDB for a DMC installation |
| DAT-4187 | Reports page is not updated if click project name on the breadcrumb |
| DAT-4172 | DMC uninstall/reinstall in production mode fails. Database has orphaned connections. |
| DAT-3612 | Date entries for change sets in status views should be presented in the timezone of the logged in DMC user |
| DAT-2994 | Handle versionStrategy=DEPLOY_LATEST better in DMC Status |
| DAT-1953 | Show source file name (sql script filename) from changeset in DMC views |
| DAT-1474 | Enable sorting by date in DMC |
| DAT-1153 | Some views in DMC show local time but other views do not |