What's new
Learn about new features and improvements in Qlik Replicate.
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 May 2023 SR and Replicate November 2023 SR.
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 Replicate November 2020 (7.0).
- Upgrade to Replicate November 2021.
- Upgrade to Replicate November 2022.
- Upgrade to Replicate May 2023 SR.
- Upgrade to Replicate May 2024.
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 November 2022.
- Upgrade to Replicate May 2023 SR.
- Upgrade to Replicate May 2024.
Note: 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 once 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
Note: This procedure does not need to be performed when upgrading from Replicate November 2022 or later.
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 Qlik 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
This version of Replicate is compatible with the following related products only:
- Enterprise Manager May 2024 or later
- Compose November 2023 or later
- Compose for Data Lakes April 2020 (6.6)
Required post-upgrade steps for tasks with a SAP ODP source endpoint
When upgrading from Replicate versions earlier than Replicate May 2023 SP2, you must perform the following steps in the Replicate Console after the upgrade completes:
- Select Advanced Run Options from the Run menu.
- Choose Metadata Only and then select Create missing tables and then stop. Click OK.
- The task will run, collect missing metadata, and then stop.
- Resume the task after it stops.
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 endpoint versions has been discontinued:
- All Oracle versions and drivers earlier than Oracle 19.x
- SQL Server 2014
- MySQL 5.7
- PostgreSQL 11
- Kafka 2.x
- IBM DB2 for LUW 10.5
- IBM DB2 for z/OS: z/OS 2.3
- MongoDB 4.4
Resolved issues
The following issues have been resolved since Replicate November 2023 SR 1.
Jira issue: RECOB-8101
Salesforce case: 138462
Type: Issue
Component/Process: Amazon Redshift
Description: When the "Limit LOB size" option was enabled, and replicating data larger than limited lob size*2 on CLOB from IBM DB2 from z/OS, a data error would occur. This issue was resolved using an internal parameter.
Jira issue: RECOB-8192
Salesforce case: 150243
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: Missing UPDATE operations would occur when replicating Advanced Compressed tables with long values.
Jira issue: RECOB-7965
Salesforce case: N/A
Type: Enhancement
Component/Process: IBM DB2 for z/OS Source
Description: The DB2 TRACE MONITOR will be auto-started when it is not active.
Jira issue: RECOB-8135
Salesforce case: N/A
Type: Enhancement
Component/Process: Oracle Source - Replicate Log Reader
Description: Improved Oracle Log Reader logging.
Jira issue: RECOB-8027
Salesforce case: 117549
Type: Issue
Component/Process: SAP ODP Source
Description: UPDATE operations would be captured as INSERT operations when using SLT.
Jira issue: RECOB-8090
Salesforce case: 135515
Type: Issue
Component/Process: MySQL Source
Description: Replication tasks from MySQL source would fail after upgrade to 2023.11.
Jira issue: RECOB-8064
Salesforce case: 144176
Type: Issue
Component/Process: Replicate Installation
Description: Added an option to force the installation to request a user and group.
Jira issue: RECOB-8021
Salesforce case: 108548
Type: Issue
Component/Process: Kafka
Description: Tasks using the Kafka target endpoint would consume excessive memory when capturing the REAL data type and using JSON message format.
Jira issue: RECOB-8066
Salesforce case: 132663
Type: Issue
Component/Process: SAP Application (DB)
Description: SAP transparent table LOB fields were not exposed in the Replicate UI.
Jira issue: RECOB-8059
Salesforce case: 132663
Type: Issue
Component/Process: SAP Application (DB)
Description: The "By partition" option of the Parallel Load feature could not be selected.
Jira issue: RECOB-8092
Salesforce case: 138709
Type: Issue
Component/Process: DB2 iSeries Source
Description: When using only RRN as a Primary Key on a table without a Primary key or Unique Index, the Primary Key position would be set to 0 instead of 1. This would result in an incorrect value being inserted in the 'primaryKeyPosition' metadata field.
Jira issue: RECOB-7760
Salesforce case: 108951
Type: Issue
Component/Process: Kafka
Description: A memory leak (a new METADATA MANAGER TABLE pool would be created) would occur each time a data problem was detected.
Jira issue: RECOB-7949
Salesforce case: 106008
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: The internal property logScanRowCount usage would sometimes cause missing operations or entire transactions. This would also result in the Sorter swap files not being deleted.
Jira issue: RECOB-7966
Salesforce case: 133745
Type: Enhancement
Component/Process: Kafka
Description: Added support for tombstone methodology for DELETE operations in Kafka. Supported using an internal parameter.
Jira issue: RECOB-7980, RECOB-8016
Salesforce case: 135999
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: Missing and duplicate records would sometimes be encountered for multi Insert operations in Oracle instances with ENABLE_GOLDENGATE_REPLICATION=TRUE.
Jira issue: RECOB-7924
Salesforce case: 108202
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: The compressed transaction log would be processed incorrectly in some specific SQL Server scenarios.
Jira issue: RECOB-7973
Salesforce case: 136823
Type: Issue
Component/Process: IBM DB2 for z/OS Source Source
Description: The IBM DB2 for z/OS source endpoint would not work with a German DB2 z/OS instance.
Known issues
Jira issue: RECOB-8210
Salesforce case: 147063
Type: Issue
Component/Process: SAP HANA Source (Log based)
Description: The capture process sometimes stops with a recoverable error.
Jira issue: RECOB-8240
Salesforce case: 152509
Type: Issue
Component/Process: Snowflake
Description: When a source table contains LOB columns, replication to Snowflake target might fail with the following error:
Invalid character length: 0. Must be between 1 and 16,777,216
Jira issue: RECOB-8187
Salesforce case: 133529
Type: Issue
Component/Process: IBM DB2 for LUW with SAP Application (DB)
Description: Replicating certain day values (HAZDT) sometimes results in missing rows in the target.
Downloads
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik’s vision is a data-literate world, where everyone can use data and analytics to improve decision-making and solve their most challenging problems. A private SaaS company, Qlik offers an Active Intelligence platform, delivering end-to-end, real-time data integration and analytics cloud solutions to close the gaps between data, insights and action. By transforming data into Active Intelligence, businesses can drive better decisions, improve revenue and profitability, and optimize customer relationships. Qlik does business in more than 100 countries and serves over 50,000 customers around the world.
qlik.com
