Qlik Replicate Release notes - May 2022 Initial Release to Service Release 2

Charlton_Book — Mon, 28 Nov 2022 13:08:19 GMT

Table of Contents

Qlik Replicate Release notes - May 2022 Initial Release

In addition to these release notes, customers are encouraged to read the IR (Initial Release) release notes for all versions later than their current version as well as the cumulative release notes for the last Service Release of the previous version.

Migration and upgrade

This section describes the issues that you may encounter when upgrading/migrating to the new version.

Upgrade paths

Qlik supports four Replicate versions (including this one).

Direct upgrade is supported from the last two versions only (including any service releases for those versions). The last two versions are Replicate November 2021 and Replicate May 2021.

Upgrading from Replicate April 2020 (6.6)
If you are upgrading from Replicate April 2020 (6.6), you need to perform the following upgrades:

Upgrade to November 2020 (7.0).
Upgrade to Replicate November 2021.
Upgrade to Replicate May 2022.

Upgrading from unsupported versions

If you are upgrading from Replicate 6.x (starting from 6.3), you need to perform the following upgrades:

Upgrade to Replicate 6.5.
Upgrade to Replicate November 2020 (7.0).
Upgrade to Replicate November 2021.
Upgrade to Replicate May 2022.

If you are upgrading from Replicate 5.5, please contact Qlik Support.

Microsoft .NET Framework 4.8 upgrade/installation prerequisite

Using the Setup Wizard – It is preferable for .NET Framework 4.8 to be installed on the Replicate Server machine before running Setup. If .NET Framework 4.8 is not present on the machine, Setup will prompt you to install it. This may require the machine to be rebooted when the installation completes.
Silent Installation – When recording an Install Shield Silent response file (ISS), the recording must be done on a machine with .NET 4.8 already installed on it as the silent installation process does not include a separate installation of .NET framework 4.8.

Deleting the Replicate self-signed certificate after upgrade

After upgrading, customers that are using Replicate's self-signed certificate (i.e. instead of their own certificate) should perform the following procedure:

Delete all *.pem files from <replicate_data_folder>/ssl/data.
Restart the Attunity Replicate Server service.

This will cause Replicate to generate a new self-signed certificate, thereby ensuring that the certificate will be accepted by newer clients (browsers) that select the more secure TLS 1.3 protocol.

Note that if you do not perform the above procedure, the following error will be encountered when connecting to Replicate Console:

SYS,GENERAL_EXCEPTION,The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

Upgrading an installation with multiple data folders

When upgrading a Replicate installation with multiple Data folders, only the default Data folder (<Product_ Dir>\Data) will be automatically upgraded. The other Data folders need to be updated manually by running the following command:

repuictl.exe -d <data_folder_path> setup install

Compatibility with related products

Qlik Replicate May 2022 is compatible with the following related products only:

Qlik Enterprise Manager May 2022 or later
Compose May 2022 or later
Compose for DataLakes Apri l2020 (6.6)

Databricks on AWS and Microsoft Databricks Delta - data type mapping changes

In earlier versions, when replicating to Databricks on AWS or Microsoft Databricks Delta, the Replicate STRING data type was mapped to STRING. From this version, when replicating to Databricks 8.x or later, STRING will be mapped to VARCHAR (length).

As support for the VARCHAR data type was introduced in Databricks 8, creating a task that replicates to Databricks 8.x and then downgrading to a Databricks version earlier than 8 (in the same task) is not supported.

What's new?

This section describes the new and enhanced features introduced in Qlik Replicate May 2022.

What's new in endpoints?

New Salesforce (Incremental Load) source endpoint

This version introduces support for the Salesforce (Incremental Load) source endpoint. Though similar to the existing Salesforce (Streaming CDC) source endpoint (previously called Salesforce), there are significant differences in their implementation.

Full Load: Salesforce (StreamingCDC) uses Bulk API v1 for Full Load while Salesforce (Incremental Load) uses Bulk API v2.
CDC: Salesforce (StreamingCDC) uses the Salesforce Streaming API which is subject to several limitations, although it does provide better performance. Salesforce (Incremental Load) is based on change polling which, although slower than Salesforce (Streaming CDC), has the advantage of supporting almost all Salesforce objects.

The decision which endpoint to use (Incremental Load or Streaming CDC) will depend on your specific replication requirements, such as the objects you need to replicate and latency considerations. To get a better idea of which endpoint is more suitable for your business needs, review the limitations and considerations for each endpoint in the online help.

The main differentiators are:

Incremental Load supports a wider set of Salesforce objects and Bulk API v2, with polling based CDC every X minutes.
Streaming CDC supports low latency capture of data changes from Salesforce from a limited set of objects.

What's new in engine?

New task notification for CDC interruptions

The new No changes were captured in the last <n> minutes notification will alert you if no changes were captured from the source database within the specified time limit. With most databases, receiving this notification will usually indicate a connectivity problem. However, with the following databases, it could simply mean that no changes occurred during the specified period.

Microsoft SQL Server
IBM DB2 for LUW
IBM DB2 for iSeries

When the task resumes capturing changes, an additional notification that change capture has resumed will be sent, and the notification timer will be reset.

New default action for data truncation errors when using parallel apply

Previously when using the Apply batched changes to multiple tables concurrently option, the default error-handling action for data truncation errors would be to suspend the relevant table. Now, if a data truncation error is encountered, the default will be to ignore the record and continue the replication of the table.

FIPS Compliance

Supported from Replicate May 2022 Service Release 02 only.

FIPS (Federal Information Processing Standards) is a set of standards developed by the United States Federal Government for use in computer systems. FIPS 140-2 is the subset of standards which defines approved encryption algorithms used for handling sensitive information. Replicate will work in FIPS mode if the following prerequisites have been met:

