With a Unified license (formerly called Dual Use License) the legacy QlikView license is complemented with a Qlik Sense license that can be applied to the QlikView server as it includes QlikView entitlement license attributes. Such license needs to be activated with the Signed License Key (SLK). When a customer enters an Analytics Modernization Program (AMP, formerly known as Dual Use program), QlikView CALs (e.g. Named User CALs, Document CALS, Session CALs and Usage CALs) are converted into Professional User, Analyzer User,  and Analyzer Capacity User allocations based on the Analytics Modernization Program conversion ratios.

Here are two scenarios:

I. If a customer transitions to AMP with on-premise (client-managed) Qlik software (e.g. converts to the perpetual estate or convert to subscription Qlik Sense Enterprise on Windows), a Unified License containing the converted quantity of Professional Users, Analyzer Users and Analyzer Capacity would be delivered. This license contains a customized Qlik Sense Enterprise Signed License Key (SLK) which can also be deployed on QlikView Server and/or QlikView Publisher. If a user is assigned a Professional or Analyzer user license, this assignment information is synchronized to all Qlik Sense and QlikView deployments activated using this Unified License key. As such one user just needs one license to access the entire Qlik software platform (regardless if it is Qlik Sense or QlikView).

In this scenario, as long as the QlikView Server and Qlik Sense edition use the same Identity Provider (IdP) the user can access apps on both environments consuming only one user license allocation.

If the user license is reallocated in any of the systems to a different user, the same will occur across both QlikView and Qlik Sense environments.

II. If a customer transitions to AMP with Qlik Sense Enterprise SaaS add-on, a Qlik Sense Enterprise SaaS tenant may use a Unified License  for the on-premise deployment. The customer is able to upload QlikView document prepared by the on-premise QlikView software directly into Qlik Sense Enterprise SaaS for distribution.

A QlikView Server or a Qlik Publisher software can be activated in two ways:

1) Using a legacy method with 16-digit QlikView license key and the corresponding control number

2) Using a modern Unified License with Signed License Key containing needed QlikView Server and Publisher Service attribute(s). In this latter scenario, user license assignment (Professional/Analyzer) and analyzer capacity would be synchronized with other deployments using the same Signed License Key as it is done in the Unified License model

If the customer opts to remain in Perpetual licensing, the existing QlikView license model can be retained. Otherwise, if the customer opts for conversion into Subscription licensing model, a set of QlikView subscription license attributes mirroring the existing QlikView perpetual license key setup would be delivered such that the customer switch to the subscription QlikView keys without the need for an immediate migration project towards using Unified licensing.

Note: Please note that Qlik is no longer starting clients on the Perpetual license model. See End of Perpetual License Sales 

Environment:

• QlikView 
• Qlik Cloud 
• Qlik Sense Enterprise on Windows 
   

Related Content:

• How to Apply an unified Signed License Key for QlikView and Qlik Sense
• Qlik Multi-Cloud Frequently Asked Questions (FAQ)

How are sessions counted in Qlik Sense? 

The following are examples of how sessions are counted within Qlik Sense.  

• One user opens Qlik Sense Hub with One browser on One machine = 1 session
• One user opens Qllik Sense Hub with One browser but Multiple tabs on One machine= 1 session
• One user opens Qlik Sense Hub with Two different browsers on One machine= 2 sessions
• One user opens Qlik Sense Hub with One browser, then closes the browser and reopens it = 2 sessions
• One user opens Qlik Sense Hub with One browser on Two different machines = 2 sessions
• One user opens Qlik Sense Hub and two Apps in one browser, two different tabs and on a mobile device = 2 sessions
• One user opens Qlik Sense Hub from Two virtual proxy with One browser on One machine= 2 sessions
• One user opens Qlik Sense Management Console (QMC) with One browser on One machine = 1 session
• One user opens a Qlik Sense Mashup using Two Apps hosted from the same proxy = 1 session

Sessions will be terminated after the currently configured Session timeout in the Qlik Sense Proxy.
If the Qlik Sense engine or Proxy are terminated or crash, Sessions are ended right away.

Once the maximum number of parallel user connections (5) is reached, this will be documented in the AuditSecurity_Repository log. To identify if this is the issue, review the relevant log and review how the user is interacting with the system. 

