This section discusses supported third-party drivers. Using one of these supported drivers is recommended.
Additional drivers are supported but not recommended. For a list of these drivers, see Section 13.5, Supported Third-Party JDBC Drivers (Not Recommended).
The following table summarizes third-party JDBC driver features:
Table 13-3 Third-Party JDBC Driver Features
The following table lists URL syntaxes for supported third-party JDBC drivers:
Table 13-4 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 13-5 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 13-6 IBM DB2 Driver: Type 4
Unlike the type 3 driver, the type 4 driver has only a minimal set of defined error codes. This absence inhibits the JDBC driver’s ability to distinguish between connectivity, retry, authentication, and fatal error conditions.
The IBM DB2 driver is backward compatible. However, it doesn’t work with database version 7. Database server updates are frequent. Driver updates are infrequent.
The IBM DB2 driver supports a variety of authentication security mechanisms but does not support encrypted transport.
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 these can be time consuming 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 13-7 Informix JDBC Driver
The Informix driver is backward compatible. Database server updates and driver updates are infrequent.
The Informix driver does not support encrypted transport.
The following table lists driver parameters that must be explicitly set for the JDBC driver to interoperate with the Informix driver against ANSI-compliant databases.
Table 13-8 Driver Settings for ANSI-Compliant Databases
|
Display Name |
Tag Name |
Value |
|---|---|---|
|
Supports schemas in metadata retrieval? |
supports-schemas-in-metadata-retrieval |
false |
|
Force username case: |
force-username-case See Force Username Case. |
upper |
The following table lists driver compatibility parameters that the JDBC driver implicitly sets at runtime. Do not override these settings.
Schema names cannot be used to retrieve metadata against an ANSI-compliant database. Set the driver compatibility parameter Supports Schemas in Metadata Retrieval? to Boolean False. The database objects available for metadata retrieval are those visible to the database user who authenticated to the database. Schema qualifiers cannot be used to identify database objects. Therefore, to avoid naming collisions (such as owner1.table1, owner2.table1), give the database authentication user only SELECT privileges on objects being synchronized.
When used against ANSI-compliant databases, usernames must be in uppercase. Set the driver compatibility parameter Force Username Case to upper.
Table 13-10 jTDS Driver Settings
The jTDS JDBC driver does not support views or stored procedures. Novell recommends that you use the Microsoft 2000 JDBC driver when Subscribing to views.
The jTDS driver works with all versions of Microsoft SQL Server. It also supports all versions of Sybase ASE, but it hasn’t been tested by Novell against that database server yet. Driver updates are infrequent.
The jTDS driver supports encrypted transport.
Delimit URL properties by using a semicolon (;).
The following table lists values for the domain URL property for the jTDS driver.
Table 13-11 Values for the Domain URL Property
The following table lists values for the SSL URL property for the jTDS driver.
Table 13-12 Values for the SSL URL Property
Table 13-13 MySQL Connector/J JDBC Driver Settings
The Connector/J driver is backward compatible. Database server updates are frequent. Driver updates are infrequent.
The Connector/J driver supports JSSE (Java Secure Sockets Extension) SSL-encrypted transport.
The following table lists driver parameters that you must set so that the JDBC driver can interoperate with the Connector/J driver against MyISAM tables.
Table 13-15 Oracle Thin Client Settings
The Thin Client driver is backward compatible. Database server updates and driver updates are infrequent.
Oracle releases thin client drivers for various JVMs. Even though all of them work with this product, we recommend that you use the 1.4 version.
The Thin Client driver supports Oracle Advanced Security encrypted transport.
The following table lists driver compatibility parameters that the JDBC driver implicitly sets at runtime. Do not explicitly override these settings.
The following table lists important connection properties for this driver.
Table 13-17 Oracle Thin Client: Connection Properties
High CPU utilization triggered by execution of embedded SQL statements:
The most common problem experienced with this driver is high CPU utilitization. As a result, this driver always indicates that more results are available from calls to method java.sql.Statement.execute(String stmt), which can lead to an infinite loop condition. This condition occurs only if all the following happen:
A value other than single, no, or one in the driver compatibility parameter Number of Returned Result Sets is being executed.
An embedded SQL statement is being executed.
The type of statement is not explicitly specified.
To avoid the conditions that produce high CPU utilization:
Do not explicitly set this parameter. Defer to the dynamic default value.
Always place a jdbc:type attribute on embedded <jdbc:statement> elements.
NOTE:The jdbc namespace prefix must map to urn:dirxml:jdbc.
Can’t retrieve synonym column metadata.
The connection property includeSynonyms must be set to true.
Can’t see synonym table primary key constraint.
The only known solution to this problem is to use a view.
Table 13-18 Oracle OCI JDBC Driver Settings
|
Supported Database Versions |
8i (Release 3 (8.1.7) or later), 9i (Release 2 (9.2.0.1) or later), 10g (Release 1 (10.0.2.1) or later), 11g (Release 1 (11.1) or later) |
|
Class Name |
oracle.jdbc.driver.OracleDriver |
|
Type |
2 |
|
URL Syntax |
jdbc:oracle:oci8:@tns-name |
|
Download Instructions |
The SQLNet infrastructure is the main requirement for OCI. SQLNet can run on any platform that Oracle supports, not just Linux. For Linux, register for free and download the following:
|
|
Filenames |
|
|
Documentation URLs |
You can install SQLNet by doing either of the following:
Use the Instant Client, which bypasses unneeded components of the full version.
Download the full package from Oracle.
If the database is running on the same server as Identity Manager, you don’t need to install SQLNet because SQLNet comes as standard on the database server.
The Oracle OCI driver is essentially the same as the Thin Client driver. See Section 13.4.8, Oracle Thin Client JDBC Driver. The OCI client differs in the following ways:
The OCI Client supports clustering, failover, and high availability.
The OCI Client has additional security options.
For information on setting up the Oracle OCI Client, see Section M.0, Setting Up an OCI Client on Linux.
Table 13-19 PostgreSQL JDBC Driver Settings
|
Supported Database Versions |
7.4.6 or later, 8.0 or later |
|
Class Name |
org.postgresql.Driver |
|
Type |
4 |
|
URL Syntax |
jdbc:postgresql://ip-address:5432/database-name |
|
Download Instructions |
|
|
Documentation URLs |
The filename of the PostgreSQL varies by database version.
The latest builds of the PostgreSQL driver are backward compatible through server version 7.2. Database server updates and driver updates are frequent.
The PostgreSQL driver supports SSL-encrypted transport for JDBC 3 driver versions.
Table 13-20 Sybase Adaptive Server Enterprise Driver Settings
* For JDBC 3 (Java 1.4) versions and later.
The Adaptive Server driver is backward compatible. Database server updates and driver updates are infrequent.
The Adaptive Server driver supports SSL-encrypted transport. To enable SSL encryption, you must specify a custom socket implementation via the SYBSOCKET_FACTORY connection property. For additional information on how to set connection properties, see Connection Properties.
The SYBSOCKET_FACTORY property can be used to specify the class name of a custom socket implementation that supports encrypted transport.