Qlik Replicate May 2025 Initial Release until Service Release 1

[Charlton_Book]

Table of Contents

• What's new
• Migration and upgrade
• Upgrade paths
• Upgrading from Replicate April 2020 (6.6)
• Upgrading from unsupported versions
• Microsoft .NET Framework 4.8 upgrade/installation prerequisite
• Upgrading an installation with multiple data folders
• Compatibility with related Qlik products
• Preventing log stream replication tasks from failing after upgrade
• Resolved issues in May 2025 Service Release 1
• Resolved issues in May 2025 Initial Release
• Known issues
• Downloads

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 2024 and Replicate November 2024.

Upgrading from Replicate April 2020 (6.6)

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

1. Upgrade to Replicate November 2020 (7.0).
2. Upgrade to Replicate November 2021.
3. Upgrade to Replicate November 2022.
4. Upgrade to Replicate May 2023 SR.
5. Upgrade to Replicate November 2023 SR.
6. Upgrade to Replicate November 2024 SR.
7. Upgrade to Replicate May 2025 SR1.

Upgrading from unsupported versions

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

1. Upgrade to Replicate 6.5.
2. Upgrade to Replicate November 2020 (7.0).
3. Upgrade to Replicate November 2021.
4. Upgrade to Replicate November 2022.
5. Upgrade to Replicate May 2023 SR.
6. Upgrade to Replicate November 2023 SR
7. Upgrade to Replicate November 2024 SR.
8. Upgrade to Replicate May 2025 SR1.

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.

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 Qlik products

This version of Replicate is compatible with the following related products only:

• Enterprise Manager May 2025 and its Service Releases
• Compose November 2023 or later
• Compose for Data Lakes April 2020 (6.6)

Preventing log stream replication tasks from failing after upgrade

The Retrieve all source columns on UPDATE option introduced in Replicate November 2024 might impact your existing log stream replication tasks if you are upgrading from a version earlier than Replicate May 2024. In this case, your replication tasks will fail if either of the following replication task setting are configured:

• Change Processing > Change Processing Tuning > DELETE and INSERT when updating a primary key column
• Error handling > Apply Conflicts > No record found for applying an UPDATE: Insert the missing target record

To prevent the task(s) from failing, you need to do one of the following for each log stream replication task (preferably the first):

• Enable the Retrieve all source columns on UPDATE option in Task Settings > Change Processing > Change Processing Tuning
  -OR-
• Add the disableLogstreamFullLoggingCheck flag to Task Settings > More Options and set it to On. This will preserve the previous behavior.

Resolved issues in May 2025 Service Release 1

The following issues have been resolved since May 2025 Initial Release.

Jira issue: RECOB-10022 

Salesforce case:  

Type: Issue 

Component/Process: SAP HANA Source (Trigger-based CDC)   

Description: When Record mode was set to Full record, a recoverable error would occur when the task was idle for a long time. 

Jira issue: RECOB-9618 

Salesforce case: 350356 

Type: Issue 

Component/Process: SAP HANA Source (Trigger-based CDC)   

Description: When working in Full record mode, a truncation error would occur when capturing large amounts of changes, resulting in missing events on the target. 

Jira issue: RECOB-9876 

Salesforce case: N/A

Type: Issue 

Component/Process: SAP HANA Source (Trigger-based CDC)   

Description: When working in Full record mode and starting a task from timestamp earlier than the first transaction, the first transaction would not be captured. 

Jira issue: RECOB-9884 

Salesforce case: N/A 

Type: Issue 

Component/Process: SAP HANA Source (Trigger-based CDC)   

Description: When working in Full record mode, record time would incorrectly be the current time instead of the event/commit time. 

Jira issue: RECOB-9968 

Salesforce case: N/A 

Type: Issue 

Component/Process: SAP HANA Source (Trigger-based CDC)   

Description: When working in Full record mode, performance issues would sometimes be encountered.  

Jira issue: RECOB-10020 

Salesforce case: 371674 

Type: Issue 

