Environment-Specific Information

The sections “For Windows Users” and “For UNIX and Linux Users” contain information specific to your operating environment.

The following sections refer to threading models. Refer to Chapter 3 “Threading” in the DataDirect Connect Series for ODBC Reference for an explanation of threading.

For Windows Users

The following are requirements for the 32- and 64-bit drivers on Windows operating systems.

32-Bit Drivers

■	All required network software that is supplied by your database system vendors must be 32-bit compliant.

■	If your application was built with 32-bit system libraries, you must use 32-bit drivers. If your application was built with 64-bit system libraries, you must use 64-bit drivers (see “64-Bit Drivers”). The database to which you are connecting can be either 32-bit or 64-bit enabled.

■	The following processors are supported:

●	x86: Intel

●	x64: Intel and AMD

■	The following operating systems are supported for DataDirect Connect for ODBC. All editions are supported unless otherwise noted.

●

Windows 7

●	Windows Server 2008

●	Windows Vista

●	Windows XP, Service Pack 1 and higher

●	Windows Server 2003

●	Windows 2000, Service Pack 1 and higher

■	The following operating systems are supported for DataDirect Connect XE for ODBC. All editions are supported unless otherwise noted.

●

Windows 7

●	Windows Server 2008 Enterprise, Datacenter, Web and Small Business Editions

●	Windows Vista

●	Windows XP Professional, Service Pack 2 and higher

●	Windows Server 2003, Service Pack 2 and higher

●	Windows 2000 Professional and Server, Service Pack 4

■	For the Salesforce driver: A 32-bit Java Virtual Machine (JVM), J2SE 5 or higher, is required. Also, you must set the PATH environment variable to the directory containing your 32-bit JVM’s jvm.dll file, and that directory’s parent directory.

■	An application that is compatible with components that were built using Microsoft Visual Studio 2010 compiler and the standard Win32 threading model.

■	You must have ODBC header files to compile your application. For example, Microsoft Visual Studio includes these files.

64-Bit Drivers

■	All required network software that is supplied by your database system vendors must be 64-bit compliant.

■	The following processors are supported:

●

Intel

●

AMD

■	The following operating systems are supported for DataDirect Connect64 for ODBC. All editions are supported unless otherwise noted.

●

Windows 7

●	Windows Server 2008

●	Windows Vista

●	Windows Server 2003

●	Microsoft Windows XP Professional Edition

■	The following operating systems are supported for DataDirect Connect64 XE for ODBC. All editions are supported unless otherwise noted.

●

Windows 7

●	Windows Server 2008 Enterprise, Standard, or Datacenter Editions

●	Windows Vista

●	Windows Server 2003, Service Pack 2 and higher

●	Windows XP Professional, Service Pack 2 and higher

■	An application that is compatible with components that were built using Microsoft C/C++ Optimizing Compiler Version 14.00.40310.41 and the standard Windows 64 threading model.

■	For the Salesforce driver: A 64-bit JVM, J2SE 5 or higher, is required. Also, you must set the PATH environment variable to the directory containing your 32-bit JVM’s jvm.dll file, and that directory’s parent directory.

■	You must have ODBC header files to compile your application. For example, Microsoft Visual Studio includes these files.

Setup of the Drivers

The drivers must be configured before they can be used. See Chapter 1 “Quick Start Connect” for information about using the Windows ODBC Administrator. See the individual driver chapters for details about driver configuration.

Driver Names

The prefix for all 32-bit driver file names is IV. The prefix for all 64-bit driver file names is DD. The file extension is .DLL, which indicates dynamic link libraries. For example, the 32-bit DB2 Wire Protocol driver file name is IVDB2nn.DLL, where nn is the revision number of the driver.

Refer to the readme file shipped with the product for the file name of each driver.

For UNIX and Linux Users

The following are requirements for the 32- and 64-bit drivers on UNIX/Linux operating systems.

32-Bit Drivers

■	All required network software that is supplied by your database system vendors must be 32-bit compliant.

