When running a Qlik Talend Cloud replication task with a SQL Server source, using the Advanced Run Options to start from a timestamp, the task fails with the following error:

SqlStat: 42000 NativeError:9005 [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Invalid parameter passed to OpenRowset(DBLog, ...).

Resolution

Instead of starting from the timestamp, get the corresponding LSN (Log Sequence Number) from the SQL Server backup history, and start the task from that LSN.

1. Instead of starting the task from the raw timestamp, identify the LSN (Log Sequence Number) that corresponds to the intended point in time.
2. Run the following query against the SQL Server source database to find the backup set that contains the target LSN, and confirm its first and last LSN values (in hexadecimal). Replace '00330E09:002FA850:0006' with the target LSN value:
3. In the Advanced Run Options for the replication task, use the LSN returned by the query as the starting point, instead of the timestamp.
   
   Example query: 

   SELECT
     [dbo].[attrep_fn_NumericLsnToHexa](bs.first_lsn),
     [dbo].[attrep_fn_NumericLsnToHexa](bs.last_lsn),
     bmf.*,
     bs.*
   FROM msdb.dbo.backupmediafamily bmf, msdb.dbo.backupset bs
   WHERE bmf.media_set_id = bs.media_set_id
     AND bs.database_name = db_name()
     AND bs.type = 'L'
     AND CAST([dbo].[attrep_fn_NumericLsnToHexa](bs.first_lsn) COLLATE SQL_Latin1_General_CP1_CI_AS AS VARCHAR(24))
         <= CAST('00330E09:002FA850:0006' COLLATE SQL_Latin1_General_CP1_CI_AS AS VARCHAR(24))
     AND CAST('00330E09:002FA850:0006' COLLATE SQL_Latin1_General_CP1_CI_AS AS VARCHAR(24))
         < CAST([dbo].[attrep_fn_NumericLsnToHexa](bs.last_lsn) COLLATE SQL_Latin1_General_CP1_CI_AS AS VARCHAR(24));

Cause

When a replication task is started from a timestamp against a SQL Server source, the timestamp value returned by SQL Server is in UTC time, not the local time zone. Using that timestamp directly with the Start from timestamp option is what causes this error.

Environment

• Qlik Talend Cloud

To point Qlik Replicate at an AG Secondary Replicate instead of the primary, follow these steps;

1. Create the publication/articles/filters the same way Replicate would or enable MS-CDC per the User's Guide for all the tables in the task.
2. Set the SQL Server Source Endpoint internal parameter ignoreMsReplicationEnablement so that Replicate will not check for publication/articles.
3. Set the SQL Server Source Endpoint internal parameter safeguardPolicyDesignator to ‘None’ so that Replicate will not try to create a transaction on the source.
4. Set the SQL Server Source Endpoint internal parameter AlwaysOnSharedSynchedBackupIsEnabled so that Replicate will not try to connect to all the AG Replicas to read the MSDB.
5. Set the SQL Server Source Endpoint ‘Change processing mode (read changes from):’ to ‘Backup Logs Only’
6. As part of their transaction log backup maintenance plan, it's needed to run a script to merge the MSDB entries across all the Replicas. This may not be necessary if the backup is done on the secondary Replica that we will be attached to. The backups should also be placed on a share the Replicate can get access to. Optionally use 'Replicate has file-level access' if the backups are not encrypted and Replicate has direct access to them.
7. It is needed to create the LSN/Numeric conversion scalar functions on the source database on the secondary.

Limitations include:

• Can read from backups only.
• Manual setup of publications/articles or MS CDC.
• Manual creation of supporting LSN conversion functions

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.

A Talend Data Integration job that retrieves exchange rates from an external government REST API fails at runtime. The failure occurs in the REST call component, and the job doesn't complete. The following exception is logged:

Exception in component tREST_1 (mJob_FT_EXCHANGE_RATE)
com.sun.jersey.api.client.ClientHandlerException:
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

Resolution

First, we will verify that the correct certificates have been imported, then outline the appropriate solution. 

Verify that the required certificates are imported

Confirm that every certificate the API server needs is imported into the truststore of the JVM used by Talend. Download every certificate in the chain, saving each one as a separate file:

echo "" | openssl s_client -showcerts -connect <api-hostname>:443 | \
  awk '/BEGIN/ { i++; } /BEGIN/, /END/ { print > "a-cert-" i ".crt" }'

Then import each certificate into the truststore. There may be several certificates in the chain. Import all of them:

keytool -import -trustcacerts -alias a-cert-1 -file /tmp/a-cert-1.crt \
  -keystore <jvm>/lib/security/cacerts -storepass <truststore-password>
keytool -import -trustcacerts -alias a-cert-2 -file /tmp/a-cert-2.crt \
  -keystore <jvm>/lib/security/cacerts -storepass <truststore-password>

Check for a cipher suite conflict

If the required certificates are already imported and the error persists, check whether the client and server support a common cipher suite.

Server side: scan the endpoint to see which cipher suites it supports.

sudo dnf install nmap
nmap --script ssl-enum-ciphers -p 443 <api-hostname>

In this case, the scan listed only TLS_RSA_* ciphers.

Client side: check the JDK's java.security file for disabled algorithms.

jdk.tls.disabledAlgorithms=..., TLS_RSA_*, ...

Since the JDK 11 release of January 2026, TLS_RSA_* is disabled by default here, which is why the handshake fails.

Any of the following tools can be used to check which cipher suites a server supports:

nmap (most detailed):

nmap --script ssl-enum-ciphers -p 443 <hostname>

Lists every supported TLS version and cipher suite, with a strength grade (A–F) for each. This is the method used in this case.

testssl.sh (full report, no install needed beyond download):

git clone https://github.com/drwetter/testssl.sh.git
cd testssl.sh
./testssl.sh --cipher-per-proto <hostname>:443

Gives a per-protocol breakdown, and flags weak or deprecated ciphers (no forward secrecy, CBC, and so on).

sslscan:

sudo dnf install sslscan
sslscan <hostname>:443

Quick output showing accepted and rejected ciphers, certificate information, and protocol support.

Apply the fix on the JDK 11 client

If the external server can't be upgraded to support newer cipher suites, apply the fix on the JDK 11 client side. To avoid modifying the JDK installation itself, use a separate, customized security file:

1. Copy <java_home>/conf/java.security to a neutral location, for example <install_dir>/TalendRemoteEngine/custom.security.
2. Edit the copy, and remove TLS_RSA_* from the jdk.tls.disabledAlgorithms property.
3. Create a dedicated run profile for this job that points to the custom file:
   

   -Djava.security.properties=<install_dir>/TalendRemoteEngine/custom.security

Re-enabling TLS_RSA_* weakens transport security, because these cipher suites lack forward secrecy. Scoping the change to this one job's run profile, rather than changing the global JDK settings, limits the exposure. It's also worth asking the API provider whether they plan to support modern cipher suites.

Cause

An SSLHandshakeException with a handshake_failure generally has one of two causes: a certificate in the server's chain isn't trusted by the JVM's truststore, or the client and server can't agree on a cipher suite. In this case, investigation confirmed a cipher suite conflict between the client and the API server:

• Server side: the external API server supports only TLS_RSA_* cipher suites.
• Client side: since the JDK 11 release of January 2026, TLS_RSA_* is disabled by default in the JDK's java.security file, through the jdk.tls.disabledAlgorithms property.

Because the client refuses the only cipher family the server offers, no common cipher suite can be negotiated, which produces the SSLHandshakeException: Received fatal alert: handshake_failure error.

Environment

• Talend Studio

This article explains how to retrieve data using Qlik Sense Analytics (on-premises and Cloud) from SAP OData services, taking into account the 2026 SAP security patches.

Background

An SAP security patch released in June 2026 technically blocks third-party use of the ODP framework over RFC (SAP Note 3255746). This is the interface most dedicated SAP connectors used. Only ODP via RFC is affected, not RFC in general, and SAP names ODP via OData as the compliant fallback for data access outside SAP systems. A time-limited revert option exists but expires in December 2026 (SAP Note 3731818).

Only Qlik's SAP ODP connector (Qlik Cloud) is affected. Depending on the access level you have in your SAP environment, you can also use our SAP connectors to extract data from SAP NetWeaver SAP connectors in Qlik Sense Client Managed, Qlik Cloud and QlikView (these are not affected by SAP restrictions).

But if data extraction only relies on OData services, Qlik's OData connector or REST connector are the only alternative.

Requirements

What is needed on the SAP side (macro level):

• AP Gateway as the OData layer. Every OData service is served by SAP Gateway (NetWeaver Gateway), either embedded in the ABAP system or as a separate hub. In S/4HANA, it's built in. This is the component that turns backend objects into OData endpoints.
• Service activation. A service must be registered and activated in /IWFND/MAINT_SERVICE (plus the underlying ICF node in SICF). SAP ships thousands of standard services inactive by default. Activation per service is a deliberate admin step, not automatic.
• A user and authorizations. A dedicated communication/service user with S_SERVICE for the endpoint plus the application-level authorizations for the data behind it. Gateway auth doesn't bypass application auth — if the user can't see the plant in SAP, the OData service won't return it either.
• Network and authentication. HTTPS with a trusted certificate and an auth method. The consumer supports:
  • Basic Auth (the simple on-prem case)
  • OAuth2/SAML for cloud scenarios
    In S/4HANA Cloud (public edition), the connection runs through communication scenarios/arrangements rather than manual Gateway configuration. For Qlik Cloud Analytics reaching an on-prem Gateway, either the endpoint is reachable from the cloud, or you go through Qlik Data Gateway – Direct Access.
• For ODP-based services, additionally, the Operational Delta Queue (ODQ) must be active, and the source object must be released for ODP extraction. Delta then works via the OData subscription/delta-link mechanism backed by ODQ.

What can be exposed as OData

Two families

Family A: ODP-based OData services. SAP Gateway can generate an OData service on
top of the ODP framework, and then the answer is essentially yes — anything ODP
supports:

• DataSources/Extractors. SAPI context: the classic 2LIS_* logistics extractors, FI
  extractors, etc., released via RSA5
• ABAP CDS views annotated with @Analytics.dataExtraction.enabled: true (ABAP_CDS
  context), delta-capable when the change-data annotations are set
• BW/BW4HANA InfoProviders. BW context
• SLT-based table replication. SLT context
• HANA information views

These services are generated in the Gateway Service Builder (SEGW) via the ODP-
extraction wizard. They support full load plus genuine delta — the extractor's delta logic
is preserved and exposed through OData delta tokens.

Family B: regular (non-ODP) OData services. Anything the ABAP stack can model:

• A CDS view with @odata.publish: true (one annotation, auto-generated service)
• Hand-built services in SEGW (mapping DDIC tables, CDS as reference data source,
  BAPIs/RFCs, or custom code)
• RAP service bindings (OData V2/V4). The modern S/4HANA way
• The standard APIs delivered from the SAP Business Accelerator Hub

These have no delta mechanism by default. Incremental loads are your problem as the
consumer. Typically $filter on a change date or timestamp field, which only works if the
underlying object carries one reliably.

Limitation with the generic OData connector in Qlik Sense Client Managed

The generic OData connector speaks plain OData, which is fine for Family B and for full loads only from Family A. (delta load can only be managed with a REST connector).

OData is a chatty protocol. While paging, $select to trim width, and gzip help, nobody should plan a nightly full load of BSEG-scale tables over it.

Options to retrieve data from SAP ODATA services

In Qlik Cloud Analytics

• How to connect to data from SAP OData services and retrieve data with Qlik Cloud Analytics REST connector
• How to connect to data from SAP OData services and retrieve data with Qlik Cloud Analytics ODATA connector 

In Qlik Sense Enterprise on Windows

• How to connect to data from SAP OData services and retrieve data with Qlik Sense Enterprise on Windows REST connector
• How to connect to data from SAP OData services and retrieve data with Qlik Sense Enterprise on Windows ODATA connector

Environment

• Qlik Cloud
• Qlik Sense Enterprise on Windows
• QlikView

When using IBM Db2 iSeries as a source endpoint, a Qlik Replicate task can, in rare cases, trigger a large number of access-attempt messages at the database level. These messages are recorded in the IBM i audit journal, generating several GB of audit data and placing a critical load on the AS/400 system. This results in resource overhead on the database.

The message at the database level may look similar to the following:

Message: The user-defined procedure or function OBJECT_STATISTICS in QSYS2 returned an SQLSTATE warning.

Cause: An SQLSTATE in the 01xxx format was returned by the user-defined procedure or function OBJECT_STATISTICS in QSYS2 (specific name QSQOBSTAT), along with the message text NOT AUTHORIZED TO OBJECT XXX/BBB *FILE.

Environment

• Qlik Replicate

Resolution

Contact the database administrator responsible for the IBM Db2 for i (AS/400) system and verify the library settings in DB2 for the current OBJAUD value. If OBJAUD is set to *ALL instead of *NONE, this is likely the cause of the excessive audit journal entries. Have the administrator adjust the value as appropriate for the environment.

Cause

This behavior is caused by a specific IBM Db2 for i library parameter: OBJAUD. For background, see Object auditing | IBM Documentation.

• If OBJAUD is set to *ALL on a library, or to *USRPRF on an object, an audit record is written every time a user reads or changes that object.
• If OBJAUD is set to *NONE, no auditing occurs.

The extensive object-access auditing on the database is typically the result of OBJAUD being set to *ALL rather than *NONE on the affected library.

The IBM DB2 for iSeries source endpoint occasionally encounters an error during the CDC stage. This issue appears to be linked to the presence of the IBM i Access ODBC Driver versions 7.1.26 and 7.1.27.

The error message in the task log file:

[SOURCE_CAPTURE ]E: Error parsing [1020109] (db2i_endpoint_capture.c:652)

The issue specifically arises during the CDC stage; however, the Full Load stage operates smoothly without any complications.

Resolution:

Qlik has certified the DB2i ODBC driver version 07.01.029. An update to the official Qlik documentation is currently pending.

Either:

• Upgrade your IBM i Access ODBC client to 07.01.029, 
• or downgrade from versions 07.01.027/07.01.026 to 07.01.025

For compatibility reasons, it's advisable to revert to version '07.01.025' if you choose to downgrade, as '07.01.026' exhibits the same issue.

Various factors can contribute to encountering the 'Error parsing' message, including:
    • DB2i ODBC Version '07.01.027' (as described in this article)
    • In a single task, the total number of captured tables exceeds 300
    • The source table is created by DDS
    • Garbage data in table
    • Special characters in table object identifier (table name, or column name)
If you continue to encounter the error after switching to '07.01.025', please reach out to Qlik Support for further assistance.

Cause:

The behavior of the IBM DB2i ODBC Versions '07.01.026' & '07.01.027' differ slightly from that of '07.01.025'. In certain scenarios, it may return incorrect column lengths

Internal Investigation ID(s):

#00158029, #00160002, QB-26413

Environment:

• Qlik Replicate All versions
• IBM DB2i All versions
• IBM DB2i Client versions '07.01.026' and '07.01.027'

Qlik Replicate 

Building an OSGI job in Talend Studio (version 2026-07 and 2026-08) fails with the following error:

ERROR] mvn <args> -rf :job_<JOB NAME>
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJob(BuildJobManager.java:305)

