A DB2 iSeries source experiences high latency, potentially leading to a high volume of transactions to fall behind in processing.
Resolution
To reduce or even eliminate the latency, there are a two of options:
- If you have less than 500 tables that you wish to replicate, consider using the Qlik UDTF to retrieve the transactions from the journal receiver files. It is much faster and will reduce latency( read times) as it performs a filtering action on the DB2 iSeries database server to pull only the transactions for your tables from the receiver files.
- If you need to run several replication tasks (that replicate data from IBM DB2 for iSeries), it is more efficient (though not essential) to create a separate journal for each task. As only one journal can be specified per endpoint, you would also need to define a separate endpoint for each task. By using this second method, you are avoiding having to sift through the large receiver files that contain the transactions for other tables that are not being replicated.
Environment
Qlik Replicate ( all currently supported versions)
IBM DB2 iSeries ( all supported versions)
Related Content
Using IBM DB2 for iSeries as a source Prerequisites | Qlik Replicate Help
