Oracle Service Cloud ODBC 7.1.6 Windows
- Last Updated: May 8, 2026
- 14 minute read
- OpenAccess SDK
- Documentation
README
Progress (R) DataDirect (R)
Progress(R) DataDirect(R) for ODBC for Oracle Service Cloud(TM) Driver
Windows Platforms (32-bit and 64-bit)
Release 7.1.6
February 2026
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
IMPORTANT: You must have the Microsoft Data Access Components (MDAC)
installed to use this product.
* For 32-bit Windows systems, version 2.6 or higher is required.
* For 64-bit Windows systems, version 2.8 or higher is required.
Depending on the version of your Windows operating system, these
components may already be installed. You can download a utility that
determines whether MDAC is installed and its version from the following
Microsoft site:
http://msdn.microsoft.com/en-us/data/aa937730.aspx
You can also download MDAC from the same site.
CONTENTS
Post-GA Product Announcements
Requirements
Installation Directory
Data Source and Platform Support
Changes Since Service Pack 7.1.6 GA
Changes for Service Pack 7.1.6 GA
The Progress DataDirect for ODBC for Oracle Service Cloud Driver
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.
* The driver requires the following runtime library:
Microsoft Visual C/C++ runtime version 14.40.33810 or higher
Installation Directory
* The default installation directory for the 32-bit driver on a
64-bit system is:
C:\Program Files (86)\Progress\DataDirect\ODBC
* The default installation directory for all other installations is:
C:\Program Files\Progress\DataDirect\ODBC
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 Service Pack 7.1.6 GA
Windows Runtime Version Upgrade
-------------------------------
Some components of the driver are now compiled with a Visual Studio 2022
compiler for Windows platforms. As a result, you must have Microsoft
Visual C/C++ runtime version 14.40.33810 or higher on your machine 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.
* To install the 32-bit drivers on 64-bit Windows platforms and start the SQL
engine service, the installer requires the 32-bit version of Java SE 11 or
higher installed on your machine and defined on your path.
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 ICU library
file names have changed:
* For the 32-bit driver: From ivicu28.dll to ivicu.dll
* For the 64-bit driver: From ddicu28.dll to ddicu.dll
Notes:
* This upgrade is available starting in build 08.02.1072 of the ICU
library files.
* ivicu27.dll and ddicu27.dll will continue to be included in the product
package to support driver functionality.
Trace Library File Name Change
------------------------------
The trace library file names have been changed from ivtrc27.dll to
ivtrc28.dll (32-bit) and from ddtrc27.dll to ddtrc28.dll (64-bit) to
have the same file names across all platforms. This change allows for
faster release of security updates and a more consistent user
experience.
Note: To support the trace library file name change, the following
ICU library files have been added to the product package:
ivicu28.dll (32-bit) and ddicu28.dll (64-bit)
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
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 on a 64-bit system:
C:\Program Files (86)\Progress\DataDirect\ODBC
- For all other installations:
C:\Program Files\Progress\DataDirect\ODBC
* 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.
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.
JVM Upgrade
-----------
The driver has been updated to require a JVM that is version Java SE 7 or
higher, including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
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 Service Pack 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.
The Progress DataDirect for ODBC for Oracle Service Cloud Driver
The Progress DataDirect for ODBC for Oracle Service Cloud driver supports
standard SQL query language to provide read-only access to data managed by the
OracleRightNow 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
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
Config Options field. See "Config Options" for details.
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."
GUI Tab:
The value for config options are specified in the Config Options field on the
Advanced tab.
Querying the CreatedTime and UpdatedTime 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.
Internet Explorer and Google Toolbar Users
------------------------------------------
Internet Explorer with the Google Toolbar installed sometimes displays
the following error when the browser is closed: "An error has occurred
in the script on this page.". This is a known issue with the Google
Toolbar and has been reported to Google. When closing the driver's
help system, this error may display.
Installing and Removing Default Data Sources
--------------------------------------------
When you first install a driver, you are given the option to install a
default data source for that driver. We recommend that you select
this option. If you do not install the default data source at this
time, you will be unable to install a default data source for this
driver later. To install a default data source for a driver after
the initial installation, you must uninstall the driver and then
reinstall it.
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 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 the 32-bit Driver
The installer copies the following files to the Windows system
directory:
ivtrc28.dll DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default:
For 32-bit drivers on 64-bit machines:
C:\Program Files (x86)\Progress\DataDirect\ODBC\:
For all other installations:
C:\Program Files\Progress\DataDirect\ODBC:
license.txt Progress DataDirect license agreement
\drivers:
ivicu27.dll Unicode conversion tables
ivicu.dll Unicode conversion tables
ivrnow27.dll Progress DataDirect Oracle Service Cloud driver
ivrnow27r.dll Progress DataDirect Oracle Service Cloud driver
resource file
ivrnow27s.dll DataDirect Oracle Service Cloud driver
setup library
ivodbc.lic DataDirect License File
ivtrc28.dll DataDirect trace library
ivtrn27.dll DataDirect sample translation DLL
qeslqext.h Header file for DataDirect-specific ODBC
Definitions
\help:
*.html HTML redirects to online connector help
systems and documentation resources
\java\lib:
rightnow.jar Oracle Service Cloud Driver and DataSource classes
\NOTICES:
ODBC FOR OSC V7.1.6
NOTICES.TXT Third-party vendor license agreements
\READMES:
ODBC FOR OSC V7.1.6
README.TXT This file
\samples:
\bulk\bulk.c Bulk example source
\bulk\bulk.exe Bulk application
\bulk\bulk.mak Bulk example make file
\bulk\bulk.sln Bulk example solution file
\bulk\bulk.vcproj Bulk example project file
\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\bulk.rc Bulk streaming example resource file
\bulkstrm\bulkstreaming.sln Bulk streaming example solution file
\bulkstrm\bulkstreaming.vcproj Bulk streaming example project file
\bulkstrm\bulkstrm.exe Bulk streaming example application
\bulkstrm\bulkstrm.txt Bulk streaming description
\bulkstrm\ddlogging.properties Log configuration file for
the Oracle Service Cloud driver
\bulkstrm\msgprintf.hpp Bulk streaming example header file
\bulkstrm\ProgressDataDirect.bmp
\bulkstrm\ProgressDataDirect.ico
\bulkstrm\winmain.cpp Bulk streaming example source file
\example\ddlogging.properties Log configuration file for
the Oracle Service Cloud driver
\example\example.c Example source
\example\Example.exe Example application
\example\example.h Example header
\example\Example.mak Example make file
\example\Example.sln Example solution file
\example\Example.vcproj Example project file
\translat\LIBMAIN.C
\translat\README.TRN Translation Library example description
\translat\TRANSLAT.C Translation Library example source file
\translat\WINNT.MAK Translation Library example make file
\tools:
ddextwin.exe License Extender utility
ddprocinfo.exe Processor Information utility
DSNconvertersil.exe Data Source Converter utility
rightnowserver.exe
XMLP.EXE A GUI demo tool that persists a result set to
an XML data file
\uninstall\*.* Files used to uninstall the product
Installed Files for 64-bit Drivers
This file list assumes a full installation of all drivers and
documentation.
The installer copies the following files to the Windows system
directory:
ddtrc28.dll DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default:
C:\Program Files\Progress\DataDirect\ODBC:
license.txt Progress DataDirect license agreement
\drivers:
ddicu27.dll Unicode conversion tables
ddicu.dll Unicode conversion tables
ddrnow27.dll Progress DataDirect Oracle Service Cloud driver
ddrnow27r.dll Progress DataDirect Oracle Service Cloud driver
resource file
ddrnow27s.dll DataDirect Oracle Service Cloud driver
setup library
ddodbc.lic DataDirect License File
ddtrc28.dll DataDirect trace library
ddtrn27.dll DataDirect sample translation DLL
qeslqext.h Header file for DataDirect-specific ODBC
Definitions
\help:
*.html HTML redirects to online connector help
systems and documentation resources
\java\lib:
rightnow.jar Oracle Service Cloud Driver and DataSource classes
\NOTICES:
ODBC FOR OSC V7.1.6
NOTICES.TXT Third-party vendor license agreements
\READMES:
ODBC FOR OSC V7.1.6
README.TXT This file
\samples:
\bulk\bulk.c Bulk example source
\bulk\bulk.exe Bulk application
\bulk\bulk.mak Bulk example make file
\bulk\bulk.sln Bulk example solution file
\bulk\bulk.vcproj Bulk example project file
\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\bulk.rc Bulk streaming example resource file
\bulkstrm\bulkstreaming.sln Bulk streaming example solution file
\bulkstrm\bulkstreaming.vcproj Bulk streaming example project file
\bulkstrm\bulkstrm.exe Bulk streaming example application
\bulkstrm\bulkstrm.txt Bulk streaming description
\bulkstrm\ddlogging.properties Log configuration file for
the Oracle Service Cloud driver
\bulkstrm\msgprintf.hpp Bulk streaming example header file
\bulkstrm\ProgressDataDirect.bmp
\bulkstrm\ProgressDataDirect.ico
\bulkstrm\winmain.cpp Bulk streaming example source file
\example\ddlogging.properties Log configuration file for
the Oracle Service Cloud driver
\example\example.c Example source
\example\Example.exe Example application
\example\example.h Example header
\example\Example.mak Example make file
\example\Example.sln Example solution file
\example\example.vcproj Example project file
\translat\LIBMAIN.C
\translat\README.TRN Translation Library example description
\translat\TRANSLAT.C Translation Library example source file
\translat\WINNT.MAK Translation Library example make file
\tools:
ddextwin.exe License Extender utility
ddprocinfo.exe Processor Information utility
DSNConverterSil.exe Data Source Converter utility
rightnowserver.exe The Oracle Service Cloud SQL Server Engine
XMLP.EXE A GUI demo tool that persists a result set to
an XML data file
\uninstall\*.* Files used to uninstall the product
~~~~~~~~~~~~~~~~
February 2026
End of README.TXT