Failed to switch thread security context w/ Oracle Connection Pooling

When using the getConnection method of a datasource set up on WAS 3.5 on S/390, I receive the following error: IBMConnMgrException: Failed to switch thread security context. In the getConnection method I include the userid and password for the Oracle database, which are different from userid/password used to authenticate to WAS. Could this be causing the problem? Any ideas on how to resolve the error?

Datasource Info:

Name: OracleJDBCis0u

Minimum Number of Connections: 10

Maximum Number of Connections: 80

Wait For Connection Timeout: 30 seconds

Idle Connection Timeout: 120 seconds

In-use Connection Timeout: disabled

Driver: oracle.jdbc.driver.OracleDriver

URL: jdbc:oracle:thin:@servername:1521:is0u

Datasource Name: is0u

Connection Identity From : connspec

NOTE: the real server name has been removed from the URL parameter above.

Environment Info:

WAS 3.5 (SE) installed on S/390 (v2.10)

[1008 byte] By [pwaite1] at [2007-9-26 1:41:51]
# 1
THE DataSource Name (DSN) is different from the SID (Service ID) in Oracle. Please make sure that the last parameter in the URL (is0u) is actually the SID and not the DSN name.
helloanand at 2007-6-29 2:33:58 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 2
In this line you need "servername" to be your hostname.URL: jdbc:oracle:thin:@servername:1521:is0u
swatdba at 2007-6-29 2:33:58 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 3
Yes, the sid name is is0u.
pwaite1 at 2007-6-29 2:33:58 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 4
In our setup servername is hostname. For the purposes of posting here, I replaced the true hostname with "servername" to make it generic. Sorry for any confusion.
pwaite1 at 2007-6-29 2:33:58 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 5

Finally resolved this - according to ibm:

"Check to ensure that the userid and password are defined to MVS

and/or your security package (e.g. RACF). The switch actually sets a security context on the thread so it has to be authenticated before your data base manager even gets the request."

Once the userid/password was added to our security package, we were able to get connections with no problems.

pwaite1 at 2007-6-29 2:33:58 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...