IBM Support

PI92626: BLOCK THE CALLING OF SEVERAL NEW METHODS ON ORACLECONNECTION IN THE OJDBC8 12.2 DRIVER THAT ARE UNSAFE.

Subscribe

You can track all active APARs for this component.

 

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

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021