IBM Support

IZ06818: DOCUMENTATION OF CHANGES IN IBM DB2 DRIVER FOR JDBC AND SQLJ VER SION 3.6.60 FOR DB2 LUW V9 FP4

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Documentation of changes in IBM DB2 Driver for JDBC and SQLJ
    version 3.6.60 for DB2 LUW V9 FP4. The previous version was
    3.4.65 for DB2 LUW V9 FP3.
    New features are documented in the IBM DB2 Database for
    Linux, UNIX, and Windows Information Center.
    Defect fixes are documented in the section that follows.
    ___________________________________________________________
    All Connectivity Types:
    A java.io.NotSerializableException was thrown when a
    DB2DataSource object was being serialized. This problem is
    now fixed.
    ___________________________________________________________
    Type-4 Connectivity: A SQLException may be thrown when
    running a PreparedStatement batch against a server
    supporting multi-row insert.  This problem can result when
    mixing compatible input parameter types between statement
    batch elements using various setter methods.  For instance,
    using setString for a parameter followed by using setReader
    for the same parameter after calling addBatch. This problem
    has been corrected and mixing of compatible input types
    within a PreparedStatement batch is fully supported.
    ___________________________________________________________
    Type-4 Connectivity: An SQLException indicating a LOB
    has become invalid is thrown when accessing the object
    even though there was no cursor movement following the LOB
    retrieval.  This occurs under certain scenarios when
    progressiveStreaming is on and particular ResultSet API
    calls for cursor movement such as absolute() have been
    called prior to LOB object retrieval and access. This issue
    has been resolved.
    ___________________________________________________________
    All Connectivity types: Trace output may be lost when using
    override and default trace files which can be specified via
    configuration properties db2.jcc.traceFile and
    db2.jcc.override.traceFile.  This can occur when new
    Connections are established after all previously existing
    connections are closed and go out of scope.  This issue has
    been corrected.
    ___________________________________________________________
    Type-4 Connectivity: DisconnectException may be thrown when
    inserting large XML data provided as Readers.  This only
    occurs when a larger SQL statement and/or data is run on or
    before the current statement.  This issue has been
    corrected.
    ___________________________________________________________
    All Connectivity types: SQLException with SQLCODE99999
    (-99999) indicating an invalid column index may be
    generated when accessing a ParameterMetaData object from a
    CallableStatement created with a return value
    (ie {? = call ADDIT (?,?,?)}).  The SQLException may also
    result when setting CallableStatement parameters.  This
    situation can occur after the method getParameterCount() is
    invoked on a the ParameterMetaData object.  This issue has
    been fixed.
    ___________________________________________________________
    JCCT2LUW: The maximum nesting limit of LUW stored
    procedures supported by the JCC T2 LUW driver is
    increased from 16 to 64.
    ___________________________________________________________
    Type-4 Connectivity:
    When using a combination of XA and trusted connections,
    XA does not use the correct securityMechanism from the
    datasource. This problem is fixed.
    ___________________________________________________________
    All connectivity types:
    Jcc can flow special registers even when the connection is
    not reset. The problem has been fixed.
    ___________________________________________________________
    Type-2 Connectivity:
    A NullPointerException occurs when using Type-2 LUW against
    LUW or z/OS server for securityMechanism
    ENCRYPTED_USER_PASSWORD_AND_DATA_SECURITY. The problem is
    fixed.
    ___________________________________________________________
    All Connectivity Types: A SQLCODE4499 (-4499) is reported
    if the user inserts a decimal number with more than 32
    digits. The problem is now fixed.
    ___________________________________________________________
    Type-4 XA Connectivity: A SQLCODE4499 (-4499) error is
    reported on executing the first SQL of a new transaction
    when a held cursor opened prior to this transaction is
    still open and property "downgradeHoldCursorsUnderXa"
    is set to true. The problem is now fixed.
    ___________________________________________________________
    All Connectivity Types:
    An SQLCODE517 may be thrown when re-executing a
    PreparedStatement set to return auto-generated keys
    following a commit or rollback.  Changes have been made to
    the driver to avoid the SQLCODE517 in these scenarios.
    ___________________________________________________________
    All ConnectivityTypes:
    A spelling error has been corrected in an SQLException
    reporting an unsupported security mechanism when attempting
    to create a connection.
    ___________________________________________________________
    All Connectivity Types:
    After one of the auto-generated keys APIs on
    java.sql.Statement is invoked, such as
    execute (String sql, int autoGeneratedKeys),
    execute (String sql, int columnIndexes[]),
    or execute (String sql, String columnNames[]),
    the driver will request auto-generated
    key information when the same statement is used
    to perform INSERTs with the non-autogenerated key APIs.
    For example, this may result in an implicit SELECT
    FROM...INSERT flow vs. a direct INSERT or an implicit
    SELECT chained after the INSERT. This has been fixed and
    auto-generated key information will only be requested when
    the auto-generated key APIs are called.
    ___________________________________________________________
    Type-2 UW Connectivity:
    Applications calling stored procedures may see
    SQLCODE4302 (-4302) returned because of an
    java.lang.ArrayIndexOutOfBoundsException condition
    encountered inside the store procedure when using
    Jcc as the stored procedure driver. This problem has been
    corrected.
    ___________________________________________________________
    All connectivity types: Calls to Clob.getSubString() with a
    zero passed in as the length argument may result in a
    SQLException.  This method will now always return an empty
    string when called with a zero length and valid position.
    

Local fix

Problem summary

  • See error description text
    

Problem conclusion

  • Problem first fixed in version 9.1 fixpak 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ06818

  • Reported component name

    DB2 UDB ESE AIX

  • Reported component ID

    5765F4100

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-10-18

  • Closed date

    2008-01-22

  • Last modified date

    2008-01-22

  • 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 UDB ESE AIX

  • Fixed component ID

    5765F4100

Applicable component levels

  • R910 PSY

       UP

  • R950 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
03 October 2021