■	If your application was built with 32-bit system libraries, you must use 32-bit drivers. If your application was built with 64-bit system libraries, you must use 64-bit drivers (see “64-Bit Drivers”). The database to which you are connecting can be either 32-bit or 64-bit enabled.

■	For the Salesforce driver: A 32-bit Java Virtual Machine (JVM), J2SE 5 or higher, is required. Also, you must set the library path environment variable of your operating system to the directory containing your JVM’s libjvm.so [sl | a] file and that directory’s parent directory.

The library path environment variable is:

●	LD_LIBRARY_PATH on Linux, HP-UX Itanium, and Oracle Solaris

●	SHLIB_PATH on HP-UX PA-RISC

●	LIBPATH on AIX

AIX

■	IBM POWER processor

■	AIX 5L operating system, version 5.3 fixpack 5 and higher, 6.1, and 7.1

■	An application compatible with components that were built using Visual Age C++ 6.0.0.0 and the AIX native threading model

NOTE FOR SALESFORCE USERS: When compiling an application on AIX for use with the driver for Salesforce, you must not use the -brtl option.

NOTE FOR TERADATA USERS: When compiling an application on AIX for use with the driver for the Teradata database, you must use the -brtl option. For example:

cc -o pgm pgm.o  –brtl -lodbc

or

ld -o pgm –brtl pgm.o -lodbc

HP-UX

■	The following processors are supported:

●

PA-RISC

●	Intel Itanium II (IPF)

■	The following operating systems are supported:

●	For PA-RISC: HP-UX 11i Versions 2 and 3 (B.11.23 and B.11.31), 11i (B.11.11), and 11

●	For IPF: HP-UX IPF 11i Versions 2 and 3 (B.11.23 and B.11.31)

■	For PA-RISC: An application compatible with components that were built using HP aC++ 3.30 and the HP-UX 11 native (kernel) threading model (posix draft 10 threads)

■	For IPF: An application compatible with components that were built using HP aC++ 5.36 and the HP-UX 11 native (kernel) threading model (posix draft 10 threads)

NOTE: All of the standard 32-bit UNIX drivers are supported on HP PA-RISC. For IPF, the following drivers are supported:

DataDirect Connect for ODBC drivers	■ DB2 Wire Protocol ■ Informix Wire Protocol ■ MySQL Wire Protocol ■ Oracle Wire Protocol ■ PostgreSQL Wire Protocol ■ Progress OpenEdge Wire Protocol ■ SQL Server Wire Protocol ■ Sybase Wire Protocol ■ Oracle ■ SQL Server Legacy Wire Protocol
DataDirect Connect XE for ODBC drivers	■ Salesforce ■ Sybase IQ Wire Protocol

NOTES FOR SALESFORCE:

■	PA-RISC: Set the LD_PRELOAD environment variable to the libjvm.sl from your JVM installation.

■

Itanium:

●	Do not link with the –lc linker option.

●	Set the LD_PRELOAD environment variable to the libjvm.so from your JVM installation.

Linux

■	The following processors are supported:

●	x86: Intel

●	x64: Intel and AMD

■	The following operating systems are supported:

●	Red Hat Enterprise Linux 4.x, 5.x, and 6.1

●	SUSE Linux Enterprise Server 10.x, 11, and 12

■	An application compatible with components that were built using g++ GNU project C++ Compiler version 3.4.6 and the Linux native pthread threading model (Linuxthreads).

NOTE: All drivers are supported on Linux except for the Informix driver.

Oracle Solaris

■	The following processors are supported:

●	Oracle SPARC

●	x86: Intel

●	x64: Intel and AMD

■	The following operating systems are supported:

●	For Oracle SPARC: Oracle Solaris 8, 9, and 10

●	For x86/x64: Oracle Solaris 10, Oracle Solaris 11

■	For Oracle SPARC: An application compatible with components that were built using Oracle Workshop v. 6 update 2 and the Solaris native (kernel) threading model

