KB489712: How to resolve the ODBC error when connecting to PostgreSQL with an existing DSN after upgrading to Strategy One (March 2026): Specified driver could not be loaded

The article explains how to fix the ODBC error: [IM003:0: on SQLHANDLE] [DataDirect][ODBC lib] Specified driver could not be loaded that occurs after upgrading to Strategy One (March 2026), where the PostgreSQL native ODBC driver path changed from pgsql-16 to pgsql-17. Existing DSNs in odbc.ini still pointing to the old pgsql-16 path cause the driver load failure.The article explains how to fix the ODBC error: [IM003:0: on SQLHANDLE] [DataDirect][ODBC lib] Specified driver could not be loaded that occurs after upgrading to Strategy One (March 2026), where the PostgreSQL native ODBC driver path changed from pgsql-16 to pgsql-17. Existing DSNs in odbc.ini still pointing to the old pgsql-16 path cause the driver load failure.

Introduction

After upgrading to Strategy One (March 2026), the PostgreSQL native ODBC driver is upgraded, the driver path changed (from pgsql-16 to pgsql-17). Existing DSNs that still reference the old path will fail to load the driver and trigger the error above. The fix is to update the DSN in odbc.ini to point to the new driver library path and ensure the library actually exists on disk.

Background:

The odbc.ini file stores DSN definitions on Linux.

By default, odbc.ini and odbcinst.ini resides under HOME_PATH, which is the home directory specified during installation.

Steps

1.Verify the new PostgreSQL ODBC driver path in odbcinst.ini:

[PostgreSQL Unicode(x64)] Driver=/opt/mstr/MicroStrategy/install/pgsql-17/lib/psqlodbcw.so Description=ODBC for PostgreSQL Setup=/opt/mstr/MicroStrategy/install/pgsql-17/lib/psqlodbcw.so FileUsage=1DriverUnicodeType=1

2. Confirm the driver exist on disk:

ls -l
/opt/mstr/MicroStrategy/install/pgsql-17/lib/psqlodbcw.so

3. Locate your odbc.ini file. It is typically under the installer-defined

HOME_PATH for the product’s user. Example path:

/opt/mstr/MicroStrategy/odbc.ini

4. Edit the DSNs in odbc.ini to point to the new driver and setup paths.

Before (old path using pgsql-16):

[YourPostgresDSN] Driver=/opt/mstr/MicroStrategy/install/pgsql-16/lib/psqlodbcw.so Servername=your_host Port=5432 Database=your_db

After (updated to pgsql-17):

[YourPostgresDSN] Driver=/opt/mstr/MicroStrategy/install/pgsql-17/lib/psqlodbcw.so Servername=your_host Port=5432 Database=your_db

Save the file.

5. Validate DSN connectivity.

6. If the error persists, check environment and permissions:

Check if path correct in env/ODBC.sh, check the line line: POSTGRESQL_PATH=

Restart the application service or session to pick up configuration changes if needed.

Comment

0 comments

Details

Knowledge Article

Published:

April 2, 2026

Last Updated:

April 2, 2026