Qlik Replicate - May 2024 Initial Release and Service Release 1

Charlton_Book — Tue, 28 Jan 2025 13:03:50 GMT

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

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

Preventing log stream replication tasks from failing after upgrade

The introduction of the new Retrieve all source columns on UPDATE option option might impact your existing log stream replication tasks. If you are upgrading from a version earlier than Replicate May 2024, 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.

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.

Endpoint versions that are no longer supported

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

Resolved issues and enhancements in Replicate May 2024 Service Release 1

The following section describes the issues resolved between Replicate May 2024 initial release and Replicate May 2024 Service Release 1.

Jira issue: RECOB-9039

Salesforce case: 156279

Type: Issue

Component/Process: ARC Source

Description: Using a network drive in AIS Router would sometimes result in missing data on the target.

Jira issue: RECOB-9005

Salesforce case: N/A

Type: Issue

Component/Process: Sorter

Description: In rare scenarios, incorrect changes would be generated by Oracle Log Reader after Stop/Resume, resulting in unpredictable behavior.

Jira issue: RECOB-8983

Salesforce case: 311921

Type: Issue

Component/Process: Log Stream

Description: Missing events would sometimes occur after Detach/Attach or Stop/Resume.

Jira issue: RECOB-9094

Salesforce case: 310873

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: When using redo event 11.22, missing INSERTs would occur when processing multiple INSERTs on a compressed page that was not compressed prior to the INSERTs.

Jira issue: RECOB-9081

Salesforce case: 320141

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: In rare scenarios, incorrect parsing of DELETE events in the redo log record would generate a "The Redo Log DELETE event contains an unknown structure" warning followed by various issues.

Jira issue: RECOB-9053

Salesforce case: 318417

Type: Issue

Component/Process: SAP Application (DB)

Description: Transparent table LOB values would not be replicated when one of the key columns was DATE (DATS in SAP).

Jira issue: RECOB-9065

Salesforce case: 316883

Type: Issue

Component/Process: SAP HANA Source (Log based)

Description: When capturing changes from large SAP HANA backup log files in Application Connection mode, errors would sometimes occur during CDC.

Jira issue: RECOB-9034, RECOB-8963

Salesforce case: 310873

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: When using redo event 11.22, missing INSERTs would occur when processing multiple INSERTs.

Jira issue: RECOB-8927

Salesforce case: 303767

Type: Issue

Component/Process: PostgreSQL Source

Description: When the year in the TIMESTAMP source column was later than 9999, a different value would be shown for Full Load and CDC on the target. This issue was resolved using an internal parameter.

Jira issue: RECOB-8856

Salesforce case: N/A

Type: Issue

Component/Process: Snowflake Target

Description: When the task settings were configured to create the control table schema, the task would fail with the following error:

Failed to delete directory

Jira issue: RECOB-8876

Salesforce case: N/A

Type: Issue

Component/Process: SAP HANA Source (Trigger based)

Description: The task would sometimes get stuck after a connection failure.

Jira issue: RECOB-8952

Salesforce case: 310514

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: After upgrading Oracle 19g to the July 2024 patch, UPDATE operations would sometimes not be captured, and the following warning would be shown:

A compressed row cannot be parsed

Jira issue: RECOB-8888

Salesforce case: 308237

Type: Enhancement

Component/Process: DB2 iSeries Source

Description: Support for the BOOLEAN data type was added (from iSeries 7.5).

Jira issue: RECOB-8891

Salesforce case: 173454

Type: Issue

Component/Process: Parallel load

Description: Tasks configured to use parallel full load would sometimes crash after reloading more than one table.

Jira issue: RECOB-8937

Salesforce case: 308087

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: The bidirectional task would fail after the first change in the corresponding task.

Jira issue: RECOB-8855

Salesforce case: 301410

Type: Issue

Component/Process: Google Cloud BigQuery Target

Description: The task would fail when connecting to Google BigQuery, due to a missing tmp folder.

Jira issue: RECOB-8802

Salesforce case: 302261

Type: Issue

Component/Process: Salesforce Source IL

Description: An option to see the object PickListValueInfo was added using an internal parameter.

Jira issue: RECOB-8799

Salesforce case: 291593

Type: Issue

Component/Process: Teradata Target

Description: Records missing due to a TPT error would result in the table being suspended, instead of continuing with a warning as in previous Replicate versions. This issue was resolved using an internal parameter.

Jira issue: RECOB-8816

Salesforce case: 170520

Type: Issue

Component/Process: SAP HANA Source