Resolution

Caused by defect QAPPINT-3008 (SUPPORT-11651) and resolved in the Talend Studio 2026-09 release. See the release notes for details.

Internal Investigation ID(s)

QAPPINT-3008, SUPPORT-11651

Environment

• Talend Studio 2026-07 and 2026-08

Databricks Unity Catalog Volumes do not consistently reflect the current state of a staging path to the very next Qlik Replicate or ODBC operation that depends on it. This occurs for either a new or not yet created path, as well as for newly created files.

Both of these scenarios trigger a FileNotFoundException/PATH_NOT_FOUND error from the Databricks backend, but not from Qlik Replicate itself.

Example:

LIST fails on staging subfolder during pre-load cleanup, even with the service account having all required permissions. 

LIST '/Volumes/…/qlik_volume/qlikstage1/<task-id>/1/'; → HiveSQLException: java.io.FileNotFoundException: No such file or directory ..

[TARGET_APPLY    ]E:  RetCode: SQL_ERROR  SqlState: 08S01 NativeError: 115 Message: [Simba][Hardy] (115) Connection failed with error: SSL_read: error code: 0 [1022502]  (ar_odbc_stmt.c:4730)

Resolution

This is caused by the Internal Parameter $info.query_syntax.error_code_connection_failure.

Remove the parameter to resolve the issue.  

