Target: MySQL Community 8.0.28 (upgraded from MySQL 5.7)
All parameters on the server have been set to utf8mb4 (as before)
In the logs, Qlick is pointing to the following ODBC Driver:
Using default driver manager 'unixODBC', path is '/opt/attunity/replicate/lib/libodbc.so.2.0.0'
In the logs, getting this error:
RetCode: SQL_ERROR SqlState: 07006 NativeError: 0 Message: [MySQL][ODBC 5.2(w) Driver][mysqld-8.0.28]Source character set not supported by client [1022502] (ar_odb c_stmt.c:3467)
I don't want to install an RPM (system wide) if Attunity(qlik) is pointing to it's own driver.
Q1. Do I need to update the driver under the attunity directory ?
Q2. If so, how do I do this ?
Q3. Will this be backward compatible as I have another replication going for MySQL 5.7
Install MySQL ODBC Unicode Driver 64-bit on the ReplicateServer machine.
Information note
Only these driver versions are supported:
5.3.11 to 5.3.13
8.0.23 to 8.0.25
By default Replicate 2021.11 look for MYSQL 8. x Unicode driver. If you want to point out the specific driver version example 5. x please follow the steps provided in the below community article:
To add to this.. I ended up installing the ODBC 8 driver on the server..
The odd thing is, the above reference saying it's using a driver under it's own directory still hold true, but after installing the latest V8 driver, the logs are showing that it's using
Going to connect to ODBC connection string: DRIVER={MySQL ODBC 8.0 Unicode Driver}
so I'm a little confused on how all this work..
On a side note, the original error has disappeared.. but I would like to know what's happening.
Install MySQL ODBC Unicode Driver 64-bit on the ReplicateServer machine.
Information note
Only these driver versions are supported:
5.3.11 to 5.3.13
8.0.23 to 8.0.25
By default Replicate 2021.11 look for MYSQL 8. x Unicode driver. If you want to point out the specific driver version example 5. x please follow the steps provided in the below community article:
