13.4 Supported Third-Party JDBC Drivers (Recommended)

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).

13.4.1 Third-Party JDBC Driver Features

The following table summarizes third-party JDBC driver features:

Table 13-3 Third-Party JDBC Driver Features

Driver

Supports Encrypted Transport?

Supports Retrieval of Auto-Generated Keys?

IBM DB2 UDB Type 4

No

No

Informix

No

No

MySQL Connector/J

Yes

Yes

jTDS

Yes

Yes

Oracle Thin Client

Yes

No

Oracle OCI

Yes

No

PostgreSQL

Yes, for JDBC 3 (Java 1.4) versions and later

No

Sybase jConnect*

Yes

No

13.4.2 JDBC URL Syntaxes

The following table lists URL syntaxes for supported third-party JDBC drivers:

Table 13-4 URL Syntaxes

Third-Party JDBC Driver

JDBC URL Syntax

IBM DB2 UDB Type 4, Universal

jdbc:db2://ip-address:50000/database-name

Informix

jdbc:informix-sqli://ip-address:1526/database-name:informixserver=server-id

jTDS

jdbc:jtds:sqlserver://ip-address/database-name

MySQL Connector/J

jdbc:mysql://ip-address:3306/database-name

Oracle OCI

jdbc:oracle:oci8:@tns-name

Oracle Thin Client

jdbc:oracle:thin:@ip-address:1521:sid

PostgreSQL

jdbc:postgresql://ip-address:5432/database-name

Sybase jConnect

jdbc:sybase:Tds:ip-address:2048/database-name

This information is used in conjunction with the Authentication Context parameter. For information on this parameter, see Authentication Context.

13.4.3 JDBC Driver Class Names

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

Third-Party JDBC Driver

Class Name

IBM DB2 UDB Type 4, Universal

com.ibm.db2.jcc.DB2Driver

Informix

com.informix.jdbc.IfxDriver

jTDS

net.sourceforge.jtds.jdbc.Driver

MySQL Connector/J

org.gjt.mm.mysql.Driver

Oracle OCI

oracle.jdbc.driver.OracleDriver

Oracle Thin Client

oracle.jdbc.driver.OracleDriver

PostgreSQL

org.postgresql.Driver

Sybase jConnect 5.5

com.sybase.jdbc2.jdbc.SybDriver

Sybase jConnect 6.05

com.sybase.jdbc3.jdbc.SybDriver

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.

13.4.4 IBM DB2 Universal Database Type 4 JDBC Driver

Driver Information

Table 13-6 IBM DB2 Driver: Type 4

Supported Database Versions

IBM DB2 7.2 or later, 8.1 or later, 9.0 or later

Class Name

com.ibm.db2.jcc.DB2Driver

Type

4

URL Syntax

jdbc:db2://ip-address:50000/database-name

Download Instructions

Download as part of the latest FixPack (recommended).

IBM Support & Downloads

or

Copy the file from the database server.

file:///database-installation-directory/java

Filename

db2jcc.jar, db2jcc_license_cu.jar, db2jcc_javax.jar (optional)

Documentation URLs

DB2 Information Center

DB2 Universal JDBC Driver

Security under the DB2 Universal JDBC Driver

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.

Compatibility

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.

Security

The IBM DB2 driver supports a variety of authentication security mechanisms but does not support encrypted transport.

Known Issues

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.

13.4.5 Informix JDBC Driver

Driver Information

Table 13-7 Informix JDBC Driver

Supported Database Versions

Dynamic Server 9.40 or later, 10.0 or later

Class Name

com.informix.jdbc.IfxDriver

Type

4

URL Syntax

jdbc:informix-sqli://ip-address:1526/database-name:informixserver=server-id

Download Instructions

Download URL

Filenames (7, 9)

ifxjdbc.jar, ifxjdbcx.jar (optional)

Filenames (10)

jdbc.jar, jdbcx.jar (optional)

Documentation URLs

Informix Information Center

Informix JDBC Driver

Compatibility

The Informix driver is backward compatible. Database server updates and driver updates are infrequent.

Security

The Informix driver does not support encrypted transport.

Required Parameter Settings for ANSI-Compliant Databases

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

See Supports Schemas in Metadata Retrieval?.

false

Force username case:

force-username-case

See Force Username Case.

upper

Dynamic Parameter Defaults

The following table lists driver compatibility parameters that the JDBC driver implicitly sets at runtime. Do not override these settings.

Table 13-9 Informix JDBC Settings Not to Override

Display Name

Tag Name

Value

Function return method:

function-return-method

See Function Return Method.

result set

Known Issues

  • 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.

13.4.6 jTDS JDBC Driver

Driver Information

Table 13-10 jTDS Driver Settings

Supported Database Versions:

Microsoft SQL Server 7.5, Service Pack 4 or later, 2000 (8) Service Pack 3a or later, 2005 (9) Service Pack 1 or later, 2008 (10), Sybase Adaptive Server Enterprise (ASE) 12.5 or later, Sybase Adaptive Server Enterprise (ASE) 15.0 or later

Class Name

net.sourceforge.jtds.jdbc.Driver

Type

4 (2 if NTLM or SSO authentication is enabled)

URL Syntax

jdbc:jtds:sqlserver://ip-address/database-name

