Preparing TDV Data Services for ODBC Client Connections
TDV does not require any special configuration for clients to connect with it using 32-bit or 64-bit ODBC drivers.
After you publish a resource, ODBC application clients can use the resources. It is recommended, though not required, that the data service have a catalog for use with the ODBC driver.
The TDV ODBC driver supports code pages for the language sets supported by the host operating system. For Windows server installations, TDV uses multibyte-to-widechar and widechar-to-multibyte system calls to perform conversions. For UNIX server installations, TDV uses the iconv library to perform conversions.
By default, TDV Server listens to port 9401 for ODBC connections. The ODBC port number is always one greater than the server’s web services HTTP base port which by default, is 9400. So the ODBC default port number is 9401. If SSL is used (encrypt is set to true), the ODBC driver automatically adds 2 to the port value so that the 9403 port is used. To determine the actual ODBC port settings, see
TDV Port Settings for Client Connections to TDV.
To support any client regardless of type
1. Create a Data Service data source and catalog.
2. Configure the ODBC client to use the 32-bit or 64-bit ODBC driver.
3. Use the published data service and catalog as targets.
5. For early releases of Oracle 11g, there is an error in DG4ODBC which causes queries that access a published TDV view to hang indefinitely if the query contains a numeric WHERE clause filter. To temporarily work around this issue execute the following command in you SQL console prior to executing any queries.
ALTER SESSION SET CURSOR_SHARING = EXACT;
Or, upgrade your Oracle 11g instance to release 11.2.0.3 or later. Refer to Oracle bug 11858021 for more information.