4700531

On Solaris, an ORACLE JDBC driver error occurs.

This new Java Database Connectivity (JDBC) driver is for Oracle (R) working with JDK1.4. The problem is caused by a combination of the Oracle 9.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.

4707531

On Solaris, accessing an Oracle 9.1 database with an Oracle 9.2 Client might cause data corruption.

If you use an Oracle (R) 9.2 client to access an Oracle 9.1 database, data corruption might occur when a number column follows a timestamp column. 

The problem might be caused by using the ojdbc14.jar file with an Oracle 9.1 database. Applying the patch might assist in addressing the situation on Solaris 32-bit machines, running an Oracle 9.1 database. This JDBC driver is for Oracle working with JDK 1.4.

Solution

Obtain the patch that Oracle might make available from the Oracle web site for Bug 2199718 and apply it to your server. 

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 in its parameter (init.ora) file.

3. Use the ojdbc14.jar file.

4. Configure the Sun Java System 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 Sun Java System Application Server is started in. For example, add them to the asenv.conf file and ensure they are exported.

5022904

Sun Java System Application Server has number of connections growing after idle time out with DB2 Type 2 Driver

Scenario: When the DB2 database is configured with the wrong datasource class, Sun Java System Application Server will run out of connections in the connection pool as the connections are not closed properly.

Solution

To avoid this problem, the DB2 Type 2 driver must be configured properly. These examples use the default DB2 client folder /opt/IBM.

1. Install a DB2 Client on the machine which hosts Sun Java System Application Server, with a database alias to the DB2 Server.

2. Modify the startserv script of the application server instance to set the DB2 environment. Add the following lines to the application server instance’s start script:

   DB2DIR=/opt/IBM/db2/V8.1
   export DB2DIR
   DB2INSTANCE=db2tmp
   export DB2INSTANCE

3. Because the client is owned by a user with a password, add these values to the connection pool:

   user: db2inst1
   password: db2inst1
   databaseName: sample2
   dataSourceName com.ibm.db2.jcc.DB2SimpleDataSource

4. Modify the Class Path to have the following values:

   /opt/IBM/db2/V8.1/java/db2jcc.jar
   /opt/IBM/db2/V8.1/java/db2jcc_license_cu.jar
   /opt/IBM/db2/V8.1/java/db2jcc_license_cisuz.jar
   /opt/IBM/db2/V8.1/java/db2java.zip