This section identifies drivers that are supported but whose use is discouraged.
The following table summarizes third-party JDBC driver features:
Table 15-21 Third-Party JDBC Driver Features
|
Driver |
Supports Encrypted Transport? |
Supports Retrieval of Auto-Generated Keys? |
|---|---|---|
|
IBM DB2 UDB Type 3 |
No |
No |
|
Microsoft 2000 |
No |
No |
|
Microsoft 2005 |
Yes |
Yes |
* For JDBC 3 (Java 1.4) versions and later.
The following table lists URL syntaxes for supported third-party JDBC drivers:
Table 15-22 URL Syntaxes
This information is used in conjunction with the Authentication Context parameter. For information on this parameter, see Authentication Context.
The following table lists the fully-qualified Java class names of supported third-party JDBC drivers:
Table 15-23 Class Names of Third-Party JDBC Drivers
This information is used in conjunction with the JDBC Driver Class Name parameter. For information on this parameter, see Third-Party JDBC Driver Class Name.
Table 15-24 IBM DB2 Driver: Type 3
IMPORTANT:The type 3 driver was deprecated as of DB2 UDB version 8.
The IBM DB2 driver can best be characterized as version-hypersensitive. It is not compatible across major or minor versions of DB2, including FixPacks. For this reason, we recommend that you use the file installed on the database server.
IMPORTANT:The IBM DB2 driver must be updated on the Identity Manager or Remote Loader server every time the target database is updated, even if only at the FixPack level.
The IBM DB2 driver does not support encrypted transport.
A version mismatch usually results in connectivity-related failures.
The most common problem experienced with the IBM DB2 driver is because of a driver/database version mismatch. The symptom of a version mismatch is connectivity-related failures such as "CLI0601E Invalid statement handle or statement is closed." To remedy the problem, overwrite the db2java.zip file on the Identity Manager or Remote Loader server with the version installed on the database server.
It’s very difficult to diagnose and remedy Java-related errors on the database server.
Numerous error conditions and error-codes can arise when you attempt to install and execute user-defined stored procedures and functions written in Java. Diagnosing them can prove time intensive and frustrating. A log file (db2diag.log on the database server) can often provide additional debugging information. In addition, all error codes are documented and available online.
Table 15-25 Microsoft SQL Server 2000 Driver Settings
NOTE:The filename, URL syntax and classname differ (often subtly) from those of the 2005 driver.
The SQL Server 2000 driver only works with SQL Server 2000. is backward compatible. However, it doesn’t work with database version 7. Database server and driver updates are infrequent.
The SQL Server 2000 driver does not support encrypted transport.
Delimit URL properties by using a semicolon (;).
The following table lists values for the SelectMethod URL property for the SQL Server 2000 driver.
Table 15-26 Values for the SelectMethod URL Property
|
Legal Value |
Description |
|---|---|
|
direct |
The default value. Doesn’t allow for multiple active statements on a single connection |
|
cursor |
Allows for multiple active statements on a single connection |
The following table lists driver compatibility parameters that the Driver for JDBC implicitly sets at runtime. Do not explicitly override these settings.
Table 15-27 SQL Server 2000 Settings Not to Override
|
Display Name |
Tag Name |
Value |
|---|---|---|
|
Reuse Statements? |
reuse-statements |
false |
Can’t start manual transaction because of cloned connections.
An implementation anomaly that doesn’t allow concurrent statements to be active on the same connection causes the most common problem experienced with the SQL Server 2000 driver. Unlike other third-party implementations, the SQL Server 2000 driver can have only one java.sql.Statementobject active at a time on a given connection.
If you attempt to use more than one statement object, the following error is issued: “Can’t start manual transaction mode because there are cloned connections.” This error can occur only if the driver compatibility parameter Reuse Statements? is set to Boolean True. As a best practice, never explicitly set this parameter. Instead, defer to the dynamic default value.
An alternative is to place the delimited property ;SelectMethod=cursor at the end of the URL string. For additional information on this issue, consult the following support articles:
Document 30096 by DataDirect Technologies*
Article 313181 by Microsoft
Association values that contain UNIQUEIDENTIFIER columns are inconsistent between driver versions.
Earlier versions of the SQL Server 2000 driver returned a non-standard java.sql.Types value for native UNIQUEIDENTIFIER columns. To compensate, the Driver for JDBC mapped that non-standard type to the standard type java.sql.Types.BINARY because it best mirrored the native database type, which is a 16-byte value. This mapping results in a Base64-encoded association value.
Later versions of the SQL Server 2000 driver return a standard type java.sql.CHAR. This mapping results in a non-Base64-encoded association value, effectively invalidating all associations generated by using earlier versions of the SQL Server 2000 driver. This change effectively breaks backward compatibility.
The best solution to this problem is to continue using the earlier version of the SQL Server 2000 driver. If you must upgrade, remove all invalidated associations and reassociate all previously-associated objects.
Table 15-28 Microsoft SQL Server 2005 Driver Settings
NOTE:The filename, URL syntax, and classname differ (often subtly) from those of the 2000 driver.
The SQL Server 2005 driver works with only SQL Server 2005. Database server and driver updates are infrequent.
The SQL Server 2005 driver does not support encrypted transport.
Delimit URL properties by using a semicolon (;).
The following table lists values for the integratedSecurity URL property for the SQL Server 2005 driver.