Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
I'm using IBM DB2 as a source and Google BigQuery as a target in my task, but when I run the task, it is stuck in the main loop.
task only has one table with 52 records.
How do I resolve this problem?
Hello @harsh2 ,
Thanks for your cooperation. Finally we found out the reason. The same query took 2 hours to response even run it in STRSQL, the query is:
SELECT OBJLONGSCHEMA, OBJLONGNAME from table(QSYS2.OBJECT_STATISTICS('*ALL', 'FILE')) J WHERE JOURNAL_LIBRARY='APACDB' and JOURNAL_NAME='QSQJRN' and JOURNALED='YES' |
Where APACDB & QSQJRN is the journal library name and journal name.
Please enable option "Skip Journal Validation" in the "IBM DB2 for iSeries" source endpoint to skip the journal validation, a sample:
Regards,
John.
logs :
Please increase logging for ~5 minutes as follows and see if it provides helpful information:
Performance = trace
Sorter = trace
Source_Capture = verbose
Source_Unload = verbose
Target_Apply = verbose
Target_Load = verbose
Please closely monitor the disk space where the data directory resides during this time as the logs will be large. Shouldn't be needed for only 5 minutes, but you can configure when to trigger new task logs in the server settings so files won't be too large to manage: Setting automatic roll over and cleanup #Setting automatic roll over and cleanup | Qlik Replicate He...
Hope this helps,
Dana
I already set all to verbose and run the task for 5 minutes.
PFA Logs of task
Thanks & regards
Harsh Patel
Hello @harsh2 ,
Seems the gap caused by the getting changes SQL. How about if you run the query manually (eg in STRSQL) to see how long it takes?
A sample SQL (take from the task log file):
SELECT * STARTING_TIMESTAMP=>'2023-11-16 18:48:32',JOURNAL_CODES=>'CDFRJ', JOURNAL_ENTRY_TYPES=>'PT,PX,UB,UP,DL,DR,BR,UR,CG,DF,CT,SC,CM,CR,RB,FN,PR', STARTING_RECEIVER_LIBRARY=>'*CURLIB', STARTING_RECEIVER_NAME=>'*CURCHAIN')) AS J |
If it takes a long time (eg several minutes) then please check DB400 side to see why it's slow. or you may adjust the starting timestamp to get fewer rows to see how about the result.
Hope this helps.
Regards,
John.
Hello @john_wang,
As you pointed out, after executing the select query, it completed within a few seconds with no significant delays. Is there any potential optimization or adjustment we can make on the Qlik Replicate side to enhance performance?
Thank & Regards,
Harsh Patel
Hello @harsh2 ,
Thanks for your update.
Please set SOURCE_UNLOAD/SOURCE_CAPTURE to Verbose and rerun the task to see if the issue persists. If yes please open a support ticket and attach the Diag Packages, support team will help you further.
Regards,
John.
Hello @harsh2 ,
Thanks for your cooperation. Finally we found out the reason. The same query took 2 hours to response even run it in STRSQL, the query is:
SELECT OBJLONGSCHEMA, OBJLONGNAME from table(QSYS2.OBJECT_STATISTICS('*ALL', 'FILE')) J WHERE JOURNAL_LIBRARY='APACDB' and JOURNAL_NAME='QSQJRN' and JOURNALED='YES' |
Where APACDB & QSQJRN is the journal library name and journal name.
Please enable option "Skip Journal Validation" in the "IBM DB2 for iSeries" source endpoint to skip the journal validation, a sample:
Regards,
John.
Thank you so much for your feedback! @harsh2 ,It's a glad to work with you.