IBM Support

PM73123: RRA SHOULD PROVIDE INFORMATION ABOUT JDBC SPEC LEVEL

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Websphere RRA should provide information about JDBC spec level
    used by JDBC driver.
    for example JDBC 3.0 spec level
                JDBC 4.0 spec level
                JDBC 4.1 spec level
    Presently RRA provides below information, however without
    trace we may not be able to detect what JDBC spec level
    supported by JDBC driver.
    ************************
    [7/20/12 20:40:33:399 UTC] 0000001d InternalGener I
    DSRA8203I:
    Database product name : Microsoft SQL Server
    
    [7/20/12 20:40:33:400 UTC] 0000001d InternalGener I
    DSRA8204I:
    Database product version : 10.00.4279
    
    [7/20/12 20:40:33:401 UTC] 0000001d InternalGener I
    DSRA8205I: JDBC
    driver name  : jTDS Type 4 JDBC Driver for MS SQL Server and
    Sybase
    [7/20/12 20:40:33:401 UTC] 0000001d InternalGener I
    DSRA8206I: JDBC
    driver version  : 1.2.5
    
    [7/20/12 20:40:33:417 UTC] 0000001d WSRdbManagedC W
    DSRA8220W:
    Enablement of validateNewConnectionTimeout requires a JDBC
    driver
    compliant with JDBC specification level 4.0 or higher.
    
    [7/20/12 20:40:35:453 UTC] 0000001d InternalGener I
    DSRA8203I:
    Database product name : DB2 UDB for AS/400
    
    [7/20/12 20:40:35:455 UTC] 0000001d InternalGener I
    DSRA8204I:
    Database product version : 05.04.0000 V5R4m0
    
    [7/20/12 20:40:35:455 UTC] 0000001d InternalGener I
    DSRA8205I: JDBC
    driver name  : AS/400 Toolbox for Java JDBC Driver
    
    [7/20/12 20:40:35:457 UTC] 0000001d InternalGener I
    DSRA8206I: JDBC
    driver version  : 9.7
    ****************
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using JDBC                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Missing JDBC specification level.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The JDBC specification level was not provided in the trace.
    

Problem conclusion

  • The JDBC specification level has been added to the JDBC trace
    information.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.29, 8.0.0.6, and 8.5.0.2.  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

    PM73123

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-18

  • Closed date

    2013-03-21

  • Last modified date

    2013-03-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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021