■	For x86/x64: An application compatible with components that were built using Oracle C++ 5.8 and the Solaris native (kernel) threading model

NOTE: All of the standard 32-bit UNIX drivers are supported on Solaris SPARC. For x86, the following drivers are supported:

DataDirect Connect for ODBC drivers	■ DB2 Wire Protocol ■ MySQL Wire Protocol ■ Oracle Wire Protocol ■ PostgreSQL Wire Protocol ■ SQL Server Wire Protocol ■ Sybase Wire Protocol ■ SQL Server Legacy Wire Protocol
DataDirect Connect XE for ODBC drivers	■ Salesforce ■ Sybase IQ Wire Protocol

64-Bit Drivers

All required network software that is supplied by your database system vendors must be 64-bit compliant.

■	For the Salesforce driver: A 64-bit Java Virtual Machine (JVM), J2SE 5 or higher, is required. Also, you must set the library path environment variable of your operating system to the directory containing your JVM’s libjvm.so [sl | a] file and that directory’s parent directory.

■	The library path environment variable is:

●	LD_LIBRARY_PATH on Linux, HP-UX Itanium, and Oracle Solaris

●	LIBPATH on AIX

AIX

■	IBM POWER Processor

■	AIX 5L operating system, version version 5.3 fixpack 5 and higher, 6.1, and 7.1

■	An application compatible with components that were built using Visual Age C++ version 6.0.0.0 and the AIX native threading model

NOTE FOR SALESFORCE USERS: When compiling an application on AIX for use with the driver for Salesforce, you must not use the -brtl option.

HP-UX

■	Intel Itanium II (IPF) processor

■	HP-UX IPF 11i operating system, Versions 2 and 3 (B.11.23 and B.11.31)

■	HP aC++ v. 5.36 and the HP-UX 11 native (kernel) threading model (posix draft 10 threads)

NOTE: The following drivers are supported on IPF:

DataDirect Connect64 for ODBC drivers	■ DB2 Wire Protocol ■ Informix Wire Protocol ■ MySQL Wire Protocol ■ Oracle Wire Protocol ■ PostgreSQL Wire Protocol ■ Progress OpenEdge Wire Protocol ■ SQL Server Wire Protocol ■ Sybase Wire Protocol ■ Oracle ■ SQL Server Legacy Wire Protocol
DataDirect Connect64 XE for ODBC drivers	■ Greenplum Wire Protocol ■ Salesforce ■ Sybase IQ Wire Protocol ■ Teradata

NOTES FOR SALESFORCE:

■	Do not link with the –lc linker option.

■	Set the LD_PRELOAD environment variable to the libjvm.so of your JVM installation.

Linux

■	The following processors are supported:

●	Intel Itanium II (IPF)

●	x64: Intel and AMD

■	The following operating systems are supported:

●	For Itanium II: Red Hat Enterprise Linux AS, ES, and WS versions 4.x and 5.x

●	For x64: Red Hat Enterprise Linux AS, ES, and WS version 4.x, 5.x, 6.0, and 6.1

NOTE: The Oracle (client) driver is not supported on the Red Hat x64 operating system.

●	For x64: SUSE Linux Enterprise Server 10.x, 11, and 12

■	For Itanium II: an application compatible with components that were built using g++ GNU project C++ Compiler version 3.3.2 and the Linux native pthread threading model (Linuxthreads)

■	For x64: an application compatible with components that were built using g++ GNU project C++ Compiler version 3.4 and the Linux native pthread threading model (Linuxthreads)

NOTE: The Salesforce Driver and the Driver for Teradata are not supported on Linux Itanium. II.

Oracle Solaris

■	The following processors are supported:

●	Oracle SPARC

●	x64: Intel and AMD

■	The following operating systems are supported:

●	For Oracle SPARC: Oracle Solaris 8, 9, and 10

●	For x64: Oracle Solaris 10 and Oracle Solaris 11 Express