jdbc:jtds:sybase://ip-address/database-name

Download Instructions

The jTDS Project

Filenames

jtds-<version>.jar

Limitations

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.

Compatibility

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.

Security

The jTDS driver supports encrypted transport.

URL Properties

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

Legal Value

Description

<any-domain-name>

When a domain name is specified, either NTLM or SSO authentication can be used. NTLM authentication is selected when a username and password are supplied. SSO authentication is selected when a username and password are not supplied.

<no-value>

JDBC authentication is used.

The following table lists values for the SSL URL property for the jTDS driver.

Table 13-12 Values for the SSL URL Property

Legal Value

Description

off

SSL is not used. This is the default.

request

SSL is used if the server supports it.

require

SSL is required. An exception is thrown if the server doesn’t support it.

authenticate

SSL is required. An exception is thrown if the server doesn’t support it. In addition, the server’s certificate must be signed by a trusted certificate authority.

13.4.7 MySQL Connector/J JDBC Driver

Driver Information

Table 13-13 MySQL Connector/J JDBC Driver Settings

Supported Database Versions

3.23.58 or later, 4.1 or later, 5.0.20 or later

Class Name

org.gjt.mm.mysql.Driver

Type

4

URL Syntax

jdbc:mysql://ip-address:3306/database-name

Download Instructions

Download and extract. The jar file is located in the extract-dir/mysql-connector-java-version directory.

MySQL Connector/J

Filename

mysql-connector-java-version-bin.jar

Documentation URLs

MySQL Connector/J Documentation

Connecting Over SSL

Also see Generation/Retrieval Method (Table-Global).

Compatibility

The Connector/J driver is backward compatible. Database server updates are frequent. Driver updates are infrequent.

Security

The Connector/J driver supports JSSE (Java Secure Sockets Extension) SSL-encrypted transport.

Required Parameter Settings for MyISAM Tables

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-14 Settings for MyISAM Tables

Display Name

Tag Name

Value

Use manual transactions?

use-manual-transactions

false

13.4.8 Oracle Thin Client JDBC Driver

Driver Information

Table 13-15 Oracle Thin Client 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

4

URL Syntax

jdbc:oracle:thin:@ip-address:1521:sid

Download Instructions

Register for free and download.

Oracle Technology Network

Filenames

  • ojdbc14.jar, orail8n.jar (optional)

Filenames for different JVM* versions

Documentation URLs

Oracle Advanced Security

JDBC FAQ

Compatibility

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.

Security

The Thin Client driver supports Oracle Advanced Security encrypted transport.

Dynamic Parameter Defaults

The following table lists driver compatibility parameters that the JDBC driver implicitly sets at runtime. Do not explicitly override these settings.

Table 13-16 Oracle Thin Client Settings Not to Override

Display Name

Tag Name

Value

Number of returned result sets:

handle-stmt-results

single

Connection Properties

The following table lists important connection properties for this driver.

Table 13-17 Oracle Thin Client: Connection Properties

Property

Significance

includeSynonyms

If the value of this property is true, synonym column metadata is available.

ORACLE.NET.ENCRYPTION_CLIENT

Defines the level of security that the client wants to negotiate with the server.

ORACLE.NET.ENCRYPTION_TYPES_CLIENT

Defines the encryption algorithm to be used.

ORACLE.NET.CRYPTO_CHECKSUM_CLIENT

Defines the level of security that it wants to negotiate with the server for data integrity.

ORACLE.NET.CRYPTO_CHEKSUM_TYPES_CLIENT

Defines the data integrity algorithm to be used.

Known Issues

  • 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.

13.4.9 Oracle OCI JDBC Driver

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

  • ojdbc14.jar, orail8n.jar (optional)

Filenames for different JVM versions

Documentation URLs

Oracle Call Interface

OCI FAQ

Oracle Advanced Security

Instant Client

Instant Client

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.

13.4.10 PostgreSQL JDBC Driver

Driver Information

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

JDBC Driver Download

Documentation URLs

JDBC Driver Documentation

Using SSL

The filename of the PostgreSQL varies by database version.

Compatibility

The latest builds of the PostgreSQL driver are backward compatible through server version 7.2. Database server updates and driver updates are frequent.

Security

The PostgreSQL driver supports SSL-encrypted transport for JDBC 3 driver versions.

13.4.11 Sybase Adaptive Server Enterprise JConnect JDBC Driver

Driver Information

Table 13-20 Sybase Adaptive Server Enterprise Driver Settings

Supported Database Versions

Adaptive Server* Enterprise 12..5 or later, 15.0 or later

Class Name

com.sybase.jdbc2.jdbc.SybDriver (for jconn2.jar) com.sybase.jdbc3.jdbc.SybDriver (for jconn3.jar)

Type

4

URL Syntax

jdbc:sybase:Tds:ip-address:2048/database-name

Download Instructions

Sybase Downloads

Filenames

jconn2.jar or jconn3.jar

Documentation URLs

jConnect Documentation

* For JDBC 3 (Java 1.4) versions and later.

Compatibility

The Adaptive Server driver is backward compatible. Database server updates and driver updates are infrequent.

Security

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.

Connection Properties

The SYBSOCKET_FACTORY property can be used to specify the class name of a custom socket implementation that supports encrypted transport.