Qlik Replicate tasks using DB2 LUW Source Endpoint experience latency when consuming data.
Resolution
Verify if the DB2 LUW configuration for the DB2 instance of the Source endpoint has its configuration parameters LOGMETHOD1 and LOGMETHOD2 set to a backup device location.
This would indicate the DB2 Log Reader Agent is loading the transaction logs from a backup device which will add overhead to the task using this DB2 Source Endpoint.
To correct the condition you can set the DB2 parameter by the DBA Overflow Log path from NULL to archive_log_path. See overflowlogpath - Overflow log path configuration parameter for more information.
This path can point to a local disk on the DB2 server for optimal access to the DB2 transaction logs.
First log archive method:
(LOGARCHMETH1) = VENDOR:/opt/simpana/Base64/libDb2Sbt.so
Second log archive method:
(LOGARCHMETH2) = DISK:/db2/P10/alternate_logpath/
Overflow log path:
(OVERFLOWLOGPATH) = archive_log_path
Cause
This is the result of the DB2 Log Reader Agent, which Qlik Replicate calls using the DB2 API and from which we access the transaction logs from DB2. In a setup in which LOGMETHOD1 is pointing to a backup device, the DB2 Log Reader Agent loading the transaction logs will lead to overhead and ultimately latency.
Related Content
Environment
