We are running DB2 on zOS as a qlik replicate source endpoint. The R4Z task/module is installed on our DB2 on zOS.
Our qlik replicate tasks are set up/defined so NO DDL changes on source endpoint should be replicated to target endpoint.
If we perform a DDL change on the DB2 zOS on a table that is NOT included in a replicate task, it's working as expected... no activity on R4C regarding the DDL changes.
However if we do a DDL change on a table that is included in a qlik replicate task... we got lot og R4Z activity (see attached pic). Remember our qlik replicate tasks are defined so NO DDL change should be replicated (see attached pic).
This is not as expected.... it seems like qlik replicate reading table structure from system tables and the full data content. If there are large number of rows in the table we are facing timeout issue on the DB2 Charge job itself. (because it takes a lot of time for qlik to read all the data)
To me it seems very strange qlik replicate have this behavior because the table having the DDL changes is NOT included in any qlik replicate task where it is defined "Replicate DDL changes to target endpoint".
Can someone help me on this ? Is the R4Z behavior as expected ?
Thank you for the post to the Qlik Community. There is a reported issue with DB2 Z/OS RECOB-7983 noted which is being included in the new 2024.5 version of Replicate to help resolve this issue with the catalog Table when a DDL change is done when the Table is being captured in the Task. Please check when the new version is released in the current weeks ahead and note the RECOB as part of the patch included in the new version. Thank you have a great day.
Besides @Dana_Baldwin comments, even we set to ignore the DDL in Qlik Replicate, however Qlik Replicate need to care about the old/new metadata of the monitored tables as Replicate need the new table definition to map the BSDS. BTW, Definitely you are correct, Qlik Replicate reading table structure from system tables.
Maybe some timeout parameters solve the timeout issue on the DB2 Charge job. Please open a support ticket and attach the Diag Package, we need further information to check the issue.
Hope this helps.
John.
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Thank you for the post to the Qlik Community. There is a reported issue with DB2 Z/OS RECOB-7983 noted which is being included in the new 2024.5 version of Replicate to help resolve this issue with the catalog Table when a DDL change is done when the Table is being captured in the Task. Please check when the new version is released in the current weeks ahead and note the RECOB as part of the patch included in the new version. Thank you have a great day.
