EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB33594: Known issues with MySQL AIX ODBC driver 5.1 (5.01.06.00)


Community Admin

• Strategy


This article outlines some known issues when using the MySQL AIX ODBC driver 5.1 (5.01.06.00)

KB33592 - Support status of MySQL Community Server 5.0/5.1 with Strategy Intelligence Server running on AIX
The following are some known issues with MySQL AIX ODBC driver 5.1 (5.01.06.00):

  • This driver does not support SQLCancel in 'Synchronous' mode. Set the 'Driver execution mode' to 'Asynchronous Connection' or 'Asynchronous Statement'. This setting is located at Configuration Managers > Database Instance Manager > Database Instance > Database Connection > Advanced
  • This driver does not recognize the 'Maximum query execution time' setting that is located at Configuration Managers > Database Instance Manager > Database Instance > Database Connection > Advanced
  • This driver supports parameterized inserts only in limited cases, depending on the data types being inserted. It fails when attempting to perform a parameterized insert involving columns with 'Decimal' or 'Double Precision' data types. The setting for parameterized queries is located at Configuration Managers > Database Instance Manager > Database Instance > Database Connection > Advanced
  • The MySQL AIX driver files can get conflicted with unixODBC or Teradata driver files, because of name and folder discrepancy, leading to “Specified driver not being loaded” error message such as below:
ka04W000000OhEBQA0_0EM440000002HST.gif
  • Therefore,  it is preferable to install this driver on a machine that does not have unixODBC or teradata files installed.
  • This is a UTF-16 driver, therefore the 'Character set encoding for UNIX drivers' setting should be set to 'Non UTF-8'in order to fetch characters correctly. This setting is located Configuration Managers > Database Instance Manager > Database Instance > Database Connection > Advanced
ka04W000000OhEBQA0_0EM440000002HSU.gif
  • This driver cannot be used to successfully fetch characters through the Strategy  DB Query Tool as it is a Non UTF-8 driver. This is expected to be addressed in a later version of the Strategy DB Query Tool as an option that can be toggled.

 
Third Party Software Installation WARNING
 
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017