PH67586: INTERMITTENT AND UNPREDICTABLE ABEND IF SQL ERROR RECEIVED DURING DATA RETRIEVAL BY TWO LOGICAL UNLOADS PROCESSED IN SQL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A Db2 HPU step intermittently terminates in ABEND after having
  reported an undetermined number of ABENDs such as ABENDS0C4,
  ABENDS0C6 or any other unpredictable ABEND. This occurs in the
  following scenario:
  - An UNLOAD TABLESPACE statement contains at least two valid
    logical unloads (SELECT ... OUTDDN) that fulfill all the
    following conditions:
      - they are processed in SQL mode (indicated by an INZU479I
        message per unload in question)
      - their processing faces an SQL error during the row
        retrieval process performed by Db2 (if this is the case,
        one INZR2004 message per unload in question is issued
        unless the failure prevents them to be displayed)
  - The Db2 parallelism indicated by the INZU226I message is
    greater than 1.
  Note: As the SELECT statements involved in the issue are valid
  ones, the more likely SQL errors triggering the issue are
  related to the unavailability of the Db2 object.
  

Local fix

• Consider disabling the Db2 parallelism by specifying PARALLELISM
  (lds,1,ts), where lds and ts stand for the values already
  specified, if any (for a value that has not been specified, no
  character should be present. An example where neither the lds
  nor the ts values have been specified would be PARALLELISM
  (,1,)).
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload for     *
  *                 z/OS                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: A Db2 HPU step intermittently           *
  *                      terminates in ABEND after having        *
  *                      reported an undetermined number of      *
  *                      ABENDs such as ABENDS0C4, ABENDS0C6 or  *
  *                      any other unpredictable ABEND. This     *
  *                      occurs in the following scenario:       *
  *                      - An UNLOAD TABLESPACE statement        *
  *                        contains at least two valid logical   *
  *                        unloads (SELECT ... OUTDDN) that      *
  *                        fulfill all the following conditions: *
  *                          - they are processed in SQL mode    *
  *                            (indicated by an INZU479I message *
  *                            per unload in question)           *
  *                          - their processing faces an SQL     *
  *                            error during the row retrieval    *
  *                            process performed by Db2 (if this *
  *                            is the case, one INZR2004 message *
  *                            per unload in question is issued  *
  *                            unless the failure prevents them  *
  *                            to be displayed)                  *
  *                      - The Db2 parallelism indicated by the  *
  *                        INZU226I message is greater than 1.   *
  *                                                              *
  *                      Note: As the SELECT statements involved *
  *                      in the issue are valid ones, the more   *
  *                      likely SQL errors triggering the issue  *
  *                      are related to the unavailability of    *
  *                      the Db2 object.                         *
  *                                                              *
  *                      Local fix :                             *
  *                      Consider disabling the Db2 parallelism  *
  *                      by specifying PARALLELISM (lds,1,ts),   *
  *                      where lds and ts stand for the values   *
  *                      already specified, if any (for a value  *
  *                      that has not been specified, no         *
  *                      character should be present. An example *
  *                      where neither the lds nor the ts values *
  *                      have been specified would be            *
  *                      PARALLELISM (,1,)).                     *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  Intermittent and unpredictable ABEND if SQL error received
  during data retrieval by two logical unloads processed in SQL
  mode concurrently
  

Problem conclusion

• Code has been changed to fix this problem
  

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:

Modules/Macros

• INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R520 PSY UO05248

     UP25/10/18 P F510

• R610 PSY UO05249

     UP25/10/18 P F510

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.