Aha ODBC 8.0.0 Linux
- Last Updated: May 8, 2026
- 10 minute read
- OpenAccess SDK
- Documentation
README
Progress(R) DataDirect(R)
Progress(R) DataDirect(R) for ODBC for Aha!(TM)
Linux Platforms (32- and 64-bit)
Release 8.0.0
August 2025
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
This README file contains information for Progress(R) DataDirect(R)
for ODBC for Aha!(TM).
This README file contains information not included in the PROGRESS
DATADIRECT(R) FOR ODBC FOR AHA!(TM) DRIVER USER'S GUIDE.
CONTENTS
Post-GA Product Announcements
Requirements
Installation Directory
Data Source and Platform Support
Changes Since 8.0.0 GA
Release 8.0.0 Features
Configuring Data Sources
Notes, Known Problems, and Restrictions
Driver WorkAround Options
Documentation
Installed Files for 32-bit Drivers
Installed Files for 64-bit Drivers
Requirements
* The installer program requires a JVM that is Java SE 11 or higher, including
Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
* The driver requires a Java Virtual Machine (JVM): Java SE, version 8 or
higher, including Oracle JDK, OpenJDK, IBM SDK (Java), or higher LTS versions.
Also, you must set the library path environment variable of your operating
system to the directory containing your JVM's libjvm.so file and that
directory's parent directory.
* The driver requires the following runtime library for Linux:
C/C++ runtime libraries version GCC 2.12 or higher
Installation Directory
* The default installation directory for the 32-bit driver is:
/opt/Progress/DataDirect/ODBC
* The default installation directory for the 64-bit driver is:
/opt/Progress/DataDirect/ODBC_64Bit
Data Source and Platform Support
For the latest data source and platform support information, refer to the
Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
Changes Since 8.0.0 GA
CVE-2022-41853 - Use of Externally-Controlled Input to Select Classes or Code
('Unsafe Reflection')
-----------------------------------------------------------------------------
Several Progress DataDirect ODBC drivers utilized a version of HyperSQL
Database that was vulnerable to remote code execution described in
CVE-2022-41853. All impacted drivers have been patched to fix this
vulnerability. For details on impacted drivers and fixed versions, refer to
the following KB article:
https://community.progress.com/s/article/DataDirect-ODBC-Critical-Security-
Bulletin-November-2022-CVE-2022-41853
Enhancements
------------
* The ICU library files that are installed with the product have been upgraded
to version 74.1. In addition, the ICU library file names have changed. For
the 32-bit driver, the ICU file name has changed from libivicu28.so to
libivicu.so. For the 64-bit driver, the ICU file name has changed from
libddicu28.so to libddicu.so.
This upgrade is available starting in build 08.02.0965 of the ICU library
files.
* A Password Encryption Tool, called ddencpwd, is now included with the product
package. It encrypts passwords for secure handling in connection strings and
odbc.ini files. At connection, the driver decrypts these passwords and passes
them to the data source as required.
Changed Behavior
----------------
* The installer program now requires you to install a JRE that is Java SE 11 or
higher before running the installer. In earlier versions, the JRE used by the
installer program was included in the product. However, to avoid potential
security vulnerabilities, the installer program no longer includes a JRE.
Instead, the installer program uses the JRE in your environment to allow for
the most secure version of a JRE to be used.
Notes:
- This change does not affect the JVM requirements for the driver. For the latest
driver requirements, refer to the Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
- The installer program cannot remove the already installed JRE files from the
install directory automatically. Remove them manually.
* The product package no longer includes the ODBC Cursor library file
(odbccurs.so) because it has some known security vulnerabilities that
could potentially expose you to security risks.
Note: The installer program cannot remove the ODBC Cursor library file
automatically while installing a new version of the driver. Remove it
manually.
* The installer program has been updated to no longer install common components
for drivers that do not use them. As a result, the installer program no longer
installs the following common components for the Aha! driver:
- OpenSSL library files, such as ivopenssl30.so, ddopenssl30.so, fips.so, and
openssl.cnf.
- Curl library files, such as libivcurl28.so and libddcurl28.so.
If the files are not used by any other DataDirect driver on your machine, you
can safely remove them from existing product directories.
* The Server Name (ServerName) connection option has been renamed Host Name
(HostName). To support existing configurations, the ServerName attribute will
continue to be supported as an alias for the Host Name option.
Release 8.0.0 Features
The Progress DataDirect for ODBC for Aha!(Aha! driver) is a driver that
supports SQL read-only access for ODBC applications to Aha! services. To
support SQL access to Aha! services, the driver creates a relational map of the
Aha! data model and translates SQL statements to Aha! REST API requests. In
addition, the driver employs a SQL engine component that provides support to
SQL constructs unavailable to Aha! services. This functionality offers a number
of advantages, including support for reporting data and metadata in a form ODBC
applications are ready to use.
Features:
* Supports SQL read-only access to Aha! endpoints
* The driver supports all ODBC Core and Level 1 functions and some Level 1 and
Level 2 features.
* Supports Aha! data types through data type inference.
* Supports Aha! custom fields, including many fields added
through third-party plug-ins
* Supports Basic, URL parameter (API key), and OAuth 2.0 authentication
* Supports SSL data encryption
* Supports the handling of large result sets with paging, and the
Fetch Size (FetchSize) Web Services Fetch Size (WSFetchSize) connection
options
* Includes the DataDirect ODBC Driver Configuration Manager for quick
configuration and testing of your driver. This Configuration Manager allows
you to:
- Configure data sources
- Generate and edit connection URLs
- Test connect data sources and connection URLs
- Execute SQL commands for testing
- Fetch OAuth tokens
- Access connection property descriptions and the full product
documentation
Configuring Data Sources
Data sources are stored in the system information file (typically,
odbc.ini). This file can be edited using a text editor or the DataDirect
Configuration Manager. For details on configuring this file, see the PROGRESS
DATADIRECT FOR ODBC FOR AHA! DRIVER USER'S GUIDE.
Notes, Known Problems, and Restrictions
The following are notes, known problems, and restrictions for the
8.0 release of the driver:
Specifying values for the same connection option multiple times
---------------------------------------------------------------
The driver does not support specifying values for the same connection
option multiple times in a connection string or DSN. If a value is
specified using the same attribute multiple times or using both
long and short attributes, the connection may fail or the driver may
not behave as intended.
Connection issues when specifying ExtendedOptions
-------------------------------------------------
When specifying a value for the Extended Options (ExtendedOptions) option in
the Configuration Manger, the driver currently adds the option and its value to
the Connection String field. However, the ExtendedOptions attribute is not
supported in Connection Strings; therefore, attempting to connect with the
generated connection string or executing a test connect with the configuration
manager will result in the an “Invalid attribute in the connection string: XO”
error.
To work around this issue, manually edit the connection string to remove
"ExtendedOptions=" from the connection string; then, specify the value of
ExtendOptions as semi-colon separated options in the string.
For example:
Driver=<driver_name>;HostName=<host_name>;ExtendedOptions=WorkArounds2=4096,
WorkArounds2=8192;
Becomes:
Driver=<driver_name>;HostName=<host_name>;WorkArounds2=4096;WorkArounds2=8192;
Out-of-memory Errors
--------------------
The driver has been designed to handle large result sets that result. However,
out-of-memory errors can still occur. The following items outline how to reduce
the likelihood of out-of-memory errors for your environment.
* Reduce Fetch Size (FetchSize) to reduce demands on memory. By lowering the
maximum number of rows as specified by Fetch Size, you lower the number of
rows the driver is required to process before returning data to the
application. Thus, you reduce demands on memory and decrease the likelihood
of out-of-memory errors.
* Decrease Result Memory Size (ResultMemorySize) until results are successfully
returned. Intermediate results larger than the value specified will be
written to disk as opposed to held in memory. When configured correctly, this
avoids memory limitations by not relying on memory to process larger
intermediate results. Be aware that while writing to disk reduces the risk of
out-of-memory errors, it also negatively impacts performance. For optimal
performance, decrease this value only to a size necessary to avoid errors. By
default, Result Memory Size is set to -1, which sets the maximum size of
intermediate results held in memory to a percentage of the max Java heap
size. If you received errors using the default configuration, use the max
Java heap size divided by 4 as a starting point when tuning this option.
* Increase the JVM heap size. By increasing the max Java heap size, you increase
the amount of data the driver can accumulate in memory and avoid
out-of-memory errors.
ODBC Development on Linux Platforms
-----------------------------------
All of the Release 8.0 Core Components (header files, etc.) needed for
development of ODBC applications on Linux are installed into the /include
directory created by the product installer.
Please read the notices.txt file in the installation directory for
licensing information regarding the ODBC Core Components. Contact your
Progress DataDirect representative if you have any questions.
Developers using programming languages other than C++:
The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC
Driver Manager can be used with any language that supports loading a
C++ shared library; however, if you are using a programming language
other than C++, you must take additional steps to ensure that the C++
libraries are initialized properly when loaded. If you are not using
C++, consult your compiler documentation for instructions on using C++
shared libraries with your application.
LANG Environment Setting on Linux Platforms
-------------------------------------------
A default installation of the product on Linux assumes that
the value of the LANG environment setting is en_US. If your locale is
not set to en_US, the drivers may not return error messages properly.
In this case, you must create a symbolic link in the
<Install_Dir>/locale directory that has the same value as the LANG
environment setting. This link must point to the
<Install_Dir>/locale/en_US directory.
SQLColAttribute(s)
------------------
The column attributes 1001 and 1002, which were assigned as DataDirect-
specific attributes, were inadvertently used as system attributes by
the Microsoft 3.0 ODBC implementation. Applications using those
attributes must now use 1901 and 1902, respectively.
SQL_C_NUMERIC
-------------
Because of inconsistencies in the ODBC specification, users attempting
to use SQL_C_NUMERIC parameters must set the precision and scale values
of the corresponding structure and the descriptor fields in the
Application Parameter Descriptor.
Driver WorkAround Options
Progress DataDirect has included non-standard connection options (workarounds)
for the driver that enable you to take full advantage of packaged ODBC-enabled
applications requiring non-standard or extended behavior. Refer to the chapter
"WorkAround options" in THE PROGRESS DATADIRECT FOR ODBC DRIVERS REFERENCE for a
description of these options.
Documentation
PROGRESS DATADIRECT FOR ODBC FOR AHA! DOCUMENTATION SET
-------------------------------------------------------
The driver documentation set is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-aha
You can access the online help system directly via the HTML redirect in the
installation Help directory.
Installed Files for the 32-bit Driver
This file list assumes a full installation of the 32-bit driver and
documentation.
The installer copies the following files and subdirectories to the
product installation directory, by default:
/opt/Progress/DataDirect/ODBC:
/<install_dir>/:
----------------
odbc.csh Setup script for C shell
odbc.ini Sample odbc.ini file
odbcinst.ini Sample odbcinst.ini file
odbc.sh Setup script for Bourne shell
IVODBC.LIC DataDirect license file
license.txt End User License Agreement
/bin/:
------
ivtestlib Test application to check that required
libraries are present and loadable
/FIXES/:
--------
fixes8.0.txt List of fixes since last release
/help/:
-------
*.html HTML redirects to online connector help systems
and documentation resources
/include/:
----------
odbcinst.h Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h
/install/:
---------
*.* Files associated with the installer program
/java/lib/:
----------
aha.jar Java components of the driver
/lib/:
------
ivaha28.so DataDirect Aha! driver
ivtrc28.so DataDirect trace library
libivicu.so Unicode conversion tables
libodbc.so ODBC Driver Manager
libodbcinst.so ODBC Installer
/locale/en_US/LC_MESSAGES/:
--------------------------
ivaha28.mo Aha! driver message file
ivaha28.po Aha! driver message file source
odbc.m ODBC Driver Manager message file
odbc.po ODBC Driver Manager message source
/NOTICES/:
----------
ODBC for Aha
v8.0 notices.txt Third-party vendor license agreements
/READMES/:
----------
ODBC for Aha
v8.0 readme.txt This file
/samples/bulk/:
---------------
bulk Bulk application
bulk.c Bulk example source
bulk.mak Bulk example make file
ddlogging.properties Log configuration file for the
Aha driver
/samples/bulkstrm/:
------------------
bulkstrm Bulk streaming example application
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
Aha driver
main.cpp Bulk streaming example source file
msgprintf.hpp Bulk streaming example header file
/samples/example/:
------------------
example Example application
example.c Example source
example.h Example header
example.mak Example make file
ddlogging.properties Log configuration file for the
Aha driver
/samples/trn/:
--------------
makefile Translation Library example make file
readme.trn Translation Library example description
translat.c Translation Library example source file
/tools/:
--------
ddencpwd Password Encryption Tool
ddextu License Extender utility
ddprocinfo Processor Information utility
launch_server.sh Script that launches the SQL Engine in
server mode
/uninstall/:
------------
*.* Files used to uninstall the product
Installed Files for the 64-bit Driver
This file list assumes a full installation of the 64-bit driver and
documentation.
The installer copies the following files and subdirectories to the
product installation directory, by default:
/opt/Progress/DataDirect/ODBC_64Bit:
/<install_dir>/:
-------------
odbc.csh Setup script for C shell
odbc.ini Sample odbc.ini file
odbcinst.ini Sample odbcinst.ini file
odbc.sh Setup script for Bourne shell
DDODBC.LIC DataDirect license file
license.txt End User License Agreement
/bin/:
------
ddtestlib Test application to check that required
libraries are present and loadable
/FIXES/:
--------
fixes8.0.txt List of fixes since last release
/help/:
-------
*.html HTML redirects to online connector help systems
and documentation resources
/include/:
----------
odbcinst.h Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h
/install/:
---------
*.* Files associated with the installer program
/java/lib/:
----------
aha.jar Java components of the driver
/lib/:
------
ddaha28.so DataDirect Aha! driver
ddtrc28.so DataDirect trace library
libddicu.so Unicode conversion tables
libodbc.so ODBC Driver Manager
libodbcinst.so ODBC Installer
/locale/en_US/LC_MESSAGES/:
---------------------------
ddaha28.mo Aha! driver message file
ddaha28.po Aha! driver message file source
odbc.m ODBC Driver Manager message file
odbc.po ODBC Driver Manager message source
/NOTICES/:
----------
ODBC for Aha
v8.0 notices.txt Third-party vendor license agreements
/READMES/:
----------
ODBC for Aha
v8.0 readme.txt This file
/samples/bulk/:
---------------
bulk Bulk application
bulk.c Bulk example source
bulk.mak Bulk example make file
ddlogging.properties Log configuration file for the
Aha! driver
/samples/bulkstrm/:
------------------
bulkstrm Bulk streaming example application
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
Aha! driver
main.cpp Bulk streaming example source file
msgprintf.hpp Bulk streaming example header file
/samples/example/:
------------------
example Example application
example.c Example source
example.h Example header
example.mak Example make file
ddlogging.properties Log configuration file for the
Aha! driver
/samples/trn/:
--------------
makefile Translation Library example make file
readme.trn Translation Library example description
translat.c Translation Library example source file
/tools/:
--------
ddencpwd Password Encryption Tool
ddextu License Extender utility
ddprocinfo Processor Information utility
launch_server.sh Script that launches the SQL Engine in
server mode
/uninstall/:
------------
*.* Files used to uninstall the product
~~~~~~~~~~~~~~~~~~
August 2025
End of README.TXT