Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
desmondchew
Creator III
Creator III

The target database is missing some records from the source database.

The target database is missing some records from the source database.

Target DB: MySQL 8

Source DB: 11.2.0.4 Oracle

 

 

[attunity.domain.com\Errors notification] NAVI_PROD8 replication task encountered the following error:
Failed to start load process for file '62'
RetCode: SQL_ERROR SqlState: HY000 NativeError: 0 Message: [MySQL][ODBC 8.0(w) Driver][mysqld-8.0.21]
Failed (retcode -1) to execute statement: 'load data local infile "d:\\Attunity\\Replicate\\data\\tasks\\NAVI_PROD8\\data_files\\1\\LOAD0000003E.csv" into table `prod-db`.`tableXYZ` CHARACTER SET UTF8MB4 fields terminated by ',' enclosed by '"' lines terminated by '\n'(
`column names ........'

Labels (1)
4 Solutions

Accepted Solutions
SwathiPulagam
Support
Support

Hi @desmondchew ,

 

I see you are using the ODBC driver 8.0.21 which is not supported.

Please refer to the below user guide link:

https://help.qlik.com/en-US/replicate/May2021/Content/Replicate/Main/MySQL/prereq_mysql.htm

After upgrading your ODBC Driver if you still see the missing records issue. Please raise a support case.

We need more logging to do the analysis.

 

Thanks,

Swathi

View solution in original post

desmondchew
Creator III
Creator III
Author

Hi,

Thank you. I have upgraded to the required ODBC driver 5.03.13. I have attached a screenshot showing this. Do I need to remove the old ODBC 8 driver or is there a way to verify which driver that it is using as default?

Desmond

 

View solution in original post

john_wang
Support
Support

Hello Desmond @desmondchew , copy @SwathiPulagam ,

Looks like you are using a inaccurate version ODBC driver. The best versions are:

1. MySQL ODBC 5.3.13 (you are meaning 5.0.13?)

2. MySQL ODBC 8.0.23/8.0.24/8.0.25 (you mentioned  8.0.21)

So far you can upgrade to 8.0.25, or use 5.3.13. These 2 versions can be installed side by side.

In Replicate endpoint, you use internal parameter "provider" to specify which version driver you want to use. For example "MySQL ODBC 8.0 Unicode Driver" (if you upgrade to 8.0.25).

Hope this helps.

Regards,

John.

 

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

john_wang
Support
Support

Hello @desmondchew ,

You are right.

For MySQL target  endpoint the internal parameter "driver" should be used.

For MySQL source endpoint the internal parameter "provider" should be used.

thanks,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

9 Replies
SwathiPulagam
Support
Support

Hi @desmondchew ,

 

I see you are using the ODBC driver 8.0.21 which is not supported.

Please refer to the below user guide link:

https://help.qlik.com/en-US/replicate/May2021/Content/Replicate/Main/MySQL/prereq_mysql.htm

After upgrading your ODBC Driver if you still see the missing records issue. Please raise a support case.

We need more logging to do the analysis.

 

Thanks,

Swathi

desmondchew
Creator III
Creator III
Author

Hi,

Thank you. I have upgraded to the required ODBC driver 5.03.13. I have attached a screenshot showing this. Do I need to remove the old ODBC 8 driver or is there a way to verify which driver that it is using as default?

Desmond

 

desmondchew
Creator III
Creator III
Author

Hi Swathi,

Apparently after installing the ODBC 5.0.13 driver and restarting Qlik services, the Qlik replicate tool is not picking up the ODBC 5.0.13 driver  but uses the old ODBC 8.0 driver. Can you advise how could I switch to the ODBC 5.0.13 please?


RetCode: SQL_ERROR  SqlState: HY000 NativeError: 0 Message: [MySQL][ODBC 8.0(w) Driver][mysqld-8.0.21] Failed (retcode -1) to execute statement:

john_wang
Support
Support

Hello Desmond @desmondchew , copy @SwathiPulagam ,

Looks like you are using a inaccurate version ODBC driver. The best versions are:

1. MySQL ODBC 5.3.13 (you are meaning 5.0.13?)

2. MySQL ODBC 8.0.23/8.0.24/8.0.25 (you mentioned  8.0.21)

So far you can upgrade to 8.0.25, or use 5.3.13. These 2 versions can be installed side by side.

In Replicate endpoint, you use internal parameter "provider" to specify which version driver you want to use. For example "MySQL ODBC 8.0 Unicode Driver" (if you upgrade to 8.0.25).

Hope this helps.

Regards,

John.

 

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
desmondchew
Creator III
Creator III
Author

Thanks John.

I see that the latest version MySQL ODBC is 8.0.28. Can we use this version?


Desmond

 

desmondchew
Creator III
Creator III
Author

Hi John,

I tried to add "parameter" in the drop down box upon clicking into "internal parameter". However the drop down values doesn't has "parameter" and I am unable to add. I have attached the screenshot to describe the issue. My attunity version is  V2021.5.0.863 

 

Thank you.

Desmond

 

john_wang
Support
Support

Hello @desmondchew ,

the latest version MySQL ODBC is 8.0.28. Can we use this version?


No, you cannot because there is some minor compatibility issues in the latest 3 versions (26/27/28).

So You can only use MySQL ODBC 8.0.23/8.0.24/8.0.25

 

...However the drop down values doesn't has "parameter" ...


You should input "provider" (remove the double-quotes pls).

Regards,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
desmondchew
Creator III
Creator III
Author

Thanks John on the ODBC.

 

As for the "provider", I have input provider as instructed, it doesn't show any value as close to provider. I however found the keyword, "driver". Can that be used?

john_wang
Support
Support

Hello @desmondchew ,

You are right.

For MySQL target  endpoint the internal parameter "driver" should be used.

For MySQL source endpoint the internal parameter "provider" should be used.

thanks,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!