Environment

• Qlik Replicate

This article explains how to connect to data from SAP OData services and retrieve data with the Qlik Cloud Analytics ODATA connector.

Requirements

• A valid SAP account to access the ODATA services in the SAP environment

  Public cloud SAP tenant only.

Configuration

1. Create a new application in your Qlik Sense workspace, and go to the Data Load editor
2. On the right panel, click New Connection and choose the ODATA connector
3. Configure the connection:
   1. Enter the URL of the SAP ODATA service and your credentials
   2. Test the connection, then click Save
      
      

How to retrieve and load data

1. Identify the entities (resources) of the ODATA service
   1. On the data connection you created, click the Data button
      
      
      
      
   2. On the left menu, choose ListResources (A) and enter $format=xml (B) in the OData Query Options, then choose application/atom+xml in Accept (C) and click Preview data (D)
      
      
      
      
      
      
   3. Retrieve the list of entities
      
      
   4. Check and click GetData, then enter the following parameters:
      • The name of the entity from which you want to retrieve data in OData Resource Path
      • $format=xml in OData Query Options
      • Application/atom+xml in Accept
        
        
        
        
   5. Click Preview data
      
      
   6. Click Insert script
      
      
      
      Example:
      
      
      
      
      
      
2. The next step is to curate the load statement and optionally provide business-friendly names for the SAP fields.
   
   Example:
   
   
   
   
