APAR status |
Closed with unknown close code.
| Error description
Setting WebSphere's preparedStatementCache to a non-zero value
causes exceptions. Local fix
Set WebSphere's prepared statement cache to zero.
Oracle's JDBC driver has it's own PreparedStatementCache, which
may be used if so desired. Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* prepared statements in Oracle with the *
* NOWAIT keyword. *
****************************************************************
* PROBLEM DESCRIPTION: When running an Oracle prepared *
* statement with the NOWAIT keyword, an *
* SQL Exception may be thrown with the *
* message text "Unsufficient number of *
* parameter were set before execution" *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When running an Oracle prepared statement with the NOWAIT
keyword, if the first execute fails because of locks, and
the statement is retried successfully without re-preparing,
the statement was cached incorrectly, resulting in failures
each time the cached statement was executed. Problem conclusion
Fixed WebSphere prepared statement caching to appropriately
handle this scenario. Temporary fixComments
APAR information | APAR number | PQ61408 | Reported component name | WEBSPHERE AE AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED | PE | NoPE | HIPER | NoHIPER | Submitted date | 2003-03-03 | Closed date | 2003-03-03 | Last modified date | 2003-03-17 |
APAR is sysrouted FROM one or more of the following: PQ66566
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:PQ66566
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WEBSPHERE AE AI | Fixed component ID | 5648C8400 |
Applicable component levels | R400 PSY | UP |
|