Component/Process: Oracle Source - General 

Description: An HCC page type in Redo Log 11.26 (Multi Insert) operation would cause missing records on the target. 

Jira issue: RECOB-9895 

Salesforce case: 360962 

Type: Issue 

Component/Process: Log Stream 

Description: It would not be possible to start a Log Stream task from a timestamp after a table became suspended. 

Jira issue: RECOB-9961 

Salesforce case: N/A 

Type: Issue 

Component/Process: Task Settings 

Description: When using the Metadata only run option, the task would drop and recreate the target tables, even when it was configured with If target table already exists: Ignore 

Jira issue: RECOB-10031 

Salesforce case: 378148 

Type: Issue 

Component/Process: IBM Informix/Sorter 

Description: To troubleshoot an issue with missing target records, verbose logging messages for Sorter operations related to the DISCARD_FROM_POSITION implementation were added. 

Jira issue: RECOB-10028 

Salesforce case: 388922 

Type: Issue 

Component/Process: Export task 

Description: Task export/import would not work when a task contained a transformation. 

Jira issue: RECOB-9954 

Salesforce case: 383865 

Type: Issue 

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

Description: When a table had column names that also existed in the lsn_time_mapping table, change processing would fail with the following error (excerpt): 

Ambiguous column name 

Jira issue: RECOB-9837 

Salesforce case: 357597 

Type: Issue 

Component/Process: Metadata Manager  

Description: Full load of tables with a TIME data type column on Databricks Delta would fail, unless the Replicate LOB columns option was enabled. This issue was resolved using a feature flag. 

Jira issue: RECOB-9684 

Salesforce case: N/A 

Type: Issue 

Component/Process: Google BigQuery Target 

Description: When the task was configured to ignore the DROP COLUMN DDL, an error would occur instead of the column becoming nullable. 

Jira issue: RECOB-9949 

Salesforce case: 380373 

Type: Issue 

Component/Process: Microsoft SQL Server Source 

Description: Tables with non-clustered indexes would be suspended because the partitions were not uniformly mapped. 

Jira issue: RECOB-9926 

Salesforce case: 379329 

Type: Issue 

Component/Process: SAP HANA Source (Application mode) 

Description: During initial load, some dates would be replicated as 01.01.0101. 

Jira issue: RECOB-9986 

Salesforce case: 382403 

Type: Issue 

Component/Process: Oracle Target 

Description: When the internal property createNetChangesTempTable was set to false and a table contained LOB columns, the task would fail when working in Batch Optimized Apply mode. 

Jira issue: RECOB-9982 

Salesforce case: 354344 

Type: Issue 

Component/Process: Error Handling 

Description: When Replicate was configured to perform an UPDATE operation as DELETE and INSERT, errors would be handled incorrectly. 

Jira issue: RECOB-9935 

Salesforce case: 292194 

Type: Issue 

Component/Process: SAP HANA Source 

Description: When there was a CPBTree index on the source, the index would not be created on the target. 

Jira issue: RECOB-9931 

Salesforce case: 301513 

Type: Issue 

Component/Process: SAP HANA Source 

Description: After upgrading to HANA versions later than 2.0 SPS 7, CDC replication would fail. 

Jira issue: RECOB-9652 

Salesforce case: 363635 

Type: Issue 

Component/Process: SAP HANA Source (Log based CDC) 

Description: When replicating from HANA SPS8 (8.80 and 8.81), Replicate would fail to retrieve the data values from DML operations, resulting in the table being suspended and the task failing. 

Jira issue: RECOB-9882 

Salesforce case: 375566 

Type: Issue 

Component/Process: Oracle Source - General 

Description: In rare scenarios, usually when most of the table columns are NUMERIC, but also depending on the table definition and bulk size, the unload operation would crash. 

Jira issue: RECOB-9906 

Salesforce case: N/A 

Type: Issue 

Component/Process: Import 

Description: Importing a task with notification settings would fails when Replicate Server was not running. 

Jira issue: RECOB-9918 

Salesforce case: 361698 