3. Repeat all steps for each entity you want to retrieve data from. Then curate the load script to avoid synthetic keys and build a functional data model in your analytic application.

The example in this article is provided as is and only documents a basic option. Further customization can be achieved using a data architecture with QVD layers.

Optional: Instead of manually going through all the steps, it is possible to use an LLM and a skill on SAP and Qlik to generate a first curated version of the full load script by providing the LLM the metadata file of the OData service. It would save some time in the building process.

Environment

• Qlik Sense Enterprise on Windows

When only a Unique Index Key is defined in the source, the task will by default create a non-clustered key in the target.

This article documents how to create a Primary Key in the target by introducing an Internal Parameter at the SQL Server target. 

Resolution

Source: Oracle
Target: SQL Server

Add the following parameter:

• $info.query_syntax.create_index  
• Value: ALTER TABLE ${QO}${TABLE_OWNER}${QC}.${QO}${TABLE_NAME}${QC} ADD CONSTRAINT ${QO}PK_${TABLE_NAME}${QC} PRIMARY KEY ( ${COLUMN_LIST} ) 

Make sure columns with a unique index defined at the source, as well as columns that are marked as Key Manually in the UI, have the NOT NULL constraint enabled.

Environment

• Qlik Cloud
• Talend Cloud

QTAC-2537 R2026-08 patch introduced a label sorting issue in the Talend Job Conductor.

