Qlik Replicate May 2026 - Technical Preview

Charlton_Book · Apr 30, 2026 5:56:20 AM

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
Resolved issues
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 2025 and Replicate November 2025.

Note: When upgrading, select All releases and all patches on the Downloads page to see all the available versions. The upgrade paths below refer to initial versions, but the upgrade path is identical for SR versions as well.

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 November 2023 SR.
Upgrade to Replicate November 2024 SR.
Upgrade to Replicate November 2025 SR.
Upgrade to Replicate May 2026.

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 November 2023 SR
Upgrade to Replicate November 2024 SR.
Upgrade to Replicate November 2025 SR.
Upgrade to Replicate May 2026.

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 2026 and all future Service Releases
Compose November 2023 or later
Compose for Data Lakes April 2020 (6.6)

Resolved issues

The following issues have been resolved in this version:

Jira issue: RECOB-11251

Salesforce case: 430619

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: In rare scenarios, an UPDATE operation might not capture an after-image value of one or more starting columns in a wide table.

Jira issue: RECOB-11215

Salesforce case: 441160

Type: Issue

Component/Process: Amazon RDS for MariaDB source

Description: Connecting to Amazon RDS for MariaDB with TLS 1.3 would fail.

Jira issue: RECOB-11197

Salesforce case: 418337

Type: Issue

Component/Process: Global Transformation

Description: Any global column transformation would remove the original endpoint column subtype of JSON and XML.

Jira issue: RECOB-10689

Salesforce case: 393670

Type: Issue

Component/Process: Security

Description: SQLite versions were upgraded to 3.51.1 due to a known vulnerability with earlier versions.

Jira issue: RECOB-10213

Salesforce case: 397801

Type: Issue

Component/Process: SAP ODP source

Description: The SAP ODP filter would not be passed to SAP when defined on an extractor running in CDC-only mode.

Jira issue: RECOB-10213

Salesforce case: 397801

Type: Issue

Component/Process: SAP ODP source

Description: The SAP ODP filter would not be passed to SAP when defined on an extractor running in CDC-only mode.

Jira issue: RECOB-10361

Salesforce case: 403874

Type: Issue

Component/Process: Notifications

Description: Test notification email would not allow the “+” sign.

Jira issue: RECOB-11122

Salesforce case: 414220

Type: Issue

Component/Process: IBM DB2 for LUW source + File target

Description: Some UPDATEs would be missing when replicating a VARCHAR column.

Jira issue: RECOB-11123

Salesforce case: 396347

Type: Issue

Component/Process: IBM DB2 for iSeries source

Description: After resuming a task, capturing changes from a table that contained binary decimal columns would cause the task to crash.

Jira issue: RECOB-11159

Salesforce case: 423853

Type: Issue

Component/Process: Sybase target

Description: Truncate table would not be performed within a multi-statement transaction.

Jira issue: RECOB-11158

Salesforce case: 416046

Type: Issue

Component/Process: Sybase target

Description: When a table on the target was defined with cluster primary key, duplicate records would cause the task to enter an endless recoverable error instead of handling it as a standard duplication error.

Jira issue: RECOB-11148

Salesforce case: 438331

Type: Issue

Component/Process: IBM DB2 for z/OS source

Description: Failure to communicate with the source database would be handled as a FATAL error in a very specific scenario.

Jira issue: RECOB-11134

Salesforce case: 442203

Type: Issue

Component/Process: Task import

Description: Importing a task would fail for task names exceeding 32 characters.

Jira issue: RECOB-11085

Salesforce case: 439592

Type: Issue

Component/Process: Task import

Description: The repctl gettaskstatus command requires the monitor_data parameter instead of it being optional.

Jira issue: RECOB-11084

Salesforce case: 439984

Type: Issue

Component/Process: Snowflake target

Description: The task would sometimes fail with a timeout error during the "COPY INTO" phase.

Jira issue: RECOB-11046

Salesforce case: 440089

Type: Issue

Component/Process: Snowflake target with Snowpipe Streaming

Description: When using Snowpipe Streaming as the loading method, loading very large tables would consume an excessive amount of memory, which would eventually result in the task crashing and entering a loop of loading and crashing.

Jira issue: RECOB-11039

Salesforce case: 437801

Type: Issue

Component/Process: Amazon Redshift target

Description: VARBYTE column in Redshift appears as a BLOB

Jira issue: RECOB-11010

Salesforce case: 437226

Type: Issue

Component/Process: Microsoft SQL Server source

Description: When specifying an Alternate backup folder which did not contain the required logs, the task would stop with an unclear message instead of issuing a warning an continuing.

Jira issue: RECOB-10997

Salesforce case: 430021

Type: Issue

Component/Process: Microsoft Fabric Target – Mirrored Database

Description: Tables would sometimes be suspended with the following error:

No data rows available

Jira issue: RECOB-10996

Salesforce case: 436142

Type: Issue

Component/Process: Microsoft SQL Server source

Description: The task would sometimes crash while reading the transaction log backup.

Jira issue: RECOB-10995

Salesforce case: 437152

Type: Issue

Component/Process: Snowflake target