A FIPS-compliant Replicate version must be installed. To obtain the FIPS-compliant version, contact Qlik Support. Upgrading from a non FIPS-compliant Replicate is not supported. You need to uninstall your current version before installing the FIPS-compliant version. Once you have installed the FIPS-compliant version, the next Replicate version that you upgrade to does not need to be FIPS-compliant (as you will already have all the FIPS-compliant software on your machine).
The operating system on which Replicate is installed is running in FIPS mode.

INSERT optimization

A new Optimize inserts option has been added to the Change Processing Tuning tab in the task settings. In order to use the new option, Apply changes using SQL MERGE must be turned on. When both of these options are tuned on and the changes consist of INSERTs only, Replicate will perform INSERTs instead of using SQL MERGE. Note that while this will usually improve performance and thereby reduce costs, it might also result in duplicate records in the target database.

The Apply changes using SQL MERGE and Optimize inserts options are available for tasks configured with the following target endpoints only: * Google Cloud BigQuery * Snowflake on Azure, Snowflake on Google, and Snowflake on Amazon

Support for replacing endpoint values using the Enterprise Manager API

This version adds the ability to edit specific endpoint values using the Enterprise Manager API. When not editing the value directly in the user interface, this was previously only possible using export, edit, and import operations. The functionality is available through the PatchEndpoint method, which is available in all of the APIs (REST, .NET, and Python).

"Use SSL" renaming
The Use SSL option in the notification email settings has been renamed to the more accurate Use secure email (SMTPS).

End of life/support features

This section provides information about End of Life versions, End of Support features, and deprecated features.

End of support

Endpoint versions
Support for the following source endpoint versions has been discontinued:

IBM Informix 11.5 and 11.7
MariaDB 10.0.x (starting from 10.0.24)
PostgreSQL 9.5
Sybase ASE 12.5, 15, 15.5, and 15.7
MySQL 5.6

Support for the following target endpoint versions has been discontinued:

MariaDB 10.0.x (starting from10.0.24)
PostgreSQL 9.5
Sybase ASE 12.5, 15, 15.5, and 15.7
MySQL 5.6

Microsoft Internet Explorer Browser

Microsoft Internet Explorer is no longer supported.

"Backup folder preprocessing" command in the Microsoft SQL Server source endpoint

The Backup folder preprocessing command option has been deprecated from the Microsoft SQL Server source endpoint and will cease to be available from Replicate November 2022. From this version, it can only be accessed using an internal parameter.

Newly supported versions and third-party software

Target endpoint versions
The following target endpoint versions are now supported:

Actian Vector 6.0
All Databricks endpoints: 9.1 LTS
Vertica11.x Supported from Replicate May 2022 Service Release 02 only.
Oracle21.x

Microsoft Edge browser support

This version introduces support for accessing the Replicate console using the Chromium-based Microsoft Edge browser.

Windows Server 2022 support
This version introduces support for running Qlik Replicate on Windows Server 2022.

Supported from Replicate May 2022 Service Release 02 only.

Resolved defects and customer-requested enhancements

This section lists the issues resolved since the Replicate November 2021 initial release.

For information about issues resolved in subsequent Replicate May 2022 Service Releases, refer to the Replicate May 2022 cumulative release notes (Qlik_Replicate_May2022_ Release_Notes_Accumulated.pdf) for the relevant service release. You can download the cumulative release notes from https://community.qlik.com/t5/Downloads/tkb-p/Downloads.

Qlik Replicate May 2022

Jira issue: RECOB-4971
Salesforce case: 19856
Type: Issue
Component/Process: Task Manager

Description: When a table configured to use Parallel Load was reloaded while Full Load was still in progress, the existing load processes would not be stopped. This would result in duplicate records on the target.

Jira issue: RECOB-4947
Salesforce case: 25690
Type: Issue
Component/Process: IBM DB2 for iSeries

Description: When the IBM DB2 for iSeries journal contained entries for objects not included in SYSTABLES (which might occur when not using a table-name filter, for example) the task would stop unexpectedly. The issue was fixed by issuing a warning and continuing the task.
In addition, the maximum number of tables in a filter has been increased to 10000.

Jira issue: RECOB-4993
Salesforce case: N/A
Type: Issue
Component/Process: SAP HANA Source

Description: CTS (Commit timestamp) trigger-based based capture mode would replicate the local timestamp for the change instead of UTC.

Jira issue: RECOB-4975

Salesforce case: 24134

Type: Issue

Component/Process: SAP HANA Source

Description: In CTS (Commit timestamp) trigger-based based capture mode, when starting the task from the current time, it would take a long time for CDC to start.

Jira issue: RECOB-4754

Salesforce case: 11912

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: Adding a new table to an existing publication would fail with a "snapshot is already generated" error. The issue was resolved with an internal parameter.

Jira issue: RECOB-4919
Salesforce case: 24055
Type: Enhancement + Issue
Component/Process: PostgreSQL Source
Description: Start Replication would fail with a fatal error if the slot was active.

Jira issue: RECOB-4674
Salesforce case: 19975
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: In rare scenarios, an empty string in the before-image would be changed to NULL.

Jira issue: RECOB-4859

Salesforce case: 19297
Type: Issue
Component/Process: Upgrade
Description: Added logging for troubleshooting upgrade errors.

Jira issue: RECOB-4465

Salesforce case: 9224

Type: Issue

Component/Process: MySQL homogenous

Description: In a MySQL homogenous task, a source column that was part of the Primary Key and that was defined with a non-default collation, would not be updated in Batch Optimized Apply mode.

Jira issue: RECOB-4817

Salesforce case: 10885

Type: Issue

Component/Process: Google Cloud BigQuery Target

