Liquibase Enterprise was formerly known as Datical DB.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Software Downloads

Go to https://download.liquibase.com/ to download files.

Enhancements

Ephemeral Packaging for Oracle Databases

For Oracle databases, two new backup restore methods are available that allow teams to create a temporary, or ephemeral, Ref DB for packaging changes. The functionality uses Oracle’s multi-tenant technology and requires the first database in the pipeline to be a pluggable database (PDB). A copy is created of this database during the packaging operation. Scripts eligible for packaging are applied to the copied database and the copy is destroyed at the end of the packaging operation. There are options to create the ephemeral database in the same CDB container as the first database in the pipeline using the BackupRestoreOracleEphemeralInternalPdb backup restore method or to create the copy in a second, or external CDB container using the BackupRestoreOracleEphemeralExternalPdb backup restore method.

Associated Tickets: DAT-13287

Associated Documentation: Configure Deployment Packager to Use an Oracle Ephemeral Database

Labels Filter added to Reports in DMC

A new column for Labels and an accompanying filter are available in the DMC under the Reports section. The label column allows users to search reports by script name or any other labels being used by the pipeline, such as release or ticket number.

Associated Tickets: DAT-16057

 New filter for Labels in Reports section
image-20240228-150018.png

Notable Improvements

Update of Oracle Instant Client and SQLPlus

Customers using Oracle should note that the Oracle Instant Client packaged with Liquibase Enterprise has been updated from 12c to 19c in Release 8.6. Customers using a SQLPlus native executor hosted outside the Liquibase Enterprise installation should consider updating their client to a 19c version as new versions of Oracle may not be compatible with the 12c client.

Associated Tickets: DAT-16005

Version 0 Rollback Support for PostgreSQL Stored Logic Scripts

Liquibase Enterprise now supports rollback to Version 0 of PostgreSQL stored logic scripts. Liquibase now tracks the initial content, or Version 0, of a PostgresSQL stored logic script prior to any modifications. This allows the Liquibase rollback to automatically return the object to its initial state or drop any newly created objects.

Note this change only applies to PostgresSQL as Version 0 support already existed for Oracle, SQLServer, and DB2 databases.

Associated Tickets: DAT-16594

Associated Documentation: PostgreSQL Server Database Objects and Packaging

Database Support

Oracle 12 and 18 are deprecated as of Liquibase Enterprise 8.6 and are no longer supported databases. Please consider updating to Oracle 19c or 21c.

Desktop Client and CLI Updates and Issues Addressed

Issue ID

Description

DAT-13287

Added the ability for Oracle to package changes on a temporary or ephemeral PDB database versus setting up a Ref DB in the pipeline.

DAT-13401

DAT-16038

Corrected an issue with scripts over 4000 characters failing to save to the DMC database.

DAT-14576

Corrected an issue with SQLParser for Oracle where indexes were being incorrectly generated for certain procedure scripts.

DAT-14604

Removed the requirement for an -ignore file to be 0-bytes. See Abandoning and Restoring a Changeset: ignore and unignore.

DAT-15077

Updated Red Hat Drools component from 7.17.0.Final to 7.48.0.Final to address EOL status for earlier version.

DAT-16005

Updated Oracle instant client packaged with Liquibase Enterprise from 12c to 19c.

DAT-16370

Corrected an issue with a -replace file not executing if committed before a -cleanup file.

DAT-16402

Removed repetitive Warning logging statements regarding oracleBackup settings.

DMC Issues Addressed

Issue ID

Description

DAT-15913

Added breadcrumbs and “Back to …” links on the Reports section to return to Project and/or Pipeline from the Reports page. Also added Pipeline Name column and accompanying filter to this page.

DAT-16057

Added labels column and accompanying filter to the Reports section of DMC.

Documentation for v8.6

Documentation is available in the following locations:

Liquibase Enterprise & Business Clients (Desktop & CLI)

Find the latest downloads here: https://download.liquibase.com/

Item

Path

File

Software

Datical_DB_Software/Datical_DB_8.6.290

Choose the Linux or Windows installation file for your system

Composite Installation Repository

Datical_DB_Software/Datical_DB_8.6.290

DaticalDBCompositeRepo-8.6.290.zip

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item

Path

File

Software

Datical_DMC_Software/Datical_DB_8.6.390

datical-service-unix-8.6.390-master.sh

Liquibase Enterprise includes a web-based Deployment Monitoring Console (DMC) that provides a centralized location to view a pipeline status and reporting information for all your Liquibase Business & Enterprise projects.

Liquibase Enterprise & Business Clients (Datical DB) and DMC Compatibility

Each DMC release only works with certain releases of Liquibase Enterprise Desktop. Consult the Deployment Monitoring Console Compatibility Matrix to ensure compatibility.

 

 Getting Started with the Deployment Monitoring Console

DMC Update Instructions

The process of updating the Deployment Monitoring Console to the latest version is similar to the installation process.

 Expand for DMC update instructions
  1. Go to https://download.liquibase.com/ , download and copy the datical-service-unix-<version>-master.sh file to your existing DMC server.

  2. Run the installer with the following command and enter your existing OS user as the admin user and admin group:

/home/datical> sudo bash /datical-service-unix-<version>-master.sh
  1. Enter the directory of the previous DMC installation when prompted for an install location.

The installer will update your installation and restart affected DMC services. You can begin using the new version of the DMC immediately.

If you have manually changed the java version used by DMC, you will need to restore DMC’s default version of Java (11.0.8) before any time that you upgrade DMC. Move or copy Java 11.0.8 from the /opt/datical/old_jre directory back to the /opt/datical/jre directory prior to starting your DMC upgrade. DMC expects Java version 11.0.8 to be in the /opt/datical/jre directory for the DMC upgrade process to be successful. After your DMC upgrade is complete, you can change to a different 11.x java version again. For more information, see How to Change the Java version for DMC. This link is especially important if you are using v7.18 or later.

  • No labels