Description: When replicating from SAP HANA Cloud, errors would occur as the task would try to create the attrep_cdc_changes table columns with CS_ column store types, which are no longer supported.

Jira issue: RECOB-8842

Salesforce case: 303478

Type: Issue

Component/Process: DB2 iSeries Source

Description: During CDC, Replicate would set the value of numeric fields with scale definition to zero, resulting in the following error:

Convert to numeric failed with error 1003

Jira issue: RECOB-8490

Salesforce case: 153406

Type: Issue

Component/Process: IBM DB2 for LUW Source

Description: Data loss would occur after using the ADMIN_MOVE_TABLE command.

Jira issue: RECOB-8747

Salesforce case: 0168123

Type: Issue

Component/Process: Salesforce Source (Incremental Load)

Description: Due to the addition of the CreatedDate to the data retrieval query, tables would be suspended after upgrading to Replicate 2024.5.

Jira issue: RECOB-8841

Salesforce case: 166673

Type: Issue

Component/Process: IBM DB2 for z/OS Source

Description: Repeated "Instance recreated” errors would be handled as fatal errors instead of recoverable errors.

Jira issue: RECOB-8830, RECOB-8943

Salesforce case: 302108

Type: Issue

Component/Process: SAP HANA Source (Log based)

Description: Excessive memory consumption would sometimes occur when running Replicate on Linux.

Jira issue: RECOB-8755

Salesforce case: 158476

Type: Issue

Component/Process: SAP HANA Source (Log based)

Description: Changes that were part of the last log file block would sometimes not be captured.

Jira issue: RECOB-8786

Salesforce case: 298081

Type: Issue

Component/Process: MongoDB Source

Description: High memory and CPU consumption would sometimes occur when capturing many changes. The issue was resolved with an internal property that controls the maximum size of the reader queue.

Jira issue: RECOB-8797

Salesforce case: 298821

Type: Issue

Component/Process: Snowflake Azure Target

Description: The Max file size setting was added to the General tab of the endpoint settings.

Jira issue: RECOB-8733

Salesforce case: 175070

Type: Issue

Component/Process: Snowflake Target

Description: When the setIgnoreCaseFlag parameter was enabled, the task would sometimes fail to remove the old staging area or create a new one.

Jira issue: RECOB-8761, RECOB-8805

Salesforce case: 168796

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: After upgrading Oracle 19g to the July 2024 patch, data would not be replicated properly due to incorrect page decompression in DIRECT-INSERT or MULTI-INSERT operations.

Jira issue: RECOB-8766

Salesforce case: N/A

Type: Enhancement

Component/Process: SAP ODP Source

Description: Support for D34R and RSTR data types was added.

Jira issue: RECOB-8750

Salesforce case: N/A

Type: Issue

Component/Process: SAP HANA Source - UI

Description: Views were not shown in the UI Table Selection dialog.

Jira issue: RECOB-8743

Salesforce case: N/A

Type: Issue

Component/Process: Amazon Kinesis Target - UI

Description: Fixed a UI typo in Message Properties.

Jira issue: RECOB-8721

Salesforce case: N/A

Type: Issue

Component/Process: Oracle Target

Description: INSERT operations would sometimes fail with the following errors (excerpt).

ORA-12838: cannot read/modify an object after modifying it in parallel

The issue was resolved using an internal property to disable the ALTER SESSION PARALLEL DML operation.

Jira issue: RECOB-8726

Salesforce case: 163674

Type: Issue

Component/Process: SAP Extractor Source

Description: The processed records counter in the SAP Extractor logs would sometimes show zero for full load and delta loads.

Jira issue: RECOB-8694

Salesforce case: 174180

Type: Issue

Component/Process: PostgreSQL Source - Logging

Description: When setting the task not to replicate LOB columns, an incorrect failure message would be printed as INFO for every event.

Jira issue: RECOB-8725

Salesforce case: N/A

Type: Issue

Component/Process: Replicate Installation

Description: The Replicate Linux installation file wrongly contained a public code-signing key.

Jira issue: RECOB-8709

Salesforce case: N/A

Type: Issue

Component/Process: Security

Description: Replicate would ship with an outdated log4net version and a vulnerable Newtonsoft.Json file.

Jira issue: RECOB-8611

Salesforce case: 159309

Type: Issue

Component/Process: SAP HANA Source + Log Stream

Description: In CTS mode, the following error would sometimes occur when replicating the /CHPDPE/CEITMPX table:

SqlState: HY000 NativeError: 4 cannot allocate enough memory

The issue was fixed with a feature flag.

Jira issue: RECOB-8678

Salesforce case: 160381

