Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
- Qlik Community
- :
- Support
- :
- Support
- :
- Product News
- :
- Release Notes
- :
- Qlik Replicate Release notes - November 2021 Initi...
- Subscribe to RSS Feed
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Qlik Replicate Release notes - November 2021 Initial Release to Service Release 2
.png "Former Employee"){kind=icon}
frida_tell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Qlik Replicate Release notes - November 2021 Initial Release to Service Release 2
Table of Contents
- November 2021 Initial Release
- Migration and upgrade
- Upgrade paths
- Microsoft .NET Framework 4.8 upgrade/installation prerequisite
- Deleting the Replicate self-signed certificate afterupgrade
- Upgrading an installation with multiple data folders
- Compatibility with related products
- Google Cloud BigQuery target - Full Load change
- Changes to the Snowflake on Google endpoint settings
- Mapping to Microsoft Azure Databricks and Databrickson Google Cloud
- What's new?
- End of life/support features
- End of support
- Impending end of support or change in functionality
- Newly supported versions and third-party applications
- Resolved defects
- November 2021
- Qlik Replicate November 2021 – Patch Release Notes (PR06 - build 2021.11.469)
- Qlik Replicate November 2021 – Release Notes for PR04 (PR04 - build 2021.11.266)
- Qlik Replicate November 2021 – Release Notes for PR03 (PR03 - build 2021.11.229)
- Qlik Replicate November 2021 – Release Notes for PR02 (PR02 - build 2021.11.165)
- Qlik Replicate November 2021 – Release Notes for PR01 (PR01 - build 2021.11.140)
- Known Issues
November 2021 Initial Release
https://help.qlik.com/en-US/replicate/November2021/pdf/Replicate-Release-Notes.pdf
In addition to these release notes, customers are encouraged to read the GA release notes for all versions later than their current version as well as the cumulative release notes for the last Service Release of the previous version.
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 2021 and Replicate November 2020.
Upgrading from Replicate April 2020 (6.6)
If you are upgrading from Replicate April 2020 (6.6), you need to perform two upgrades. First upgrade to November 2020, and then upgrade to Replicate November 2021.
Upgrading from unsupported versions
If you are upgrading from Replicate 6.x (starting from 6.3), you first need to upgrade to Replicate 6.5, then to Replicate November 2020 (7.0) and finally to Replicate November 2021.
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 when 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
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 resolving any certificate trust issues when connecting to Replicate Console.
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
Qlik Replicate November 2021 is compatible with the following related products:
- Qlik Enterprise Manager November 2021
- Compose August 2021 SR1(Patch04) or later
- Compose for Data Lakes April 2020(6.6)
Google Cloud BigQuery target - Full Load change
In earlier versions, when the If target table already exists option was set to Truncate before loading (in the task settings' Full Load Settings tab), a DELETE statement would be executed. Starting from this version, a TRUNCATE statement will be executed instead.
Changes to the Snowflake on Google endpoint settings
The Target folder field in the endpoint settings' General tab was renamed Staging folder. In addition, the ODBC driver and Additional ODBC connection properties fields were removed from the Advanced tab (but can still be set via an internal parameter).
Mapping to Microsoft Azure Databricks and Databricks on Google Cloud
In earlier versions, when replicating to Microsoft Azure Databricks and Databricks on Google Cloud, the Replicate STRING data type was mapped to STRING. From this version, when replicating to Databricks 8.x or later, STRING will be mapped to VARCHAR (length).
As support for the VARCHAR data type was introduced in Databricks 8, creating a task that replicates to Databricks 8.x and then downgrading to a Databricks version earlier than 8 (in the same task) is not supported.What's new?
https://help.qlik.com/en-US/replicate/November2021/Content/Replicate/Release_Notes/features.htm
End of life/support features
This section provides information about End of Life versions, End of Support features, and deprecated features.
End of support
Deprecated driver versions
To optimize the replication process and minimize connectivity issues, support for old driver versions has been discontinued for several endpoints. For information about which drivers are currently supported for a particular endpoint, refer to the "Prerequisites" section for that endpoint in the Replicate Help.
Error count task notification
The More than (X) errors occurred when applying changes to a table task notification is no longer available.
Impending end of support or change in functionality
Endpoint versions
From Replicate May 2022, support for the following target endpoint versions will be discontinued:
- Databricks on AWS, Databricks on GoogleCloud, Microsoft Azure Databricks, and Microsoft Azure Databricks Delta:
- All versions that are not 7.3 LTS or 8.2 and later
- MicrosoftAzureHDInsight3.6
- Google Dataproc 1.x
- AmazonEMR5.x
- Kafka:
- Kafka1.x
- Confluent Platform 5.x
- Hadoop – Cloudera 5.x
- Hadoop – Hortonworks 2.x
- Hortonworks Data Platform(HDP) 2.x
Microsoft Internet Explorer Browser
From Replicate May 2022, Microsoft Internet Explorer will no longer be supported.
Change to Kerberos KDC options - Hadoop and Horton Data Platform endpoints
From Replicate May 2022, the option to choose Active Directory or MIT KDC when Replicate is installed on Windows will be superseded by the following options:
- Replicate on Windows - Active Directory KDC only
- Replicate on Linux - MIT KDC only
Newly supported versions and third-party applications
Source endpoint versions
The following source endpoint versions are now supported:
- PostgreSQL 13
Support for PostgreSQL 13 was first introduced in Replicate May 2021 SR3.Target endpoint versions
The following target endpoint versions are now supported:
- Databricks on AWS 8.x (starting from 8.2)
- Microsoft Azure Databricks (Blob or Data Lake Storage Gen2) 8.x (startingfrom8.2)
- Microsoft Azure Databricks Delta 8.x (starting from 8.2)
- PostgreSQL 13
Support for PostgreSQL 13 was first introduced in Replicate May 2021 SR3.Microsoft Edge Browser
This version introduces support for accessing the Replicate console using the Chromium-based Microsoft Edge browser.
Resolved defects
This section lists the resolved issues for the Replicate November 2021 initial release.
November 2021
| Component/Process: Engine - Character Substitution | Description: Character conversions involving source or substitute UTF16 characters ending in 3f do not work. |
| Jira issue: RECOB-3836 | |
| Salesforce case: 2241338 | |
| Type: Issue | |
| Component/Process: Oracle Source | Description: Enable CDC support of tables using long names under an internal property |
| Jira issue: RECOB-3886 | |
| Salesforce case: 00007622 | |
| Type: Issue | |
| Component/Process: IBM DB2 for z/OS Source | Description: Improved DO4GRANT JCL |
| Jira issue: RECOB-3881 | |
| Salesforce case: | |
| Type: Issue |
| Component/Process: SAP Extractors Source | Description: Improved Replicate SAP Extractors ABAP filtering |
| Jira issue: RECOB-3823 | |
|
Salesforce case: 2169999 |
|
| Type: Enhancements | |
| Component/Process: SAP Application (DB) Source | Description: Replication of SAP Catalog tables DD02L and DD03L would fail. |
| Jira issue: RECOB-3857 | |
| Salesforce case: 2267543 | |
| Type: Issue | |
| Component/Process: SAP Extractors Source | Description: The DROP command would fail for inactive tables. |
| Jira issue: RECOB-3861 | |
| Salesforce case: 2264657 | |
| Type: Issue | |
| Component/Process: Character Substitution | Description: UTF16 character conversions would not work for codes ending in 3F (e.g. 2A3F, 1E3F, etc.). |
| Jira issue: RECOB-3833 | |
| Salesforce case: 2241338 | |
| Type: Issue | |
| Component/Process: Microsoft SQL Server Source | Description: The header__timestamp would sometimes contain an invalid date (1969-12-31 23:59:59.'00000"), resulting in failed inserts on the target. Logging was added to assist with troubleshooting in the event that the fix does not resolve the issue. |
| Jira issue: RECOB-3537 | |
| Salesforce case: 2199292 | |
| Type: Issue |
| Component/Process: Metadata Manager | Description: Added the option to create multiple tables with the same name on target endpoints that do not support schemas. The option is enabled with a use of a common setting property. |
| Jira issue: RECOB-3797 | |
| Salesforce case: 2264084 | |
| Type: Issue |
| Component/Process: Oracle Source - Replicate Log Reader | Description: After upgrading the database to version 19c, tasks defined with a transformation would crash when capturing an UPDATE on an advanced compressed table. |
| Jira issue: RECOB-3777 | |
| Salesforce case: 2239919 | |
| Type: Issue | |
| Component/Process: MySQL Source | Description: Added logging to assist with troubleshooting CDC parsing errors. |
| Jira issue: RECOB-3781 | |
| Salesforce case: 2251636 | |
| Type: Issue | |
| Component/Process: IBM DB2 for z/OS Source | Description: An online status report was added for alerting about database lock issues. |
| Jira issue: RECOB-3414 | |
| Salesforce case: 2206746 | |
| Type: Enhancement |
| Component/Process: Amazon RDS PostgreSQL Source | Description: The timestamp of a captured DDL would be 1970-01-01 00:00:00. |
| Jira issue: RECOB-3786 | |
| Salesforce case: 2260088 | |
| Type: Issue | |
|
Component/Process: Kafka target |
Description: Added an internal property for exceeding the 10MB message size limitation when loading AVRO-formatted messages into Kafka. |
| Jira issue: RECOB-3744 | |
| Salesforce case: 2240034 | |
| Type: Enhancement | |
| Component/Process: Server | Description: In a Hybrid Data Delivery task, the change_sequence in the CT table would be different from the task_audit. |
| Jira issue: RECOB-3679 | |
| Salesforce case: N/A | |
| Type: Issue |
| Component/Process: Engine | Description: Replicate would fail to capture some of the changes after a Hybrid Data Delivery task recovered from a crash. |
| Jira issue: RECOB-3678 | |
| Salesforce case: N/A | |
| Type: Issue | |
| Component/Process: Oracle Target | Description: When working in Transactional Apply mode or when switching to a one-by-one process, Oracle SQL statements exceeding 32K would wrongly cause ORA-01460 to be interpreted as a recoverable error instead of a data error. |
| Jira issue: RECOB-3738 | |
| Salesforce case: N/A | |
| Type: Issue | |
|
Component/Process: Oracle Source, Log Stream |
Description: When replicating from an Oracle Standby database via a Log Stream staging task, the internal parameter for determining how long to wait for changes to be applied to the standby database would not work properly. This would result in missing records on the target. |
| Jira issue: RECOB-3645 | |
| Salesforce case: 2232270 | |
| Type: Issue |
| Component/Process: File Channel | Description: Added support for providing additional FTS (File Transfer Service) connection string properties. |
| Jira issue: RECOB-3056 | |
| Salesforce case: 2115294 | |
| Type: Enhancement | |
| Component/Process: Microsoft Azure Synapse Analytics Target | Description: After a recoverable error, the task would stop with a fatal error when reattaching the target component. |
| Jira issue: RECOB-3651 | |
| Salesforce case: 2227947 | |
| Type: Issue | |
| Component/Process: Replicate Log Reader | Description: UPDATEs to the target would fail when replicating a table with advanced compression. |
| Jira issue: RECOB-3629 | |
| Salesforce case: 2243866 | |
| Type: Issue | |
|
Component/Process: Oracle Target |
Description: WhenUse direct path full loadwas enabled in the endpoint settings, columns of DATE type would not be loaded to the target. |
| Jira issue: RECOB-3641 | |
| Salesforce case: 2245555 | |
| Type: Issue |
| Component/Process: RDS SQL SERVER Source | Description: When capturing changes from wide tables (tables with a large number of columns), the data of all target columns except for the Primary Key/Unique Index segment would be NULL. |
| Jira issue: RECOB-3273 | |
| Salesforce case: N/A | |
| Type: Issue | |
| Component/Process: Snowflake target + Hybrid Data Delivery (HDD) | Description: When working with the Qlik Cloud Landing profile and a Snowflake target endpoint, Replicate will create an audit event report every 60 seconds about the last change sequence applied to the Changes Tables as well as a list of tables that were changed. HDD will then apply those changes to the storage app. |
| Jira issue: RECOB-3360 | |
| Salesforce case: N/A | |
| Type: Enhancement | |
| Component/Process: SAP Application (DB), SAP Application | Description: The AR_H_USER header column was missing from the Transformation dialog's header list. |
| Jira issue: RECOB-3624 | |
| Salesforce case: N/A | |
| Type: Issue | |
|
Component/Process: Sap Hana Trigger-Based Source |
Description: The max row id selection performance has been improved. |
| Jira issue: RECOB-3491 | |
| Salesforce case: 2207449 | |
| Type: Enhancement |
| Component/Process: Oracle Source, DB2Z Source, DB2 LUW Source, Microsoft SQL Server Source, Sybase ASE Source, File source, IBM for DB2 iSeries Source, Informix Source | Description: A memory leak would occur when using the listed source endpoints. |
| Jira issue: RECOB-3588, RECOB-3590, RECOB-3592, RECOB-3596, RECOB-3597, RECOB- 3594, RECOB-3591, RECOB-3595 | |
| Salesforce case: 2237164 | |
| Type: Issue |
| Component/Process: SAP Application (DB) | Description: When updating a Pool table or when changing a column, a default Before Image value would be replicated as an After Image value. |
| Jira issue: RECOB-3532 | |
| Salesforce case: N/A | |
| Type: Issue | |
| Component/Process: IBM DB2 for z/OS Source | Description: When parallel transactions were executed with a different CORRELATION ID, the AR_H_ USER header value for some of the data events would sometimes contain the CORRELATION ID of one of the parallel transactions. |
| Jira issue: RECOB-3547 | |
| Salesforce case: 2240572 | |
| Type: Issue | |
|
Component/Process: Salesforce Source |
Description: When capturing GAP events, the following error would occur: Error "Operation 'send BEGIN' and 'send COMMIT' exception message: hexBinary needs to be even-length" |
| Jira issue: RECOB-3525 | |
| Salesforce case: 2237092 | |
| Type: Issue | |
| Component/Process: Oracle Source - Replicate Log Reader | Description: The warning message "Partial INSERT event is ignored" would be reported when a table contained a LONG column and an UPDATE operation was performed. The warning was reported only when ALTER TABLE was used to add columns to the table. In such a case, the added columns would not be updated. |
| Jira issue: RECOB-3541 | |
| Salesforce case: 2229387 | |
| Type: Issue |
| Component/Process: Databricks on AWS | Description: Added support for the AWS GovCloud (US-East) and AWS GovCloud (US-West) regions. |
| Jira issue: RECOB-3523 | |
| Salesforce case: 2233793 | |
| Type: Enhancement | |
| Component/Process: Salesforce Source | Description: When Full Load failed with a recoverable error, the Salesforce bulk job would remain open. |
| Jira issue: RECOB-3246 | |
| Salesforce case: 2179781 | |
| Type: Issue | |
|
Component/Process: Databricks endpoints |
Description: Replicate will now identify itself via the User-Agent property when connecting to all Databricks endpoints. |
| Jira issue: RECOB-3438 | |
| Salesforce case: N/A | |
| Type: Enhancement | |
| Component/Process: SAP Extractor | Description: When using old SAP versions, SAP Extractor would fail with the following error: "The field 'SRSC_C_PROGCLASS_SEGM' is unknown". |
| Jira issue: RECOB-3305 | |
| Salesforce case: 2203763 | |
| Type: Issue |
| Component/Process: Java SDK Based Endpoints | Description: After removing a table with a DDL change from a task, stopping the task, adding the table back to the task, and then resuming the task, the table would still not be replicated. |
| Jira issue: RECOB-3371 | |
| Salesforce case: 2187829 | |
| Type: Issue | |
| Component/Process: SAP Application Source (DB) | Description: The Full Load passthru filter would create an incorrect statement when the client column was nested in the SAP table. |
| Jira issue: RECOB-3450 | |
| Salesforce case: 2233328 | |
| Type: Issue | |
|
Component/Process: SAP Application Source (DB) |
Description: The exposed size of character columns would be three times larger than the actual size. |
| Jira issue: RECOB-3372 | |
| Salesforce case: 2184987 | |
| Type: Issue | |
| Component/Process: Sybase ASE Source | Description: After capturing a DDL, Apply Changes or Store Changes tasks would fail to capture any more changes when the number of pages in the database exceeded 2147483647. |
| Jira issue: RECOB-3339 | |
| Salesforce case: 2228237 | |
| Type: Issue |
| Component/Process: Microsoft SQL Server Source | Description: After a table's metadata had been altered, Replicate would make redundant calls to retrieve other tables' metadata, resulting in degraded performance and latency. |
| Jira issue: RECOB-2873 | |
| Salesforce case: 2196532 | |
| Type: Issue | |
| Component/Process: Microsoft SQL Server Source | Description: When the endpoint's Replicate has file-level access to the backup log files option was enabled, Replicate would fail to decompress the transaction log. |
| Jira issue: RECOB-3058 | |
| Salesforce case: 2149163 | |
| Type: Issue | |
|
Component/Process: Microsoft SQL Server Source |
Description: When capturing changes from wide tables (tables with a large number of columns), the data of all target columns except for the Primary Key/Unique Index segment would be NULL. |
| Jira issue: RECOB-3269 | |
| Salesforce case: N/A | |
| Type: Issue | |
| Component/Process: SAP Application (DB) | Description: The Full Load passthru filter would create an incorrect statement when the client column was nested in the SAP table. |
| Jira issue: RECOB-3427 | |
| Salesforce case: 2233328 | |
| Type: Issue |
| Component/Process: Oracle Target | Description: An OCI timeout would occur when execution of a statement exceeded 10 seconds. |
| Jira issue: RECOB-3410 | |
| Salesforce case: 2227982 | |
| Type: Issue | |
| Component/Process: Oracle Target | Description: DELETE and UPDATE operations would not be replicated to the target when the WHERE clause contained a UNISTR function and the internal parameter useUnistrForWideChars was set. |
| Jira issue: RECOB-3385 | |
| Salesforce case: 2231710 | |
| Type: Issue | |
|
Component/Process: Salesforce Source |
Description: "Unable to stop HTTP transport" messages would be reported every few hours when the logging was set to "Error". As this is an EMP (Enterprise Messaging Platform) issue and Replicate successfully reconnects immediately after the error, the message will now only be reported when the logging is set to Trace/Verbose. |
| Jira issue: RECOB-3182 | |
| Salesforce case: 2206758 | |
| Type: Enhancement | |
| Component/Process: Replicate Engine | Description: Excessive memory consumption would sometimes be encountered in the case of repeated connection attempts. |
| Jira issue: RECOB-3237 | |
| Salesforce case: 2180466 | |
| Type: Issue |
| Component/Process: Amazon RDS for SQL Server Source | Description: Change capture would sometimes result in NULL value being replicated for LOB columns instead of the actual data. |
| Jira issue: RECOB-3125 | |
| Salesforce case: 2209255 | |
| Type: Issue | |
| Component/Process: SAP Extractor Source | Description: The SAP extractor delta job would fail when executed by Replicate. |
| Jira issue: RECOB-3227 | |
| Salesforce case: 2213864 | |
| Type: Issue | |
|
Component/Process: IBM for DB2 iSeries Source |
Description: Added support for the $AR_H_PROGRAM_NAME custom header column. The column contains the name of the iSeries program that changed the table data. |
| Jira issue: RECOB-3230 | |
| Salesforce case: N/A | |
| Type: Enhancement | |
| Component/Process: Amazon Redshift and Amazon S3 Targets | Description: Added support for the AWS GovCloud (US-East) region. |
| Jira issue: RECOB-3198 | |
| Salesforce case: 2219130 | |
| Type: Enhancement |
| Component/Process: IBM DB2 for iSeries Source | Description: If the IBM DB2 for iSeries endpoint was configured to use a UDTF and the journal events included CREATE TABLE (CT) entries, some changes would not be captured. |
| Jira issue: RECOB-3082 | |
| Salesforce case: 2149866 | |
| Type: Issue | |
| Component/Process: IBM Informix Source | Description: Capturing changes from tables with the BIGINT data type would fail. |
| Jira issue: RECOB-3224 | |
| Salesforce case: 2207371 | |
| Type: Issue | |
|
Component/Process: Amazon Redshift Target |
Description: The following Redshift error would be wrongly identified by Replicate as a data error, which would cause the task to switch to transactional apply mode: "error occurred while trying to execute a query: [SQLState 00000] SSL SYSCALL error: Connection timed out" |
| Jira issue: RECOB-3156 | |
| Salesforce case: 02217068 | |
| Type: Issue | |
| Component/Process: Replicate Installation | Description: Missing Active Directory read permissions on the Computers container would sometimes cause the installation to fail. The issue was resolved with a CLI parameter that prevents PrincipalContext from attempting to access the Computers container. |
| Jira issue: RECOB-3191 | |
| Salesforce case: N/A | |
| Type: Enhancement |
| Component/Process: PostgreSQL Source/Target | Description: When replicating to/from unsupported PostgreSQL versions, a warning would be returned instead of an error. |
| Jira issue: RECOB-3210 | |
| Salesforce case: N/A | |
| Type: Issue | |
| Component/Process: Upgrade | Description: Replicate Server would crash after upgrade due to a compatibility issue between the Scheduler and the automatic log cleanup option. |
| Jira issue: RECOB-3006 | |
| Salesforce case:N/A | |
| Type: Issue | |
|
Component/Process: Salesforce Source |
Description: Full Load would sometimes fail with a timeout error. |
| Jira issue: RECOB-3183 | |
| Salesforce case: 2211434 | |
| Type: Issue | |
| Component/Process: Salesforce Source | Description: After upgrade, the following error would sometimes be encountered: Buffering capacity 1048576 exceeded |
| Jira issue: RECOB-3181 | |
| Salesforce case: 2217080 | |
| Type: Issue |
| Component/Process: Databricks on Google Cloud endpoint | Description: Added support for Databricks on Google Cloud as a target endpoint. |
| Jira issue: RECOB-3017 | |
| Salesforce case: N/A | |
| Type: Enhancement | |
| Component/Process: SAP Extractor Source | Description: Extractors with names starting with a slash sign (e.g. /CRMBW/ACT_CAT_TXT) could not be activated. |
| Jira issue: RECOB-3038 | |
| Salesforce case: 2203757 | |
| Type: Issue | |
|
Component/Process: UI - Change Data Partitioning |
Description: Added an option to select 15 Minutes from the Partition every drop-down list. |
| Jira issue: RECOB-3151 | |
| Salesforce case: N/A | |
| Type: Enhancement | |
| Component/Process: Oracle Source, Microsoft SQL Server Source | Description: The password replace functionality would not work as expected. |
| Jira issue: RECOB-2737 | |
| Salesforce case: 2190539 | |
| Type: Issue |
| Component/Process: Microsoft SQL Server Source | Description: Tasks would fail to work with a table containing computed columns. |
| Jira issue: RECOB-3084 | |
| Salesforce case: 2204554 | |
| Type: Issue | |
| Component/Process: Snowflake on Azure Target | Description: When the internal parameter to ignore case was set in Snowflake, Replicate would not be able to retrieve the Primary Key information. This resulted in all DML operations being applied one-by-one. |
| Jira issue: RECOB-3048 | |
| Salesforce case: 2201519 | |
| Type: Issue | |
|
Component/Process: SAP Application (DB) Source |
Description: Changing a transformation on a SAP table and resuming the task would impact task performance. |
| Jira issue: RECOB-2631 | |
| Salesforce case: 2146786 | |
| Type: Issue | |
| Component/Process: SAP Application (DB) Source | Description: Cluster events would not be generated for a cluster object when the next change was performed on an object in another cluster, in the same transaction. |
| Jira issue: RECOB-3080 | |
| Salesforce case: 2206730 | |
| Type: Issue |
| Component/Process: Microsoft SQL Server Source | Description: In rare scenarios when encountering a non-standard UPDATE operation, the task would stop abnormally (without any errors). |
| Jira issue: RECOB-2978 | |
| Salesforce case: 2185703 | |
| Type: Issue | |
| Component/Process: SAP Application (DB) Source | Description: Performance issues would be encountered when the backend database tables had a large number of version definitions, which would be inserted into the dynamic metadata. After installing this patch release, it is strongly recommended to continue SAP Application (DB) Source tasks using the "Tables are already loaded. Start processing changes from" Run option, thereby cleaning the dynamic metadata. |
| Jira issue: RECOB-2735 | |
| Salesforce case: 2193906 | |
| Type: Issue | |
|
Component/Process: SAP HANA Source - Trigger-based CDC |
Description: When resuming a task from the "Source change position", the task would start from the subsequent interval instead of from the specified interval. |
| Jira issue: RECOB-2980 | |
| Salesforce case: 2160944 | |
| Type: Issue | |
| Component/Process: SAP Application Source | Description: Partial DELETE operations would be performed on cluster tables without converting primary key column values from the backend database data type to the corresponding SAP data type. When using SAP Application with IBM DB2 for iSeries, all cluster table primary key columns are defined as UTF-16. This would result in the DELETE operation not being performed on the target. |
| Jira issue: RECOB-3029 | |
| Salesforce case: 2131345 | |
| Type: Issue |
| Component/Process: Google Cloud BigQuery Target | Description: Apply Log debug messages were changed from trace to verbose severity. |
| Jira issue: RECOB-2856 | |
| Salesforce case: NA | |
| Type: Issue | |
| Component/Process: Microsoft SQL Server Source | Description: Queries for retrieving table metadata would sometimes take a long time when the schema contained a large number of tables. The issue was resolved by optimizing the query. The modified query can be enabled using an internal parameter. |
| Jira issue: RECOB-2911 | |
| Salesforce case: 2199568 | |
| Type: Enhancement | |
|
Component/Process: Microsoft SQL Server Source |
Description: Replicate would create future partitions (header__timestamp) after a server restart. |
| Jira issue: RECOB-2826 | |
| Salesforce case: 2188762 | |
| Type: Issue | |
| Component/Process: SAP Application (DB) Source, SAP Application Source | Description: Uninstalling R4SAP does not remove all installed SAP objects. |
| Jira issue: RECOB-2958 | |
| Salesforce case: 2203870 | |
| Type: Issue | |
| Component/Process: Sybase ASE Source | Description: Changes would not be captured when the event page number was bigger than 2147483647. |
| Jira issue: RECOB-2881 | |
| Salesforce case: 2200644 | |
| Type: Issue |
| Component/Process: Oracle Source - Replicate Log Reader | Description: In very rare situations, a "Failed to build 'where' statement" error would be encountered when reading the redo logs. |
| Jira issue: RECOB-2909 | |
| Salesforce case: 2189154 | |
| Type: Issue | |
|
Component/Process: IBM DB2 for z/OS Source |
Description: When encountering a connection issue on startup, the task would fail with a fatal error, instead of attempting to recover. |
| Jira issue: RECOB-2801 | |
| Salesforce case: 2164113 | |
| Type: Issue | |
| Component/Process: Sybase ASE Source | Description: Apply Changes or Store Changes tasks would fail to start (either from the beginning or from a timestamp) when the number of pages in the database exceeded 2147483647. |
| Jira issue: RECOB-2744 | |
| Salesforce case: 2192758 | |
| Type: Issue | |
| Component/Process: Sybase ASE Source | Description: The task would fail when trying to resume from a timestamp that preceded the first event in the log. Now, when a timestamp that precedes the first event in the log is specifier, the task will resume from the first event in the log. |
| Jira issue: RECOB-2832 | |
| Salesforce case: 2196747 | |
| Type: Issue |
| Component/Process: Google Cloud BigQuery Target | Description: When a connection error occurred and Replicate recovered the task automatically, the reported number of records replicated during Full Load would sometimes differ from the actual number. |
| Jira issue: RECOB-2322 | |
| Salesforce case: 2148578 | |
| Type: Issue | |
|
Component/Process: SAP Extractor Source |
Description: The task would fail if a column of type ACCP, DATS, or TIMS contained an invalid value. Now the task will not fail. Instead a placeholder with the default value will replace the invalid value: For DATS and ACCP: 1970-01-01 For TIMS: 00:00:00 |
| Jira issue: RECOB-2672 | |
| Salesforce case: 2188728 | |
| Type: Issue | |
| Component/Process: SAP Application (DB) Source Source | Description: All Primary Key columns in Pool tables would be exposed by the endpoint as nullable, resulting in failure to create the Primary Key on some targets. |
| Jira issue: RECOB-2701 | |
| Salesforce case: 2190057 | |
| Type: Issue | |
| Component/Process: Oracle Source - Replicate Log Reader | Description: When Unique Index columns containing NULL values were located near the end of the table, changes would sometimes not be captured. |
| Jira issue: RECOB-2767 | |
| Salesforce case: 2189273 | |
| Type: Issue |
| Component/Process: Oracle Source - Replicate Log Reader | Description: When capturing a SHRINK SPACE operation on Advanced Compressed tables, a DELETE operation that should have be ignored would be sent to the target. |
| Jira issue: RECOB-2291 | |
| Salesforce case: 2158576 | |
| Type: Issue | |
|
Component/Process: Oracle Source - Replicate Log Reader |
Description: In rare scenarios, when a bulk delete operation was performed on a source table, incorrect data might have been replicated to the target. |
| Jira issue: RECOB-2392 | |
| Salesforce case: 2145519 | |
| Type: Issue | |
| Component/Process: Oracle Source - Replicate Log Reader | Description: In rare scenarios, the task would crash when capturing changes from an Advanced Compression table that contained a LONG_RAW column. |
| Jira issue: RECOB-2427 | |
| Salesforce case: 2171158 | |
| Type: Issue | |
| Component/Process: Oracle Source - Replicate Log Reader | Description: In rare scenarios, UPDATE operations would sometimes not be captured after Oracle Split events. |
| Jira issue: RECOB-2639 | |
| Salesforce case: 2164535 | |
| Type: Issue |
| Component/Process: Oracle Source - Replicate Log Reader | Description: When capturing an UPDATE operation on a HCC COLUMN WISE table row, Replicate |
| Jira issue: RECOB-2284 | |
| Salesforce case: 2156140 | |
| Type: Issue | |
|
Component/Process: Oracle Source - Replicate Log Reader |
Description: In rare scenarios (involving a transformation being defined for the table), capturing UPDATE operations on wide Advanced Compression tables would cause the task to stop unexpectedly. |
| Jira issue: RECOB-2576 | |
| Salesforce case: 2180071 | |
| Type: Issue | |
| Component/Process: Oracle Source - Replicate Log Reader | Description: In rare scenarios (involving a transformation being defined for the table), capturing UPDATE operations on an Advanced Compressed record would cause the task to stop unexpectedly. |
| Jira issue: RECOB-2669 | |
| Salesforce case: 2187973 | |
| Type: Issue | |
| Component/Process: IBM DB2 for iSeries Source | Description: Replicate would fail to capture changes when the journal library and journal receiver library contained special characters. The issue was resolved using internal property. |
| Jira issue: RECOB-2673 | |
| Salesforce case: 2185127 | |
| Type: Issue |
| Component/Process: Hadoop Target | Description: When failover occurred during Full Load, the table would be suspended. Now, Replicate will try and upload the table with the newly updated name node. |
| Jira issue: RECOB-2688 | |
| Salesforce case: 2125169 | |
| Type: Issue | |
|
Component/Process: Oracle Source - Replicate Log Reader |
Description: When a row trailing column(s) was changed to NULL, the NULL value would sometimes not be replicated to the target. |
| Jira issue: RECOB-2711 | |
| Salesforce case: 2189593 | |
| Type: Issue | |
| Component/Process: UI - Adding tasks | Description:Added the Qlik Cloud Landing replication profile for use with Qlik Cloud Hybrid Data Delivery |
| Jira issue: RECOB-2805 | |
| Salesforce case: N/A | |
| Type: Enhancement | |
| Component/Process: Salesforce Source | Description: When capturing GAP events, the following error occurs: Error "Operation 'send BEGIN' and 'send COMMIT' exception message: hexBinary needs to be even- length" |
| Jira issue: RECOB-3876 | |
| Salesforce case: 2237092 | |
| Type: Issue | |
| Component/Process: Engine - Character Substitution | Description: UTF16 character conversions do not work for codes ending in 3F (e.g. 2A3F, 1E3F, etc.). |
| Jira issue: RECOB-3836 | |
| Salesforce case: 2241338 | |
| Type: Issue | |
| Component/Process: Google Cloud BigQuery Target | Description: When a CSV file cannot be loaded, missing events would occur on the target instead of reattach. |
| Jira issue: RECOB-3884 | |
| Salesforce case: 2255503 | |
|
Type: Issue |
Qlik Replicate November 2021 – Patch Release Notes (PR06 - build 2021.11.469)
These release notes provide details on the resolved issues and/or enhancements included in this patch release. All patch releases are cumulative, meaning that they include the fixes and enhancements provided in previous patch releases.
Jira issue: RECOB-5530
Salesforce case: 34641
Type: Issue
Component/Process: SAP HANA Source
Description: Filtering archiving user names that contained a period would not work.
Jira issue: RECOB-5456
Salesforce case: 34455
Type: Issue
Component/Process: SAP HANA Source
Description: SAP HANA views could not be replicated after upgrading to 2021.11.
Jira issue: RECOB-5516
Salesforce case: 37119
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: INSERT operations in a compressed table would be missing when Goldengate was enabled in Oracle.
Jira issue: RECOB-5510
Salesforce case: 37728
Type: Issue
Component/Process: MySQL Source
Description: A new table added during CDC would not be captured until the task was stopped and resumed.
Jira issue: RECOB-5500
Salesforce case: 38566
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: When the following settings were enabled in the endpoint's Advanced tab, the redo files would not be deleted automatically.
- Copy redo logs to temporary folder
- Replicate has file level access to temporary folder
- Access archived redo logs in folder
- Delete processed archived redo log files
Jira issue: RECOB-5490
Salesforce case: 36583
Type: Issue
Component/Process: PostgreSQL Source
Description: Change processing would fail when a timestamp record contained '-infinty' as a value.
Jira issue: RECOB-5220
Salesforce case: 32297
Type: Issue
Component/Process: MySQL Homogeneous
Description: ALTER TABLE operations would result in an unexpected character set being defined on the target.
Jira issue: RECOB-5468
Salesforce case: 38416
Type: Enhancement
Component/Process: Salesforce (Streaming CDC) Source Description: Added support for configuring the subscribe timeout value.
Jira issue: RECOB-5434
Salesforce case: 36027
Type: Issue
Component/Process: SAP Application (DB) Source
Description: When a captured cluster table was changed, SAP Client records that were not configured in SAP Application (DB) would be replicated.
Jira issue: RECOB-5444
Salesforce case: 21090
Type: Issue
Component/Process: Salesforce (Streaming CDC) Source
Description: Excessive memory would be consumed when reconnecting the HTTP client.
Jira issue: RECOB-5428
Salesforce case: 36960
Type: Issue
Component/Process: Salesforce (Streaming CDC) Source
Description: When only the LastModifiedDate column was changed, the UPDATE event would not be captured.
Jira issue: RECOB-5420 Salesforce case: 33783 Type: Issue
Component/Process: Microsoft SQL Server Source
Description: The LSN on a secondary replica in an AlwaysOn environment could not be located.
Jira issue: RECOB-5432
Salesforce case: 38075
Type: Issue
Component/Process: Teradata Target
Description: The TPT Log table name was formatted incorrectly (test patch).
Jira issue: RECOB-5397
Salesforce case: 3898
Type: Issue
Component/Process: File Target
Description: When the task was stopped and then started, the CDC files generated before the task was stopped would not be uploaded to Google Cloud. This would result in missing data on the target.
Jira issue: RECOB-5373
Salesforce case: 34751
Type: Issue
Component/Process: Installation
Description: The Qlik Replicate installation timeout was increased to 300 seconds.
Jira issue: RECOB-5363
Salesforce case: 33794
Type: Issue
Component/Process: Snowflake Azure Target
Description: In Batch Optimized Apply mode, when CLOB column length exceeded 65535 characters, and the JSONandXMLColumns-SnowflakeTarget option was turned on (the default), the task would fail.
Jira issue: RECOB-5175
Salesforce case: 30284
Type: Issue
Component/Process: Microsoft Azure SQL (MS-CDC) Source
Description: Replicating a non-MDY DATE format in the default language, would cause the Full Load task to fail.
Jira issue: RECOB-5374
Salesforce case: 31588
Type: Issue
Component/Process: SAP Application (DB) Source
Description: After upgrading to Replicate 2021.11 and resuming a task, the first DDL change would cause the associated table to be suspended.
Jira issue: RECOB-5381
Salesforce case: 25486
Type: Issue
Component/Process: Snowflake Target
Description: In Batch Optimized Apply mode, explicit COMMITs would be performed when applying changes to Snowflake, resulting in unacceptable costs.
Jira issue: RECOB-5367
Salesforce case: 27920
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: When a wide SQL Server table contained long VARCHAR columns, in rare scenarios, the VARCHAR column values would be replicated to the wrong record.
Jira issue: RECOB-5341
Salesforce case: 30113
Type: Issue
Component/Process: SAP Application (DB) Source
Description: A special SAP date using the year 0101 would not be replicated correctly.
Jira issue: RECOB-5326
Salesforce case: 32256
Type: Issue
Component/Process: SAP HANA Source - Trigger Based Capture
Description: When using the Commit-Timestamp internal parameter, latency issues would be encountered when processing changes from non-captured tables.
Jira issue: RECOB-5323
Salesforce case: 34585
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: When starting the task from a timestamp, Replicate Log Reader would sometimes capture Dynamic Partition table operations from the wrong Dynamic Partition table.
Jira issue: RECOB-5306
Salesforce case: 34640
Type: Issue
Component/Process: Sybase ASE source
Description: Sybase ASE endpoint would replicate FLOAT data type incorrectly during Full Load and CDC.
Jira issue: RECOB-5275 Salesforce case: 33320
Type: Issue
Component/Process: Microsoft Databricks Azure Source
Description: When the Sequence storage format and gzip compression were selected, empty files would be left in the Databricks partition when the load operation was interrupted.
Jira issue: RECOB-5267
Salesforce case: 28583
Type: Issue
Component/Process: SAP Application (DB) Source
Description: Changes would sometimes not be captured when replicating from SAP cluster tables with Microsoft SQL Server as the backend database.
Jira issue: RECOB-5292
Salesforce case: 31453
Type: Issue
Component/Process: SAP Extractor Source
Description: The temporary Z-programs generated during the activation of an extractor would not be assigned to the Qlik protected namespace (QTQVC) or any SAP authorization group.
Jira issue: RECOB-5241
Salesforce case: 33124
Type: Issue
Component/Process: PostgresSQL Source
Description: The task would sometimes crash if a large number of tables were truncated in one operation.
Jira issue: RECOB-5233
Salesforce case: 28485
Type: Issue
Component/Process: SAP Extractor Source
Description: When reactivating the extractor in the extractors dashboard, the corresponding z-table would always be created with a different name, instead of its existing name.
Jira issue: RECOB-5163
Salesforce case: 31074
Type: Issue
Component/Process: Control Tables - Microsoft SQL Server Source, Hadoop Target
Description: When the DDL History Control table was enabled, and a column was changed from TEXT to VARCHAR(max) or vice versa, the task would encounter a recoverable error.
Jira issue: RECOB-5231
Salesforce case: 4844
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: Replicate Log Reader would crash after parsing a Direct Insert Redo Log Event 19.1.
Jira issue: RECOB-5169
Salesforce case: 23555
Type: Issue
Component/Process: Amazon Redshift Target
Description: Replicate would not attempt to reconnect to Amazon Redshift if the connection was lost.
Jira issue: RECOB-4870
Salesforce case: 2101374
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: When the Primary Key contained a DATETIME column, LOB lookup would fail, resulting in missing LOB columns.
Jira issue: RECOB-5192
Salesforce case: 26823
Type: Issue
Component/Process: SAP Application (DB) Source
Description: Replicating cluster LCHR values longer that 255 bytes would result in an error.
Jira issue: RECOB-5173
Salesforce case: 32472
Type: Issue
Component/Process: LOB Support
Description: LOB support would be disabled when the No record found for applying an update INSERT the missing target record error handling option was selected, AND a table was changed with a transformation.
These release notes provide details on the resolved issues and/or enhancements included in this patch release. All patch releases are cumulative, meaning that they include the fixes and enhancements provided in previous patch releases.
Jira issue: RECOB-5071
Salesforce case: NA
Type: Issue
Component/Process: Google Cloud BigQuery Target, Security
Description: When Create tables clustered by primary key was enabled in the endpoint's Advanced tab, and Apply changes using SQL MERGE was turned on in the task settings, INSERTs would expose the Primary Key data in the log.
Jira issue: RECOB-5179
Salesforce case: 31399
Type: Issue
Component/Process: SAP Application (DB) Source with a Microsoft SQL Server backend
Description: When trying to capture changes from a Cluster table, the task would sometimes crash with the following error: Incorrect PART_NO <> in the Cluster '<>' object part <>, possible changes are ignored
Jira issue: RECOB-5067
Salesforce case: 30567
Type: Issue
Component/Process: Google Cloud BigQuery Target
Description: When Create tables clustered by primary key was enabled in the endpoint's Advanced tab, and Apply changes using SQL MERGE was turned on in the task settings, INSERTs would fail when the Primary Key started or ended with a single quote.
Jira issue: RECOB-5145
Salesforce case: NA
Type: Issue
Component/Process: Addon samples
Description: The MyTransformation.c sample ADDON program could not be compiled.
Jira issue: RECOB-5049
Salesforce case: NA
Type: Issue
Component/Process: Microsoft Azure ADLS Target, Google Cloud Storage Description: Removed an old log4j version.
Jira issue: RECOB-5106
Salesforce case: 28058
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: When a table contained an enlarged LONG column, UPDATE operations would result in the following error (excerpt): Multiple assignments to same column
Jira issue: RECOB-5098
Salesforce case: 26207
Type: Issue
Component/Process: SAP Extractor Source
Description: Scheduling an extractor in the /QTQVC/EXTREP dashboard would not allow the execution mode to be changed.
Jira issue: RECOB-5096
Salesforce case: 20656
Type: Issue
Component/Process: SAP Extractor Source
Description: SAP Syslog space would reach full capacity when the max size parameter in SAP was not set correctly.
Jira issue: RECOB-5094
Salesforce case: 28485
Type: Issue
Component/Process: SAP Extractor Source
Description: When reactivating an extractor in the /QTQVC/EXTREP dashboard, a new table would be generated.
Jira issue: RECOB-5057
Salesforce case: 20548
Type: Issue
Component/Process: Log Stream with Microsoft SQL Server Source
Description: The task would fail when the source was Microsoft SQL Server and the forceDataRowLookup internal parameter was set.
Jira issue: RECOB-4971
Salesforce case: 19856
Type: Issue
Component/Process: Task Manager
Description: When a table configured to use Parallel Load was reloaded while Full Load was still in progress, the existing load processes would not be stopped. This would result in duplicate records on the target.
Jira issue: RECOB-5033
Salesforce case: 28664
Type: Issue
Component/Process: Snowflake on Azure, Apply changes using SQL MERGE
Description: Excessive memory consumption would occur when using the Apply changes using SQL MERGE option.
Jira issue: RECOB-4947
Salesforce case: 25690
Type: Issue
Component/Process: IBM DB2 for iSeries
Description: When the IBM DB2 for iSeries journal contained entries for objects not included in SYSTABLES (which might occur when not using a table- name filter, for example) the task would stop unexpectedly. The issue was fixed by issuing a warning and continuing the task.In addition, the maximum number of tables in a filter has been increased to 10000.
Jira issue: RECOB-4993 Salesforce case: N/A Type: Issue
Component/Process: SAP HANA Source
Description: CTS (Commit timestamp) trigger-based based capture mode would replicate the local timestamp for the change instead of UTC.
Jira issue: RECOB-4975
Salesforce case: 24134
Type: Issue
Component/Process: SAP HANA Source
Description: In CTS (Commit timestamp) trigger-based based capture mode, when starting the task from the current time, it would take a long time for CDC to start.
Jira issue: RECOB-4754
Salesforce case: 11912
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: Adding a new table to an existing publication would fail with a "snapshot is already generated" error. The issue was resolved with an internal parameter.
Jira issue: RECOB-4496
Salesforce case: NA
Type: Enhancement
Component/Process: Amazon S3 Target Description: Added support for Parquet file format.
Jira issue: RECOB-4924
Salesforce case: 28274
Type: Issue
Component/Process: MySQL Source
Description: Transactions would sometimes not be captured after resuming the task.
Jira issue: RECOB-4919
Salesforce case: 24055
Type: Enhancement + Issue
Component/Process: PostgreSQL Source
Description: Start Replication would fail with a fatal error if the slot was active.
Jira issue: RECOB-4674
Salesforce case: 19975
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: In rare scenarios, an empty string in the before-image would be changed to NULL.
Jira issue: RECOB-4815
Salesforce case: 24364
Type: Issue
Component/Process: Teradata Source, ODBC with CDC, Parallel Load
Description: When loading a table with parallel load in Full Load and Apply Changes replication mode, the task would sometimes crash.
Qlik Replicate November 2021 – Release Notes for PR04 (PR04 - build 2021.11.266)
This section describes the enhancements and resolved issues in this patch release.
Jira issue: RECOB-4859
Salesforce case: 19297
Type: Issue
Component/Process: Upgrade
Description: Added logging for troubleshooting upgrade errors.
Jira issue: RECOB-4465
Salesforce case: 9224
Type: Issue
Component/Process: MySQL homogenous
Description: In a MySQL homogenous task, a source column that was part of the Primary Key and that was defined with a non-default collation, would not be updated in Batch Optimized Apply mode.
Jira issue: RECOB-4817
Salesforce case: 10885
Type: Issue
Component/Process: Google Cloud BigQuery Target
Description: Importing a task JSON with credentials in clear text format would result in the following Test Connection error (excerpt): JSON parsing error: Invalid escape character in string. [1022
Jira issue: RECOB-4867
Salesforce case: 26834
Type: Issue
Component/Process: SAP Application (DB) Source
Description: When new columns are added to a table using a transformation, the values of columns added to a SAP transparent table after the task started would be replicated as NULL.
Jira issue: RECOB-4799
Salesforce case: 13634
Type: Issue
Component/Process: Google Cloud BigQuery Target
Description: When loading data to Google Cloud BigQuery, the following error would sometimes occur: sqlite3: database is locked.
Jira issue: RECOB-4810
Salesforce case: 24134
Type: Issue
Component/Process: SAP HANA Source -Trigger Based CDC
Description: Replicate would fail to create the artifact table when working in Commit Timestamp mode.
Jira issue: RECOB-4811
Salesforce case: 24134
Type: Issue
Component/Process: SAP HANA Source -Trigger Based CDC
Description: The query for retrieving the max commit timestamp from the CDC changes table would cause performance issues when there were a large number of changes.
Jira issue: RECOB-4812
Salesforce case: 24134
Type: Issue
Component/Process: SAP HANA Source -Trigger Based CDC
Description: When starting a new task with a new artifact table, performance issues would be encountered when using the MaxFetchIntervalSize internal parameter.
Jira issue: RECOB-4844
Salesforce case: 24994
Type: Issue
Component/Process: Informix Source
Description: The task would stop abnormally when capturing an uncommon UPDATE event.
Jira issue: RECOB-4732
Salesforce case: NA
Type: Enhancement
Component/Process: Google Cloud BigQuery Target
Description: Added QRI (Qlik Resource Identifiers) to Google Cloud BigQuery Target.
Jira issue: RECOB-4766
Salesforce case: 24122
Type: Issue
Component/Process: ARC Sources
Description: Replicate would skip a CSV file if the file name was earlier than the file that preceded it, which would result in data loss. The issue was resolved with the internal parameter.
Jira issue: RECOB-4711
Salesforce case: 22311
Type: Issue
Component/Process: Replicate Log Reader
Description: When starting a task from an SCN or a timestamp, some rows would not be captured when the table was Dynamic Partitioned and new partitions were created after the SCN start position.
Jira issue: RECOB-4829
Salesforce case: 26834
Type: Issue
Component/Process: SAP Application DB
Description: After a table metadata change, Replicate would sometimes fail to process a change to a transparent table.
Qlik Replicate November 2021 – Release Notes for PR03 (PR03 - build 2021.11.229)
This section describes the enhancements and resolved issues in this patch release.
Jira issue: RECOB-4795
Salesforce case: 1866
Type: Issue
Component/Process: Metadata Manager
Description: In rare cases, a task that included many transformations would abend on starting.
Jira issue: RECOB-4791
Salesforce case: 24955
Type: Issue
Component/Process: Databricks Azure
Description: In CDP mode, Replicate would insert the partition value at the end of the row, which would result in it being overridden by the the newly added VARCHAR column.
Jira issue: RECOB-4758
Salesforce case: 22128
Type: Issue
Component/Process: Transformations
Description: Adding a transformation to change the DateTime scale would have no effect.
Jira issue: RECOB-4716
Salesforce case: 22610
Type: Enhancement Component/Process: IBM DB2 for iSeries
Description: An option to keep char trailing spaces was added via an internal parameter.
Jira issue: RECOB-4641
Salesforce case: 7507
Type: Enhancement
Component/Process: Microsoft Azure Event Hubs
Description: An option to configure the maximum batch size was added via an internal parameter.
Jira issue: RECOB-4546
Salesforce case: 12706
Type: Issue
Component/Process: Replicate Server
Description: Replicate server on Linux would hang when Enterprise Manager started monitoring it.
Jira issue: RECOB-3871
Salesforce case: 2230521
Type: Issue
Component/Process: Replicate Installation
Description: Upgrading Replicate would result in the following error: repuictl.exe service stop returns 1
And the following warning message:
The application tried to install a more recent version of the protected Windows file C:\WINDOWS\system32\ucrtbase.
dll. You may need to update your operating system for this application to work correctly.
Jira issue: RECOB-4717
Salesforce case: 00023316
Type: Issue
Component/Process: Databricks Delta Azure
Description: When recreating the Net Changes table with new primary keys, Databricks would not update the new table immediately resulting in a failed transaction. The issue was resolved using internal parameters.
.
Jira issue: RECOB-4730, RECOB-4746
Salesforce case: NA
Type: Enhancement
Component/Process: SAP Extractor Source
Description: Full Load performance has been improved. The improvement must be turned on with an internal parameter.
Jira issue: RECOB-4312
Salesforce case: 15612
Type: Issue
Component/Process: Google Cloud BigQuery Targe
Description: After upgrading from Replicate 7.0 to 2021.5 sp08, tasks would fail.
Jira issue: RECOB-4383
Salesforce case: 14781
Type: Issue
Component/Process: MySQL Source
Description: When replicating from MySQL 8, change processing would fail and the table would be suspended with the following error (excerpt): Error parsing column - overflow occurred
Jira issue: RECOB-4285
Salesforce case: 14022
Type: Enhancement
Component/Process: PostgreSQL Source
Description: Added last commit timestamp to the stream position to enable resumption of stopped tasks.
Jira issue: RECOB-4679
Salesforce case: 20199
Type: Enhancement
Component/Process: Transformation add-on
Description: Improved the transformations add-on example.
Jira issue: RECOB-4645
Salesforce case: 2257301
Type: Issue
Component/Process: Oracle Source
Description: LOB lookup would not find a record when a key contained an NCHAR column.
Jira issue: RECOB-4549
Salesforce case: 5255
Type: Enhancement
Component/Process: Transformations
Description: Improved the error-handling of transformation verifications.
Jira issue: RECOB-4643
Salesforce case: 17445
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: Change capture would fail when capturing a redo log operation from a table configured with Advanced Compression 11.6 in an Oracle 12.1.0.2 compatible version.
Jira issue: RECOB-4640
Salesforce case: NA
Type: Enhancement
Component/Process: SAP HANA Trigger-Based Source
Description: Improved performance when using SAP HANA trigger-based CDC mode. The new capability must be turned on using a feature flag.
Jira issue: RECOB-4587
Salesforce case: 19658
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: When running on Microsoft SQL Server 2019, Windows Server 2022 Datacenter Azure Edition VM, Replicate would fail and show an incorrect error message.
Jira issue: RECOB-4578
Salesforce case: 19384
Type: Issue
Component/Process: IBM DB2 for iSeries Source
Description: Using a UDTF to capture changes from a journal library and a journal receiver library that contained special characters would not work. The issue was resolved using an internal parameter.
Jira issue: RECOB-4128
Salesforce case: N/A
Type: Issue
Component/Process: AIS Source
Description: Replicate would fail to parse an event and issue the following warning: "Number of fields retrieved (XX) does not match metadata (YY)".
Jira issue: RECOB-4536
Salesforce case: 15763
Type: Enhancement
Component/Process: Google BigQuery Target
Description: Added a new 'Apply Conflicts' error-handling policy that performs INSERTs instead of MERGE, when the Apply changes using SQL MERGE option is enabled and there are only INSERTs.
The option is enabled using an internal parameter.
Jira issue: RECOB-4559
Salesforce case: 19712
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: The assertion warning "Cannot convert a client identifier <> from codepage <> to UTF8" would be printed to the log numerous times resulting in severe performance degradation.
Jira issue: RECOB-4487
Salesforce case: 15759
Type: Issue
Component/Process: Snowflake Azure Target
Description: The task would crash in truncate mode when the target table had more columns than the source.
Jira issue: RECOB-4523
Salesforce case: 13303
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: Some changes would not be captured when the Oracle RAC instance Compatible Version was 12.1.0.2.
Jira issue: RECOB-4050
Salesforce case: 10044
Type: Issue
Component/Process: Batch Optimized Apply
Description: In Batch Optimized Apply mode, LOB lookup would not find a record when a DELETE operation and an INSERT operation were combined into a single UPDATE operation.
Jira issue: RECOB-4141
Salesforce case: 2264071
Type: Issue
Component/Process: Task Manager
Description: When a table was loaded using Parallel Load, some of the cached events would not be replicated.
Jira issue: RECOB-4506
Salesforce case: 8114
Type: Issue
Component/Process: Oracle Source - Replicate Log reader
Description: When GoldenGate was enabled in the Oracle instance, some INSERT operations would not be captured when capturing from a table configured with Advanced Compression.
Jira issue: RECOB-4228
Salesforce case: 10221
Type: Issue
Component/Process: SAP HANA Source
Description: When a table ID was larger than 268435455, Replicate would save it as a negative number. This would cause the resume process to fail with the following message: "Failed to create CDC artifacts for table id= '0'"
Qlik Replicate November 2021 – Release Notes for PR02 (PR02 - build 2021.11.165)
This section describes the enhancements and resolved issues in this patch release.
Jira issue: RECOB-4359 Salesforce case: NA
Type: Issue Component/Process: Security
Description: Addresses all log4j critical vulnerabilities (CVE-2021-45105, CVE-2021-45046, CVE-2021-44228, and CVE-2021-44832). CVE-2021-45105 and CVE-2021-44832 were addressed by ensuring that they do not apply to our products, while CVE-2021-45046 and CVE-2021-44228 were addressed by replacing the vulnerable log4j library with version 2.16.
Jira issue: RECOB-4422
Salesforce case: 16640
Type: Issue
Component/Process: SAP Extractor Source
Description: Importing the SAP Extractor transport into newer versions of S4HANA systems would fail.
Jira issue: RECOB-4059, RECOB-4061
Salesforce case: 4582
Type: Issue
Component/Process: Salesforce Source
Description: When exceeding the maximum buffer size in Salesforce, a buffer exceeded error would occur (as expected), but each retry attempt would be considered as if it was the first. This would result in an endless loop of reconnection attempts, all failing with the same error.
Jira issue: RECOB-4334
Salesforce case: NA
Type: Enhancement
Component/Process: Qlik Cloud Landing
Description: Added a new audit_event_type message "AuditPayloadQCLMetadata", and an audit event "AuditPayloadQCLMetadata".
Jira issue: RECOB-4378
Salesforce case: 16714
Type: Issue
Component/Process: SAP HANA Source
Description: Tasks configured to use SAP HANA Log-based CDC would sometimes consume excessive memory and crash.
Jira issue: RECOB-4238
Salesforce case: 00009224
Type: Issue
Component/Process: MySQL Homogenous
Description: In a MySQL homogenous task, if a source table contained a Unique Index with nullable columns but did not have a Primary Key, the table would be suspended.
Jira issue: RECOB-4193 Salesforce case: 8272
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: Timeouts would sometimes occur when reading from SQL Server system tables.
Jira issue: RECOB-4283
Salesforce case: 10044
Type: Issue
Component/Process: Sybase Source
Description: LOB Lookup would not retrieve values when one of the key values was NULL.
Jira issue: RECOB-4354
Salesforce case: 15913
Type: Issue
Component/Process: MS-CDC based endpoint
Description: LOB columns would be removed from tables without a Primary Key or Unique Index.
Jira issue: RECOB-4341
Salesforce case: 12875
Type: Issue
Component/Process: SAP HANA Source Log based
Description: INSERT operations to SAP HANA tables created by ABAP load scripts would not be captured.
Jira issue: RECOB-3936
Salesforce case: 2255408
Type: Enhancement
Component/Process: Salesforce Source
Description: Added an internal parameter to prevent connections from being reset during Full Load. When the parameter is set to “true”, Replicate will write Salesforce batches to intermediate files before sending them to the target endpoint.
Qlik Replicate November 2021 – Release Notes for PR01 (PR01 - build 2021.11.140)
This section describes the enhancements and resolved issues in this patch release.
Jira issue: RECOB-4222
Salesforce case: NA
Type: Issue
Component/Process: Microsoft Azure SQL (MS-CDC) Source
Description: Removed a redundant table portion collection, added trace messages, and resolved the "Cannot process events" error message when stopping a task.
Jira issue: RECOB-4223
Salesforce case: NA
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: Sensitive data might have been included in the log file.
Jira issue: RECOB-4296
Salesforce case: 12949
Type: Issue
Component/Process: SAP Extractor Source
Description: An authorization error would occur when trying to run SAP Extractor endpoint with transport version 900260.
Jira issue: RECOB-4250
Salesforce case: 5818
Type: Issue
Component/Process: IBM DB2 for LUW Source
Description: In rare scenarios, when a record was moved from one page to another as the result of an UPDATE operation, the transaction ID and stream position would not be replicated correctly.
Jira issue: RECOB-4152
Salesforce case: N/A
Type: Enhancement
Component/Process: Qlik Cloud Landing
Description: Prior to this patch, the Qlik Cloud Landing replication profile allowed both Full Load and Store Changes replication. From this patch, only Full Load replication is allowed.
Jira issue: RECOB-4148
Salesforce case: N/A
Type: Enhancement
Component/Process: Bidirectional Replication
Description: Bidirectional replication support was added for databases that do not produce an event when updating a record with the same values (e.g. IBM DB2 for z/OS).
Jira issue: RECOB-4215
Salesforce case: N/A
Type: Issue
Component/Process: SAP Application (DB)
Description: When the same table was captured in different tasks (e.g. the first task captured table A while the second task captured tables A and B), the tasks would sometimes generate different stream position values for identical changes if tables A and B were updated in the same transaction.
Jira issue: RECOB-4188 Salesforce case: 9982 Type: Issue
Component/Process: SAP HANA
Description: Defining the $AR_H_USER header variable (which is not supported with SAP HANA) in a transformation resulted in the table to being
suspended.
Jira issue: RECOB-4064
Salesforce case: N/A
Type: Enhancement
Component/Process: Oracle Source
Description: Added extra logging to gather information about the Oracle instance configuration.
Jira issue: RECOB-3975
Salesforce case: N/A
Type: Issue
Component/Process: SAP Application (DB)
Description: When updating a Pool table or when changing a column, a default Before Image value would be replicated as an After Image value.
Jira issue: RECOB-4122
Salesforce case: 02260579
Type: Issue
Component/Process: Microsoft SQL Server Source Description: The SQL Server safeguard commit would time out.
Jira issue: RECOB-3875
Salesforce case: 2264084
Type: Issue
Component/Process: Task Manager
Description: A warning about duplicate tables would be shown even though the parameter to suppress such warnings was set.
Jira issue: RECOB-3798
Salesforce case: 2264084
Type: Issue
Component/Process: Metadata Manager
Description: Added the option to create multiple tables with the same name on target endpoints that do no support schemas. The option is enabled with a use of a common setting property.
Jira issue: RECOB-3877
Salesforce case: 02251636
Type: Issue
Component/Process: MySQL Source
Description: Added logging to assist with troubleshooting CDC parsing errors.
Jira issue: RECOB-4007
Salesforce case: NA
Type: Issue
Component/Process: Microsoft Azure SQL (MS-CDC)
Description: SQL Server errors would occur while enabling MS-CDC system tables.
Jira issue: RECOB-4120
Salesforce case: NA
Type: Issue
Component/Process: Databricks Azure
Description: Databricks with Blob storage would not work when using Access Directly mode.
Jira issue: RECOB-4132
Salesforce case: 4113
Type: Issue
Component/Process: SAP Application (DB)
Description: Change capture would fail when a structure with a name exceeding 16 characters is defined in a captured table.
Jira issue: RECOB-3858
Salesforce case: 2267543
Type: Issue
Component/Process: SAP Application (DB)
Description: SAP Catalog tables DD02L and DD03L would not be replicated.
Jira issue: RECOB-3882
Salesforce case: N/A
Type: Enhancement
Component/Process: IBM DB2 for z/OS Source (R4DB2) Description: The DO4GRANT script was improved.
Jira issue: RECOB-4084
Salesforce case: 4707
Type: Issue
Component/Process: Oracle Source
Description: An Oracle UPDATE operation on a Long data value would cause a crash or suspend the table.
Jira issue: RECOB-4136
Salesforce case: 4702
Type: Issue
Component/Process: SAP Application
Description: When using an Oracle backend database, key date columns would be wrongly replicated when capturing partial DELETE operations.
Known Issues
This section lists the known issues for this release.
Component/Process: Microsoft Azure Databricks Delta
Jira issue: N/A
Salesforce case: N/A
Type: Issue
Description: Applying ADD COLUMN DDL operations to the target is not supported.
Component/Process: Metadata Manager
Jira issue: RECOB-3798
Salesforce case: 2264084
Type: Issue
Description: Creating multiple tables with the same name on target endpoints that do no support schemas results in duplicate table errors.
About Qlik
Qlik’s vision is a data-literate world, where everyone can use data and analytics to improve decision-making and solve their most challenging problems. A private SaaS company, Qlik offers an Active Intelligence platform, delivering end-to-end, real-time data integration and analytics cloud solutions to close the gaps between data, insights and action. By transforming data into Active Intelligence, businesses can drive better decisions, improve revenue and profitability, and optimize customer relationships. Qlik does business in more than 100 countries and serves over 50,000 customers around the world.