Go to https://software.datical.com to download files. See details for the release below.
Starting with the 6.10 release, Datical DB will run in the OpenJDK runtime instead of the Oracle Java runtime.
|
Documentation for the base release is available in the following forms:
Item | Path | File |
---|---|---|
Software | COMMON/Datical_DB_Software/Datical_DB_7.3.6587 | Choose the Linux or Windows installation file for your system. |
Datical DB Documentation | COMMON/Datical_Documentation/Datical_DB_Documentation | datical_db_docs_v7.3.pdf |
Composite Installation Repository | COMMON/Datical_DB_Software/Datical_DB_7.3 | DaticalDbCompositeRepo- |
Item | Path | File |
---|---|---|
Software | COMMON/Datical_DMC_Software/Datical_DMC_7.3.159 | datical-service-unix-7_3_159-master.sh |
DMC Documentation | Online @ dmc.datical.com | <N/A> |
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 7.3 is very similar to the installation process. Consult the instructions below.
|
The Deploy Packager will fail if it detects any errors during the Restore phase, which reverts the Reference DB to its last known good state. Many times in Oracle environments, errors will be generated during restore that won't negatively impact Packaging activity. We have provided a new setting in the deployPackager.properties
file that will let you list the Oracle error codes that can be safely ignored during the restore phase.
Property Name | oracleRestoreErrorWhitelist |
Property Description | A comma separated list of Oracle error codes to be ignored when evaluating
Example: oracleRestoreErrorWhitelist=ORA-31684,ORA-39111,ORA-39151 |
At the end of every Deploy and Deploy Packager operation Datical performs tasks to ensure that the environment is prepared for future use. When a Deploy or Deploy Packager job is prematurely terminated due to user intervention or a catastrophic failure, the operating environment can be left in a state that prevents the subsequent execution of jobs. The conditions that can block future jobs are:
locked
state. This lock is used to ensure one client is updating a database at a time to prevent concurrent operations from colliding with one another.locked
state (Oracle environments only. This table is used to capture error messages for reporting purposes during the execution of sqlplus
scripts.To assist users in cleaning up these conditions Datical has provided the following utilities:
releaseLocks
command will clean up the DATICAL_SPERRORLOG
table in addition to unlocking the DATABASECHANGELOGLOCK
tableThe releaseLocks
command can be used to unlock the locked DATABASECHANGELOGLOCK
. It will now also look for and drop the DATICAL_SPERRORLOG
if it detects that the target database is Oracle. If it is unable to perform either task an informative error will be displayed. Click here for more information on the releaseLocks
command.
cleanup
mode that will run the releaseLocks
command and restore the Reference DatabaseThe Deploy Packager's cleanup mode takes care of all three conditions that can block future operations. Below is an example of running Deploy Packager in cleanup mode.
/home/datical/<MyBlockedProject>/hammer groovy deployPackager.groovy pipeline=mypipeline cleanup |
For more information check out the Deploy Packager Documentation
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.
To get started with DMC check out the following documentation resources:
Issue ID | Description |
---|---|
DAT-4516 | Forecast is Executing non-DML sql_direct SqlPlus Scripts when dmlForecast=true |
DAT-4493 | Add New Packager Cleanup Option How To: Use ReleaseLocks Command and Packager with Cleanup Option |
DAT-4492 | Make releaseLocks command production ready |
DAT-4453 | Packager with convert packageMethod throws 'ERROR: type modifier is not allowed for type "_int4"' for postgres array type field int[] |
DAT-4213 | Allow Management of Manual Interruptions to Packaging & Deploy Operations How To: Use ReleaseLocks Command and Packager with Cleanup Option |
DAT-4167 | CX :: GUI :: There is only one attempt to enter a valid AuditDB password |
DAT-4166 | CX :: GUI :: Mixed Delayed Credentials do not work with AuditDB |
DAT-4027 | GUI: Snapshot breaks Runtime Credentials |
DAT-3841 | multiCatalog="true" when you have Oracle dbDefs should throw an error that more closely indicates it is a settings mismatch |
DAT-3788 | Ability to specify which ORA- errors to be handled as warning only (instead of failing packager) |
Issue ID | Description |
---|---|
DAT-4460 | Render reports in DMC instead of downloading them |
DAT-4424 | PHX - Inconsistent navigation if no known operation in an environment |
See Customer Success Resources in the Releases with Doc Spaces section for a list of spaces available for older releases (prior to 6.7).