Type: Issue 

Component/Process: Task Manager 

Description: After a transformation rule was changed, resuming a CDC-only task would reload the table. 

Jira issue: RECOB-9900 

Salesforce case: 351200 

Type: Issue 

Component/Process: Oracle Source - General 

Description: When a table contains numerous LOB columns, the task would sometimes crash during Full Load. 

Jira issue: RECOB-9738 

Salesforce case: 364509 

Type: Issue 

Component/Process: Google BigQuery Target 

Description: Nullability checks would be unnecessarily performed on a MERGE query for a unique index, thereby slowing down the query process. 

Jira issue: RECOB-9879 

Salesforce case: 377455 

Type: Issue 

Component/Process: Databricks Lakehouse (Delta) 

Description: Test connection would fail when using the Liquid Clustering option with Databricks SQL Warehouse. 

Jira issue: RECOB-9843/ RECOB-9797 

Salesforce case: 354344 

Type: Issue 

Component/Process: Oracle Source - Replicate Log Reader 

Description: In rare scenarios, an advanced compressed table would be suspended when the task was configured to apply UPDATE operations as DELETE and INSERT. 

Jira issue: RECOB-9816 

Salesforce case: 350194 

Type: Issue 

Component/Process: Microsoft SQL Server Source 

Description: “Failure in executing add article through batch” and “Failure upon initial CAPTURE fitness checking” errors would sometimes occur when replicating from Microsoft SQL Server 2022. 

Jira issue: RECOB-9799 

Salesforce case: 346864 

Type: Enhancement 

Component/Process: IBM DB2 for iSeries Source 

Description: Added support for table names with NLS characters using an internal parameter. 

Jira issue: RECOB-9576 

Salesforce case: 324951 

Type: Issue 

Component/Process: Microsoft Fabric Data Warehouse Target 

Description: When loading a VARCHAR data type, a truncation error would occur when the data contained wide characters. 

Jira issue: RECOB-9869 

Salesforce case: 371674 

Type: Issue 

Component/Process: Oracle Source - Replicate Log Reader 

Description: A previously unsupported HCC page type in Redo Log 11.11 (Multi Insert) operation would cause incorrect data to be generated. 

Jira issue: RECOB-9823 

Salesforce case: 301410 

Type: Issue 

Component/Process: Google BigQuery Target 

Description: Test connection would fail when the JSON credentials ended with an empty line. 

Jira issue: RECOB-9694 

Salesforce case: 362694 

Type: Issue 

Component/Process: Microsoft SQL Server Source 

Description: In “Backup only” mode, changes would not be captured after a Rebuild Index operation. 

Jira issue: RECOB-9827 

Salesforce case: N/A 

Type: Issue 

Component/Process: Oracle XStream Source 

Description: Replicate would fail to create an outbound XStream Server in a CDB/PDB environment. 

Jira issue: RECOB-9785 

Salesforce case: 370481 

Type: Issue 

Component/Process: IBM DB2 for iSeries Source 

Description: The R4Z Start Monitor command incorrectly used NDBD instead of DBST. 

Jira issue: RECOB-9791 

Salesforce case: 354327 

Type: Issue 

Component/Process: Task Manager 

Description: Multiple reconnections to the source would be performed during Target Apply Detach/Attach. The issue was fixed using a Feature Flag. 

Jira issue: RECOB-9782 

Salesforce case: 357893 

Type: Issue 

Component/Process: Log Stream - Hadoop Target 

Description: When the data file size reached the maximum size defined, and was not divisible by 4000, the file would be overwritten resulting in missing data on the target. 

Jira issue: RECOB-9767 

Salesforce case: 368345 

Type: Issue 

Component/Process: Hortonworks Data Platform (HDP) Target 

Description: When resuming a task after DDL failure, some changes would not be captured if the Stop task on table error setting was enabled. The issue was resolved using an internal parameter. 

Resolved issues in May 2025 Initial Release

The following issues have been resolved since Replicate November 2024 Service Release 1.