Description: The Snowflake hostname for China account (.cn) would not work.

Jira issue: RECOB-10983

Salesforce case: 435943

Type: Issue

Component/Process: Table transformation

Description: Table transformation would cause the table key columns to be ordered incorrectly, even if the index was not changed in the manipulation.

Jira issue: RECOB-10970

Salesforce case: 432837

Type: Issue

Component/Process: PostgreSQL source

Description: After resuming a task that did not capture any changes for the minute before it was stopped, no changes would be captured.

Jira issue: RECOB-10967

Salesforce case: 432391

Type: Issue

Component/Process: Kafka target

Description: Excessive memory consumption during the task, that steadily increases.

Jira issue: RECOB-10936

Salesforce case: 433474

Type: Issue

Component/Process: Amazon S3 target

Description: Corrupted data file would be treated as a recoverable error instead of a fatal table error.

Jira issue: RECOB-10933

Salesforce case: 430775

Type: Issue

Component/Process: Security

Description: The org.apache.logging.log4j:log4j-core component was upgraded to 2.25.3 due to known vulnerabilities with the installed versions.

Jira issue: RECOB-10930

Salesforce case: 435016

Type: Issue

Component/Process: Oracle source

Description: Incorrect 11.12 parsing of multi-delete operation would occur when a table was created with ROWDEPENDENCIES.

Jira issue: RECOB-10880

Salesforce case: 424255

Type: Issue

Component/Process: SAP HANA source

Description: Full record mode would sometimes not work properly with tables that contained numerous columns.

Jira issue: RECOB-10878

Salesforce case: 432913

Type: Issue

Component/Process: SAP ODP source

Description: Capture from CDS View would start failing after stopping and resuming the task.

Jira issue: RECOB-10869

Salesforce case: 417562

Type: Issue

Component/Process: SAP Extractor source

Description: CDC was aborted one hour after a table was reloaded, which caused the task to enter a recoverable error.

Jira issue: RECOB-10861

Salesforce case: 420989

Type: Issue

Component/Process: SAP Hana Log based CDC

Description: When capturing changes from partitioned tables, DELETE operations would sometimes fail at the target with a 'row not found' error.

Jira issue: RECOB-10856

Salesforce case: 404961

Type: Issue

Component/Process: Metadata run option

Description: After Stopping the task and using the “Recreate all tables” run option, the task would be resumed from NOW instead of the last LSN/LRI stream position.

Jira issue: RECOB-10853

Salesforce case: 428408

Type: Issue

Component/Process: Snowflake target

Description: After replicating to Snowflake, intermediate files on Replicate server would never be deleted.

Jira issue: RECOB-10805

Salesforce case: 427401

Type: Issue

Component/Process: Oracle source

Description: Clarification of the v$transaction permission in the help.

Jira issue: RECOB-10797

Salesforce case: 427417

Type: Issue

Component/Process: Engine

Description: When a user without CREATE SCHEMA permission tried to create an existing schema, an error would be returned incorrectly.

Jira issue: RECOB-10774

Salesforce case: 423114

Type: Issue

Component/Process: Microsoft SQL Server source

Description: The task would sometimes crash after DBCC Lookup invocation.

Jira issue: RECOB-10773

Salesforce case: 427484

Type: Issue

Component/Process: Oracle source

Description: When a table contained a long raw and the maximum LOB size was greater than or equal to 64K, the task would crash.

Jira issue: RECOB-10748

Salesforce case: 420235

Type: Issue

Component/Process: Oracle source

Description: The table would be suspended if the limited LOB size value was changed and a DDL was detected.

Jira issue: RECOB-10667

Salesforce case: 421961

Type: Issue

Component/Process: MySQL-to-MySQL task

Description: When the schema of the source and target are in the same MySQL instance and a control table is included in the replication, the task would sometime fail with the following error:

Process crashed with signal 11

Jira issue: RECOB-10637

Salesforce case: 419699

Type: Issue

Component/Process: Amazon S3 staging

Description: During Full Load, tasks would sometimes fail with the following error due to the connection being actively refused by Amazon:

Unable to execute HTTP request: Connect to s3.amazonaws.com:443

The issue was resolved by implementing a retry mechanism with a maximum of three retries before the error occurs.

Jira issue: RECOB-10577

Salesforce case: 403115

Type: Issue

Component/Process: SAP extractor

Description: When using the internal parameter removeJobAfterTaskStop, failed tasks used the existing job run in SAP instead of initiating a new process, resulting in missing data on the target.

Jira issue: RECOB-10824

Salesforce case: 428945

Type: Issue

Component/Process: IBM Informix source

Description: The task would sometimes not recover automatically after database maintenance.

Jira issue: RECOB-10746

Salesforce case: 408429

Type: Issue

Component/Process: PostgreSQL target

Description: Failure to load the CSV file into the Net Changes table would return a recoverable error (resulting in an endless loop) instead of switching to one-by-one apply.

Known issues

Salesforce (Incremental Load) source endpoint: In the Technical Preview version, the new option to connect via HTTPS to the proxy server is not supported.

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

Qlik Replicate May 2026 - Technical Preview