2082209, 5022904

DB2 Server has connection growing after idle time-out with DB2 Type II driver

Solution

Set the SteadyPoolSize and MaxPoolSize to the same number, and in addition, set the Idle Connection timeout also to 0 (zero). This will disable the timing-out of idle connections and the user will have the full set of connections available.

4700531

On Solaris, an Oracle JDBC driver error occurs with JDK 1.4.

This affects the new JDBC driver for Oracle (R) when working with JDK1.4. The problem is caused by a combination of the Oracle 9.0.1 database and ojdbc14.jar. Applying the patch will fix the problem on Solaris 32-bit machine, running an Oracle 9.0.1.3 database. 

Solution

Obtain and apply the patch to your server from the Oracle Web site for Bug 2199718. Perform the following steps: 

1. Go to the Oracle Web site.

2. Click the ’patches’ button.

3. Type 2199718 in the patch number field.

4. Click the 32-bit Solaris OS patch.Go to Metalink.oracle.com.

5. Click patches.

6. Under patch number, enter 2199718.

7. Click the 32 bit Solaris OS patch.

4991065

Oracle JDBC drivers must be configured properly to be compliant with J2EE 1.3.

Solution

Use the following configuration for Type 2 and Type 4 drivers: 

1. Use the JDBC from 9.2.0.3 or later.

2. The Oracle database needs to have compatible=9.0.0.0.0 or higher in its parameter (init.ora) file.

3. Use the ojdbc14.jar file.

4. Configure the Application Server to define the following JVM property:

   -Doracle.jdbc.J2EE13Compliant=true

In addition, for Type-2 drivers both the ORACLE_HOME and LD_LIBRARY_PATH (which must include $ORACLE_HOME/lib) need to be defined in the environment that the Application Server is started in. For example, add them to the asenv.conf file and ensure they are exported.