APAR status |
Closed as program error.
| Error description
Customer's jdbc driver is Oracle 8.17- the error message below
is incorrect, and it leads to "No suitable driver" error later:
.
[02.03.14 14:33:16:449 EST] e4ceb3 TranRecoveryS <
getRecoveryData
[02.03.14 14:33:16:450 EST] e4ceb3 JTSXA D
numResourcesToRecover: 2
[02.03.14 14:33:16:465 EST] e4ceb3 JTSXA D recovering:is incorrect, and it leads to "No suitable driver" error later:.[02.03.14 14:33:16:449 EST], e4ceb3 TranRecoveryS
.
com.ibm.ejs.jts.jta.factory.OraJTAXAResourceFactory, sledb:null,
0
[02.03.14 14:33:16:466 EST] e4ceb3 OraJTAXAResou > getXAResource
[02.03.14 14:33:16:466 EST] e4ceb3 OraJTAXAResou D Oracle 8.1.6
JTA
Driver:e4ceb3 JTSXA D recovering:.com.ibm.ejs.jts.jta.factory.OraJTAXAResourceFactory, sledb:null,0[02.03.14 14:33:16:466 EST], e4ceb3 OraJTAXAResou>, getXAResource[02.03.14 14:33:16:466 EST], e4ceb3 OraJTAXAResou D Oracle 8.1.6JTA
... (several lines deleted)
[02.03.14 14:33:16:538 EST] e4ceb3 SharedLogWrit < log
[02.03.14 14:33:16:510 EST] e4ceb3 OraJTAXAResou W Encountered
an error while creating XA connection and XA resource
java.sql.SQLException: No suitable driver
... (several lines deleted)
at
oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleX
ADataSou
rce.java:88) Driver:... (several lines deleted)[02.03.14 14:33:16:538 EST], e4ceb3 SharedLogWrit<, log[02.03.14 14:33:16:510 EST], e4ceb3 OraJTAXAResou W Encounteredan error while creating XA connection and XA resourcejava.sql.SQLException: No suitable driver... (several lines deleted)atoracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:88) Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* Oracle JTA resources. *
****************************************************************
* PROBLEM DESCRIPTION: During recovery of Oracle transactions *
* error message 'No suitable driver' is *
* produced. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During recovery of Oracle resources, WebSphere attempts to
reconstruct an Oracle driver to talk to Oracle, but it
builds the driver incorrectly. As a result, WebSphere is not
able to perform the recovery correctly. Problem conclusion
The code used to construct the Oracle driver will be corrected
to ensure that the driver is built correctly.
This problem does not occur on WebSphere V4. Temporary fix
The temporary fix is available in PQ59204-3.5.5-3.5.6.jar Comments
APAR information | APAR number | PQ59204 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-03-19 | Closed date | 2002-05-09 | Last modified date | 2002-05-09 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|