Fixes are available
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
If the customer uses any of the methods which are being blocked, they could see unexplained exceptions or data integrity issues.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * with the Oracle JDBC Driver * **************************************************************** * PROBLEM DESCRIPTION: In the Oracle 12.2 ojdbc8.jar JDBC * * driver, several methods were added * * which * * should not be used with WebSphere. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the Oracle 12.2 ojdbc8.jar JDBC driver, several methods were added to OracleConnection which should not be used with WebSphere Application Server, as they could lead to possible exceptions or data integrity issues. These methods have been added to the forbidden method list, so they cannot be called on OracleConnection when accessed through the JDBC 4.0 wrapper pattern. The new methods which cannot be used are: attachServerConnection, beginRequest, closeLogicalConnection, createConnectionBuilder, createPooledConnectionBuilder, createXAConnectionBuilder, detachServerConnection, endRequest, setShardingKeyIfValid, and setShardingKey.
Problem conclusion
The methods were added to the forbidden methods list so they cannot be accessed through the JDBC 4.0 wrapper pattern. The fix for this APAR is currently targeted for inclusion in WebSphere traditional fix packs 8.5.5.14 and 9.0.0.7 and WebSphe Liberty 18.0.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI92626
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-19
Closed date
2018-01-29
Last modified date
2018-09-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022