Issue:

Qlik data replication tasks from DB2 iSeries can fail due to communication errors with the source system. A common cause is that log stream tasks fail to resume because the CURCHAIN journal receiver has exceeded its connection limit. Below are the details of this issue and recommended solutions.

Scenario:

A log stream task configured with the Advance Run option, starting from a specific timestamp, failed and returned the following error:

The system logged this error message:

Troubleshooting Findings:

• Behavior When Resuming from Timestamp: When a task is resumed using a specific timestamp, the system references the journal receiver library *CURLIB and the receiver name *CURCHAIN.

  The following warnings were observed:

   

   

  00051632: 2024-10-03T01:39:14:491526 [SOURCE_CAPTURE] Execute status=1022502, native=-443 (db2i_endpoint_capture.c:1602) 00051632: 2024-10-03T01:39:14:491526 [SOURCE_CAPTURE] Execute status=1022511, native=-502 (db2i_endpoint_capture.c:1602)

Root Cause:

The CURCHAIN journal receiver has a connection limit (in this case, 1024 connections). When the environment exceeds this limit, the task fails if it attempts to resume from a timestamp.

However, if the task is resumed normally (without a timestamp), the system reads from a different receiver name, bypassing the CURCHAIN limit, and the task runs successfully.

Resolution:

To resolve the issue:

• Monitor Journal Receiver Chains: Regularly monitor the journal receiver chain to ensure that connection limits are not exceeded.
• Receiver Management: Implement a cleanup mechanism to detach old or unused journal receivers.
• Increase Connection Limits: If the environment requires it, consider increasing the CURCHAIN connection limit to allow for more connections during data replication processes.

Leveraging the power of Qlik and Talend for increased productivity and reduced time to value with automated data pipelines.

• Lambda architecture is a data-processing architecture designed to handle massive quantities of data by taking advantage of both batch and stream-processing methods.
• Design and implementation of a Lambda architecture is typically complex due to the number of technologies needed to implement batch and streaming layers.
• In this white paper, we’ll demonstrate an approach that leverages the combined Qlik and Talend Data Integration stack to achieve a no-code implementation.

How the DoD makes decisions is changing. Historical transaction reporting and static batch data analyses are giving way to predictive data science, streaming analytics, machine learning (ML), and artificial intelligence (AI). The DoD must embrace these new paradigms for more informed, real-time decisions to impact business, operations, and mission performance.

This whitepaper will address how Qlik can enable the DoD to achieve it's mission.