Qlik Replicate - November 2025 Initial Release until Service Release 1

Charlton_Book — Tue, 10 Feb 2026 16:34:09 GMT

Table of Contents

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

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.

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

Resolved issues in Replicate November 2025

This section describes all issues that have been resolved since Replicate May 2025 initial release.

Resolved issues in Replicate November 2025 Service Release 1

The following issues have been resolved in Replicate November 2025 Service Release 1:

Jira issue: RECOB-10762

Salesforce case: 412967

Type: Issue

Component/Process: Microsoft Azure SQL Database Target

Description: In homogenous replication, when working in “Transactional apply” mode or in “Batch Optimized Apply” mode that switched to one-by-one mode, a “0 rows affected” error would occur when a DATETIME column was part of the primary key on the target.

Jira issue: RECOB-10311

Salesforce case: N/A

Type: Enhancement

Component/Process: Logging

Description: The Log Record Trace was improved to report key values correctly.

Jira issue: RECOB-10753

Salesforce case: N/A

Type: Issue

Component/Process: Metadata Manager

Description: Long VARCHAR columns would be incorrectly replicated into Microsoft SQL Server LOB columns, when Allow unlimited LOB size was selected.

Jira issue: RECOB-10750

Salesforce case: 408429

Type: Issue

Component/Process: PostgreSQL Target

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

Jira issue: RECOB-10722

Salesforce case: 413986

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: An error would occur when decompressing a transaction log that contained encrypted blocks. The issue was resolved by leaving the log compressed in such cases.

Jira issue: RECOB-10693

Salesforce case: 423275

Type: Issue

Component/Process: IBM DB2 for LUW Source

Description: Replicate would sometimes falsely detect a DB2 pureScale environment.

Jira issue: RECOB-10684

Salesforce case: 407419

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: Values are replicated to incorrect columns in multi-insert operations for a table defined as HCC or COMPRESS ADVANCED HIGH.

Jira issue: RECOB-10736

Salesforce case: N/A

Type: Issue

Component/Process: IBM DB2 for z/OS Source

Description: After adding a new LOB column, UPDATE and DELETE operations would not be replicated for records that existed before the column was added.

Jira issue: RECOB-10521

Salesforce case: N/A

Type: Enhancement

Component/Process: Salesforce Source

Description: Added support for OAuth authentication.

Jira issue: RECOB-10705

Salesforce case: 415967

Type: Issue

Component/Process: IBM DB2 for z/OS Source

Description: The Replicate log would sometimes be flooded with R4DB2 messages related to DB2 z/OS command ‘START TRA(MON) CLASS(1) SCOPE(GROUP)’ failure.

Jira issue: RECOB-10699

Salesforce case: 407010

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: Redundant errors would be shown when using an alternate backup folder, due to an unnecessary validation check for existing files.

Jira issue: RECOB-10407

Salesforce case: 404410

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: The task would crash when a referenced column value was in a very rare non-standard format.

Jira issue: RECOB-10673

Salesforce case: N/A

Type: Enhancement

Component/Process: IBM DB2 for z/OS Source

Description: Added support for the DB2 z/OS IFI feature CDDS (APAR PH61836) by setting the R4Z parameter useCDDS.

Jira issue: RECOB-10612

Salesforce case: N/A

Type: Issue

Component/Process: Replicate Installation

Description: The Replicate installation would fail on RHEL 9.7 with a “Missing OPENSSL_3.4.0 library” error.

Jira issue: RECOB-10635

Salesforce case: 419617

Type: Issue

Component/Process: SAP Application (DB), SAP Application, Sorter

Description: Tasks configured to use a SAP Application (DB) or SAP Application source with a backend process that generated self-committed events, would sometimes crash after reloading a table.

Jira issue: RECOB-10603

Salesforce case: 418235

Type: Issue

Component/Process: Microsoft Azure Synapse Target

Description: The task would crash following a connection timeout if the target component was configured to use external tables, and was closed following a connection timeout.

Jira issue: RECOB-10622

Salesforce case: 388202

Type: Issue

Component/Process: SAP Application (DB), Sorter

Description: When a task contained both cluster tables and transparent tables, changes would sometimes not be captured.

Jira issue: RECOB-10631

Salesforce case: N/A

Type: Issue

Component/Process: Microsoft Fabric Target

Description: When replicating to a Mirrored Database, changes would not be applied to the target.

Jira issue: RECOB-10630

Salesforce case: 413329

Type: Issue

Component/Process: SAP HANA Trigger Based

Description: In Full Record mode, resuming a task with numerous tables would result in significant latency on the target.

Jira issue: RECOB-10607

Salesforce case: 413913

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: When an UPDATE operation was performed on a wide table with Advanced Compression, a crash would sometimes occur when applying the change to the target.

Jira issue: RECOB-10628

Salesforce case: 413329

Type: Issue

Component/Process: SAP HANA Trigger Based

Description: In Full Record mode, the task would fail to create CDC artifacts for a table that contained a column with the suffix _OLD, resulting in a “Duplicate column name" error.

Jira issue: RECOB-10584

Salesforce case: 416618

Type: Issue

Component/Process: Google BigQuery Target

Description: When using the Apply changes using SQL MERGE option with batch optimized apply, BYTES columns would sometimes contain incorrect data.

Jira issue: RECOB-10596

Salesforce case: 415216

Type: Issue

Component/Process: UI

Description: A table’s primary key would sometimes be incorrectly indicated as transformed.

Jira issue: RECOB-10544

Salesforce case: 408429

Type: Issue

Component/Process: Batch optimized apply

Description: If the target used CSV files to load data to the NET Changes table and an error occurred in batch optimized apply mode, the task would crash after the next insert to the Net Changes table.

