Oracle Service Cloud ODBC 7.1.6 UNIX
- Last Updated: May 8, 2026
- 17 minute read
- OpenAccess SDK
- Documentation
README
Progress (R) DataDirect (R)
Progress(R) DataDirect(R) for ODBC for Oracle Service Cloud(TM) Driver
UNIX and Linux Platforms (32-bit and 64-bit)
Release 7.1.6
January 2026
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
CONTENTS
Post-GA Product Announcements
Requirements
Installation Directory
Data Source and Platform Support
Changes Since 7.1.6 GA
Changes for 7.1.6 GA
Progress DataDirect for ODBC for Oracle Service Cloud Driver
Required Operating System Patches
Notes, Known Problems, and Restrictions
Driver Work Around Options
Documentation
Installed Files for the 32-bit Driver
Installed Files for the 64-bit Driver
Post-GA Product Announcements
The readme files will no longer be updated with product announcements and new
features after the General Availability (GA) of the product. For the latest
updates and enhancements, please refer to the release notes
(https://www.progress.com/datadirect-connectors/whats-new).
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) that is Java SE 8
or higher, including Oracle JDK, OpenJDK, and IBM SDK (Java)
distributions. Also, you must set the library path environment
variable of your operating system to the directory containing your
JVM's libjvm.so [a] file and that directory's parent directory.
* The driver requires the following runtime libraries:
- AIX: C/C++ runtime libraries version 16.1 or higher
- Linux: C/C++ runtime libraries version GCC 2.12 or higher
- Solaris: C/C++ runtime libraries version 12.6 or higher
Installation Directory
* The default installation directory for the 32-bit driver is:
/opt/Progress/DataDirect/ODBC_32bit
* The default installation directory for the 64-bit driver is:
/opt/Progress/DataDirect/ODBC_64bit
If you do not have /opt directory permissions, the installer program installs
the driver to your home directory by default. For example, the directory for
32-bit installation would be:
/<home_directory>/Progress/DataDirect/ODBC_32bit
where
<home_directory>
is the home directory for the user who is installing the product.
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 7.1.6 GA
ICU Library Upgrade (74.1)
--------------------------
The ICU library files that are installed with the product have been upgraded
to version 74.1. As a part of this upgrade, the following platforms and their
file names have been updated:
* AIX platforms
- 32-bit product package: From libivicu28.a to libivicu.a
- 64-bit product package: From libddicu28.a to libddicu.a
Note - This upgrade is available starting in build 08.02.1072 of the ICU
library files.
* Linux platforms
- 32-bit product package: From libivicu28.so to libivicu.so
- 64-bit product package: From libddicu28.so to libddicu.so
Note - This upgrade is available starting in build 08.02.0965 of the ICU
library files.
* Solaris platforms (Sparc and Solaris X)
- 32-bit product package: From libivicu28.so to libivicu.so
- 64-bit product package: From libddicu28.so to libddicu.so
Note - This upgrade is available starting in build 08.02.1799 of the ICU
library files.
As part of this upgrade, the following platforms and their compiler versions
have been changed as follows:
* For AIX platforms, the compiler version has been upgraded to xlclang++ 16.1.
As a result, you must have C/C++ runtime libraries of 16.1 or higher
installed to run the driver.
* For Linux platforms, the compiler version has been upgraded to GCC 7.3.1.
As a result, you must have C/C++ runtime libraries of GCC 2.12 or higher
installed to run the driver.
* For Solaris platforms, the compiler version has been upgraded to Oracle
Developer Studio 12.6. As a result, you must have C/C++ runtime libraries
of 12.6 or higher installed to run the driver.
JRE Requirement for the Installer
---------------------------------
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.
Driver Manager Upgrade (8.0)
----------------------------
The Driver Manager has been upgraded to version 8.0. The purpose of
this upgrade is to have all DataDirect for ODBC drivers use the latest
version of the Driver Manager, which allows for faster security updates
and a consistent user experience. Note that the Driver Manager is
backward compatible.
As part of this upgrade:
* The following ICU library files have been added to the product
package:
- For UNIX: libivicu28.so (32-bit) and libddicu28.so (64-bit)
- For Linux: libivicu.so (32-bit) and libddicu.so (64-bit)
* The trace library file names have been changed for both UNIX and Linux:
- 32-bit: From ivtrc27.so to ivtrc28.so
- 64-bit: From ddtrc27.so to ddtrc28.so
Note: libivicu27.so (32-bit) and libddicu27.so (64-bit) will continue to
be included in the product package to support driver functionality.
The Driver Manager build included with the product is 08.02.1997 (U1987).
ODBC Cursor Library
-------------------
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.
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
Password Encryption Tool
------------------------
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.
Installer Upgrade
-----------------
The installer program has been enhanced to use a more modern and
secure technology. As a result of this enhancement:
* The default installation location has been changed to:
- For the 32-bit driver:
/opt/Progress/DataDirect/ODBC_32Bit
- For the 64-bit driver:
/opt/Progress/DataDirect/ODBC_64Bit
* The new installer program does not support upgrading installations
made with earlier versions of the installer. You will need to
uninstall the existing installation and reinstall with the new
installer to resume upgrades in the same directory.
* The existing data sources cannot be used until they are
updated to point to the new installation location. To learn
how to update them, refer to the best practices documented
at https://community.progress.com/s/.
* License keys you have used for the retired 7.1 installer cannot
be used with the new installer. Request new keys by either
contacting the Progress DataDirect Technical Support team or visiting
https://www.progress.com/datadirect-connectors/request-upgrade.
Documentation
-------------
Any product package made available after February 9, 2021 will not include the
HTML help system or user's guide PDF. The full documentation set, including
these items, is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-oracle-service-cloud
While the product packages will not include these documentation items, the
installation Help directory will provide an HTML redirect for direct access
to the HTML help.
Note that all Progress DataDirect for ODBC documentation has been migrated to
the Progress Information Hub:
https://docs.progress.com/
Timestamp Logging in Packet Logs
--------------------------------
The drivers using base version B0548 and later have been enhanced to include
timestamp in the internal packet logs by default. If you want to disable the
timestamp logging in packet logs, set PacketLoggingOptions=1. The internal
packet logging is not enabled by default. To enable it, set
EnablePacketLogging=1.
Setting Unicode Encoding Type for Connections
---------------------------------------------
The Driver Manager for UNIX/Linux has been enhanced to support setting the
Unicode encoding type for applications on a per connection basis. By passing a
value for the SQL_ATTR_APP_UNICODE_TYPE attribute using SQLSetConnectAttr, your
application can specify the encoding at connection. This allows your
application to pass both UTF-8 and UTF-16 encoded strings with a single
environment handle.
The valid values for the SQL_ATTR_APP_UNICODE_TYPE attribute are SQL_DD_CP_UTF8
and SQL_DD_CP_UTF16. The default value is SQL_DD_CP_UTF8.
This enhancement is available in build 07.16.0398 of the driver manager.
Java 7 Support
--------------
Java SE 7 has reached the end of its product life cycle and will no longer
receive generally available security updates. As a result, the drivers will
no longer support JVMs that are version Java SE 7 or earlier. Support for
distributed versions of Java SE 7 and earlier will also end, including
IBM SDK (Java Edition).
Support for API 1.4
-------------------
The driver has been enhanced to support Oracle RightNow CX API version 1.4.
When attempting to connect with the enhanced driver for the first
time, either delete the existing native files manually or set the Create Map
connection option to ForceNew.
Managed Objects connection option
---------------------------------
The driver may not fetch metadata for the newly added managed objects by
default. You can specify them using the Managed Objects connection option
to fetch metadata for them.
Enable Access Request Header connection option
----------------------------------------------
The new Enable Access Request Header connection option allows you to enable
the access request header for a connection to improve its performance and
quality of service.
Deprecation of Interface Name connection option
-----------------------------------------------
The Interface Name connection option has been deprecated. The driver will
continue to provide backward copatibility for it, but will not use it for
connections in the current and new versions.
NamedIDBehavior Config Option
-----------------------------
The new NamedIDBehavior config option allows you to determine whether the
Name attribute of NamedID fields is exposed in the relational map. This
option can be used to avoid "poor performing query" errors by reducing
the size of result sets. For details, see "'Poor Performing Query' Error
Message" and "NamedIDBehavior Config Option" in "Notes, Known Problems,
and Restictions."
Refer to the fixes.txt file in the product installation directory for a list of
changes by build number.
Changes for 7.1.6 GA
Min Long Varchar
----------------
The new Min Long Varchar Size connection option allows you to fetch
SQL_LONGVARCHAR columns whose size is smaller than the minimum
imposed by some third-party applications.
Varchar Threshold
-----------------
The new Varchar Threshold connection option allows you to fetch columns
that would otherwise exceed the upper limit of the SQL_VARCHAR type for some
third-party applications.
For more information about these features, refer to THE PROGRESS DATADIRECT FOR
ODBC FOR ORACLE SERVICE CLOUD DRIVER USER'S GUIDE AND REFERENCE.
Progress DataDirect for ODBC for Oracle Service Cloud Driver
Progress DataDirect for ODBC for Oracle Service Cloud driver supports
standard SQL query language to provide read-only access to data managed by
the Oracle RightNow CX Cloud Service. The driver maps the Oracle Service Cloud
data model to a set of relational tables and uses a client-side data cache
for improved performance.
In addition:
* The driver supports Oracle RightNow CX API version 1.2 against sites
whose version is February 2014, May 2014, or August 2014.
* The driver supports all ODBC Core functions.
* The driver supports the core SQL-92 grammar.
* The driver supports the following data types:
- BASE_64_BINARY maps to SQL_LONGVARBINARY
- BOOLEAN maps to SQL_BIT
- DATE maps to SQL_TYPE_DATE
- DATETIME maps to SQL_TYPE_TIMESTAMP
- DECIMAL maps to SQL_DOUBLE
- ID maps to SQL_BIGINT
- INTEGER maps to SQL_INTEGER
- LONG maps to SQL_BIGINT
- LONGTEXT maps to SQL_LONGVARCHAR
- STRING maps to SQL_VARCHAR
Configuring Data Sources
Data sources are stored in the system information file (typically,
odbc.ini). For details on configuring this file, see the PROGRESS DATADIRECT
FOR ODBC FOR ORACLE SERVICE CLOUD DRIVER USER'S GUIDE AND REFERENCE.
Notes, Known Problems, and Restrictions
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.
Error Against Long Varchar Type Fields
--------------------------------------
When attempting to fetch 30720 bytes of data from Long Varchar type fields,
the driver returns the following error: "Unexpected response:
502 (Bad Gateway): --MIMEBoundary759d7ff0-6f2b-1ea1-29f5-0010e06fe42a."
Note: This issue has been noticed only with Oracle Service Cloud 19D, but it
may occur with other versions of the data source as well.
"Poor Performing Query" Error Message
-------------------------------------
Oracle Service Cloud returns a "Poor performing query" error when executing
certain queries with the driver. This typically occurs when executing a query
that requires the Oracle Service Cloud service to perform join operations on
tables containing a large number of rows. We are currently working on a
permanent solution to this problem; however, in the interim, you can work
around this issue by doing the following:
1. Configure the following connection options to the values provided:
ConfigOptions
-------------
Note: In addition to specifying the following recommended value, include any
other value-pairs that you currently specify for ConfigOptions. These
value-pairs should be specified within the curly brackets in a
comma-separated list.
Value: {NamedIDBehavior=2}
CreateDB
--------
Value: 1 (ForceNew)
EnablePagingWithOrderByID
-------------------------
Value: 1 (Enabled)
Note: This is the default value for this option.
Refer to "Configuring and Connecting to Data Sources" in the User's Guide
and Reference for information on configuring connection options for your
data source.
2. Connect to your Oracle Service Cloud instance. At connection, the driver
deletes the current local map files and creates new files using the updated
config option settings.
3. Change the value of CreateDB to your preferred setting before your next
connection. We recommend specifying a value of 2 (NotExist).
4. Test your settings by executing a query that previously returned the error.
Based on the results, choose one of the following:
- If you receive the "Poor Performing Query" error, proceed to the
next step.
- If your query is successfully returned, skip to the "Results" section.
5. Tune the driver's fetching behavior. Using the WSFetchSize option, decrease
the number of rows the driver attempts to fetch until the
"Poor Performing Query" error is no longer returned. For optimal
performance, configure WSFetchSize so that the driver returns the maximum
number of rows possible without returning the error. For example, if you
receive the error fetching 500 rows, but not 499 rows, set WSFetchSize=499
for maximum throughput.
Be aware that decreasing the fetch size can increase the number of web
service calls the driver makes to the Oracle Service Cloud service. If your
query exceeds the statement call limit, increase the number of rows fetched
using WSFetchSize or increase the statement call limit using the
StatementCallLimit option to work around this issue.
Notes:
* You will need to disconnect and reconnect for changes to connection option
values to have effect.
* In the default setting, WSFetchSize=0, the driver uses the maximum page
size allowed by the database to determine the number of rows it attempts
to fetch for Oracle Service Cloud versions August 2014 or later. For
versions earlier than August 2014, the driver attempts to fetch a maximum
of 10,000 rows.
Results:
This configuration will allow you to avoid the "Poor performing query" error in
subsequent connections. If you begin receiving the error again, tune the
WSFetchSize connection option according to the guidelines provided in step 4.
NamedIDBehavior Config Option
-----------------------------
NamedIDBehavior
Attribute:
NamedIDBehavior
Purpose:
Determines whether the Name attribute of NamedID fields is exposed in the
relational map.
Valid Values:
1 | 2
The value for this option is specified as a key=value pair in the
ConfigOptions value.
Behavior:
If set to 1, the driver exposes the Name attribute of the NamedID fields in
the relational model. Specify this setting if your application needs to
access the Name strings associated with NamedID columns.
If set to 2, the driver does not expose the Name attribute of the NamedID
fields in the relational model. This setting can be used to avoid "poor
performing query" errors received when executing SELECT * queries against
tables containing a large number of rows.
Default:
1
Notes:
- If you are receiving "poor performing query" errors, you can work around
this issue by setting NamedIDBehavior=2. This reduces the size of the
result set, allowing the Oracle Service Cloud service to successfully
return the query. For this change to have effect, you will need recreate
the local mapping files by setting CreateDB=1; then, connecting to your
Oracle Service Cloud instance. After creating your new local mapping files,
you should reconfigure CreateDB to your preferred setting. We recommend a
setting of CreateDB=2. For more information, see "Poor Performing
Query errors."
Querying the CreatedTime and Updated Time fields on Custom Objects
------------------------------------------------------------------
Although the CreatedTime and UpdatedTime fields on custom objects map to the
relational view, you cannot query against them unless you enable the
fields within the Object Designer in the Oracle Service Cloud admin tool.
Querying File Attachments for Sub-Objects
------------------------------------------
Queries against file attachments for sub-objects fail to retrieve the
attachment data.
Creating Views With Two-Part Names
----------------------------------
The driver returns an invalid schema error when creating a view using a
two-part name in the view definition.
Drop Cache Statement
--------------------
In some situations, the driver reports that executing a DROP CACHE statement
completed successfully without dropping the cache.
ODBC Development on UNIX and Linux Platforms
--------------------------------------------
All of the Release 7.1 Core Components (header files, etc.) needed for
development of ODBC applications on UNIX and 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 UNIX and Linux Platforms
----------------------------------------------------
A default installation of the product on UNIX and 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.
For AIX Users
------------------------------
Some IBM AIX C compilers, such as xlc 3.1.4, do not support the use
of C++ build binaries. C developers on AIX should consult their
compiler documentation and verify that their AIX C compiler supports
the use of C++ shared libraries or the application could be unstable.
Unexpected behavior may occur randomly if the LIBPATH variable
exceeds 178 characters AND the ORACLE_HOME variable is relatively
long. To resolve this, create a shorter symbolic link for
ORACLE_HOME.
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 ORACLE SERVICE CLOUD DOCUMENTATION SET
-----------------------------------------------------------------------
The driver documentation set is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-oracle-service-cloud
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_32bit
If you do not have /opt directory permissions, the installer program installs
the driver to your home directory by default. For example, the directory for
32-bit installation would be:
/<home_directory>/Progress/DataDirect/ODBC_32bit
where
<home_directory>
is the home directory for the user who is installing the product.
fixes.txt List of fixes since last release
license.txt Progress DataDirect license agreement
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
/bin:
ivtestlib Test application to check that required libraries
are present and loadable
/help:
*.html HTML redirects to online connector help
systems and documentation resources
rightnow_connect.txt Help text for the Oracle Service Cloud driver
SQLDriverConnect dialog
/include:
odbcinst.h Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h
/java/lib:
rightnow.jar Java components for the Oracle Service Cloud driver
/lib:
Resource library file names end in r; setup library file names end in s.
The resource and setup libraries are for use by the LINUX ODBC
Administrator and appear in the file list ONLY on Linux platforms.
ivrnow27.so Oracle Service Cloud driver
ivtrc28.so Progress DataDirect trace library
ivtrn27.so Progress DataDirect sample translation library
libivicu.a Unicode conversion tables for AIX platforms
libivicu.so Unicode conversion tables for Linux and
Solaris platforms
libivicu27.so Unicode conversion tables [.a on AIX]
libodbc.so ODBC Driver Manager [.a on AIX]
libodbcinst.so ODBC Installer [.a on AIX]
odbc.so ODBC Driver Manager (dynamically loadable)
[AIX only]
odbcinst.so ODBC Installer (dynamically loadable)
[AIX only]
/locale/en_US/LC_MESSAGES:
ivrnow27.mo Oracle Service Cloud library message file
ivrnow27.po Oracle Service Cloud library message source
odbc.m ODBC Driver Manager message file
odbc.po ODBC Driver Manager message source
/NOTICES:
ODBC for
Oracle Service Cloud
v7.1.6 notices.txt Third-party vendor license agreements
/READMES:
ODBC for
Oracle Service Cloud
v7.1.6 readme.txt This file
/samples:
/bulk/bulk Bulk application
/bulk/bulk.c Bulk example source
/bulk/bulk.mak Bulk example make file
/bulk/bulk.txt Bulk example description
/bulk/ddlogging.properties Log configuration file for the
Oracle Service Cloud driver
/bulkstrm/bulk.cpp Bulk streaming example source
/bulkstrm/bulk.hpp Bulk streaming example header
/bulkstrm/bulkstrm Bulk streaming example application
/bulkstrm/bulkstrm.txt Bulk streaming example description
/bulkstrm/main.cpp Bulk streaming example source
/bulkstrm/msgprintf.hpp Bulk streaming example header
/bulkstrm/streambulk.mak Bulk streaming example make file
/bulkstrm/ddlogging.properties Log configuration file for the
Oracle Service Cloud driver
/example/example Example application
/example/example.c Example source
/example/example.h Example header
/example/example.mak Example make file
/example/ddlogging.properties Log configuration file for the
Oracle Service Cloud driver
/tools:
ddencpwd Password Encryption Tool
ddextu License Extender utility
ddprocinfo Processor Information utility
/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
If you do not have /opt directory permissions, the installer program installs
the driver to your home directory by default. For example, the directory for
64-bit installation would be:
/<home_directory>/Progress/DataDirect/ODBC_64bit
where
<home_directory>
is the home directory for the user who is installing the product.
fixes.txt List of fixes since last release
license.txt Progress DataDirect license agreement
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
/bin:
ddtestlib Test application to check that required libraries
are present and loadable
/help:
*.html HTML redirects to online connector help
systems and documentation resources
rightnow_connect.txt Help text for the Oracle Service Cloud driver
SQLDriverConnect dialog
/include:
odbcinst.h Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h
/java/lib:
rightnow.jar Java components for the Oracle Service Cloud driver
/lib:
Resource library file names end in r; setup library file names end in s.
The resource and setup libraries are for use by the LINUX ODBC
Administrator and appear in the file list ONLY on Linux platforms.
ddrnow27.so Oracle Service Cloud driver
ddtrc28.so Progress DataDirect trace library
ddtrn27.so Progress DataDirect sample translation library
libddicu.a Unicode conversion tables for AIX platforms
libddicu.so Unicode conversion tables for Linux and Solaris
platforms
libddicu27.so Unicode conversion tables [.a on AIX]
libodbc.so ODBC Driver Manager [.a on AIX]
libodbcinst.so ODBC Installer [.a on AIX]
odbc.so ODBC Driver Manager (dynamically loadable)
[AIX only]
odbcinst.so ODBC Installer (dynamically loadable)
[AIX only]
/locale/en_US/LC_MESSAGES:
ddrnow27.mo Oracle Service Cloud driver message file
ddrnow27.po Oracle Service Cloud driver message file source
odbc.m ODBC Driver Manager message file
odbc.po ODBC Driver Manager message source
/NOTICES:
ODBC for
Oracle Service Cloud
v7.1.6 notices.text Third-party vendor license agreements
/READMES:
ODBC for
Oracle Service Cloud
v7.1.6 readme.txt This file
/samples:
/bulk/bulk Bulk application
/bulk/bulk.c Bulk example source
/bulk/bulk.mak Bulk example make file
/bulk/bulk.txt Bulk example description
/bulk/ddlogging.properties Log configuration file for the
Oracle Service Cloud driver
/bulkstrm/bulk.cpp Bulk streaming example source
/bulkstrm/bulk.hpp Bulk streaming example header
/bulkstrm/bulkstrm Bulk streaming example application
/bulkstrm/bulkstrm.txt Bulk streaming example description
/bulkstrm/main.cpp Bulk streaming example source
/bulkstrm/msgprintf.hpp Bulk streaming example header
/bulkstrm/streambulk.mak Bulk streaming example make file
/bulkstrm/ddlogging.properties Log configuration file for the
Oracle Service Cloud driver
/example/ddlogging.properties Log configuration file for
the Oracle Service Cloud driver
/example/example Example application
/example/example.c Example source
/example/example.h Example header
/example/example.mak Example make file
/example/example64.txt Example description
/tools:
ddencpwd Password Encryption Tool
ddextu License Extender utility
ddprocinfo Processor Information utility
uninstall/*.* Files used to uninstall the product
~~~~~~~~~~~~~~~~
January 2026
End of README.TXT