■	For Oracle SPARC: An application compatible with components that were built using Oracle Workshop v. 6 update 2 and the Solaris native (kernel) threading model

■	For x64: An application compatible with components that were built using Oracle C++ Compiler version 5.8 and the Solaris native (kernel) threading model

NOTE: All of the standard 32-bit UNIX drivers are supported on Solaris SPARC. For x64,The following drivers are supported for Oracle Solaris:

DataDirect Connect for ODBC drivers	■ DB2 Wire Protocol ■ MySQL Wire Protocol ■ Oracle Wire Protocol ■ PostgreSQL Wire Protocol ■ SQL Server Wire Protocol ■ Sybase Wire Protocol ■ SQL Server Legacy Wire Protocol
DataDirect Connect XE for ODBC drivers	■ Greenplum Wire Protocol ■ Salesforce ■ Sybase IQ Wire Protocol

AIX

If you are building 64-bit binaries, you must pass the define ODBC64. Demoodbc provides an example of this. See the installed file demoodbc.txt and “The demoodbc Application” for details.

You must also include the correct compiler switches if you are building 64-bit binaries. For example, to build demoodbc, you would use:

xlC_r –DODBC64 -q64 -qlonglong -qlongdouble -qvftable -o demoodbc

  -I../include demoodbc.c -L../lib -lc_r -lC_r -lodbc

HP-UX 11 aCC

The ODBC drivers require certain runtime library patches. The patch numbers are listed in the readme file for your product. HP-UX patches are publicly available from the HP Web site www.hp.com.

HP updates the patch database regularly; therefore, the patch numbers in the readme file may be superseded by newer versions. If you search for the specified patch on an HP site and receive a message that the patch has been superseded, download and install the replacement patch.

If you are building 64-bit binaries, you must pass the define ODBC64. Demoodbc provides an example of this. See the installed file demoodbc.txt and “The demoodbc Application” for details. You must also include the +DD64 compiler switch if you are building 64-bit binaries. For example, to build demoodbc, you would use:

aCC -Wl,+s +DD64 -DODBC64 -o demoodbc -I../include demoodbc.c -L../lib -lodbc

Linux

If you are building 64-bit binaries, you must pass the define ODBC64. Demoodbc provides an example of this. See the installed file demoodbc.txt and “The demoodbc Application” for details.

You must also include the correct compiler switches if you are building 64-bit binaries. For example, to build demoodbc, you would use:

g++ -o demoodbc -DODBC64 -I../include demoodbc.c -L../lib -lodbc -lodbcinst

  -lc

Oracle Solaris

If you are building 64-bit binaries, you must pass the define ODBC64. Demoodbc provides an example of this. See the installed file demoodbc.txt and “The demoodbc Application” for details.

You must also include the -xarch=v9 compiler switch if you are building 64-bit binaries. For example, to build demoodbc, you would use:

CC -mt –DODBC64 -xarch=v9 -o demoodbc -I../include demoodbc.c -L../lib -lodbc

  –lCrun

Setup of the Environment and the Drivers

On UNIX and Linux, several environment variables and the system information file must be configured before the drivers can be used. See Chapter 1 “Quick Start Connect” for a brief description of these variables and information about using the DataDirect ODBC Data Source Administrator for Linux. See the individual driver chapters for details about driver configuration. See Chapter 4 “Configuring the Product on UNIX/Linux” for complete information about using the drivers on UNIX and Linux.

Driver Names

The drivers are ODBC API-compliant dynamic link libraries, referred to in UNIX and Linux as shared objects. The prefix for all 32-bit driver file names is iv. The prefix for all 64-bit driver file names is dd. The driver file names are lowercase and the extension is .so, the standard form for a shared object. For example, the 32-bit DB2 Wire Protocol driver file name is ivdb2nn.so, where nn is the revision number of the driver. For drivers on HP-UX PA-RISC only, the extension is .sl, for example, ivdb2nn.sl.

Refer to the readme file shipped with your DataDirect product for the file name of each driver.