DB2 Version 10.1 for Linux, UNIX, and Windows

IBM Data Server Driver restrictions

Application deployment can take advantage of IBM® Data Server Driver Package. However, certain restrictions apply.

The following restrictions apply to IBM Data Server Driver Package:
  • You cannot install any other database product in the same path with the IBM Data Server Driver Package.
  • On Windows operating systems, you can install a maximum of 16 copies of IBM Data Server Driver Package.
  • To connect to DB2® for z/OS® or DB2 for i server, you must register a DB2 Connect™ license key. (Retrieve the license file from your Passport Advantage® distribution, for example db2conpe.lic, and then copy the license file to the license directory under the directory where the driver was installed.)
  • XA connections against DB2 for z/OS server are supported. However, XA connections against DB2 for i server are not supported.
  • If you use the db2dsdriver.cfg configuration file to specify aliases, the following entries must contain a value:
    • <dsncollection> entries (alias, name, host, and port)
    • <database> entries (name, host, port).
  • The CLI/ODBC configuration keyword DBNAME is not supported.
  • The CLI LOAD utility statement attribute, sql_attr_use_load_api, is not supported.
  • IBM Data Server Driver package is supported only for DB2 JDBC type 4 driver.
  • The CLIENT type authentication is not supported with IBM Data Server Driver Package or IBM Data Server Driver for ODBC and CLI. The CLIENT type authentication type is ignored if specified.
Start of change
  • There is a 32-bit version and a 64-bit version of the IBM Data Server Driver Package, however, you cannot have both a 32-bit copy and a 64-bit copy of the software installed at the same time.
End of change

Functionality supported with restrictions

  • There is no local database directory. Lightweight Directory Access Protocol (LDAP) is supported, but the LDAP cache is not saved to disk.
  • Runtime support for embedded SQL is available with the following restrictions:
    • Support is runtime only; there is no PREP or BIND capability.
    • Support is available for DDL and DML SQL statements that are called from EXEC SQL or cursors.
    • Start of changeWhen reading the db2dsdriver.cfg configuration file, embedded SQL applications can access connection information (for example, database name, host name, and port number), automatic client reroute (ACR) related parameters, workload balancing (WLB) related parameters, connection parameters, and listed communication-related parameters from the database section:
      • ReceiveTimeout
      • ConnectionTimeout
      • tcpipConnectTimeout
      • MemberConnectTimeout
      • keepAliveTimeOut
      • CommProtocol
      • Authentication
      • SSLClientLabel
      • TargetPrincipal
      • SecurityTransportMode
      • SSLclientkeystoredb
      • SSLclientkeystash
      • SSLClientKeystoredbPassword
      End of change
    • The following APIs are not supported:
      • APIs for loading (db2Load and db2LoadQuery), exporting (db2Export), and importing (db2Import) data.
      • API for getting the current user authorities (sqluadau).
      • API for forcing users and applications off the system (sqlefrce).
  • Executing an embedded compound statement with substatements is not supported.

Functionality not supported

  • DB2 Command Line Processor (CLP)
  • Administrative APIs
  • Installation program
  • Visual Explain (VE) tool
  • Optimization Service Center (OSC) tool
  • The CLIENT type authentication is not supported by the IBM Data Server Driver for ODBC and CLI and by the IBM Data Server Driver Package.
  • The MAP file support as used in DCS directory is not supported with SQLCODEMAP db2dsdriver.cfg, db2cli.ini, connection string keyword, and SQL_ATTR_SQLCODEMAP connection attribute.
Related concepts:
IBM data server client and driver types