Release Announcement Replication Server 7.3

This article was originally published on November 16, 2022

WHAT’S NEW

Highlights of this release include the following:

Enhancements

• Replication Server now provides the ability to define custom column data type mappings for replication of tables between Oracle and EDB Postgres Advanced Server or PostgreSQL.  The data types in the source and target databases must be of compatible types.
• Replication Server is now certified to work with the Microsoft provided SQL Server JDBC driver versions 10.2 and 11.2.  Although the open source  jTDS driver can still be used for connections to Microsoft SQL Server, it is recommended that the Microsoft provided SQL Server JDBC driver be used instead as it provides support for the more recent versions of SQL Server.
• Replication Server is now certified to work on the Debian 11 platform.
• The Synchronize process has been enhanced to optimize the “replicateDDL” operation so that it is able to complete within a reasonable time window during peak activity. [Support Ticket # 84057]
• Removed the limitation of only being able to add 1000 tables to a single Oracle Publication.

Security Fixes

• Updated the version of the zlib library provided with the Replication Server Windows installer to version 1.2.13 to address a security vulnerability identified in CVE-2022-37434.  This vulnerability is not present in the Linux distributions of Replication Server.

Bug Fixes

• Fixed an issue that results in Publication creation failure for trigger-based replication mode if two or more tables have the common name pattern. [Support Ticket # 83414]
• Fixed an issue encountered in a MMR cluster where the UPDATE-UPDATE conflict resolution might not discard some of the modified column values on the database node whose values are marked to be discarded. [Support Ticket # 83594] 
• Fixed an issue that causes the Synchronize operation to fail when an Oracle Publication table primary key is based on NCHAR/NVARCHAR type and the table contains a LOB column. 
• Fixed an issue encountered in a trigger-based MMR cluster where the history cleanup job is not configured to fire automatically for non-MDN nodes.
• Fixed an issue where the Synchronize operation fails if the standard_conforming_strings is off and the source Oracle column contains “\’” character combination.
• Fixed an issue where the “reloadconf” Rep CLI command reports success even when the conf file is not found. 

End-of-Support Reminder: 

We recommend you update to the most recent software version. If you have not yet updated to the most current version, please note the end-of-support notes below**: 

• Software: Replication Server 
• Version: 6.2
• End of Standard Support: May 25, 2023

**Additional details can be found at EDB Platform Compatibility.

NOTE: 

Version 7.x  provides a non-breaking upgrade path for existing 6.2.x  based cluster deployments; however, it is strongly recommended that the upgrade be verified in a staging or nonproduction environment before applying the upgrade in a production environment. 

For more information about Replication Server, please see the Replication Server Documentation.

This announcement is for EDB customers who are using, or are interested in Replication Server and have a subscription plan purchased for:

• Standard
• Enterprise

Replication Server 7.3 is available in EDB Repos in the form of RPM and DEB native packages. It is also packaged and delivered as interactive installers available on the EDB Downloads site. 

If you experience any problems around the installation, migration, upgrade or general use of your EDB software please contact our Technical Support teams.

Customers may reach us at the EDB Customer Support Portal, and we’re also available 24x7 via email and phone at the details below:

techsupport@enterprisedb.com

trial-help@enterprisedb.com

UK +44-2033719820

Brazil +55-2139581371

India +91-20-66449612