how to replicate table logical file in source database DB2 for iseries as400

[Minhajul]

Hi Team Qlik Replicate,

How to replicate table logical file DB2 for iseries on qlik replicate?

in my case, we have qlik replicate environment production with version 6.x and qlik replicate environment development version 7.x

in environment prodcution we can add table logical file to replicate using qlik replicate but when we use qlik replicate development we can't add the table logical file.

please advice me for the solution.

Thanks,
Regards,
Minhajul.

[john_wang · Accepted solution]

Hello @Minhajul ,

Thanks for reaching out to Qlik Community!

If I understand you correctly, you are meaning how to replicate VIEW in DB400 to target side, is that correct?

If yes, then you can configure ODBC DSN in Replicate machine, and then use the ODBC DSN connect to AS400 to replicate VIEWs (logical files). There were some articles:

How to load data load from DB2 iSeries Views to the target Snowflake?

Can we replicate view from IBM DB2 as 400 iSeries source Database

BTW, Replicate is log based CDC product, because VIEW's data are not recorded in Journal so no way to get delta data from VIEW. Full Load is supported method only.

Hope this helps.

Regards,

John.

[Minhajul]

Dear John Wang,

thanks for help, this is works for my case.

but when we apply the solution in qlik replicate version 7.x the task can't started because need license in source.

do we have to buy a new license for this replication task?

Regards,
Minhajul.

[john_wang]

Hello @Minhajul ,

Thanks for your update.

Looks to me there is not any difference between v6.6 and v7.0 regarding ODBC source endpoint support. If you have ODBC source license, then it will work for both v6.6 and v7.0. Or are you using Express License in v7.0? you may register your official license in v7.0 and try again.

If you do not have such a license yet, please reach out to your region QDI Sales team, or your Account Manager for help. 

BTW, please take note both v6.6 and v7.0 had reached its end of support (EOS) date ,  please update to supported versions, Replicate 2022.11 is highly recommended.

Feel free to let us know if you need any additional assistance.

Best Regards,

John.

[Minhajul]

Hello John Wang,

well noted, Thank you very much for the help.

Best Regards,
Minhajul.

[Minhajul]

Hello John Wang,

i have a question about license, in this case, we replicate object (logical files), we have license in PROD environment and DEV environment,

when we use license in prod env we success the task replicate (Object Files).

but when we try in DEV environment get error.

the question is, what the different of 2 license we have?

Thanks,
Best Regards,
Minhajul.

[john_wang]

Hello @Minhajul ,

Thanks for the update.

There are 2 different endpoint types in source available list:

• IBM DB2 for iSeries = DB2iSeries
• ODBC = ODBC

the screen samples in GUI:

DB2iSeries is used for "IBM DB2 for iSeries" driver, in your scenario it's required for DB2 Physical files tasks.

ODBC token is needed for ODBC generic source driver, in your scenario it's used to replicate DB2 Logical files (VIEW).  BTW,  Object Files can be different, includes Physical Files (Table), Logical Files (View), Alias etc.

Regards,

John.

[Minhajul]

Hello John Wang,

Thanks for reply.

when we see the prod server, we don't use source end point connection ODBC but IBM DB2 for iSeries.

and we can replicate the logical file (view).

why this condition can happen, any suggestion for this case?

note: implementor of this project have expired contract and we get the maintenance project in this case.

Thanks,
Best Regards,
Minhajul.

[john_wang · Accepted solution]

Hello @Minhajul ,

Thanks for the update.

If my memory serves me well, I do not think this part of code changed between v6.0/v7.0 and current major version 2022.11/2023.5. If you set SERVER component to Verbose and check the "repsrv.log", we may see the SQL which Replicate uses to prepare the available tables list (The below SQL was took from Replicate 2022.11), like:

select TABLE_SCHEMA,TABLE_NAME from QSYS2.SYSTABLES where

... and TABLE_TYPE in ('T','P')

Replicate only gets the T and P type from DB400 database .
T: Table

P: Physical file

but not V , or L (View, or Logical file). Would you please confirm the object type of "UTRNPND" ?

Regards,

John.

[nareshkumar]

Hi John Wang,

Here logical files means not View's .. In iSeries DB2 Logical files  are noting but Indexes where AS400 programs refer  Logical files Unique keys  instead of Physical file(tables).