Sorting the label on the Execution Plan page in previous patches works as expected. The issue is specific to sorting label names in the Job Conductor, whereas sorting the label name in ascending or descending order fails. 

Resolution

This issue will be fixed in an upcoming Talend Administration Center patch. If a solution is required as soon as possible, another alternative is to revert to a previous patch, as this only impacts version QTAC-2537 (R2026-08).

Review the Talend Release Notes for details.

Internal Investigation ID(s)

QTAC-2707

Environment

• Talend Administration Center

Jobs show significantly degraded performance when running on a Dynamic Engine compared to executing on a Remote Engine.

Environment:

• Talend Cloud

Resolution

On a Dynamic Engine, the job runs inside a pod, i.e., a container. This container has its own operating system and libraries, separate from the host node. Because of this, it is sometimes necessary to add Java options at job launch (for example, on a run profile in the Talend Management Console) to allocate more resources to the job inside the container.

There are two main options to add, depending on the root cause of the problem:

Large data volume processing (memory-bound)

This is typically a memory issue. Add the following options:

1. Kubernetes-specific:

   • -XX:MaxRAMPercentage= sets the maximum JVM heap size as a percentage of the memory allocated to the container (similar to Xmx).
     
     

2. Talend-specific, at the container level (not the job itself):

   • -K8S:PodRAMRequest=
   • -K8S:PodRAMLimit=
     
     

   These set the memory usage for the pod itself.

Complex data processing (CPU-bound)

When the processing logic itself is complex, it is preferable to adjust the CPU allocation instead. By default, a job is limited to 30% of the Kubernetes node's CPU. This limit exists mainly to prevent a single job from completely freezing the node.

This limit can be raised with the following options, which allocate more CPU to the pod:

• -K8S:PodCPURequest specifies the initial CPU allocation for the pod.
• -K8S:PodCPULimit sets an upper limit on the pod's CPU usage, preventing it from monopolizing CPU resources.

Examples:

• -K8S:PodCPURequest=0.5: request to use 50% of node CPU for the job
• -K8S:PodCPULimit=1: can use up to 100% of node CPU
• -XX:MaxRAMPercentage=50: allocate 50% of pod RAM for the job heap size

Cause

The default CPU usage is 0.3, as defined in the Dynamic Engine's env file. This value is set to prevent any node CPU overhead.