Jira issue: RECOB-9572 

Salesforce case: 320154 

Type: Issue 

Component/Process: UI 

Description: The Endpoint Servers tab would be missing from the UI when using a license for SAP ODP. 

Jira issue: RECOB-9706 

Salesforce case: 364921 

Type: Issue 

Component/Process: Oracle Source - Replicate Log Reader 

Description: Incorrect decompression of a rare Advanced Compression page format would cause unpredictable data problems. 

Jira issue: RECOB-9734 

Salesforce case: 362878 

Type: Issue 

Component/Process: Microsoft SQL Server Source 

Description: An unexpected error occurred in DRD due to new operations introduced with SQL Server 2022.   

Jira issue: RECOB-9588 

Salesforce case: 120540 

Type: Issue 

Component/Process: IBM DB2 for iSeries Source 

Description: When using DB2 iSeries ODBC driver 7.1.26/27 on Linux, incorrect data would be applied to the target. The issue was fixed using an internal parameter. 

Jira issue: RECOB-9512 

Salesforce case: 347786 

Type: Issue 

Component/Process: Snowflake on Azure Target 

Description: Snowflake OAuth authentication with Azure AD would fail when the code message was too long. 

Jira issue: RECOB-9547 

Salesforce case: 328818 

Type: Issue 

Component/Process: SAP HANA Source - Log based 

Description: Significantly improved performance by optimizing memory allocation. 

Jira issue: RECOB-9542 

Salesforce case: 346653 

Type: Issue 

Component/Process: SAP HANA Source - Log based 

Description: In rare cases, the task would stop with a recoverable error when reading the head of the Hana Log. 

Jira issue: RECOB-9546 

Salesforce case: 361613 

Type: Issue 

Component/Process: IBM DB2 for LUW Source 

Description: In rare cases, the task would fail during CDC when replicating a table with LOB columns that did not have a primary key or unique index. 

Jira issue: RECOB-9343 

Salesforce case: 328209 

Type: Issue 

Component/Process: IBM DB2 for iSeries Source 

Description: Duplicated records on the target would be created during Full Load for tables with no key. This also occurred when the Prevent creation of duplicate records on the target check box was selected. 

Jira issue: RECOB-9501 

Salesforce case: 313075 

Type: Enhancement 

Component/Process: IBM DB2 for z/OS Source 

Description: Some changes to tables that were committed during Full Load (and were therefore cached) would not be applied to the target. 

Jira issue: RECOB-9518 

Salesforce case: 350194 

Type: Issue 

Component/Process: Microsoft SQL Server Source 

Description: A deadlock would sometimes occur when running a CDC only task with multiple tables. This issue was resolved using an internal parameter. 

Jira issue: RECOB-9524 

Salesforce case: 334167 

Type: Issue 

Component/Process: Snowflake Target 

Description: After saving the endpoint, Test Connection would fail if the data folder had a non-default name. 

Jira issue: RECOB-9522 

Salesforce case: 355944 

Type: Issue 

Component/Process: Parallel Load 

Description: When a table was defined with parallel loading and full load was subsequently disabled, the task would still perform a full load of that table, even when it was resumed from timestamp. 

Jira issue: RECOB-9502 

Salesforce case: N/A 

Type: Issue 

Component/Process: SAP HANA - Full Record Mode 

Description: The task would be resumed from the incorrect position when Record mode was set to Full record. 

Jira issue: RECOB-9504 

Salesforce case: N/A 

Type: Issue 

Component/Process: SAP HANA - Full Record Mode 

Description: The task would fail when replicating more than two tables when Record mode was set to Full record.  

Jira issue: RECOB-9483 

Salesforce case: N/A 

Type: Issue 

Component/Process: Engine 

Description: When executing commands in sub processes, a file descriptor leak would occur on Linux with kernel version 5.3 or later. 

Jira issue: RECOB-9437 

Salesforce case: N/A 

Type: Enhancement 

Component/Process: SAP Application (DB) 

Description: Various enhancements to Datetime data type support using internal parameters. 