The log is stored in:
C:\Programdata\Qlik\Sense\Log\Repository\Audit\AuditSecurity_Repository.txt

The related message reads: 
Access was denied for User: 'Domain\USER', with AccessID '264ff070-6306-4f1b-85db-21a8468939b5', SessionID: 'e3cd957b-a501-4bec-a3f8-d35170a73efa', SessionCount: '5', Hostname: '::1', OperationType: 'UsageDenied'

Related content:

Troubleshoot too many sessions active in parallel
Qlik Sense April 2018 and later- Service account getting "You cannot access Qlik Sense because you have no access pass"
 

The QlikView Services can be set up to either use the local QlikView Administrators Group, or Digital Certificates. The Service Account has specific requirements. 

The two options during installation are Use digital certificates and Use QlikView Administrators Group.

Use digital certificates: 

Authenticate communication between QlikView servers using digital certificates and SSL. This alternative is recommended in environments where not all servers have access to a common Windows Active Directory or when the security provided by certificate authentication is required. Note that digital certificates are only supported by Windows Server 2008 R2 and later.

Use QlikView Administrators Group: 

Authenticate communication between QlikView services based on membership in the local Windows group QlikViewAdministrators. This alternative can be used in environments where all servers that are part of the QlikView installation can authenticate using a common Windows Active Directory.

Regardless of the option chosen, the service account used to run the services has to be:

• A local administrator on the host operating system
• Be able to run as a network service
• Have access to all the QlikView related folder structure, such as ProgramData, Program Files, and configured application data (.qvw storage, .qvd storage, log files) locations. 

Note:  GMSA (Standalone Managed Service Accounts) are not supported for Qlik products

Environment: 

Related Content:

• How to Change QlikView Service Account
• Is GMSA supported for use with Qlik Products 
   

If your Qlik Sense Enterprise on Windows version is not compatible with the QSR database. 

This may occur if:

• You have upgraded Qlik Sense (for example: from May 2023 to November 2023) and have started the services. This will have migrated your QSR database from the May 2023 schema to the November 2023 schema.
  
  You have then decided to roll back to May 2023 and are attempting to restore the November 2023 QSR. They are not compatible and the migration will fail.
  
  the DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.
  
  
• If an incorrect version was installed during an upgrade of a Qlik Sense Enterprise on Windows multi node environment, such as installing different versions on RIM nodes, the Qlik Sense Repository service will not start on any node (including the central node). 
  

An incorrect version of Qlik Sense Enterprise on Windows in a multi node environment will trigger a database migration to this version. The result is that the Qlik Sense Repository service fails to start with the error: 

Fatal exception during startup Unable to update database to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based migration or enable automatic migration. Set DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.↵↓An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext

Resolution

As database migration started which had caused database corruption, you need to revert back to the old database backup to resolve this issue or contact Qlik Support for assistance.

Internal Investigation ID(s)

QB-8813

Environment

Qlik Sense Enterprise on Windows all versions

Qlik Talend Data Integration Data Movement Gateway supports connecting to a DB2i Source Endpoint using SSL. This article documents the step-by-step requirements to set up an ODBC connection to an iSeries with SSL enabled.

For general information about Qlik Data Movement Gateway, see Qlik Data Gateway - Data Movement.

1. Install the DB2i driver using the Qlik Talend Data Integration installation procedure.
   
   See Driver setup.
   
   

   $ cd /opt/qlik/gateway/movement/drivers/bin
   $ ./install db2iseries

2. Download the attached ibmi.conf (ibmi.zip) file and save it to /etc/stunnel before changing its permissions as follows:

   chmod 755 ibmi.conf

3. Place your certificate (AS400-7CA.txt) in /etc/stunnel before changing its permissions as follows:

   chmod 755 AS400-7CA.txt

4. Update the /etc/odbc.ini file, adding this section:

   [DB400]
   Description = SSL-enabled IBM i DSN
   Driver = IBM i Access ODBC Driver
   #System = as400-7.iSeries.com
   System = 127.0.0.1

5. Start the stunnel service using the following command:

   [root@RHEL8 ~]#sudo stunnel /etc/stunnel/ibmi.conf

