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

KB486761: Exasol ODBC Updates in MicroStrategy ONE (June 2024)


Yao Fu

Quality Engineer, Senior • MicroStrategy


MicroStrategy ONE (June 2024) upgrades Exasol ODBC driver to 24.1.0 which may impact current user behavior.

Symptom


Strategy ONE (June 2024) Exasol ODBC connection may display the following errors:

  • Database error <5>: Connect failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [IM003:0 on SQLHANDLE] [DataDirect][ODBC lib] Specified driver could not be loaded.
  • [HY000:-30139776: on SQLHANDLE] [Exasol][Exasol Driver]Connection String contains invalid parameters.

Cause


Strategy ONE (June 2024) upgrades Exasol ODBC driver to 24.1.0 and the new version driver has the following updates, which may impact current user behavior:

  • The driver name was updated from EXASolution Driver to Exasol Driver.
  • Multiple versions of Exasol ODBC driver on Linux were removed and the driver file name was updated from libexaodbc-dd.so to libexaodbc.so.
  • The deprecated connecttimeout parameter was removed.
  • The new version driver checks if the connection string parameter names are supported, if they are not supported, an invalid parameter error occurs.


For more information, see ODBC Driver Version 24.0.0 Release Notes and ODBC Driver Version 24.1.0 Release Notes .

Solution

  1. The existing Linux Exasol DSN in odbc.ini must be modified manually to point to the new libexaodbc.so driver file, as shown below:

[Exasol]
Driver =<ODBCLIBPATH>/exasol_odbc/libexaodbc.so
EXAHOST=ip+address:port

EXASCHEMA=schema

  1. If you have any existing DSN drivers that are required to be DSN-less, perform the conversion before upgrading the Strategy ONE (June 2024) or convert the data source using the following API after upgrading:

POST /datasources/connections/{id}/conversion

ka0PW0000002UZtYAM_0EMPW000006ScRv.jpeg
  1. If you want to update any existing DSN-less connection strings to remove invalid parameters, use the following API for the patch scripts:

PATCH /datasources/connections/{id}

ka0PW0000002UZtYAM_0EMPW000006Sla1.jpeg

Additional Information
KB485854: Convert data sources based on DSN to be DSN-Less through REST APIs, Data Sources and Scripts entry.
Convert a DSN Data Source to DSN-less
Top Tips: Getting Started with MicroStrategy REST API
Introduction to MicroStrategy REST API


Comment

0 comments

Details

Knowledge Article

Published:

May 14, 2024

Last Updated:

June 21, 2024