This article explains how to connect to data from SAP OData services and retrieve data with the Qlik Sense Enterprise on Windows ODATA connector.

Requirements

• A valid SAP account to access the ODATA services in the SAP environment
• (Optional) A certificate installed on the Qlik Sense Enterprise on Windows server if you communicate with the ODATA services through SSL

Configuration

1. Create a new application in your Qlik Sense workspace, and go to the Data Load editor
2. On the right panel, click New Connection and choose the ODATA connector
3. Configure the connection:
   1. Enter the URL of the SAP ODATA service and your credentials
   2. Test the connection, then click Save
      
      

How to retrieve and load data

1. Identify the entities (resources) of the ODATA service
   1. On the data connection you created, click the Data button
      
      
      
      
   2. On the left menu, choose ListResources (A) and enter $format=xml (B) in the OData Query Options, then choose application/atom+xml in Accept (C) and click Preview data (D)
      
      
      
      
      
      
   3. Retrieve the list of entities
      
      
   4. Check and click GetData, then enter the following parameters:
      • The name of the entity from which you want to retrieve data in OData Resource Path
      • $format=xml in OData Query Options
      • Application/atom+xml in Accept
        
        
        
        
   5. Click Preview data
      
      
   6. Click on Insert script
      
      
      
      
      
      
2. The next step is to curate the load statement and optionally provide business-friendly names for the SAP fields.
   
   Example:
   
   
   
   
3. Repeat all steps for each entity you want to retrieve data from. Then curate the load script to avoid synthetic keys and build a functional data model in your analytic application.

The example in this article is provided as is and only documents a basic option. Further customization can be achieved using a data architecture with QVD layers.

Optional: Instead of manually going through all the steps, it is possible to use an LLM and a skill on SAP and Qlik to generate a first curated version of the full load script by providing the LLM the metadata file of the OData service. It would save some time in the building process.

Environment

• Qlik Sense Enterprise on Windows

This article explains how to connect to data from SAP OData services and retrieve data with the Qlik Sense Enterprise on Windows REST connector.

Requirements

• A valid SAP account to access the ODATA services in the SAP environment
• Optional: A certificate installed on the Qlik Sense Enterprise on Windows server if you communicate with the ODATA services through SSL

Configuration

1. Create a new application in your Qlik Sense workspace, and go to the Data Load editor
2. On the right panel, click New Connection and choose the REST connector
3. Configure the connection:
   1. Enter the URL of the SAP ODATA service
      
      
      
      
   2. Choose Basic Authentication and enter your credentials
      
      
      
      
   3. Under Query parameters, add sap_client and enter its value; do the same for $format, then check Allow “WITH CONNECTION”
      
      
      
      
   4. Test the connection, then click Save

How to retrieve and load data

1. Identify the entities (resources) of the ODATA service
   1. On the data connection you created, click the Data button
      
      
      
      
   2. Expand the left menu and choose EntitySets
      
      
      
      
   3. Retrieve an Entity from the list, edit the connection again, and paste the Entity at the end of the URL
      
      
      
      
   4. Test and save the connection
      
      
   5. Expand the left menu and tick results:
      
      
      
      
   6. Click on Insert script
      
      
      
      
2. The next step is to curate the load statement by adding the WITH CONNECTION statement and defining variables for the SAP environment used in the connection.
   
   Example:
   
   
   
   (Optional) Followed by providing business-friendly names for the SAP fields.
   
   Example:
   
   
   
   
   
3. Repeat all steps for each entity you want to retrieve data from. Then curate the load script to avoid synthetic keys and build a functional data model in your analytic application.

The example in this article is provided as is and only documents a basic option. Further customization can be achieved using a data architecture with QVD layers.

Optional: Instead of manually going through all the steps, it is possible to use an LLM and a skill on SAP and Qlik to generate a first curated version of the full load script by providing the LLM the metadata file of the OData service. It would save some time in the building process.

Environment

• Qlik Sense Enterprise on Windows

This article explains how to connect to data from SAP OData services and retrieve data with the Qlik Cloud Analytics REST connector.

Requirements

• A valid SAP account to access the ODATA services in the SAP environment
• A functional Qlik Data Gateway Direct Access
• The SAP OData generic URL added in the gateway settings under the REST connector; the URLs are case-sensitive
  
  
  
  
• Optional: A certificate installed on the Qlik Sense Client Managed server if you communicate with the ODATA services through SSL

