IBM Support

IT13175: TO DOCUMENT ALL THE JCC APAR AND DEFECTS SHIPPED WITH DB2V97FP11RELEASE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • Type-4 connectivity: The Connection's isValid(int timeout)
    API may throw NPE when client reroute is enabled. Also,
    the isValid (int timeout) API may not honor the specified
    timeout in certain scenarios.
    (wsdbu01064344)
    
    
    A special register configured on a connection URL or a
    datasource may fail to take effect when 1) JCC triggers
    a license check immediately after acquiring a connection
    and 2) application invokes a commit() or rollback() as the
    first thing on the connection before any other SQL
    operations. Incorrect special register values can cause
    applications to receive SQL errors such as
    SQLCODE204(-204) in this scenario.
    (wsdbu01064526).
    
    A special register configured on a connection URL or a
    datasource may fail to take effect when 1) JCC triggers
    a license check immediately after acquiring a connection
    and 2) application invokes a commit() or rollback() as the
    first thing on the connection before any other SQL
    operations. Incorrect special register values can cause
    applications to receive SQL errors such as
    SQLCODE204(-204) in this scenario.
    (wsdbu01064526)
    
    Type-4 connectivity: Currently committed semantics are not
    applied if a SELECT subquery is embedded in an UPDATE/INSERT
    query. The driver requests concurrent access resolution of
    USE CURRENTLY COMMITTED only for purely SELECT queries.
    However, when SELECT queries are embedded within INSERT or
    UPDATE queries, the driver does not request USE CURRENTLY
    COMMITTED concurrent access resolution even though the
    driver property concurrentAccessResolution is configured
    as
    DB2BaseDataSource.CONCURRENTACCESS_USE_CURRENTLY_COMMITTED
    (1).
    (wsdbu01064526)
    
    All Connectivity: Presence of odd number of single quotes
    within comments in an sql affects the correct counting of
    number of parameters. This results in an SQLException with
    SQLCODE(-4461) SQLSTATE(42815). "Invalid parameter 1:
    Parameter index is out of range. ERRORCODE=-4461,
    SQLSTATE=42815" . Example: String sql="-- this sql doesn't
    update set\n AUTH_DOMAIN_ID = ?" This issue has been
    fixed. (wsdbu01064553)
    
    
    Type-4 connectivity: Invoking getCatalog() API always
    returns CURRENT SERVER value by default which should not
    be the default behavior. This problem has been fixed.
    Introduced a new global boolean property
    retCatalogAsServer, to control the RETCAT option
    getCatalog() API uses when invoking SYSIBM.SQLTABLES
    stored procedure. When SYSIBM.SQLTABLES is invoked with a
    RETCAT option of 0 (retCatalogAsServer set to 0, or the
    default), a null value on return is not replaced with
    CURRENT SERVER value. If the RETCAT option used is 1
    (retCatalogAsServer set as 1), a null value on the
    invocation of SYSIBM.SQLTABLES is replaced with the
    CURRENT SERVER value.
    (wsdbu01065287)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of the IBM Data Server Driver for JDBC and SQLJ        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See the APAR Error Description                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Update to DB2 LUW 97 FixPack 11                              *
    ****************************************************************
    

Problem conclusion

  • Problems fixed in DB2 LUW 97 FixPack 11
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT13175

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-27

  • Closed date

    2016-01-27

  • Last modified date

    2016-01-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT13175

Modified date: 27 January 2016