Type: Issue

Component/Process: SAP ODP

Description: “Batch optimized apply” mode would ignore DELETE operation when a record was also updated in the same batch.

Jira issue: RECOB-8680

Salesforce case: 165375

Type: Issue

Component/Process: SAP ODP

Description: When capturing changes from a BW table, an “Out of bounds” error would sometimes occur.

Jira issue: RECOB-8679

Salesforce case: 155357

Type: Issue

Component/Process: SAP ODP

Description: Missing data would occur during Full Load, following SAP network errors.

Jira issue: RECOB-8542

Salesforce case: 165719

Type: Issue

Component/Process: Replicate Installation

Description: The Replicate Linux installation would fail if there was no systemctl.

Jira issue: RECOB-8576

Salesforce case: 162044

Type: Issue

Component/Process: SAP HANA Source

Description: The task would crash when source lookup was configured in the transformation.

Jira issue: RECOB-8698

Salesforce case: 295901

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: The task would crash after upgrading Oracle 19g to the July 2024 patch.

Jira issue: RECOB-8598

Salesforce case: 153905

Type: Issue

Component/Process: Kafka target

Description: Stopping the task would cause a crash when the endpoint server license was missing or when the endpoint server was not running. This issue was resolved using an internal parameter.

Jira issue: RECOB-8633
Salesforce case: 128634
Type: Issue
Component/Process: Parallel apply in Batch optimized apply mode
Description: When the Apply batched changes to multiple tables concurrently option was enabled, data would sometimes be missing after reattaching to the target (following a disconnect). The issue was resolved using a feature flag, which returns a recoverable error instead of attempting to reattach.

Jira issue: RECOB-8691

Salesforce case: N/A

Type: Issue

Component/Process: Snowflake targets

Description: The task would sometimes fail when using Snowflake internal storage.

Jira issue: RECOB-8651

Salesforce case: 171424

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: When the last table column of a table with supplemental logging set on all columns was marked as unused, UPDATE operations would sometimes result in unexpected results on the target

Jira issue: RECOB-8560

Salesforce case: 153711

Type: Issue

Component/Process: Databricks (Cloud Storage)

Description: When running multiple tasks against the same database, the CDC partition table files would be created with same name, thereby overriding each other.
The issue was resolved with a Feature Flag at task level.

Jira issue: RECOB-8614

Salesforce case: 175635

Type: Issue

Component/Process: SAP Application (DB)

Description: When a captured cluster document change deleted all rows of all its captured tables, missing DELETE operation and unnecessary assertion messages would be encountered.

Jira issue: RECOB-8626

Salesforce case: 171607

Type: Issue

Component/Process: Metadata Manager

Description: Tasks would fail when using the use_manipulation_pk_for_apply feature flag with Store Changes replication.

Jira issue: RECOB-8637

Salesforce case: N/A

Type: Enhancement

Component/Process: Databricks Lakehouse (Delta)

Description: Added support for Databricks Volumes.

Jira issue: RECOB-8627

Salesforce case: 161454

Type: Issue

Component/Process: Amazon Kinesis

Description: The connection would fail when using IAM Role for EC2 to connect to Amazon Kinesis, after using Key Pair authentication to connect to Amazon S3.

Jira issue: RECOB-8582

Salesforce case: 153169

Type: Issue

Component/Process: Microsoft SQL Server Target

Description: When Use BCP for loading tables was enabled in the endpoint settings, the maximum LOB size would be limited to 63 KB.

Jira issue: RECOB-8604

Salesforce case: 166180

Type: Issue

Component/Process: Replicate Engine

Description: After upgrading to Replicate 2024.5, it would not be possible to connect to Databricks (Delta) if FIPS was enabled on Windows.

Jira issue: RECOB-8537

Salesforce case: 154701

Type: Enhancement

Component/Process: Security

Description: Added an option to install Replicate on Linux without using "RPM", and without allowing the creation of a new USER/GROUP.

Jira issue: RECOB-8620

Salesforce case: 162987

Type: Issue

Component/Process: Oracle Source - Replicate Log Reader

Description: In rare scenarios, INSERT operations on wide tables would be replicated with partial column values.

Jira issue: RECOB-8565

Salesforce case: 170484

Type: Issue

Component/Process: Microsoft SQL Server Source

Description: When moving data from SQL Server, a missing column name in the table definitions would cause an infinite notification loop in the repsrv.log file, with the following message:

mssql_resolve_sqlserver_table_column_attributes(...) failed to find column

Jira issue: RECOB-8592

Salesforce case: 158504

