IBM Support

IC76663: DOCUMENTATION OF CHANGES IN IBM DATA SERVER DRIVER FOR JDBC AND SQLJ VERSION 3.63.52/4.13.53 FOR DB2 LUW V9.7 FIXPACK 5

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • All connectivity types: When CCSID 16684 is used,
    SQLException with message unsupported ccsid, encoding,
    or locale: "Cp16684". may occur. This problem is fixed.
    (wsdbu00740081)
    
    All connectivity types: When one of the encryption
    security mechanisms is used, Client userid special
    register is not set correctly. This problem is fixed.
    (wsdbu00840342)
    
    All connectivity types: Internal binary XML parser buffer
    size is changed for performance reason.
    (wsdbu00714222)
    
    All connectivity types: NPE may happen when the driver
    prints out the out of package diagnostics information
    for SQL code -805. The problem has been fixed.
    (wsdbu00720606)
    
    All connectivity types: When data type cursor is used
    as the stored procedure parameters and there are multiple
    resultset returned from the stored procedure,
    ArrayIndexOutOfBoundException may occur. This problem
    is fixed. (wsdbu00728452)
    
    Type-4 Connectivity: Under sysplexWLB environment,
    after a failover scenario JCC driver might not balance
    the workload correctly. The problem has been fixed.
    (wsdbu00707444)
    
    Type-4 or Type-2 Connectivity: When JCC driver is waiting
    for the reply from the DB2 server and the value set by
    blockingReadConnectionTimeOut property is expired, JCC
    driver will try auto client reroute to a new connection
    without cleaning up the old connection to DB2 server.
    This can result in a lockwait if there was a transaction
    held by this old connection before
    blockingReadConnectionTimeOut occurred.The problem has
    been fixed. (wsdbu00716902)
    
    Type-4 Connectivity: Under sysplexWLB environment,
    JCC driver might create more transport objects than
    the value set by db2.jcc.maxTranportObjects global
    property while doing auto fail-over. The problem has
    been fixed.(wsdbu00836844)
    
    Type-4 Connectivity :JCC driver has now added a new
    
    property    activateDatabase    at DataSource/Connection
    level against DB2 LUW V10 and above. This new property
    will control if the database needs to be activated or not
    during connection establishment. For more details on
    this property refer to JCC driver documentation.
    (wsdbu00710583)
    
    Type-4 or Type-2 Connectivity :JCC driver has now added a
    new feature to provide the monitoring support for commit
    
    and rollback operation as well against DB2 LUW V10 and
    above servers. (wsdbu00710590)
    
    Type-4 Connectivity :JCC driver has now added three new
    
    properties traceOption, traceFileSize and traceFileCount,
    on data source/driver manager level as well as at the
    global driver level. These new properties will enhance
    the existing JCC tracing to support circular tracing
    option that will help to limit the total generated
    trace file size. For more details on these tracing
    properties refer to JCC driver documentation.
    (wsdbu00731407)
    
    Type-4 Connectivity - If application sets
    maxTransportsObjects property on a datasource and
    maxTransportObjectWaitTime property at a global level
    then connection requests could hang instead of receiving
    a SqlTimeoutException even after waiting longer than the
    time set by maxTransportObjectWaitTime. This problem
    has been fixed. (wsdbu00708417).
    
    
    SQLJ ALL  Connectivity Types:
    In a Websphere environment an SQLJ application
    may hit an  ArrayIndexOutOfBoundsException thrown
    from the Websphere runtime. This is more likely to occur
    when the application issues a SELECTstatement , closes
    the SQLJ iterator and the Java Finalizer thread drives a
    close on the underlying statement concurrently.
    If the SQLJ ConnectionContext is closed after the
    iterator close in the application the chances of hitting
    this timing window is eliminated. The fix just ensures
    the PreparedStatement close is not done twice.
    (wsdbu00718833)
    
    SQLJ ALL  Connectivity Types:
    In a Websphere environment an SQLJ application
    may hit a 'Statement is closed' error. This is
    more likely to occur when Connection Sharing in enabled
    for the Websphere  application. The error occurs when
    SQLJ Runtime reuses a Statement which was closed by
    Websphere at the transaction boundary. The fix ensures
    the statement  is re-prepared if it was closed by Websphere.
    (wsdbu00734485)
    
    All Connectivities:  Starting DB2 for LUW v9.7 FP5, the
    server allows nested ROW type and nested ARRAY type as
    parameters for stored procedures executed via the clients.
    The driver provides the corresponding support
    for the same. (wsdbu00722707)
    
    Type-4 Connectivity: JCC driver reports
    an unexpected NullPointerException
    during the failover processing for
    applications connecting to a data sharing
    or a HADR system. (wsdbu00738031)
    
    Type-4 Connectivity: New feature for supporting
    alternate group DVIPA on a sysplex environment.
    (wsdbu00975951)
    
    Type-4 Connectivity: New feature for enabling
    statement caching on connections that are coming from
    java.sql.DriverManager and DB2SimpleDataSource.
    (wsdbu00738895)
    
    All Connectivities: Starting DB2 for iSeries v7 the server
    allows ARRAY type as parameters for stored procedures
    executed by clients. The driver provides the corresponding
    support for the same. (wsdbu00733662)
    
    All Connectivities: Added a new function that is for
    accessing the parent logger of all the loggers in
    this class of the type java.util.logging.Logger as
    mandated by top level interface
    javax.sql.CommonDataSource. However, since
    java.util.logging is not supported by the driver at
    present we only throw a
    SQLFeatureNotSupportedException in this case.
    (wsdbu00723182)
    
    All Connectivities: Added a new function that is for
    accessing the parent logger of all the loggers in this
    class of the type java.util.logging.Logger as mandated
    by top level interface java.sql.Driver. However, since
    java.util.logging is not supported by the driver at
    present we only throw a
    SQLFeatureNotSupportedException in this case.
    (wsdbu00726320)
    
    All Connectivities: Added new functions that allow
    a Statement to be closed as soon as all the
    dependent Result Sets are closed. This change is also
    reflected in all the implementing classes of
    java.sql.Statement. Also enhanced the execute methods
    of Statement class to throw an SQLTimeoutException
    if a query timeout (specified by the setQueryTimeout()
    function) occurs and the executing Statement has been
    cancelled. (wsdbu00728096)
    
    All Connectivities: Added two new functions. The first is
    to specify whether a Select query can invoke a generated
    key by specifying the correct column names and indexes.
    The second allows fetching all the hidden (pseudo) columns
    of a certain database by specifying necessary filters for
    Catalog, Schema, Table and Column name patterns.
    Also, enhanced the current getColumns() function to
    return a result set compatible with the JDBC 4.1
    specifications but also as per the older specification if the
    user so chooses by setting a new property in DataSource.
    (wsdbu00732297)
    
    All Connectivities: For the JDBC 4.1 enhancement of
    SQLTimeoutException a new argument, sqlCode,
    is considered when mapping exceptions. However the
    sqlCode is not alwaysset especially in case where the
    statement is cancelled by the client. In such cases the
    null pointer exception is encountered when fetching
    sqlCode. To counter this condition we now pass a
    default value.
    (wsdbu00974784)
    
    All Connectivities: The new function getPseudoColumns()
    has a method signature that mandates returning of a
    ResultSet objectimplying a java.sql.ResultSet. In the local
    implementation of DatabaseMetaData a ResultSet object
    stands for the local implementation of ResultSet and
    hence a signature mismatch occurs when the function
    is invoked. To resolve this we explicity set the
    return type of the function as java.sql.ResultSet.
    (wsdbu00975509)
    
    All Connectivities: The Stored Procedure spelling
    was fixed to access the correct procedure
    SQLPSEUDOCOLUMNS on the informix server.
    (wsdbu00977461)
    
    All Connectivities: JDBC 4.1 has introduced
    5 new methods in Connection : abort,
    setNetworkTimeout, getNetworkTimeout,
    setSchema, getSchema. These methods are
    implemented. (wsdbu00740903)
    
    All Connectivities: JDBC 4.1 has added support
    for java.util.Calender, java.util.Date and
    java.lang.BigInteger. Conversion from these types
    are implemented as per the conversion table
    of the spec. (wsdbu00740425)
    
    All Connectivities: com.ibm.db2.jcc.am.Configuration
    throws NoSuchMethodException during driver.
    This problem is fixed (wsdbu00740531)
    
    Type-2 Connectivity: Accessing large lob within a
    distributed transaction causes null pointer exception.
    This problem is fixed (wsdbu00739149)
    
    All Connectivities:  am.Configuration has refrence
    of ref. wrong class name and
    am.MappedCallableStatem. The
    class name ref. updated and this problem is fixed.
    (wsdbu00740531)
    
    Type-4 Connectivity: JCC driver reports
    an unexpected NullPointerException
    during the failover processing for
    applications connecting to a data sharing
    or a HADR system. (wsdbu00738031)
    
    Type-4 Connectivity: With client affinities,
    or HADR or DB2 with data sharing
    (LUW only) environment, JCC driver can
    wait for 10 minute wait to close a
    connection if all DB2 instances go
    down before the close.
    The problem has
    been fixed. (wsdbu00723426)
    
    Type-4 Connectivity: When (enableSeamlessFailover)
    property is set to true, JCC driver did not retry the
    Statement.executeBatch() statement after
    successful fail-over. The problem
    has been fixed. (wsdbu00977617)
    
    Type-4 or Type-2 Connectivity: NPE may happen
    when the driver manager connects to a database
    and the license procedure fails. The problem
    has been fixed.(wsdbu00981164)
    
    Type-4 Connectivity: Under sysplexWLB environment,
    if system is heavy loaded with multiple threads
    competing with small amount of the transport pool
    objects, JCC driver might get distribution protocol
    error with ERRORCODE=-4499. The problem has been
    fixed.(wsdbu00977620)
    
    Type-4 Connectivity: New feature for enabling
    seamless sysplex migration support for pureScale server.
    (wsdbu00825858)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of the IBM Data Server Driver for JDBC and SQLJ        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 LUW V9.7 Fixpack 5                            *
    ****************************************************************
    

Problem conclusion

  • Problems fixed in DB2 LUW V9.7 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC76663

  • Reported component name

    DB2 CONNECT

  • Reported component ID

    DB2CONNCT

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-26

  • Closed date

    2011-12-07

  • Last modified date

    2011-12-07

  • 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

    DB2 CONNECT

  • Fixed component ID

    DB2CONNCT

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC76663

Modified date: 07 December 2011