...
| Item | Path | File |
|---|---|---|
| Software | COMMON/Datical_DB_Software/Datical_DB_6.7.xxxx6180 | Choose the Linux or Windows installation file for your system. |
| Documentation | COMMON/Datical_Documentation/Datical_DB_Documentation | datical_db_docs_v6.7.pdf |
| Composite Installation Repository | COMMON/Datical_DB_Software/Datical_DB_ | DaticalDbCompositeRepo- |
Datical Service
If you use Datical Service, note that you need to use the same version of Datical DB and Datical Service. If you upgrade Datical DB, you need to upgrade Datical Service to the same version.
| Item | Path | File |
|---|---|---|
| Software | COMMON/Datical_Service_Software/Datical_Service_v6.7 |
|
| Documentation | COMMON/Datical_Service_Documentation/ | DaticalServiceDocumentation_v6.7 |
New Features
Oracle: Datapump API Support for Backup and Restore
You now have the choice of setting a Deployment Packager option that causes it to use the Oracle Datapump API to perform backup and restore during packaging.
The default method is to run expdp/impdp locally, which requires that you download it and call it through the Oracle Full Client.
If you set Deployment Packager to use the Oracle Datapump API, you do not need to install the Oracle full client or the expdp/impdp binaries.
See Configuring Deployment Packager to Use the Oracle Datapump API for Backup and Restore.
New Project Option: storedLogicValidityAction
You can now change the way failures in the stored logic validity check are handled. Currently a warning message is printed.
Staring Starting with v6.6 and v6.7:
- Use the Datical DB GUI to choose
warnorfailin thestoredLogicValidityActionoption. If set to fail, the deployment halts and prints an error when the stored logic validity check returns errors. - Use the CLI to set
invalidsActiontowarnorfail.
...
See storedLogicValidityAction in /wiki/spaces/DDOC66/pages/892539125 in Configuring Project Settings.
Issues Addressed
Fixes Provided in v6.7
(INTERNAL NOTE: Before release, "x" prefix means this fix was done in v6.6, which did not ship. The "x" will be removed before v6.7 ships)
...
Version Numbers
Starting with this version (v6.7), we are returning to delivering releases using a sequential version numbering scheme.
Previously we experimented with a quarterly feature release scheme and produced maintenance releases for bug fixes between the feature releases.
Documentation on Confluence
Starting with this version (v6.7), we are returning to a single, centralized documentation space on Confluence. It is updated for every release.
If you stay on a release, you can get a PDF of the documentation for that release from software.datical.com.
Documentation Spaces for Individual Releases
See DDD in the Releases with Doc Spaces section for a list of spaces available.
Issues Addressed
| Description | ||
|---|---|---|
| DAT-1924 | SQL Parser: Quick Deploy still calls SQL Parser. | |
| xDATDAT-2018 | Doc + Test: Add documentation of hammer runRules to Datical CLI References page. See /wiki/spaces/DDOC66/pages/892540203See CLI Commands#runRules. | |
| DAT-2116 | Ignore version 0 change sets from status operations | |
| xDATDAT-2122 | In the deploy report, ID column is overwriting the Author column when sql filename is long | |
| xDATDAT-2214 | DOC + TEST: Work around instructions for when packager has forecast errors due to SQL Parser limitations. See "Debugging Procedures..." in /wiki/spaces/DDOC66/pages/892539609in Using SQL Parser. | |
| DAT-2236 | "Full Output" link in forecast report not working if forecast was successful | |
| xDATDAT-2396 | DOCUMENTATION ONLY: Provide instructions on how to add labels using the logical operators AND and OR in the dbDef settings See new instructions and examples: /wiki/spaces/DDOC66/pages/892539688 | xDAT|
| DAT-2509 | Packager: Convert_sql should not run stored logic validity check | |
| xDATDAT-2773 | DOC + TEST :: Set NLS_LANG for Oracle Sqlplus Character Issues. See updates in /wiki/spaces/DDOC66/pages/892539754.xDATin Writing SQL Scripts for Liquibase Enterprise. | |
| DAT-2801 | DOC & TEST :: Configuration of Schema Name for Multi-Catalog. Always use fully-qualified object names in SQL scripts for multi-database projects. See updates: xDAT | |
| DAT-2873 | DOC & TEST: Update ALPHANUMERIC packagerOrderStrategy with a useful example (attached) See example in /wiki/spaces/DDOC66/pages/892539710. xDAT | |
| DAT-2946 | Spaces in SQL file names fails to forecast and deploy in higher DbDefs | |
| xDATDAT-2953 | Implement Oracle Backup/Restore Using Datapump Packages. See /wiki/spaces/DDOC66/pages/893059122.xDATSee Configuring Deployment Packager to Use the Oracle Datapump API for Backup and Restore. | |
| DAT-2963 | DOC - GUI crashes / cannot access existing projects after installing new 2019.2.x GUI | |
| xDATDAT-3018 | Add new project property :: storedLogicValidityAction. See storedLogicValidityAction in /wiki/spaces/DDOC66/pages/892539125Configuring Project Settings | |
| DAT-3093 | As a user, when I successfully package a valid cleanup change set, I get an error (only in my daticaldb.log) which is misleading and confusing | |
| DAT-3111 | DOCUMENTATION ONLY: As a user, I need to know how to increase RAM performance used by Datical on Windows OS | |
| DAT-3227 | DOC Infrastructure - move back to centralized doc space | |
| DAT-3239 | GUI: "Identifier" field in "Edit Connection" dialog is not properly reverting or saving data | |
| DAT-3271 | Liquibase checksum mismatch for Unique Constraint changes deployed prior to 2019.2.2 - See Known Issues, "Checksum Errors..." |
Known Issues
Editing a Connection with Datical DB GUI
...
Checksum Errors when Performing Status on Deployed AddUniqueConstraints Changes
...
Datical now notes version matching for clients working on the same release pipeline. See Datical DB Liquibase Enterprise Version Requirements.