Jira issue: RECOB-9503 

Salesforce case: 343566 

Type: Issue 

Component/Process: SAP HANA Source (Log based CDC) 

Description: DATE, SECONDDATE and TIMESTAMP columns would be replicated as NULL using SAP HANA SPS7 from version 7.73. 

Jira issue: RECOB-9488 

Salesforce case: 350135 

Type: Issue 

Component/Process: Oracle Source - Replicate Log Reader  

Description: In rare cases, the task would crash when a regular UPDATE operation was followed by an UPDATE (on the same table) that consisted of separate INSERT and DELETE operations. 

Jira issue: RECOB-9448 

Salesforce case: 346629 

Type: Issue 

Component/Process: Snowflake Target 

Description: During CDC, a NOT NULL constraint violation would occur when trying to apply changes to LOB columns. The issue was resolved using a feature flag. 

Known issues

The following is the list of known issues in Replicate May 2025.

Jira issue: RECOB-9718

Salesforce case: 364509 

Type: Issue 

Component/Process: Google BigQuery Target 

Description: Nullability checks are unnecessarily performed on a MERGE query for a unique index, thereby slowing down the query process. 

Jira issue: RECOB-9724 

Salesforce case: 367453 

Type: Issue 

Component/Process: SAP HANA Source 

Description: In HANA SPS7, if a DML updated more than 131040 records, Replicate performs delete and update operations causing the records to be deleted in the target table. 

Jira issue: RECOB-9625

Salesforce case: 362694 

Type: Issue 

Component/Process: Microsoft SQL Server Source 

Description: In “Backup only” mode, changes are not captured after a Rebuild Index operation. 

Jira issue: RECOB-9792

Salesforce case: 350194

Type: Issue 

Component/Process: Microsoft SQL Server Source 

Description: “Failure in executing add article through batch” and “Failure upon initial CAPTURE fitness checking” errors sometimes occur when replicating from Microsoft SQL Server 2022. The workaround is to create the article manually.

Jira issue: RECOB-9446

Salesforce case: 350236 

Type: Issue 

Component/Process: SAP Application with SAP HANA 

Description: Excessive latency might occur when replicating a VRBK table.

Jira issue: RECOB-9402

Salesforce case: 350358 

Type: Issue 

Component/Process: SAP HANA - Full Record Mode 

Description: The cdcFixedWaitInterval and cdcMaxWaitInterval internal parameters do not work when Record mode is set to Full record.

Jira issue: RECOB-9401

Salesforce case: 350353 

Type: Issue 

Component/Process: SAP HANA - Full Record Mode 

Description: The SAP archiving users to filter endpoint setting does not work when Record mode is set to Full record. 

Jira issue: RECOB-9384

Salesforce case: N/A 

Type: Issue 

Component/Process: SAP HANA - Full record mode 

Description: The Metadata only Advanced Run option does not work when Record mode is set to Full record. 

Jira issue: RECOB-9757

Salesforce case: 370426

Type: Issue

Component/Process: SAP HANA Source

Description: When using the sapHanaAppSupport internal parameter, negative currency values are replicated as positive numbers during Full Load.

Jira issue: RECOB-9741

Salesforce case: 357893

Type: Issue

Component/Process: Hadoop target via Log Stream

Description: intermittent data loss sometimes might occur when replicating to Hadoop target via Log Stream. The workaround is to restart the Log Stream-to-Hadoop replication task.

Jira issue: RECOB-9696

Salesforce case: 368345

Type: Issue

Component/Process: Hadoop Target

Description: Records might sometimes be missing from the Hadoop partition when a DDL change occurs on the source.

Jira issue: RECOB-9531

Salesforce case: N/A

Type: Issue

Component/Process: Snowflake Target

Description: The Eclipse Adoptium 17 JVM used by Replicate consumes excessive CPU when using thew Snowpipe Streaming loading method.

Downloads

Download this release from the Product Downloads page on Qlik Community.

About Qlik

Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.

qlik.com