Skip Journal Validation in Source Endpoint

[ilham-alldata]

Journal validation does have skip journal validation, it's a good idea to check it or don't check it. safe or not? what effect?
what is the good and correct way to export import. in the source endpoint, the journal name and library journal are used as a reference for searching the table? What if it's empty? how's the configuration? because if the input is wrong, the endpoint connection can still be successful

[Dana_Baldwin]

Hi @ilham-alldata 

I'm not clear on all the items you are asking, but I can comment on journal validation. If it is enabled, it can cause lengthy delays starting the task. If you're sure you've got all your tables logged to the same journal defined, or you've already run the task once with journal validation enabled, it is safe to disable it so the task starts more quickly.

Are you referring to export/import of a task? You can use the user interface for these activities. If you are using one task to create a separate but similar one, edit the task name the 2 or 3 places it appears in the task JSON file before importing so a new task is created rather than overwriting the existing one.

Change data for the tables need to be written to a journal, and all in the same journal defined in the task endpoint. Yes, with the journal blank a basic connection test will succeed, but without it defined, and the tables all included in that journal, you will not get CDC data in the task.

Hope this helps!

Dana

[john_wang]

In addition to @Dana_Baldwin comments:

>> in the source endpoint, the journal name and library journal are used as a reference for searching the table? What if it's empty? how's the configuration? because if the input is wrong, the endpoint connection can still be successful

The Journal Name and Journal Library are used to capture changes. It's not relate to the connection test, or available tables retrieve. so even they are set to empty, the Endpoint Ping Test succeeds still, and you can still get tables list in task design.

Regards,

John.

[SushilKumar]

Hello @ilham-alldata 

As per my knowledge Journal validation does have skip journal validation, it's a good idea to check it or don't check it. safe or not? what effect?

its not about check it or not check it. if journal is present then Qlik replicate process the changes post extracting information for the participating table. 

Sometimes it suggested to customer when Qlik submits Querry to DB to get the general information and it takes long time to get the response. then we suggest Skipping journal to seed up the validation. 

if journal is not available against the table it will anyhow.

Regards,

Sushil Kumar

[Kent_Feng]

Hi team,

Please check the user's guide for "skip journal validation":

https://help.qlik.com/en-US/replicate/May2024/Content/Replicate/Main/IBM%20DB2%20for%20iSeries/advan...

Skipping Journal Validation
From IBM DB2 for iSeries 7.3, Replicate automatically validates the specified journal. This involves checking that the journal exists and that it contains the tables selected for replication. When numerous tables are selected for replication, this process may take some time. In such cases, if you are sure that the specified journal exists and that it contains the correct tables, you may want to skip the validation phase.

To do this, select the Skip journal validation check box.

Thanks

Kent