Configuration

1. Create a new application in your Qlik Sense workspace, and go to the Data Load editor
2. On the right panel, click New Connection and choose the REST connector
3. Configure the connection:
   1. Choose the data gateway and enter the URL of the SAP ODATA service; do not forget the forward slash (/) at the end of the URL
      
      
      
      
   2. Choose Basic Authentication and enter your credentials
      
      
      
      
   3. Under Query parameters, add sap_client and enter its value; do the same for $format, then check Allow “WITH CONNECTION”
      
      
      
      
   4. Test the connection, then click Save

How to retrieve and load data

1. Identify the entities (resources) of the ODATA service
   1. On the data connection you created, click the Data button
      
      
      
      
   2. Select JSON as Response type and expand the left menu, then choose EntitySets
      
      
      
      
   3. Retrieve an Entity from the list, edit the connection again, and paste the Entity at the end of the URL
      
      
      
      
   4. Test and save the connection
      
      
   5. Expand the left menu and check results:
      
      
      
      
   6. Click on Insert script
      
      
      
      
2. The next step is to curate the load statement by adding the WITH CONNECTION statement and defining variables for the SAP environment used in the connection.
   
   Example:
   
   
   
   (Optional) Followed by providing business-friendly names for the SAP fields.
   
   Example:
   
   
   
   
   
3. Repeat all steps for each entity you want to retrieve data from. Then curate the load script to avoid synthetic keys and build a functional data model in your analytic application.

The example in this article is provided as is and only documents a basic option. Further customization can be achieved using a data architecture with QVD layers.

Optional: Instead of manually going through all the steps, it is possible to use an LLM and a skill on SAP and Qlik to generate a first curated version of the full load script by providing the LLM the metadata file of the OData service. It would save some time in the building process.

Environment

• Qlik Cloud Analytics

Testing the PostgreSQL Source Endpoint in Qlik Replicate may fail with the following error:

Failed to load Postgres driver. Cannot load libpq.dll

Resolution

You should have two entries in the system environment variables pointing to the following folders (default locations):

• C:\Program Files\PostgreSQL\12\bin
• C:\Program Files\psqlODBC\1202\bin

Both folders must include the libpq.dll file.

If the connection test fails even with libpq.dll present in both directories, then:

1. Copy the libpq.dll file from odbc\bin (C:\Program Files\psqlODBC\1202\bin) to  ~\Replicate\bin 
2. Restart the Qlik Replicate server service and the Replicate UI server service

Environment

• Qlik Replicate

After upgrading Qlik Compose from 2022.5 to 2023.11 or 2024.12, attempting to generate and run the Data Mart job fails with the following error:

SQL compilation error: invalid identifier "MASTER_CONSIGNMENTLEG_MASTER_CONSIGNMENT_GLOBI_consignment_INVOICE_GLOBI_relations_OID" 

Resolution

To resolve, change the "is_pk" property from false to true for the OID columns in the Aggregate Fact definition.

For new Data Mart jobs, the OID column defaults to true. This issue only affects older Aggregate Facts that include dimensions.

Detailed steps:

1. Create a deployment package of the project where the issue exists.
2. Extract the ZIP file and open the JSON file.
3. Locate the Aggregate Fact table definition in the JSON file that has the issue. For example: FACT_GLOBI_AGG_FINANCIAL_PLAN_NON_FIN_REP.
   
   
   
   
4. Locate the _OID columns within the Aggregate Fact definition.
   For example, FACT_GLOBI_AGG_FINANCIAL_PLAN_NON_FIN_REP contains four OID columns:
   • S_sec_department_id_GLOBI_department_GLOBI_department_OID
   • S_invoice_relation_id_GLOBI_relations_GLOBI_relations_OID
   • S_sec_branch_id_GLOBI_branchGLOBI_branch_OID
   • S_sec_branch_id_GLOBI_relation_address_GLOBI_branch_OID
5. For each _OID column, check the value of the "is_pk" property.
6. If "is_pk" is set to false for any _OID column, update it to true.
7. Save the changes, then re-ZIP the JSON file along with the readme.txt file.
8. Deploy the updated ZIP file into the existing project.
9. Regenerate the statements for the Data Mart.
10. Run the Datamart ETL job.

Environment

• Qlik Compose

The CICD publishing phase may fail with the following error:

org.talend.ci:cloudpublisher-maven-plugin:8.0.13:publish (default) on project <project>: Get the latest published version failed