Type: Issue

Component/Process: SAP Application (DB)

Description: Added an internal property to prevent the addition of SAP Catalog tables to the list of SAP Application (DB) backend tables.

Jira issue: RECOB-8550

Salesforce case: 164667

Type: Issue

Component/Process: UI

Description: The task settings’ Environmental errors tab would not show the proper settings.

Jira issue: RECOB-8465

Salesforce case: 165513

Type: Issue

Component/Process: UI

Description: The total number of the selected tables would no longer be shown at the bottom of Designer view.

Jira issue: RECOB-8538

Salesforce case: 162298

Type: Issue

Component/Process: SAP HANA Source

Description: Log-based CDC would fail or would keep reading from the same position when processing large multi-segment backup logs.

Jira issue: RECOB-8518

Salesforce case: N/A

Type: Issue

Component/Process: UI

Description: The table keys would be incorrectly shown in the UI after defining key transformations.

Jira issue: RECOB-8477

Salesforce case: 154293

Type: Issue

Component/Process: Log Stream

Description: Replication over log stream tasks would sometimes fail during task initialization.

Jira issue: RECOB-8507

Salesforce case: 150857

Type: Issue

Component/Process: SAP HANA Source

Description: The task would sometimes start very slowly, impacting the creation of its captured tables list.

Jira issue: RECOB-8405

Salesforce case: 156279

Type: Issue

Component/Process: AIS Source

Description: Added an internal parameter: printCSVFileNamesInInfo

When the parameter is set to TRUE (and logging is set to INFO or higher), the Replicate IMS source endpoint will write CSV file names and their creation date to the Replicate log.

As turning on the parameter will increase the log size, customers should monitor it to avoid storage issues. To reduce the logging impact, best practice is to maintain only a reasonable backlog of CSV files, and to delete CSV files that have already been applied to target. If the log size becomes excessive, set the parameter to FALSE to stop the additional logging.

Jira issue: RECOB-8400

Salesforce case: 152188

Type: Issue

Component/Process: Microsoft Azure Synapse Analytics Target

Description: Older files would not be deleted from ADLS staging during reload. This would result in the task failing due to duplicate records or because of non-matching records.

Jira issue: RECOB-8469

Salesforce case: 158504

Type: Issue

Component/Process: SAP Application (DB)

Description: Added an internal property to prevent the addition of SAP Catalog tables to the list of SAP Application backend tables.

Jira issue: RECOB-8481

Salesforce case: N/A

Type: Issue

Component/Process: Security - UI

Description: Updated Angular to a version that resolves known vulnerabilities.

Jira issue: RECOB-8475

Salesforce case: 161767

Type: Issue

Component/Process: Log Stream

Description: The "Retrieve all source columns on UPDATE" option would be turned off after upgrade, resulting in failure of tasks that needed this option to be turned on. The issue was resolved using a feature flag.

Jira issue: RECOB-8451

Salesforce case: 117989

Type: Issue

Component/Process: Infrastructure

Description: Added logging for troubleshooting the following intermittent error:

Message size <369295616> exceeds maximum of 16Mb

Jira issue: RECOB-8433

Salesforce case: N/A

Type: Issue

Component/Process: Microsoft Azure SQL Database Target

Description: Creation of the Primary Key/Unique Index would fail when the constraint name exceeded 128 characters.

Jira issue: RECOB-8338

Salesforce case: 147998

Type: Issue

Component/Process: Hadoop

Description: When using Hadoop without Hive access, the Full Load task would fail.

Jira issue: RECOB-8402

Salesforce case: 159978

Type: Issue

Component/Process: Databricks Delta

Description: When a data value contained binary zeros, both the Full Load and the CDC task would fail.

Jira issue: RECOB-8410

Salesforce case: N/A

Type: Issue

Component/Process: Security

Description: The java_file_factory component was updated to a version with non-vulnerable dependencies.

Resolved issues in Replicate May 2024 initial release

The following section describes the issues resolved in Replicate May 2024 initial release.

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.

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 - May 2024 Initial Release and Service Release 1 in Release Notes

Qlik Replicate - May 2024 Initial Release and 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

Deleting the Replicate self-signed certificate after upgrade

Upgrading an installation with multiple data folders

Compatibility with related products

Preventing log stream replication tasks from failing after upgrade

Required post-upgrade steps for tasks with a SAP ODP source endpoint

End of life/support features

Endpoint versions that are no longer supported

Resolved issues

Resolved issues and enhancements in Replicate May 2024 Service Release 1

Resolved issues in Replicate May 2024 initial release

Downloads