Versions Compared

Old Version 17

changes.mady.by.user Amy Smith

Saved on

compared with

New Version 18

changes.mady.by.user Amy Smith

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Software Downloads

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

Notable Improvements

Tip

Certifications

Liquibase Enterprise added certifications for the following database versions

  • EDB Postgres Advanced Server - 14 and 15

  • Microsoft SQL Server - 2022

  • Oracle - 21c

  • Oracle Amazon RDS - 21c

  • PostgreSQL Amazon RDS - 15

  • PostgreSQL Aurora - 14 and 15

  • PostgreSQL Community - 15

Associated Tickets: DAT-15858

Tip

Update of MSSQL JDBC driver

The MSSQL JDBC driver has been updated in this release. This update requires configuration changes regarding encryption.

It is important to note that the default value for the encrypt parameter was changed from false to true, which could cause potential issues. Learn how to navigate this configuration at the Associated Documentation link below.

Associated Tickets: DAT-15885

Associated Documentation: https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit-v2/3489464335?draftShareId=dbe6175f-c12f-4502-9b89-a6aa633db084&inEditorTemplatesPanel=auto_closed

Tip

Support for filenames and labels containing UTF-8 double-byte characters

Liquibase Enterprise now supports for UTF-8 alphanumeric characters such as ä, ö, ü, and ß which can be used in both filenames and labels.

Associated Tickets: DAT-16065

Associated Documentation: https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit/896569942?draftId=898957370&draftShareId=5417723b-5937-4855-acb2-b75f7d4d643a&

Enhancements

Tip

Rollback Report

A new Rollback Report is available in Liquibase Enterprise. The rollback report is similar to the deploy report and is accessible in the Reports folder of the Liquibase Project and in the Reports section of DMC.

Expand the “Sample Rollback Report” content below to see a sample Rollback Report.

Associated Tickets: DAT-9994

Associated Documentation: https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit/896570540?draftId=903839752&draftShareId=4b741473-90c3-4c8d-a2a5-d73dc8ecc038&, https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit/896570504?draftId=898039826&draftShareId=3a261273-663d-4f35-9d8a-0334229a9eef&,https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit/896828552?draftId=1069121545&draftShareId=a6aa0925-6191-46b8-acbd-a06349892af2&,https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/edit-v2/3111256073

Expand
titleSample Rollback Report
Tip

Oracle Datapump API Configuration Settings

Three new Oracle Datapump API configuration settings are now available. The properties are set in the deployPackager.properties file as:

  • oracleBackupNoDropSchema - prevents Liquibase from dropping the schema during the restore operation. Instead a dropAll function is used to drop tables, constraints, storedlogic, synonyms, and user types within that schema.

  • oracleBackupNoCrossSchemaFk - prevents Liquibase from backing up and restoring cross schema foreign keys during the Packager operation.

  • oracleBackupNoGrants - prevents Liquibase from backing up and restoring grants during the Packager operation.

Associated Tickets: DAT-15690

Associated Documentation: Use the Required deployPackager.properties File

Desktop Client and CLI Updates and Issues Addressed

Issue ID

Description

DAT-3558

Addressed issue where runtime command labels were missing after pipeline merge. Now runtime command labels will be appended to pipeline labels when merging pipelines.

DAT-9994

A Rollback Report has been added. The report is generated for rollback actions such as rollback lastDeploy and precise rollback.

DAT-11403

Certification for SQL Server 2022 was completed along with an MSSQL JDBC driver update.

DAT-13662

Corrected an issue where Oracle database connections were failing when the DEFAULT_ADMIN_CONTEXT value in the TNSnames file contained quotes.

DAT-15425

Corrected an issue where only the first dbDef pipeline label was being set when multiple dbDef pipeline labels were present.

DAT-15526

Certification for Oracle 21c and Amazon RDS Oracle 21c was completed.

DAT-15528

Certification for EDB Postgres Advanced Server 14 and 15 was completed.

DAT-15529

Certification for PostgreSQL 15 and Amazon RDS PostgreSQL 15 was completed.

DAT-15590

Corrected an issue for Oracle Flashback restore point creation if project name contains a dash (“-”).

DAT-15635

Addressed an ORA-00933 error when views contain a -- comment at the end of a script.

DAT-15690

Added three Oracle Datapump API configuration settings to control the backup and restore behavior during the Packager operation. Settings are oracleBackupNoDropSchema, oracleBackupNoCrossSchemaFk, and oracleBackupNoGrants. Further information can be found at Use the Required deployPackager.properties File.

DAT-15869

Corrected issue with Oracle SqlParser misinterpreting ADD POLICY ROW statements as columns.

DAT-15873

Corrected issue with Oracle SqlParser misinterpreting MODIFY LOB statements as columns.

DAT-15918

Certification for PostgreSQL on Amazon Aurora 14 and 15 was completed.

DAT-16009

Corrected issue where -replace file was not executing if committed before a corresponding -cleanup file.

DAT-16065

Added support for double-byte UTF-8 alphanumeric characters such as ä, ö, ü, and ß to be used for both filenames and labels.

DMC Issues Addressed

Issue ID

Description

DAT-9994

Reports section of DMC will now house any rollback reports generated by the GUI and CLI.

Documentation for v8.5

Documentation is available in the following locations:

Liquibase Enterprise & Business Clients (Desktop & CLI)

Info

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

Item

Path

File

Software

Datical_DB_Software/Datical_DB_<VERSION>

Choose the Linux or Windows installation file for your system

Composite Installation Repository

Datical_DB_Software/Datical_DB_<VERSION>

DaticalDBCompositeRepo-<VERSION>

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item

Path

File

Software

Datical_DMC_Software/Datical_DMC_<VERSION>

datical-service-unix-<VERSION>-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.

 

Expand
titleGetting 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
titleExpand 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:

Code Block
/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.

Info

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.