PQ78967: WRONG SQLDA VALUE FOR DESCRIBE OUTPUT AFTER FETCH ON CLOB OR LOBLOCATOR FOR DISTRIBUTED PROCESSING

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DDFL09 DB2DRDA DB2LOB
  INVALID SQLDA VALUE RETURNED TO WORKSTATION THAT CAUSES
  WORKSTATION TO RECEIEVE FOLLOWING ERROR.
  [IBM][JDBC Driver] CLI0600E  Invalid connection handle or
  connection is
  closed. SQLSTATE=S1000
  [IBM][CLI Driver] CLI0106E  Connection is closed. SQLSTATE=08003
  [IBM][CLI Driver] CLI0108E  Communication link failure.
  SQLSTATE=40003
  .
  The customer scenario.
  PREPARE stmt
  OPEN CURSOR1
  FETCH from CURSOR1 <-- specifies lob locator
  DESCRIBE OUTPUT for stmt
  where the 'selected' columns for the table include a LOB, and
  the FETCH specifies a LOB LOCATOR
  **************************************************
  Additional symptoms and keywords:
  . DB2 Connect client systems may write the following
    information to the "db2diag.log" file:
      sqlijrParseSqldaGrp6 Probe:210 (probe 210 probe210)
      Error code ZRC=0x8037009D ZRC 8037009D ZRC8037009D
      SQL30020N SQLCODE -30020 SQLCODE30020
      sqlerrmc 0x220E 220E sqljrpdd
      sqlerrd 1 0x8037009D
    at which time the DB2 Connect client system will
    terminate (or drop) the connection to the DB2 z/OS server
    system.
  . JDBC CLI client applications may observe the following:
      [IBM][JDBC Driver] CLI0600E  Invalid
      connection handle or connection is
        closed. SQLSTATE=S1000
      [IBM][CLI Driver] CLI0106E  Connection
        is closed. SQLSTATE=08003
      [IBM][CLI Driver] CLI0108E
        Communication link failure.
        SQLSTATE=40003
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB2 z/OS server systems may return      *
  *                      an invalid DRDA SQLDARD when the SQL    *
  *                      statement being prepared refers to a    *
  *                      result table that contains a LOB        *
  *                      data type.                              *
  *                      The invalid SQLDARD will cause          *
  *                      unpredictable results at the client     *
  *                      system.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A DB2 z/OS server may generate an incorrect DRDA reply for a
  DESCRIBE of an SQL statement which contains a LOB data type.
  An incorrect SQLDARD may be built by the DB2 z/OS server
  as the reply to a DSCSQLSTT for a cursor that has already
  had FETCHs executed against it.
  After a FETCH has been executed against a cursor, certain
  information was updated in the SQLDA.  This resulted in
  an incorrect SQLDA being used for the DESCRIBE processing.
  

Problem conclusion

• When FETCH operations can switch between using LOB or
  LOB locators, DB2 now ensures that it uses an SQLDA that uses
  LOB data types when generating the SQLDARD reply message
  for a DESCRIBE SQL statement request.
  

Temporary fix

Comments

APAR Information

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

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

  UQ81115

Modules/Macros

•    DSNLXRSS
  

Fix information

• Fixed component name

  5740 IBM DATABA

• Fixed component ID

  5740XYR00

Applicable component levels

• R710 PSY UQ81115

     UP03/10/30 P F310

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.