Jira issue: RECOB-10562

Salesforce case: 413905

Type: Issue

Component/Process: Supportability

Description: Multiple tasks would not stop after 30 minutes and would eventually time out. A Feature Flag was added to produce a Linux dump when a task is forcefully ended in such a scenario.

Jira issue: RECOB-10539

Salesforce case: 388639

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: When replicating a table with invisible columns, and the Support invisible columns endpoint option was enabled, a crash would sometimes occur when applying the change to the target.

Jira issue: RECOB-10499

Salesforce case: 403578

Type: Issue

Component/Process: SAP HANA Source (SAP Application Server)

Description: When resuming a task and the table metadata was changed when the task was stopped, the metadata would not be retrieved, and the task would fail.

Jira issue: RECOB-10529

Salesforce case: 405607

Type: Issue

Component/Process: Batch optimized apply, Oracle target

Description: INSERT operations would sometimes be missing from the target when replicating to Oracle.

Jira issue: RECOB-10494

Salesforce case: 412746

Type: Issue

Component/Process: Oracle Target, Batch optimized apply

Description: When batch optimized apply failed and the task changed to one-by-one replication, if the Preserve transactional integrity task setting was enabled, Replicate would try to apply the records which it already applied.

This would result in all the changes included in the operation to be written to the apply_exceptions control table, which would impact performance and increase target latency.

Resolved issues in Replicate November 2025 initial release

The following issues have been resolved in Replicate November 2025 initial release:

Jira issue: RECOB-10056

Salesforce case: 383886

Type: Issue

Component/Process: PostgreSQL Source

Description: BYTEA value would be changed to empty string when it was not changed during an UPDATE.

Jira issue: RECOB-9913

Salesforce case: 374875

Type: Issue

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

Description: A recoverable error would sometimes be interpreted as a table error, resulting in the table being suspended.

Jira issue: RECOB-10137

Salesforce case: 394229

Type: Issue

Component/Process: Log Stream

Description: The log stream replication task would sometimes stop capturing changes without returning an error.

Jira issue: RECOB-9872

Salesforce case: 361285

Type: Issue

Component/Process: Microsoft Azure ADLS Target

Description: When using parquet file format, the header column change_mask would pad zeros to the right instead of to the left. This issue was resolved using a feature flag.

Jira issue: RECOB-10130

Salesforce case: 385138

Type: Issue

Component/Process: Notifications

Description: On edit latency conditioned notification, the values for "Latency exceeds" and "Clear notification" cannot be changed.

Jira issue: RECOB-10127

Salesforce case: 387202

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: When no Oracle Wallet settings were configured and an encrypted Redo Record was detected, the task would continue reporting a warning message instead of stopping with a fatal error.

Jira issue: RECOB-10113

Salesforce case: 380079

Type: Issue

Component/Process: SAP ODP Source

Description: Full Load for several tables would remain in Queue status when the Delta extraction interval was set to 0.

Jira issue: RECOB-10030

Salesforce case: 386285

Type: Issue

Component/Process: Test Connection

Description: Snowflake test connection would fail when using the ADDON API for credentials.

Jira issue: RECOB-10009

Salesforce case: 370435

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: When the archived redo log was being prepared by the Oracle archiver process (ARCn), the task would stop with the following non-recoverable error:

Archived Redo log with the sequence 'nnnnnnn' RLID 'nnnnnnnnnn' does not exist

Jira issue: RECOB-9908

Salesforce case: N/A

Type: Issue

Component/Process: Task Manager

Description: Replicate would sometimes incorrectly report a table's loading status as completed, even though it had not.

Jira issue: RECOB-10098

Salesforce case: 378148

Type: Issue

Component/Process: Informix Source

Description: The Informix Discard process would remove records incorrectly when the LSN contained an odd number of hexadecimal digits.

Jira issue: RECOB-9920

Salesforce case: 376773

Type: Issue

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

Description: During CDC, UPDATEs would sometimes be applied as INSERTs, resulting in duplicate records on the target.

Jira issue: RECOB-10082

Salesforce case: 378148

Type: Issue

Component/Process: IBM Informix Source

Description: When an Informix Discard data operation occurred after the transaction was already written to the SWAP file, the last event would not be sent to a target.

Jira issue: RECOB-10077

Salesforce case: 339762

Type: Issue

Component/Process: IBM DB2 for z/OS Source

Description: During Full Load, XML data would sometimes be malformed, resulting in task crashes and other unpredictable behavior.

Jira issue: RECOB-9970

Salesforce case: N/A

Type: Issue

Component/Process: Snowflake Target

Description: Generating a refresh token would prompt for the Client ID/Client Secret each time.

Jira issue: RECOB-9761

Salesforce case: N/A

Type: Enhancement

Component/Process: Unified Snowflake Target

Description: When a task is configured with the drop_column": "IGNORE" property, the target column will now become nullable instead of being dropped.

Jira issue: RECOB-10064

Salesforce case: 383808

Type: Issue

Component/Process: Oracle Source - General

Description: When SELECT permission for SYS.OBJ$ was not provided, clicking Test Connection in the endpoint dialog would return an error.

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:

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:

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:

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 fail 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.

Jira issue: RECOB-10374

Salesforce case: N/A

Type: Issue

Component/Process: SAP Extractor Source

Description: The transfer count would be shown as zero after Full Load completed. Note that this issue does not impact customers using the usesqlconnector internal parameter.

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

article Qlik Replicate - November 2025 Initial Release until Service Release 1 in Release Notes

Qlik Replicate - November 2025 Initial Release until Service Release 1

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 in Replicate November 2025

Resolved issues in Replicate November 2025 Service Release 1

Resolved issues in Replicate November 2025 initial release

Downloads