IBM Support

IZ17660: DOCUMENTATION OF CHANGES IN IBM DATA SERVER DRIVER FOR JDBC AND SQLJ VERSION 3.7.73 FOR DB2 LUW V9.1 FIXPACK 5 (PART 1)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ============================================================
    Documentation of changes in IBM Data Server Driver for JDBC
    and SQLJ version 3.7.73 for DB2 LUW V9.1 Fixpack 5.  The
    previous version was 3.6.60 for DB2 LUW V9.1 Fixpack 4.
    
    ____________________________________________________________
    SQLJ: The SQLJ Translator was incorrectly throwing an
    error when static import was used. The static field OR
    method of the imported static class was not being
    resolved correctly with semantics applicable for static
    member resolution. The SQLJ Translator has now been fixed
    so that no error occurs during translation with static
    imports.
    ____________________________________________________________
    All Connectivity Types:
    When a result set is obtained from the zOS server
    with connection properties fullyMaterializeLobData
    set to FALSE and progressiveStreaming set to 2, and
    that result set contains a large number of Clobs,
    SQLCODE805 can result.
    ____________________________________________________________
    All Connectivity Types:
    When trying to deregister an XML object on DB2 Linux, Unix,
    Windows server, DB2 Universal driver converted all input to
    upper case, but text in double quotes should not be
    converted. Text in double quotes is now treated as case
    sensitive.
    ____________________________________________________________
    All Connectivity Types:
    A SQLCODE4461 is received during the getNextWarning() call
    due to an SQLException being present on the SQLWarning
    chain. SQLExceptions will no longer be put onto the
    SQLWarning chain.
    ____________________________________________________________
    All Connectivity Types: When running with the system
    monitor trace level: DB2BaseDataSource.TRACE_SYSTEM_MONITOR
    and the DB2BaseDataSource property:
    RetrieveMessagesFromServerOnGetMessage = true, the system
    monitor may be prematurely stopped resulting in inaccurate
    times and a warning message with SQLWARN4470 (+4470).
    ____________________________________________________________
    All Connectivity Types: The following methods are not
    thread safe:
      - Connection.prepareStatement(String, int)
      - Connection.prepareStatement(String, int[])
      - Connection.prepareStatement(String, String[])
    These methods are now thread safe.
    ____________________________________________________________
    Type-4 Connectivity: While establishing the connection, the
    driver uses the error message
    "org.ietf.jgss.GSSException is caught when getting a ticket
    from SUN JGSS. See attached Throwable for details." if it
    is not able to obtain the kerberos security ticket. Starting
    from this release, the term "SUN" is removed from the above
    
    message.  The driver throws the error with the message
    "org.ietf.jgss.GSSException is caught when getting a ticket
    from JGSS.  See attached Throwable for details."
    ____________________________________________________________
    Type-4 Connectivity: The client application hangs when an
    invalid security mechanism was specified as the exception
    was accumulated and never thrown to the client.  The
    problem is now fixed by throwing the exception to the
    client.
    ____________________________________________________________
    Type-2 LUW Connectivity:
    When using the IBM Data Server Driver for JDBC for running
    Java routines in DB2 v9 (DB2_USE_DB2JCCT2_JROUTINE=YES),
    calling a Java routine which uses an external class/JAR
    can cause a NoClassDefFoundError exception to be thrown.
    ____________________________________________________________
    All Connectivity types:
    The db2sqljupgrade utility included with the IBM Data Server
    Driver for JDBC and SQLJ contains corrupted .class files.
    The files are
    COM/ibm/db2os390/sqlj/custom/DB2SQLJCustomizer.class
    COM/ibm/db2os390/sqlj/custom/DB2SQLJEntryInfo.class
    COM/ibm/db2os390/sqlj/custom/DB2SQLJProfile.class
    ____________________________________________________________
    Type-2 LUW Connectivity:
    The IBM Data Server Driver for JDBC using Type 2
    connectivity does not perform client reroute if the server
    returns AGNPRMRM.  A connection exception is thrown and
    a reroute is not attempted.
    ____________________________________________________________
    Type-4 XA Connectivity:
    XAResource.end()/XAResource.prepare() throws XAException
    (XAER_NOTA) if a stored procedure defined with
    'COMMIT ON RETURN YES' is called inside a global
    transaction.
    ____________________________________________________________
    Type-2 LUW Connectivity:
    A NullPointerException is thrown when retrieving LOBs
    greater than 1 MB with progressive streaming enabled.
    ____________________________________________________________
    All Connectivity types:
    The IBM Data Server Driver for JDBC does not allow retrieval
    of an empty BLOB  i.e. Blob.getBytes(1,0) throws a
    SQLException SQLCODE99999 (-99999).  The operation should
    return a byte array of zero length.
    ____________________________________________________________
    Type-4 Connectivity:
    DatabaseMetaData.storesUpperCaseIdentifiers returns false if
    called against DB2 on i5/OS.  It should return true and
    storesMixedCaseQuotedIdentifiers currently returns true.
    It should return false.
    ____________________________________________________________
    Type-2 LUW Connectivity:
    A NullPointerException is thrown while obtaining a
    connection if no password is provided and encryption is
    enabled via the database manager configuration parameter
    AUTHENTICATION.
    ____________________________________________________________
    All Connectivity types:
    An overflow error is thrown when inserting a BigDecimal with
    negative scale using JRE 5.0+.
    SQLException message:
    Message = [ibm][db2][jcc][converters] Overflow occurred
    during numeric data type conversion
    ____________________________________________________________
    Type-2 LUW Connectivity:
    A NullPointerException is thrown executing a statement after
    reuseDB2Connection/resetDB2Connection is called, under
    one of the following conditions:
    -Using a Type-2 TCP/IP connection to a DB2 Connect gateway
    against DB2 z/OS
    -Using a Type-2 TCP/IP connection to DB2 LUW with an
    alternate server defined.
    ____________________________________________________________
    Type-4 connectivity:
    When the primary server is down and the connection has been
    rerouted to the alternative server, a java.sql.SQLException
    with message "dss length not 0 at end of same id chain
    parse" may occur.
    ____________________________________________________________
    Type-4 connectivity:
    When using the encryption securityMechanism
    ENCRYPTED_USER_AND_PASSWORD_SECURITY or
    ENCRYPTED_PASSWORD_SECURITY, a SQLException with SQLCode
    -1042 may occur.
    ____________________________________________________________
    Type-4 connectivity:
    JCC previously supports only SSL protocols. The TLS
    protocols are now also supported.
    ____________________________________________________________
    Type-4 connectivity: If the initial connection is a SSL
    connection, LUW server now uses the TCPIP port for interrupt
    requests instead of the SSL port.  Changes have been made in
    the Jcc driver to accommodate the server change.
    ____________________________________________________________
    Type-4 connectivity: When setting clientDebugInfo using
    Jcc against iSeries v6 server, Jcc issues an exception with
    message "Set Client debuginfo is not supported on this
    version of server".
    ____________________________________________________________
    Type-4 connectivity: When using trusted connections, if
    the primary server is down and the alternative server is
    configured, an exception with message
    "Connection authorization failure occurred.  Reason:
    Security mechanism not supported" may occur.
    ____________________________________________________________
    SQLJ:
    The SQLJ Upgrade utility db2sqljupgrade was not handling
    VARCHAR FOR BIT DATA columns correctly, resulting in
    'Invalid conversion error' . The upgrade utility has been
    fixed to handle BIT DATA columns in both parameter and
    resultset meta data.
    ____________________________________________________________
    SQLJ:
    SQLJ Upgrade Utility has been enhanced to use information
    in the legacy profile in a more accurate fashion.
    It does not affect profiles already upgraded and working as
    expected. Upgraded profiles using earlier versions of the
    upgrade utility which exhibit runtime problems may be
    upgraded again using this version of the upgrade utility.
    ____________________________________________________________
    SQLJ:
    The SQLJ Customizer is unable to resolve unqualified UDFs
    in the SQL statement during the on-line check phase
    resulting in -440 errors.
    The url provided to the customizer should contain the
    currentFunctionPath for UDF resolution like:
     "jdbc:db2://server:port/DBNAME:currentFunctionPath=xxxx;"
    Customizer resolves unqualified UDFs based on this setting.
    ____________________________________________________________
    SQLJ: Java 5 Enum Types were not handled correctly by the
    SQLJ Translator. It is now fixed to generate correct code
    when Enum Types are used.
    ____________________________________________________________
    SQLJ: Perform SQLJ Profile Size Optimization during the
    SQLJ Customization step, thereby reducing the Profile size
    and using less storage for deserialized Profiles at runtime.
    Applications need to run the SQLJ Customizer
    (db2sqljcustomize) again for optimizing/reducing the size of
    the Profiles. Running the SQLJ Customizer again is an
    optional step and is needed only if Profile size reduction
    is desired. There is no runtime impact for the already
    existing Profiles.
    ____________________________________________________________
    SQLJ: The SQLJ Upgrade utility db2sqljupgrade was not
    copying the null indicator field from the legacy profile
    correctly resulting in wrongly marking a filed nullable.
    This caused problems at runtime when the null indicator
    field was checked when a field was not null. db2sqljupgrade
    has been fixed to correctly copy the null indicator field
    from the legacy profile.
    

Local fix

  • n/a
    

Problem summary

  • see problem description
    

Problem conclusion

  • first fixed in DB2 LUW 9.1 fixpak 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ17660

  • 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

    2008-03-12

  • Closed date

    2008-07-10

  • Last modified date

    2008-07-10

  • 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

[{"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:
04 October 2021