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 10 Current »

The driver installation logic issue that occurred in Liquibase Enterprise 8.2 is resolved. All drivers install as expected in Liquibase Enterprise 8.2.7595. Find the latest download at the link below.

Software Downloads

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

Notifications

DB2 on zOS and LUW in v8.2.7595

Liquibase Enterprise is now compatible with DB2 on zOS and LUW starting in version 8.2.7595. It is important to note that new documentation on these topics is available at the links below.
Packaging with DB2 on zOS
DB2 on zOS Roles and Permissions for Liquibase Enterprise
JDBC Driver Installation for DB2 on z/OS
Roles and Permissions for Liquibase Enterprise on DB2 LUW

Notable Changes

Liquibase Enterprise: Supported Databases

We have expanded the databases supported by Liquibase Enterprise including:

PostgreSQL Community v14
PostgreSQL on Amazon RDS v14
EDB Postgres v13
Azure Database for PostgreSQL (single server type) v11
DB2 on z/OS v12.1.15


Find all supported database documentation at the link below.
Hardware, Software, and Database Requirements

Associated Tickets: DAT-11700, DAT-12384, DAT-10482, DAT-10226

Oracle Flashback for Backup and Restore

The new Oracle Flashback for Backup and Restore feature allows you to configure it with Deployment Packager, eliminating the need to install the client and expdp/impdp.

Learn more at the links below:
Using the Required deployPackager.properties File
Configure Deployment Packager to Use the Oracle Flashback for Backup and Restore

Associated Tickets: DAT-11444

Azure Postgres Setup Update

Liquibase Enterprise 8.2.7595 now supports Azure Database connection with Postgres. New content is available to learn how to configure said connection.
Postgres EDB, PostgreSQL, and Azure Database for Postgres Setup

Associated Tickets: DAT-12645

multiSubnetFailover

multiSubnetFailover is a new SqlServerDbDef property available in the 8.2.7595 release.
It allows you to connect to the availability group listener of a SQL Server availability group or a SQL Server Failover Cluster Instance.

Learn more at the link below:
Configuring Step Settings (DbDefs)

Associated Ticket: DAT-11914

DB2 on zOS Support and Packaging

DB2 on zOS is now supported with Liquibase Enterprise! Learn more about packaging and installing the JDBC driver at the links below.

Packaging with DB2 on zOS
JDBC Driver Installation for DB2 on z/OS

Associated Ticket: DAT-11700

DB2 on zOS Roles and Permissions

New content is available on the roles and permissions for DB2 on zOS.
DB2 on zOS Roles and Permissions for Liquibase Enterprise

Associated Ticket: DAT-11700

Database Migration Between DMC Demo Mode Instances guide

New content that covers Database Migration between Demo Mode instances is now available.
https://dmc.datical.com/install/demo-mode/dmc-demo-mode.htm?Highlight=Database%20Migration%20Between%20DMC%20Demo%20Mode
https://dmc.datical.com/install/demo-mode/demo-home.htm?Highlight=DMC%20Demo%20Mode

Associated Ticket: DAT-12361

Install the JDBC Driver for DB2 LUW and DB2 on z/OS guide

A new guide that covers installing the JDBC Driver for DB2 LUW and DB2 on z/OS is available. Specificially for DB2 on z/OS, you will need to add an environment property to specify a path to db2jcc_license_cisuz.jar file. Learn more at the link below.
JDBC Driver Installation for DB2 on z/OS

Associated Tickets: DAT-11698

Desktop Client and CLI Updates and Issues Addressed

Issue ID

Description

DAT-11914

multiSubnetFailover is available to use with SQLServer. It allows you to connect to the availability group listener of a SQL Server availability group or a SQL Server Failover Cluster Instance.

DAT-11700

DB2 on zOS is supported by Liquibase Enterprise

DAT-12384

Postgres Docker & Postgres RDS 14 are certified with Liquibase Enterprise

DAT-10482

Postgres EDB 13 are supported by Liquibase Enterprise

DAT-10226

Azure Database is certified for PostgreSQL v11 with Liquibase Enterprise.

DAT-10227

PSQL invalid port number error with Postgres Azure is resolved.

DAT-12677

Azure Postgres : Autogenerated snapshots that appeared in single and multi schema, if connected to public schema, now appear blank or contain content generated by Liquibase prior to running snapshot.

DAT-10212

Postgres: Setting the schemaName in the metadata.properties file for Postgres (non-EDB) resulted in incorrect ALTER SESSION syntax with sqlfile packageMethod. This has been resolved and packaging succeeds as expected.

DAT-12350

liquibase.exception.DatabaseException: ERROR: function inventory_in_stock(integer) does not exist error message no longer occurs during deployment

DAT-12006

Stack Trace is suppressed during logs for DMC connection issues when executing a rollback action.

DAT-11901

Valid MSSQL trigger displays correctly in the Deploy Report.

DAT-11698

The DB2 database driver for DB2 on zOS and DB2 LUW is updated to version 1.0.52.

DAT-11444

Oracle Flashback is available to use with Liquibase Enterprise. This improves the restore performance.

DAT-7853

Both CLI and GUI drivers can be installed simultaneously with the hammer installDrivers command.

DAT-8053

table_statistics and index_statistics are excluded by the BackupRestoreOracleExpdp class.

DMC Issues Addressed

Issue ID

Description

DAT-12192

Disabled users no longer appear on the Project Settings page even if they are assigned to a project.

DAT-12035

There is no longer a delay in Groups displaying on the User Settings page when a user is deleted from any group.

DAT-12033

You can add a project to a user from the User Settings page even when this user also belongs to a group that already has permissions to view this project.

DAT-12031

If a project is viewable only by a Group, you cannot select it on the User Settings Page. There is a tooltip available on the visible project that explains if the project is viewable by a group only

DAT-11913

The redundant Actions button was removed from the General Settings page.

DAT-11704

The column size in the tables in DMC can be resized however necessary for your project.

DAT-9371

The troubleshoot command recognizes certificates signed by non-standard signers.

Documentation for v8.2.7595

Documentation is available in the following locations:

Liquibase Enterprise & Business Clients (Desktop & CLI)

Item

Path

File

Software

COMMON/Datical_DB_Software/Datical_DB_8.2..7595

Choose the Linux or Windows installation file for your system

Composite Installation Repository

COMMON/Datical_DB_Software/Datical_DB_8.2.7595

DaticalDbCompositeRepo-8.2.7595.zip

Liquibase Enterprise Deployment Monitoring Console (DMC)

Item

Path

File

Software

COMMON/Datical_DMC_Software/Datical_DMC_8.2.331

datical-service-unix-8_2_331-master.sh

Starting with release 7.0, Liquibase 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 from version 7.0 or later 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-8_1_317-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-8_1_317-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