Configuring access to data sources of type 4
For this type of ODBC data sources, you must download the ODBC driver from the data source vendor and perform some configurations for using it but data sources support are not optimized. Currently, this type includes data sources such as IBM® Red Brick® Warehouse, IBM InfoSphere® Classic Federation Server for z/OS® data sources, or any other 3rd party data sources supported to be accessed through its own ODBC driver.
Before you begin
- Federation must be installed on the server that acts as the federated server.
Note: If you configure the system environment variables or modify
the db2dj.ini file, to enable them to be effective you must stop and
restart the federation component.
About this task
Restrictions
- The ODBC wrapper does not support the following functions and
statements:
- Two-phase commit transactions
- LOCK TABLE statements on nicknames
- Features deprecated in ODBC 3.x
- X/Open or SQL/CLI drivers
- Stored procedure nicknames
- Statement-level atomicity enforcement using remote savepoint statements
- WITH HOLD cursors
- For data sources that do not support positioned update and delete operations, positioned UPDATE and DELETE statements and certain searched UPDATE and DELETE statements on a nickname will fail if a unique index on non-nullable columns does not exist on the nickname or its corresponding remote table. The error SQL30090 with the reason code 21 is returned when these statements fail.
- The ODBC wrapper does not support INSERT, UPDATE, or DELETE statements against data sources that restrict the number of active statements for each connection. Consult the documentation for your data source to determine if the data source restricts the number of active statements for each connection. One of the ODBC data sources that this restriction applies to is IBM Red Brick Warehouse.
- The ODBC wrapper does not support operations on tables that contain columns with data types that use driver-specific SQL data type indicators. The type of operations that are not supported included the CREATE NICKNAME and SELECT statements in the pass-through mode. The ODBC wrapper supports only the SQL data type indicators that are defined by the ODBC standard in the Microsoft ODBC Programmer's Reference.
- The ODBC wrapper does not support the following statement with IBM InfoSphere Classic Federation Server for z/OS data sources:
CREATE TABLE - The following datatypes are not supported for use with IBM InfoSphere Classic Federation Server for z/OS data sources:
The data sources that are accessed through the ODBC API are
referred to in this text as ODBC data sources.
- BLOB
- CLOB
- DBCLOB
- CHAR FOR BIT DATA
- VARCHAR FOR BIT DATA
The data sources that are accessed through the ODBC API are referred to in this procedure as ODBC data sources.
Procedure
This procedure applies to IBM InfoSphere Classic Federation Server for z/OS.
Do one
of the following depending on your operating system:
- On Windows, ensure that the node name for the data source is defined as a system DSN. If you used Microsoft ODBC Data Source Administrator to define the DSN, you can use the Control Panel to verify that it is registered as a system DSN.
- On UNIX, configure the ODBC driver.
You might be required to add the data source client library
directory to the DB2LIBPATH environment variable
so that the client libraries load properly. Run the db2set command
to set the DB2LIBPATH environment variable and
specify the installation directory of the data source client library:
db2set DB2LIBPATH="client_library_directory"For 64-bit versions, ensure that you set the DB2LIBPATH environment variable to the 64-bit lib directory.
Examples:
For
the IBM InfoSphere Classic Federation Server for z/OS Version 8.2 client:
db2set DB2LIBPATH="/opt/IBM/DB2IIClassic82/cli/lib"
db2set DB2LIBPATH="/opt/IBM/WSClassic91/cli/lib"
db2set DB2LIBPATH="/opt/IBM/WSClassic95/cli/lib"