Setting up Oracle 817 connection pool with JDBC thin driver and WLS 6.0

[jms]

I am having some problems setting up a connection pool with WLS 6.0 SP1
on Solaris. Because the database is Oracle 8.1.7, I am using Oracle's
thin driver. WLS 6.0 and Oracle are setup on the same host, running
under different user accounts. Oracle SID is sunora81.

Here is what I have done:

1) Added classes12.zip into the CLASSPATH in startWebLogic.sh, so that
it now looks like this:

CLASSPATH=$WL_HOME:$WL_HOME/lib/classes12.zip:$WL_HOME/lib/weblogic_sp.jar:$WL_HOME/lib/weblogic.jar

2) Created a connection pool and datasource through the admin console.
Here is the end-result in the config.xml file:

<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="5"
MaxCapacity="10" Name="Oracle817 on Solaris"
Properties="user=system;password=manager"
TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
TestTableName="all_users"
URL="jdbc:oracle:thin:@pssydsun01.pssyd.powerserve.com.au:1521:sunora81"/>
<JDBCDataSource JNDIName="au.com.powerserve.sunora81.datasource"
Name="Oracle 817 Data Source" PoolName="Oracle817 on Solaris"/>

3) I have also turned on JDBC logging, as shown also in the config.xml file:

<Server JDBCLogFileName="config/mydomain/logs/jdbc.log"

4) Restart WLS

However, I do not get any connections on the pool, nor are there any
errors / warnings / exceptions in weblogic.log and jdbc.log regarding
attempts to make a JDBC connection .... as if the JDBC connection pool
definition is being ignored.

I remember that with WLS 5.1, any mistake in weblogic.properties in
defining the connection pool will actually and therefore preventing any
JDBC connection attempts will make WLS log the errors that it tried but
failed .... but I dont get the same behaviour with WLS 6.0

Any help appreciated,

John