Change Cast type in ODBC TARGET

[Yves_s]

hello,

We use the Target ODBC

When we reload Target DB2 z -> ODBC mysql it's work

but after  we got an error

00012460: 2022-08-18T11:57:21 [TARGET_APPLY ]E: RetCode: SQL_ERROR SqlState: 42000 NativeError: 1064 Message: [MySQL][ODBC 5.3(w) Driver][mysqld-5.7.22-log]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'varchar(15)) , CAST( `attrep_changes2A1F3B2C31F9DD56`.`col2` as varchar(15)) , ' at line 1 [1022502] (ar_odbc_stmt.c:3974)

I thinks it's because of varchar in the cast , it should be CHAR in place of varchar

is there a way to force the type of the cast ?

[Steve_Nguyen · Accepted solution]

1. why not use native MySQL target?

2. for ODBC , this have to be our Professional Service :

The ODBC target endpoint can be used to access targets that are not included in Qlik Replicate’s extensive Support Matrix. However, unless enabled through Professional Services and approved by your Account Manager, the ODBC target endpoint should not be used. Additionally, the ODBC target endpoint should not be used to access any targets already listed in the Support Matrix.

[Yves_s]

we do not use the Mysql target because we do not have the license.
however, we have ODBC license, as well as a MYSQL ODBC client.

So from what I understand, you are selling odbc license,but that won't work if another license of a target exists...

[Steve_Nguyen]

if you want to use MySQL target , then get the license a it is in the Support Matrix, 

as stated in the user guide.

if you want to use ODBC, then you would need PS and account manager approved . 

you are trying to use the ODBC endpoint in an incorrect way.

[Yves_s]

I use the odbc target as it should be expected, that is to say, to use an odbc client

and we shouldn't have to pay a PS for that

[Steve_Nguyen]

@Yves_s if MySQL is part of the Native support Matrix,

then use the Mysql endpoiht, if you have no license then contact your account manager.

using ODBC for native supported endpoint is incorrect.