Description: Importing a task JSON with credentials in clear text format would result in the following Test Connection error (excerpt): JSON parsing error: Invalid escape character in string. [1022

Jira issue: RECOB-4867

Salesforce case: 26834

Type: Issue

Component/Process: SAP Application (DB) Source

Description: When new columns are added to a table using a transformation, the values of columns added to a SAP transparent table after the task started would be replicated as NULL.

Jira issue: RECOB-4799

Salesforce case: 13634

Type: Issue

Component/Process: Google Cloud BigQuery Target
Description: When loading data to Google Cloud BigQuery, the following error would sometimes occur: sqlite3: database is locked.

Jira issue: RECOB-4810
Salesforce case: 24134
Type: Issue
Component/Process: SAP HANA Source -Trigger Based CDC
Description: Replicate would fail to create the artifact table when working in Commit Timestamp mode.

Jira issue: RECOB-4811

Salesforce case: 24134

Type: Issue

Component/Process: SAP HANA Source -Trigger Based CDC

Description: The query for retrieving the max commit timestamp from the CDC changes table would cause performance issues when there were a large number of changes.

Jira issue: RECOB-4812

Salesforce case: 24134

Type: Issue

Component/Process: SAP HANA Source -Trigger Based CDC

Description: When starting a new task with a new artifact table, performance issues would be encountered when using the MaxFetchIntervalSize internal parameter.

Jira issue: RECOB-4844
Salesforce case: 24994
Type: Issue
Component/Process: Informix Source
Description: The task would stop abnormally when capturing an uncommon UPDATE event.

Jira issue: RECOB-4766

Salesforce case: 24122

Type: Issue

Component/Process: ARC Sources

Description: Replicate would skip a CSV file if the file name was earlier than the file that preceded it, which would result in data loss. The issue was resolved with the internal parameter.

Jira issue: RECOB-4711

Salesforce case: 22311

Type: Issue

Component/Process: Replicate Log Reader

Description: When starting a task from an SCN or a timestamp, some rows would not be captured when the table was Dynamic Partitioned and new partitions were created after the SCN start position.

Jira issue: RECOB-4829

Salesforce case: 26834

Type: Issue

Component/Process: SAP Application DB

Description: After a table metadata change, Replicate would sometimes fail to process a change to a transparent table.

Jira issue: RECOB-4795
Salesforce case: 1866
Type: Issue
Component/Process: Metadata Manager
Description: In rare cases, a task that included many transformations would abend on starting.

Jira issue: RECOB-4791

Salesforce case: 24955

Type: Issue

Component/Process: Databricks Azure

Description: In CDP mode, Replicate would insert the partition value at the end of the row, which would result in it being overridden by the the newly added VARCHAR column.

Jira issue: RECOB-4758
Salesforce case: 22128
Type: Issue
Component/Process: Transformations
Description: Adding a transformation to change the DateTime scale would have no effect.

Jira issue: RECOB-4716
Salesforce case: 22610
Type: Enhancement
Component/Process: IBM DB2 for iSeries
Description: An option to keep char trailing spaces was added via an internal parameter.

Jira issue: RECOB-4641
Salesforce case: 7507
Type: Enhancement
Component/Process: Microsoft Azure Event Hubs
Description: An option to configure the maximum batch size was added via an internal parameter.

Jira issue: RECOB-4546
Salesforce case: 12706
Type: Issue
Component/Process: Replicate Server
Description: ReplicateserveronLinuxwouldhangwhenEnterpriseManagerstartedmonitoringit.

Jira issue: RECOB-3871

Salesforce case: 2230521
Type: Issue
Component/Process: Replicate Installation
Description: Upgrading Replicate would result in the following error: repuictl.exe service stop returns 1

And the following warning message: The application tried to install a more recent version of the protected

Windows file C:\WINDOWS\system32\ucrtbase.dll. You may need to update your

operating system for this application to work correctly.

Jira issue: RECOB-4717
Salesforce case: 00023316
Type: Issue
Component/Process: Databricks Delta Azure

Description: When recreating the Net Changes table with new primary keys, Databricks would not update the new table immediately resulting in a failed transaction. The issue was resolved using internal parameters.

Jira issue: RECOB-4730, RECOB-4746

Salesforce case: NA

Type: Enhancement

Component/Process: SAP Extractor Source

Description: Full Load performance has been improved. The improvement must be turned on with an internal parameter.

Jira issue: RECOB-4312
Salesforce case: 15612
Type: Issue
Component/Process: Google Cloud BigQuery Target
Description: After upgrading from Replicate 7.0 to 2021.5 sp08, tasks would fail.

Jira issue: RECOB-4383

Salesforce case: 14781

Type: Issue

Component/Process: MySQL Source

Description: When replicating from MySQL 8, change processing would fail and the table would be suspended with the following error (excerpt): Error parsing column - overflow occurred

Jira issue: RECOB-4285
Salesforce case: 14022
Type: Enhancement
Component/Process: PostgreSQL Source
Description: Added last commit timestamp to the stream position to enable resumption of stopped tasks.

Jira issue: RECOB-4679
Salesforce case: 20199
Type: Enhancement
Component/Process: Transformation add-on
Description: Improved the transformations add-on example.

Jira issue: RECOB-4645
Salesforce case: 2257301
Type: Issue
Component/Process: Oracle Source
Description: LOB lookup would not find a record when a key contained an NCHAR column.

Jira issue: RECOB-4549

Salesforce case: 5255

Type: Enhancement

Component/Process: Transformations
Description: Improved the error-handling of transformation verifications.

Jira issue: RECOB-4643

Salesforce case: 17445

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: Change capture would fail when capturing a redo log operation from a table configured with Advanced Compression 11.6 in an Oracle 12.1.0.2 compatible version.

Jira issue: RECOB-4640

Salesforce case: NA

Type: Enhancement

Component/Process: SAP HANA Trigger-Based Source

Description: Improved performance when using SAP HANA trigger-based CDC mode. The new capability must be turned on using a feature flag.

Jira issue: RECOB-4587

Salesforce case: 19658

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: When running on Microsoft SQL Server 2019, Windows Server 2022 Datacenter Azure Edition VM, Replicate would fail and show an incorrect error message.

Jira issue: RECOB-4578

Salesforce case: 19384

Type: Issue

Component/Process: IBM DB2 for iSeries Source

Description: Using a UDTF to capture changes from a journal library and a journal receiver library that contained special characters would not work. The issue was resolved using an internal parameter.

Jira issue: RECOB-4128

Salesforce case: N/A

Type: Issue

Component/Process: AIS Source

Description: Replicate would fail to parse an event and issue the following warning: "Number of fields retrieved (XX) does not match metadata (YY)".

Jira issue: RECOB-4559

Salesforce case: 19712

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: The assertion warning "Cannot convert a client identifier <> from codepage <> to UTF8" would be printed to the log numerous times resulting in severe performance degradation.

Jira issue: RECOB-4487

Salesforce case: 15759

Type: Issue

Component/Process: Snowflake Azure Target

Description: The task would crash in truncate mode when the target table had more columns than the source.

Jira issue: RECOB-4523

Salesforce case: 13303

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: Some changes would not be captured when the Oracle RAC instance Compatible Version was 12.1.0.2.

Jira issue: RECOB-4050

Salesforce case: 10044

Type: Issue

Component/Process: Batch Optimized Apply

Description: In Batch Optimized Apply mode, LOB lookup would not find a record when a DELETE operation and an INSERT operation were combined into a single UPDATE operation.

Jira issue: RECOB-4141

Salesforce case: 2264071

Type: Issue

Component/Process: Task Manager

Description: When a table was loaded using Parallel Load, some of the cached events would not be replicated.

Jira issue: RECOB-4506

Salesforce case: 8114

Type: Issue

Component/Process: Oracle Source - Replicate Log reader

Description: When GoldenGate was enabled in the Oracle instance, some INSERT operations would not be captured when capturing from a table configured with Advanced Compression.

Jira issue: RECOB-4228
Salesforce case: 10221
Type: Issue
Component/Process: SAP HANA Source

Description: When a table ID was larger than 268435455, Replicate would save it as a negative number. This would cause the resume process to fail with the following message: "Failed to create CDC artifacts for table id= '0'"

Jira issue: RECOB-4359

Salesforce case: NA

Type: Issue

Component/Process: Security

Description: Addresses all log4j critical vulnerabilities (CVE-2021-45105, CVE-2021-45046, CVE-2021- 44228, and CVE-2021-44832). CVE-2021-45105 and CVE-2021-44832 were addressed by ensuring that they do not apply to our products, while CVE-2021-45046 and CVE-2021-44228 were addressed by replacing the vulnerable log4j library with version 2.16.

Jira issue: RECOB-4422
Salesforce case: 16640
Type: Issue
Component/Process: SAP Extractor Source
Description: Importing the SAP Extractor transport into newer versions of S4HANA systems would fail.

Jira issue: RECOB-4059, RECOB-4061

Salesforce case: 4582
Type: Issue
Component/Process: Salesforce Source

Description: When exceeding the maximum buffer size in Salesforce, a buffer exceeded error would occur (as expected), but each retry attempt would be considered as if it was the first. This would result in an endless loop of reconnection attempts, all failing with the same error.

Jira issue: RECOB-4334

Salesforce case: NA

Type: Enhancement

Component/Process: Qlik Cloud Landing

Description: Added a new audit_event_type message "AuditPayloadQCLMetadata", and an audit event "AuditPayloadQCLMetadata".

Jira issue: RECOB-4378
Salesforce case: 16714
Type: Issue
Component/Process: SAP HANA Source

Description: Tasks configured to use SAP HANA Log-based CDC would sometimes consume excessive memory and crash.

Jira issue: RECOB-4238

Salesforce case: 00009224

Type: Issue

Component/Process: MySQL Homogenous

Description: In a MySQL homogenous task, if a source table contained a Unique Index with nullable columns but did not have a Primary Key, the table would be suspended.

Jira issue: RECOB-4193
Salesforce case: 8272
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: Timeouts would sometimes occur when reading from SQL Server system tables.

Jira issue: RECOB-4283
Salesforce case: 10044
Type: Issue
Component/Process: Sybase Source
Description: LOB Lookup would not retrieve values when one of the key values was NULL.

Jira issue: RECOB-4354
Salesforce case: 15913
Type: Issue
Component/Process: MS-CDCbasedendpoint
Description: LOB columns would be removed from tables without a Primary Key or Unique Index.

Jira issue: RECOB-4341

Salesforce case: 12875

Type: Issue

Component/Process: SAPHANASourceLogbased

Description: INSERT operations to SAP HANA tables created by ABAP load scripts would not be captured.

Jira issue: RECOB-3936
Salesforce case: 2255408
Type: Enhancement Component/Process: Salesforce Source

Description: Added an internal parameter to prevent connections from being reset during Full Load. When the parameter is set to “true”, Replicate will write Salesforce batches to intermediate files before sending them to the target endpoint.

Jira issue: RECOB-4222

Salesforce case: NA

Type: Issue

Component/Process: Microsoft Azure SQL (MS-CDC) Source

Description: Removed a redundant table portion collection, added trace messages, and resolved the "Cannot process events" error message when stopping a task.

Jira issue: RECOB-4223
Salesforce case: NA
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: Sensitive data might have been included in the log file.

Jira issue: RECOB-4296

Salesforce case: 12949

Type: Issue

Component/Process: SAP Extractor Source

Description: An authorization error would occur when trying to run SAP Extractor endpoint with transport version 900260.

Jira issue: RECOB-4250

Salesforce case: 5818

Type: Issue

Component/Process: IBM DB2 for LUW Source

Description: In rare scenarios, when a record was moved from one page to another as the result of an UPDATE operation, the transaction ID and stream position would not be replicated correctly.

Jira issue: RECOB-4152

Salesforce case: N/A

Type: Enhancement

Component/Process: Qlik Cloud Landing

Description: Prior to this patch, the Qlik Cloud Landing replication profile required both Full Load and Store Changes replication. From this patch, it's now possible to select Full Load only replication.

Jira issue: RECOB-4148

Salesforce case: N/A

Type: Enhancement

Component/Process: Bidirectional Replication

Description: Bidirectional replication support was added for databases that do not produce an event when updating a record with the same values (e.g. IBM DB2 for z/OS).

Jira issue: RECOB-4215
Salesforce case: N/A
Type: Issue
Component/Process: SAP Application (DB)

Description: When the same table was captured in different tasks (e.g. the first task captured table A while the second task captured tables A and B), the tasks would sometimes generate different stream position values for identical changes if tables A and B were updated in the same transaction.

Jira issue: RECOB-4188

Salesforce case: 9982

Type: Issue

Component/Process: SAP HANA

Description: Defining the $AR_H_USER header variable (which is not supported with SAP HANA) in a transformation resulted in the table to being suspended.

Jira issue: RECOB-4064
Salesforce case: N/A
Type: Enhancement
Component/Process: Oracle Source
Description: Added extra logging to gather information about the Oracle instance configuration.

Jira issue: RECOB-3975

Salesforce case: N/A

Type: Issue

Component/Process: SAP Application (DB)

Description: When updating a Pool table or when changing a column, a default Before Image value would be replicated as an After Image value.

Jira issue: RECOB-4122
Salesforce case: 02260579
Type: Issue
Component/Process: Microsoft SQL Server Source

Description: The SQL Server safeguard commit would time out.

Jira issue: RECOB-3875

Salesforce case: 2264084

Type: Issue

Component/Process: Task Manager

Description: A warning about duplicate tables would be shown even though the parameter to suppress such warnings was set.

Jira issue: RECOB-3798

Salesforce case: 2264084

Type: Issue

Component/Process: Metadata Manager

Description: Added the option to create multiple tables with the same name on target endpoints that do no support schemas. The option is enabled with a use of a common setting property.

Jira issue: RECOB-3877
Salesforce case: 02251636
Type: Issue
Component/Process: MySQL Source
Description: Added logging to assist with troubleshooting CDC parsing errors.

Jira issue: RECOB-4007
Salesforce case: NA
Type: Issue
Component/Process: Microsoft Azure SQL (MS-CDC)
Description: SQL Server errors would occur while enabling MS-CDC system tables.

Jira issue: RECOB-4120
Salesforce case: NA
Type: Issue
Component/Process: Databricks Azure

Description: Databricks with Blob storage would not work when using Access Directly mode.

Jira issue: RECOB-4132

Salesforce case: 4113

Type: Issue

Component/Process: SAP Application (DB)

Description: Change capture would fail when a structure with a name exceeding 16 characters is defined in a captured table.

Jira issue: RECOB-3858
Salesforce case: 2267543
Type: Issue
Component/Process: SAP Application (DB)
Description: SAP Catalog tables DD02L and DD03L would not be replicated.

Jira issue: RECOB-3882
Salesforce case: N/A
Type: Enhancement
Component/Process: IBM DB2 for z/OS Source (R4DB2)

Description: The DO4GRANT script was improved.

Jira issue: RECOB-4084

Salesforce case: 4707

Type: Issue

Component/Process: Oracle Source

Description: An Oracle UPDATE operation on a Long data value would cause a crash or suspend the table.

Jira issue: RECOB-4136

Salesforce case: 4702

Type: Issue

Component/Process: SAP Application

Description: When using an Oracle backend database, key date columns would be wrongly replicated when capturing partial DELETE operations.

Jira issue: RECOB-4925
Salesforce case: 28274
Type: Issue
Component/Process: MySQL Source
Description:Transactions would sometimes not be captured after resuming the task.

Jira issue: RECOB-5068
Salesforce case: 30567
Type: Issue
Component/Process: Google Cloud BigQuery
Description: When the Primary Key column name included a single quote character, INSERTs would fail.

Jira issue: RECOB-5058

Salesforce case: 20548

Type: Issue

Component/Process: Log Stream with Microsoft SQL Server Source

Description: The task would fail when the source was Microsoft SQL Server and the forceDataRowLookup internal parameter was set.

Jira issue: RECOB-5034
Salesforce case: 28664
Type: Issue
Component/Process: Snowflake on Azure, Apply changes using SQL MERGE

Description: Excessive memory consumption would occur when using the Apply changes using SQL MERGE option.

Jira issue: RECOB-4850
Salesforce case: 24994
Type: Issue
Component/Process: IBM Informix Source
Description: The task would stop abnormally when capturing a rare UPDATE event.

Jira issue: RECOB-4891

Salesforce case: 23316

Type: Issue

Component/Process: Microsoft Azure Databricks Delta

Description: An error about a missing column in the attrep_changes Control Table would sometimes be encountered, even though the column was present in the target.

Qlik Replicate May 2022 – Patch Release Notes (PR02 - build 2022.5.499)

These release notes provide details on the resolved issues and/or enhancements included in this patch release. All patch releases are cumulative, meaning that they include the fixes and enhancements provided in previous patch releases.

Jira issue: RECOB-5686
Salesforce case: N/A
Type: Enhancement
Component/Process: Microsoft Azure ADLS and Google Cloud Storage Targets Description: Added Parquet file format support.

Jira issue: RECOB-5684
Salesforce case: N/A
Type: Enhancement
Component/Process: Amazon S3 target Description: Added AWS PrivateLink support.

Jira issue: RECOB-5661
Salesforce case: N/A
Type: Enhancement
Component/Process: SAP HANA Source Description: Added SSL connectivity support.

Jira issue: RECOB-5660
Salesforce case: N/A
Type: Enhancement
Component/Process: SAP HANA Trigger Based
Description: Added support for SAP HANA tables with no Primary Key, that are used in SAP with the corresponding SAP Primary Key.

Jira issue: RECOB-5680
Salesforce case: N/A
Type: Enhancement
Component/Process: Feature flags with Java SDK and auto generated endpoints
Description: Added partial support for feature flags with Java SDK and auto generated endpoints.

Jira issue: RECOB-5678
Salesforce case: N/A
Type: Enhancement
Component/Process: IBM DB2 for iSeries Source, IBM DB2 for z/OS Source, and IBM DB2 for LUW Source Description: Added support for SSL connectivity using internal parameters.

Jira issue: RECOB-5659
Salesforce case: N/A
Type: Enhancement
Component/Process: SAP HANA Source
Description: Added support for connecting to a specific tenant database by providing the database name in the endpoint connection settings.

Jira issue: RECOB-5673
Salesforce case: N/A
Type: Enhancement
Component/Process: Microsoft SQL Server (MS-CDC) Source
Description: Added a new Microsoft SQL Server (MS-CDC) source endpoint.

Jira issue: RECOB-5668
Salesforce case: N/A
Type: Enhancement
Component/Process: Sybase ASE Source
Description: Added an internal parameter for enabling FIPS support.

Jira issue: RECOB-5666
Salesforce case: N/A
Type: Enhancement
Component/Process: Google Cloud SQL for SQL Server Target Description: Added a new Google Cloud SQL for SQL Server target endpoint.

Jira issue: RECOB-5664
Salesforce case: N/A
Type: Enhancement
Component/Process: Databricks Delta
Description: Added a new Databricks Delta endpoint that supports Amazon, Azure, and Google Cloud Storage.

Jira issue: RECOB-5491
Salesforce case: 36583
Type: Issue
Component/Process: PostgreSQL Source

Description: When a timestamp record had '-infinty' as value, CDC would fail.

Jira issue: RECOB-5544
Salesforce case: 38075
Type: Issue
Component/Process: Teradata Target
Description: The TPT Log table name was being built incorrectly.

Jira issue: RECOB-5588
Salesforce case: 29650
Type: Issue
Component/Process: SAP Extractor Source
Description: The task would invoke an extractor job for a SAP table that was not a part of the task's table list.

Jira issue: RECOB-5623
Salesforce case: 38632
Type: Issue
Component/Process: SAP Hana Log-Based Source
Description: The sorter transaction swap files would accumulate and not be deleted.

Jira issue: RECOB-5568
Salesforce case: 40156
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: This is a debug patch for the crash caused by rapid DROP/CREATE table processing.

Jira issue: RECOB-5529

Salesforce case: 34820

Type: Issue

Component/Process: SAP HANA Source Log based

Description: An empty string for both VARCHAR and NVARCHAR columns would sometimes be replicated incorrectly. Additionally, a table would sometimes be replicated incorrectly if its columns were modified.

Jira issue: RECOB-5593
Salesforce case: 41792
Type: Issue
Component/Process: Oracle Source
Description: A source transaction would fail in the Sorter when it contained changes of a captured table and SYS.OBJ$, and was then rolled back.

Jira issue: RECOB-5599

Salesforce case: 38960

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: When "Read the backup log directly from a file" was enabled, the backup log usage would always be prioritized, even if the online logs priority was configured.

Jira issue: RECOB-5621
Salesforce case: 33656
Type: Issue
Component/Process: Metadata Manager
Description: Events from some tables would not be captured when the table ID of the number of captured tables was greater than 2*32.

Jira issue: RECOB-5459
Salesforce case: N/A
Type: Enhancement
Component/Process: SAP Application (DB) Source
Description: Business Objects changes processing was improved.

Jira issue: RECOB-5330
Salesforce case: 12867
Type: Issue
Component/Process: Microsoft Azure Databricks Target
Description: Added logging to troubleshoot a count difference between source and target issue.

Jira issue: RECOB-5307
Salesforce case: 34640
Type: Issue
Component/Process: Sybase ASE source
Description: The FLOAT data type would be replicated incorrectly during both Full Load and CDC.

Jira issue: RECOB-5487
Salesforce case: 00036960
Type: Issue
Component/Process: Salesforce Source
Description: When only the LastModifiedDate field was changed, the change would be ignored.

Jira issue: RECOB-5212
Salesforce case: 24055
Type: Issue
Component/Process: PostgreSQL Source

Description: Amazon RDS for PostgreSQL would not handle network issues properly.

Jira issue: RECOB-5522
Salesforce case: N/A
Type: Issue
Component/Process: Replicate General
Description: Replicate on Linux was built using FIPS mode

Jira issue: RECOB-5527
Salesforce case: 34091
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: When a captured table had no CAPTURE DATA CHANGES attribute, the corresponding warning messages would not be issued.

Jira issue: RECOB-5484
Salesforce case: 3898
Type: Issue
Component/Process: Google Cloud Storage
Description: When a task was stopped and then resumed, the CDC files generated before the task was stopped would not be uploaded to Google Cloud.

Jira issue: RECOB-5511
Salesforce case: 37728
Type: Issue
Component/Process: MySQL (MariaDB)
Description: A new table added to the source would not be replicated in CDC until the task was stopped and resumed.

Jira issue: RECOB-5564
Salesforce case: 38064
Type: Issue
Component/Process: Salesforce Source (Incremental Load) Description: Timeout errors would sometimes occur during Full Load.

Jira issue: RECOB-5237

Salesforce case: N/A

Type: Issue

Component/Process: BigQuery Target

Description: When Create tables clustered by primary key was enabled in the endpoint's Advanced tab, and Apply changes using SQL MERGE was turned on in the task settings, INSERTs would expose the data in the log.

Jira issue: RECOB-5509

Salesforce case: 21512

Type: Enhancement

Component/Process: Log Stream

Description: When using Log Stream and the Source change position (e.g. SCN or LSN) field is set to 0, the task will resume from the first event of the latest timeline.

Jira issue: RECOB-5176
Salesforce case: 30284
Type: Issue
Component/Process: Microsoft Azure SQL (MS-CDC) source
Description: When the date format in the default language was not MDY, Full Load would fail.

Jira issue: RECOB-5485
Salesforce case: N/A
Type: Issue
Component/Process: Amazon S3 Target
Description: The Region code UI label was incorrectly named Bucket region.

Jira issue: RECOB-5364

Salesforce case: 33794

Type: Issue

Component/Process: Snowflake Azure Target

Description: When the Optimize Inserts option was enabled in Batch Optimized Apply mode and JSONandXMLColumns-SnowflakeTarget was turned on (the default), the task would fail when trying to insert a CLOB column whose length exceeded 65535 characters.

Jira issue: RECOB-5445
Salesforce case: 21090
Type: Issue
Component/Process: SalesForce Source
Description: The task was stop capturing changes every few weeks, with the following error (excerpt) exception=java.lang.OutOfMemoryError: Java heap space

Jira issue: RECOB-5457
Salesforce case: 34455
Type: Issue
Component/Process: SAP HANA Source
Description: SAP HANA views would not be replicated after upgrading.

Qlik Replicate May 2022 – Release Notes for PR01 (PR01 - build 2022.5.395)

This section describes the enhancements and resolved issues in this patch release.

Jira issue: RECOB-5540
Salesforce case: 38064
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: A timeout error would sometimes occur when unloading a table.

Jira issue: RECOB-5532
Salesforce case: 34641
Type: Issue
Component/Process: SAP HANA Source
Description: Filtering archiving user names that contained a period would not work.

Jira issue: RECOB-5232
Salesforce case: 4844
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: Replicate Log Reader would crash after parsing a Direct Insert Redo Log Event 19.1.

Jira issue: RECOB-5517
Salesforce case: 37119
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: INSERT operations in a compressed table would be missing when Goldengate was enabled in Oracle.

Jira issue: RECOB-5523
Salesforce case: NA
Type: Feature
Component/Process: SAP Application Description: Added support for SNC.

Jira issue: RECOB-5072

Salesforce case: NA

Type: Issue

Component/Process: Google BigQuery Target, Security

Jira issue: RECOB-5180 Salesforce case: 31399

Type: Issue
Component/Process: SAP Application (DB) Source with a Microsoft SQL Server backend

Description: When trying to capture changes from a Cluster table, the task would sometimes crash with the following error: Incorrect PART_NO <> in the Cluster '<>' object part <>, possible changes are ignored

Jira issue: RECOB-5439
Salesforce case:
Type: Issue
Component/Process: Salesforce Source (Streaming CDC)
Description: Parsing of a custom time field would fail during Full Load with the following error: Unable to parse '<time>' as TIME. Will use null instead.

Jira issue: RECOB-5394
Salesforce case:
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: A "Read timed out" error would sometimes occur when working with Bulk API.

Jira issue: RECOB-5501
Salesforce case: 38566
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: When the following settings were enabled in the endpoint's Advanced tab, the redo files would not be deleted automatically.

Copy redo logs to temporary folder
Replicate has file level access to temporary folder Access archived redo logs in folder
Delete processed archived redo log files

Jira issue: RECOB-5368

Salesforce case: 27920

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: When a wide SQL Server table contained long VARCHAR columns, in rare scenarios, the VARCHAR column values would be replicated to the wrong record.

Jira issue: RECOB-5352
Salesforce case: 34292
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Confusing warning messages would be shown in certain scenarios.

Jira issue: RECOB-5269

Salesforce case: 37942
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Compound field types such as Address would replicated as NULL when using SOAP API.

Jira issue: RECOB-5321
Salesforce case: 34832
Type: Issue
Component/Process: Salesforce Source (Incremental Load) Description: Remove column DDL cause to recoverable error loop

Jira issue: RECOB-5378
Salesforce case:
Type: Issue
Component/Process: Salesforce Source (Incremental Load)
Description: Unicode characters would not be replicated when using BULK API.

Jira issue: RECOB-5324

Salesforce case: 34585

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: When starting the task from a timestamp, Replicate Log Reader would sometimes capture Dynamic Partition table operations from the wrong Dynamic Partition table.

Jira issue: RECOB-5472
Salesforce case: 37942
Type: Issue
Component/Process: Salesforce Source (Incremental Load) Description: Full Load would sometimes fails when a task was resumed.

Jira issue: RECOB-5221
Salesforce case: 32297
Type: Issue
Component/Process: MySQL Homogeneous
Description: ALTER TABLE operations would result in an unexpected character set being defined on the target.

Jira issue: RECOB-4881
Salesforce case: 02101374
Type: Issue
Component/Process: Microsoft SQL Server Source (from 2016)

Description: When the Primary Key was DATETIME, LOB lookup would fail, resulting in missing LOB columns.

Jira issue: RECOB-5242
Salesforce case: 33124
Type: Issue
Component/Process: PostgreSQL Source
Description: The task would sometimes crash when a large number of tables were truncated in a single operation.

Jira issue: RECOB-4880
Salesforce case: 24364
Type: Issue
Component/Process: Teradata Source
Description: When using Parallel Load, in a task defined with the Full Load and Apply Changes options, the task would sometimes crash during Full Load.

Jira issue: RECOB-5486
Salesforce case: 37690
Type: Issue
Component/Process: Snowflake
Description: Incorrect default values were assigned to some of the internal parameters.

Jira issue: RECOB-5435
Salesforce case: 36027
Type: Issue
Component/Process: SAP Application (DB)
Description: When a captured cluster table was changed, SAP Client records that were not configured in SAP Application (DB) would be replicated.

Jira issue: RECOB-5448
Salesforce case: NA
Type: Enhancement
Component/Process: Replicate Engine
Description: Updated the Kerberos OpenSSL libraries.

Jira issue: RECOB-5276

Salesforce case: 33320

Type: Issue

Component/Process: Microsoft Databricks Azure

Description: When the Sequence storage format was used and the files were compressed with gzip, empty files would be left in the Databricks partition if the load operation was interrupted.

Jira issue: RECOB-5427

Salesforce case: 37749
Type: Issue
Component/Process: Amazon Redshift Target
Description: It would not be possible to save the endpoint settings without changing the default Bucket region.

Jira issue: RECOB-5327

Salesforce case: 32256

Type: Issue

Component/Process: SAP HANA Trigger Based Capture

Description: When using the Commit-Timestamp internal parameter, latency issues would be encountered when processing changes from non-captured tables.

Jira issue: RECOB-5419
Salesforce case: 33783
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: The LSN on a secondary replica in an AlwaysOn environment could not be located.

Jira issue: RECOB-5372
Salesforce case: 34751
Type: Issue
Component/Process: Installer
Description: The Qlik Replicate installation timeout was increased to 300 seconds.

Jira issue: RECOB-5375
Salesforce case: 31588
Type: Issue
Component/Process: SAP DB
Description: After upgrading to Replicate 2021.11 and resuming a task, the first DDL change would cause the associated table to be suspended.

Jira issue: RECOB-5068

Salesforce case: 30567

Type: Issue

Component/Process: BigQuery TARGET

Jira issue: RECOB-5170
Salesforce case: 23555
Type: Issue
Component/Process: Amazon Redshift

Description: Replicate would not attempt to reconnect to Amazon Redshift if the connection was lost.

Jira issue: RECOB-5380

Salesforce case: 25486

Type: Issue

Component/Process: Snowflake

Description: In Batch Optimized Apply mode, explicit COMMITs would be performed when applying changes to Snowflake, resulting in unacceptable costs.

Jira issue: RECOB-5164

Salesforce case: 31074

Type: Issue

Component/Process: Control Tables

Description: When the DDL History Control table was enabled, and a column was changed from TEXT to VARCHAR(max) or vice versa, the task would encounter a recoverable error.

Jira issue: RECOB-5342
Salesforce case: 30113
Type: Issue
Component/Process: SAP DB
Description: A special SAP date using the year 0101 would not be replicated correctly.

Jira issue: RECOB-5268
Salesforce case: 28583
Type: Issue
Component/Process: SAP DB
Description: Changes would sometimes not be captured when replicating from SAP cluster tables with Microsoft SQL Server as the underlying database.

Jira issue: RECOB-5174

Salesforce case: 32472

Type: Issue

Component/Process: LOB Support

Description: LOB support would be disabled when the No record found for applying an update INSERT the missing target record error handling option was selected, AND a table was changed with a transformation.

Known Issues

This section lists the known issues for the Replicate May 2022 initial release.

All issues except REP-1275 have been resolved in Replicate May 2022 SR2.

Jira issue: REP-1275
Salesforce case: N/A
Type: Issue
Component/Process: SingleStore Target
Description: The SingleStore Target endpoint is not certified for use with Replicate on Linux.

Jira issue: RECOB-4880

Salesforce case: 24364

Type: Issue

Component/Process: Teradata Source - ODBC with CDC, Parallel Load

Description: When loading a table with parallel load in Full Load and Apply Changes replication mode, the task might sometimes crash.

Jira issue: RECOB-4881

Salesforce case: 2101374

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: When the Primary Key was DATETIME, LOB lookup might fail, resulting in missing LOB columns.

Jira issue: RECOB-5221
Salesforce case: 32297
Type: Issue
Component/Process: MySQL Target

Description: When applying a DDL change, columns defined as utf8mb4_0900_ai_ci on the source will be created as UTF16 on the target.

Jira issue: RECOB-5242
Salesforce case: 33124
Type: Issue
Component/Process: PostgreSQL Source
Description: The task might crash if too many tables are truncated in a single operation.

Jira issue: RECOB-5212
Salesforce case: 24055
Type: Issue
Component/Process: PostgreSQL Source
Description: Starting a task might fail with a fatal error if the slot is active.

Jira issue: RECOB-5377

Salesforce case: N/A

Type: Issue

Component/Process: Salesforce (Incremental) Source

Description: When using the BULK API loading option, UNICODE letters will not be loaded during Full Load.

Endpoint	Comments
File source and target	-
IBM DB2 for z/OS source	The SSL connection is FIPS compliant. To connect using SSL, set the following internal parameters in the endpoint's Advanced tab: UseSSL Enables SSL SSLClientKeystoredb. The SSL keystore database file that is used for an SSL connection with or without the CERTIFICATE authentication. SSLClientKeystash. The fully qualified path of the stash file ( .sth ), which stores an encrypted password to the key database file. -OR- SSLClientKeystoreDbPassword. The password of the keystore in string format. This password is defined when the keystore is generated.
IBM DB2 for iSeries source	Supported with Replicate on Windows only. The SSL connection is FIPS compliant. To connect using SSL, set the useSSL internal parameter in the endpoint's Advanced tab.
IBM DB2 for LUW source	The SSL connection is FIPS compliant. To connect using SSL, set the following internal parameters in the endpoint's Advanced tab: UseSSL Enables SSL SSLClientKeystoredb. The SSL keystore database file that is used for an SSL connection with or without the CERTIFICATE authentication. SSLClientKeystash. The fully qualified path of the stash file ( .sth ), which stores an encrypted password to the key database file. -OR - SSLClientKeystoreDbPassword The password of the keystore in string format. This password is defined when the keystore is generated.
Microsoft Azure ADLS target	Supported when using Azure Data Lake Storage (ADLS) Gen1 only.
Microsoft Azure Event Hubs target	-
Oracle source and target	For instructions on how to enable FIPS, see https://docs.oracle.com/cd/E28271_01/network.1111/e10746/asoappe.htm
Sybase ASE source	To enable FIPS, set the EnableFIPS internal parameter in the endpoint's Advanced tab to true.
Vertica target	Supported with Replicate on Linux only. Requires a FIPS compliant driver, which can be downloaded from: https://www.vertica.com/download/vertica/client- drivers/

article Qlik Replicate Release notes - May 2022 Initial Release to Service Release 2 in Release Notes

Qlik Replicate Release notes - May 2022 Initial Release to Service Release 2