The JDBC driver requirements
vary by database management system, whether for EGL debug time or run time:
- DB2® UDB
The DB2 Universal
driver is compatible with EGL, but the related App driver is not compatible;
specifically, the App driver cannot process an EGL open or get statement
that includes the option forUpdate.
IBM® recommends that you not use the Net
driver at all.
If you are running J2EE applications in WebSphere® Application
Server v6.x, you need DB2 version 8.1.6 or higher. If you are running those
applications in WebSphere v5.x
Test Environment, you need DB2 version 8.1.3 or higher.
- Informix®
- The minimum acceptable Informix JDBC driver is 2.21.JC6. This driver level
does not comply with JDBC 3.0 and therefore does not support the hold option
in the EGL open statement. An Informix JDBC
3.0-compliant driver may now be available and should support the hold option.
- Oracle
- The JDBC driver that is packaged with Oracle 10i is acceptable.
The following rules apply to any JDBC driver used with EGL:
- The driver must support JDBC 2.0 or higher
- The value java.sql.ResultSet.CONCUR_UPDATABLE must be allowed in these
contexts:
- As the second argument to java.sql.Connection.createStatement(int,int)
- As the third argument to java.sql.Connection.prepareStatement(String,int,int)
and java.sql.Connection.prepareCall(String,int,int)
- If you wish to support the hold option in the EGL open statement,
the driver must support JDBC 3.0, and the value java.sql.ResultSet.HOLD_CURSORS_OVER_COMMIT
must be allowed in these contexts:
- As the third argument to java.sql.Connection.createStatement(int,int,int)
- As the fourth argument to java.sql.Connection.prepareStatement(String,int,int,int)
and java.sql.Connection.prepareCall(String,int,int,int)
For any database management system, JDBC drivers from third- or fourth-party
vendors are acceptable.