This article identifies the two most common root causes and their solutions:

Get the latest published version failed: Unauthorized
Caused by: jakarta.ws.rs.NotAuthorizedException: HTTP 401 Unauthorized

Get the latest published version failed: Not Found
Caused by: jakarta.ws.rs.NotFoundException: HTTP 404 Not Found

Identify which root cause applies to you by reviewing the log stack.

Resolution

Unauthorized

This indicates an invalid Talend Management Console (TMC) token and may require a review of what TMC region is currently in use.

Resolution

• Validate the TMC token. If unsuccessful, create a new token to use.
• Verify the TMC region: Storing your global variables in Jenkins 

Not Found

Not Found points to an incorrect TMC URL.

Resolution

• Review the TMC URL currently configured as per Storing your global variables in Jenkins 

Internal Investigation ID(s)

00470337, 00470122

Environment

• Talend Data Integration

While reloading data from a SQL server using ODBC or OLE DB connection, the error below is seen in Hub. Part of this may also be reference in the reload script logs.


The following error occurred:
Connector reply error: ***

The error occurred here:


Data has not been loaded. Please correct the error and try loading again.

Environment:

• Qlik Sense Enterprise on Windows 

The error above may indicate a typo, incorrect syntax, or incorrect table naming in the reload script. It generally does not indicate a connectivity issue or inability to query data in the source SQL database.

Resolution:

Confirm there are no typos, incorrect syntax, or incorrect table naming in the reload script. One way to approach this is by going to the "Select Data" option on the Connection listed in Hub, re-selecting the desired data to be loaded, and "Inserting Script" for comparing if there were any changes in the database since the reload script was first created.

Qlik Replicate task data synchronization failed to replicate data from SQLMI to an AS400 (iSeries/DB2) target via an ODBC endpoint, with new tasks failing during initialization when generating and executing CREATE TABLE statements for internal control tables (such as attrep_apply_exceptions) on the target.

Example error:

Attributes not valid

Detailed log:

Stream component 'st_0_AS400 - PSFWEB - MC - Target' terminated
Stream component failed at subtask 0, component st_0_AS400 - PSFWEB - MC - Target
Error executing command
Cannot create Exception table
Cannot create Special table
execute create table statement failed, statement CREATE TABLE "attrep_apply_exceptions" ( "TASK_NAME" VARCHAR(128) NOT NULL, "TABLE_OWNER" VARCHAR(128) NOT NULL, "TABLE_NAME" VARCHAR(128) NOT NULL, "ERROR_TIME" TIMESTAMP NOT NULL, "STATEMENT" CLOB(0) NOT NULL, "ERROR" CLOB(0) NOT NULL )
RetCode: SQL_ERROR SqlState: 42000 NativeError: -604 Message: [IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0604 - Attributes not valid.
Failed (retcode -1) to execute statement: CREATE TABLE "attrep_apply_exceptions" ( "TASK_NAME" VARCHAR(128) NOT NULL, "TABLE_OWNER" VARCHAR(128) NOT NULL, "TABLE_NAME" VARCHAR(128) NOT NULL, "ERROR_TIME" TIMESTAMP NOT NULL, "STATEMENT" CLOB(0) NOT NULL, "ERROR" CLOB(0) NOT NULL )

Resolution

Set Provider Syntax to DB2 in the target endpoint.

• Go to your Target Endpoint
• Switch to the Advanced tab
• Set the correct Provider Syntax 

  Engage Qlik's Professional Services for more direct assistance for custom ODBC endpoint setups due to provider-specific SQL syntax rules.

Cause

SQL0604 / NativeError -604 means Db2 for IBM i rejected an invalid data-type attribute, typically a column or expression with an unsupported length, precision, scale, timestamp precision, or ALLOCATE value. This is normally an SQL-definition problem, not a network or ODBC connection problem. (on QR V2023.5.0.322)

The task fails because Qlik Replicate generates this invalid Db2 for i definition:

"STATEMENT" CLOB(0) NOT NULL,
"ERROR"     CLOB(0) NOT NULL

On Db2 for IBM i, a CLOB length must be between 1 byte and 2 GB. Therefore, CLOB(0) produces SQL0604 / -604 – Attributes not valid.  Other column definitions are valid.

That indicates the target endpoint is missing or uses the wrong configuration for the Endpoint --> Advanced tab --> Provider syntax setting.
 

Environment

• Qlik Replicate