6. Test the connection using isql:

   [root@RHEL8 ~]# isql -v DB400 IVAN IVAN

   +---------------------------------------+
   | Connected! |
   | |
   | sql-statement |
   | help [tablename] |
   | quit |
   | |
   +---------------------------------------+

   
   SQL> SELECT REMOTE_ADDRESS, REMOTE_PORT, LOCAL_PORT_NAME, LOCAL_PORT, JOB_NAME FROM QSYS2.NETSTAT_INFO Where LOCAL_PORT = 9471

Related Content

• IBM SSL requirements for SSL ODBC connectivity
• Qlik Replicate: LINUX SSL setup for DB2i connection 
• stunnel 

Environment

• Qlik Talend Data Integration

The conclusions in this article were reached in collaboration with cjgorrin from the European Commission's Joint Research Centre Qlik Sense team.

Custom QVX connectors stopped working after upgrading to Qlik Sense Enterprise on Windows November 2024.

After selecting Select Data in the Data Load Editor, the Select Data dialog window will display the following message and not proceed:

Please wait – analyzing the selected data

This worked as expected in previous versions of Qlik Sense Enterprise on Windows.

Resolution

This issue is related to a defect (SUPPORT-998, QCB-30758) reported in Qlik GeoAnalytics Plus November 2024, which was resolved in Qlik Sense November 2024 Patch 6.

See the relevant release notes for details.

Internal Investigation ID(s):

SUPPORT-998, QCB-30758

Environment

• Qlik Sense Enterprise on Windows November 2024
• Qlik GeoAnalytics

Before you can start using Qlik Sense Desktop, you need to authenticate yourself against a Qlik Sense Enterprise server. You need to have a working network connection to enable authentication.

The following requirements need to be met:

• A functioning network connection to the Qlik Sense Enterprise Client-Managed Server or Enterprise SaaS/Business tenant.
• Use of a Professional license. Analyzer licenses do not support Desktop Authentication
  For legacy token license: User and Login Passes allow Desktop Authentication
• No TEST license. Test licenses disallow the use of authentication links 
• Compatibility must be met. See Qlik Sense Desktop patch process and compatibility with on-premise installs and Qlik Cloud .

After you have been authenticated once, internet access is not required to continue using Qlik Sense Desktop. However, you have to re-authenticate yourself if thirty days have passed since you last authenticated.

Environment

Qlik Sense Desktop 
Qlik Cloud 
Qlik Sense Enterprise on Windows 
Qlik Sense Business 

Related Content 

Starting Qlik Sense Desktop | Qlik Sense on Windows Help 
Starting Qlik Sense Desktop | Qlik Cloud Help
Configuring Qlik Sense Desktop authentication link 
How to authenticate Qlik Sense Desktop against SaaS editions 
How to authenticate Qlik Sense Desktop against a Qlik Sense Enterprise on Windows server  

Talend Remote Engine Heart Beat is failing hourly with 'GOAWAY received' error and the karaf.log shows below:

2024-08-01T10:16:58,638 | ERROR | pool-28-thread-1 | JAXRSUtils | 469 - org.apache.cxf.cxf-rt-frontend-jaxrs - 3.6.2 | | Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
2024-08-01T10:16:58,638 | WARN | pool-28-thread-1 | PhaseInterceptorChain | 467 - org.apache.cxf.cxf-core - 3.6.2 | | Interceptor for {http://pairing.rt.ipaas.talend.org/}PairingService has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
Caused by: java.io.IOException: /<IP>:<port>: GOAWAY received

This could also be a possible solution when the following error is also showing in the log:

Caused by: java.io.IOException: HTTP/1.1 header parser received no bytes

Resolution

1. Stop Remote Engine.
2. Edit the <RemoteEngineInstallation>/etc/org.talend.ipaas.rt.pairing.agent.cfg file and replace the line 

   heartbeat.interval=60 (by default) 

   with 

   heartbeat.interval=65

3. In the file <RemoteEngineInstallation>/etc/system.properties, remove or comment out the line below (if it exists):
   

   org.apache.cxf.transport.http.forceVersion=1.1​

4. Restart Remote Engine.

Do not set heart interval to more than 180 seconds(3 mins). If Talend Cloud does not receive a heartbeat from the Remote Engine for more than 3 mins, it will show the Remote Engine's status as unavailable.

Cause

The connection to the server pair.xx.cloud.talend.com is kept during 60 seconds and Heartbeat.interval > 60 seconds allows to close this connection and prevent "GOAWAY received" error message.

Related Content

For more information about heartbeat concept and heartbeat interval, please refer to documentation:

Monitoring-remote-engine-health

Internal Investigation ID(s)

 Internal Jira Case ID: TMC-4122

Environment

Talend Cloud 

To disable all current triggers in a QlikView distribution environment, modify the Trigger.xml. 

Disabling all triggers

1. Open Windows Explorer and browse to the location of the QVPR folder
2. Edit the file Trigger.xml
3. Replace Enabled="true" with Enabled="false"
4. Save the file
5. Resend the Work Order
   1. Open the QlikView Management Console
   2. Go to System
   3. Go to Setup
   4. Go to your Distribution Service
   5. Switch to the Advanced tab
   6. Click Send Work Order
6. Restart the QlikView Management Service
7. You should now see that all triggers are disabled.

Enabling all triggers

1. Open Windows Explorer and browse to the location of the QVPR folder
2. Edit the file Trigger.xml
3. Replace Enabled="false" with Enabled="true"
4. Save the file
5. Resend the Work Order
   1. Open the QlikView Management Console
   2. Go to System
   3. Go to Setup
   4. Go to your Distribution Service
   5. Switch to the Advanced tab
   6. Click Send Work Order
6. Restart the QlikView Management Service
7. You should now see that all triggers are disabled.

Environment

• QlikView

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Support has collected a number of resources helpful for the implementation of Qlik Sense Version Control functionality.

• QS event driven cross site app promoter:  https://github.com/eapowertools/qs-event-driven-cross-site-app-promoter
• EAPowertools - QMCU- SCLite:  https://github.com/eapowertools/qmcu-sclite
• Qlik Sense Developers Help                 
• C# .NET Example: https://github.com/StevenJDH/Qlik-Sense-.NET-Example
• QRS API Endpoints (subset)  
• Qlik Branch (Garden)  https://developer.qlik.com/garden      

Qlik Partner Solutions:

• Gitoqlok: A Chrome Extension that adds source versioning control to Qlik, Gitoqlok 
  For more information from the vendor, see How to use git with Qlik Sense 
• EBIExperts Solution:  WIP: https://www.ebiexperts.com/products/
• In4BI Solution:  Platform Manager: https://in4bi

The tFtpGet component is unable to filter and download the necessary file according to the designated filemask. In the FTP UI tool, the file is listed and displayed with uppercase characters. However, when using the same uppercase-based filemask to filter the file, no file is downloaded.

Cause

The file was saved in lowercase, but it appears in uppercase when viewed through the FTP client UI. This inconsistency between the saved filename and its displayed version in the UI indicates a case-mismatch issue in the FTP system.

Resolution

To resolve this issue, adjust the character case in the Filemask settings. Alternatively, enable the "Use Perl5 Regex Expression as Filemask" option to create a new filter that disregards case sensitivity. (This can be achieved by using "/i" in the Perl5 Regex Expression, which enables case-insensitive pattern matching, allowing "A" to match "a".)

Related Content

tFTPGet Standard properties

Perl Regular-Expressions

Environment

• Talend Data Integration 8.0.1

Some Qlik Replicate tasks intermittently show a high amount of false latency. Latency may be observed at random times and will then immediately be gone again. Stopping and resuming the task may resolve the issue.

Resolution

This is often observed when the Qlik Replicate server is out of sync with the time on the source and target endpoint servers.

Resolve the time sync issue.

Cause

Time is out of sync between servers.

Environment

• Qlik Replicate

Your jobs maybe failing in 30s with an error below from Talend Management Console.

org.talend.remote.commons.exception.ClientServerException: TimeOutInterruptor has interrupted the socket stream, timeout has been reached
org.talend.remote.commons.exception.ClientServerException: org.talend.remote.commons.exception.ClientServerException: TimeOutInterruptor has interrupted the socket stream, timeout has been reached

All jobs can be impacted by that and happen at any time.

Resolution

As this issue is caused by timeout issue during file transferring in Qlik Talend Remote Engine, it can be resolved by excluding the Remote Engine folder from Antivirus Scanning or Firewall. Please double check your Antivirus Software and Windows defender.

Or if above solution does not help, please try to increase the timeout value by following below steps:

1. Go into the folder <RE_FOLDER>\system\org\talend\jobserver\org.talend.remote.jobserver.client\8.0.x.yyyymmdd_xxxx_patch

   cd <RE_FOLDER>\system\org\talend\jobserver\org.talend.remote.jobserver.client\8.0.x.yyyymmdd_xxxx_patch

2. Extract the file job_server_client.properties from the jar file
   

   jar xvf org.talend.remote.jobserver.client-8.0.2.20240904_0703_patch.jar job_server_client.properties
   inflated: job_server_client.properties

3. Edit the file job_server_client.properties and change the value of JobServerClient.conf.timeout

   JobServerClient.conf.timeout=300000 -→ increase this to the time desired in milliseconds.

4. Replace the file job_server_client.properties in the jar file by the one modified
   

   jar uf org.talend.remote.jobserver.client-8.0.2.20240904_0703_patch.jar 
   job_server_client.properties

5. Restart the Remote Engine Server to apply the change.
    

    

Cause

From Karaf logs, the issue occurs due to timeout issue during file transferring in Talend Remote Engine, where the default timeout is set to 30 seconds in the existing system.properties

The socket related errors in context of ClientServerException + TimeOutInterruptor indicate there is a networking related congestion that prevents opening socket connections, which could also hint to an exhaustion of the network.

Internal Investigation ID(s) 

Internal Jira ID: TMC-1915

Environment

Talend Cloud 

Creating a tenant in a specific region using either Automation or the available API fails. 

The API call returns:

"Forbidden" error (status 403)

The Automation block for Application Automation - Platform operations → Create Tenant is restricted to a different region.

Resolution

Create a region-level OAuth client for the specific region. For instructions, see Create a region level M2M OAuth2 client.

Cause

It is necessary to have a dedicated OAuth client for each region.

Environment

• Qlik Cloud Analytics
• Qlik Application Automation

Saving an edited task in Qlik Cloud may lead to the error:

Unable to save task

Analyzing the issue with the browser's developer tools, we see that the error 500 Internal Server Error is returned. For tips on how to use developer tools, see Save network web traffic (HAR/XML file) and console logs from the browser's developer tools.

Resolution

To resolve the issue, we remove the connection to the corrupt cron job, then set the task to its correct schedule:

1. Edit the task again, set the schedule to When data is refreshed and Save. This will remove the connection to a corrupt cron job.
   
   
   
   
2. Edit the task again, this time with the correct schedule and the desired change.

Cause

There was a problem with the task's cron job in Qlik Cloud.

Environment

• Qlik Cloud

This article outlines the steps for CICD P2 zero install for pipeline using Maven and provides command examples.

1. Install the necessary jar files.  
   

   mvn org.talend.ci:builder-maven-plugin:8.0.19:install  -Dtalend.studio.p2.update= https://update.talend.com/Studio/8/updates/R2024-12 -Dlicense.path='/home/use1/cicd/license8    -s C:\app\apache-maven-3.9.0\conf\maven_settings.xml

2. Prepare poms for Job building.  
   

   mvn org.talend.ci:builder-maven-plugin:8.0.18:generateAllPoms  -Dtalend.studio.p2.update='https://update.talend.com/Studio/8/updates/R2024-12'   -Dfilter.include.dependencies=true  -Dgeneration.type=local -e -X -s /home/wguo/cicd/maven_settings.xml -Dcodes.compile.failOnError=false   -Dlicense.path='/home/use1/cicd/license8' -Dinstall.org.eclipse.equinox.p2.transport.ecf.retry=10  -Dstudio.error.on.component.missing=false

3. Build/Compile, package and publish project artifacts.
   

   mvn -X clean deploy -U -f /home/user1/ws/project1/poms/pom.xml -Dlicense.path='/home/use1/cicd/license8'  -Dtalend.studio.p2.update= https://update.talend.com/Studio/8/updates/R2024-12 -Dpackaging=zip -Dgeneration.type=local -Dinstall.org.eclipse.equinox.p2.transport.ecf.retry=10 -s /home/wguo/cicd/maven_settings.xml -DaltDeploymentRepository=dmt-releases::default:: http://s.ap.abc.net:8081/repository/dmt-releases/ -DaltSnapshotDeploymentRepository=dmt-snapshots::default:: http://s.ap.abc.net:8081/repository/dmt-snapshots/ -DaltReleaseDeploymentRepository=dmt-releases::default:: http://s.abc.net:8081/repository/dmt-releases/

For Windows-based CICD host machines, use the --define "xxx=yyy" option instead of -Dxxx=yyy to circumvent parameter passing failures.

Additionally, you can filter and specify which project items to generate in order to make the POM generation faster. For further details, please refer to Filtering project items | Talend Software Development Life Cycle Best Practices Guide Help.

Environment

• Talend Data Integration 8.0.1

In Qlik Sense, when there is a commented out portion of the script, if "//" is deleted and the script is saved, all the text will turn black and all syntax highlighting will be lost. If pages of the script are toggled between, a message that says "we have disabled syntax highlight to maintain performance" appears and the highlighting will come back but if previous steps are followed again,commenting will also be disabled again.  

This is working as designed.

It is the current solution for dealing with deeply nested if statements. In many cases these deeply nested if blocks will cause real performance issues (crashing the browser). The best practice is to not use nested ifs when possible. The commenting/uncommenting works because we count the levels. Pretty sure 10 levels deep we trigger the perf warning. So if they comment out one and it's only 9 it won't complain.

Environment: 

Internal Investigation ID(s):

Qlik Answers is Qlik's personalized AI assistant that generates on-point answers from your own trusted business content. See this article to learn how to get started with Qlik Answers

This connector unlocks new powerful use cases like indexing new data ad-hoc and taking your action oriented automations to the next level by including unstructured insights. This article explains how the Qlik Answers connector in Qlik Application Automation can be used.

Article contents

• Authentication
• Use cases
• 1. Re-indexing a knowledge base
• 2. Ask questions
• Notes
• Related Content

Authentication

This connector does not require additional configuration to authenticate, it will automatically connect to the automation owner's Qlik account. Whenever blocks of this connector are executed, they will use that account.

Use cases

For this connector's first release, we will introduce blocks that can re-index knowledge bases and ask questions to an assistant. We will deliver more blocks in future releases, do not hesitate to request new blocks through Ideation.

1. Re-indexing a knowledge base

This use case focuses on ad-hoc updates to the knowledge base. The creation and initial configuration of a knowledge base should happen through the Qlik Answers UI as described here:

Once your knowledge base is configured and you've set up a data connection to a cloud storage location, you can then use Qlik Application Automation to add specific files to the Cloud Storage location and trigger a re-indexing. This could be useful in scenarios when you only want to index specific records that might depend on a context.

For this use case, you can use the blocks Add Data Source To A Knowledge Base and Sync Knowledge Base Data Source. The below example will fetch incidents from ServiceNow, store them in a Dropbox folder and then add the Dropbox folder as a data source to a Knowledge Base in Qlik Answers. After this, the data source will be synced to the knowledge base index.

2. Ask questions

By using the blocks Create Thread and Execute Synchronous Prompt, you can ask questions from an assistant to enrich other messages that are sent through automations with unstructured insights. In the below example, these blocks are added to the existing "Notify your team on Microsoft Teams based on a measure" template that can be found in the template picker:

Notes

Don't ask a question immediately after indexing. Asking a question should be done after the knowledge base has completed indexing successfully.

Related Content

• Introducing Qlik Answers
• Qlik.com product page for Qlik Answers

Environment

• Qlik Cloud Analytics
• Qlik Application Automation
• Qlik Answers

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

After applying the Oracle July 2024 patch, the following error will be seen when working with compressed tables:

[ASSERTION       ]W:  A compressed row cannot be parsed for table  (oradcdc_parse.c:2640)

The error leads to missing records.

Only Oracle instances with compressed tables are affected.

Resolution

R&D addressed the compression warning and also another missing insert events.

Fix versions

• 2023.11 and later
• 2024.5 and later

Before rolling out the fix in production, always first test in UAT or other pre-release environments.

If you are uncertain whether or not you are using compressed tables, run the following query:

select owner, table_name, COMPRESSION,COMPRESS_FOR from dba_tables where compression='ENABLED'

Cause

Oracle July 2024 Patch with compressed tables. 
RECOB-8914 by Qlik.

Environment

• Qlik Replicate 
• Oracle with July 2024 patch