IBM Support

PK92163: V9 WORKFILE TABLE SPACES UNAVAILABLE WITH SQLCODE904 RC00C90084 (TYPICALLY WILL OCCUR IN PARALLELISM, BUT NOT LIMITED TO IT)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MSGDSNT501I ( DSNT501I ) DSNIWKFL RESOURCE UNAVAILABLE was seen
    with REASON RC00C20103 TYPE 00000220 and NAME
    DSNHP0B.DSNDBC.WRKHP1 due to a failed GetPage request for a
    SpaceMap page, which is because of a parallel query group
    termination that ended RC00C20042 with CTRURESN = 00E30701
    When this occurs on a header page during open, Buffermanager
    will convert the 00C20042 into a 00C20103 failure and mark the
    32K workfile unavailable with WACTPUNAV set.
    Any attempt to access these 32K workfiles until STOP/START of
    the table space(s), will fail and result in SQLCODE -904 and
    RC00C90084
    ADDITIONAL KEYWORDS: DB2PARALL/K
    

Local fix

  • If encountered, apply this APARfix, or alternatively
    issue -STOP, then -START on suspected workfile table space(s)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 for z/OS users of Workfile         *
    *                 database                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: MSGDSNT501I SQLCODE904 -904 DSNIWKFL    *
    *                      RESOURCE UNAVAILABLE RC00C90084         *
    *                      TYPE00000100 on Workfile database       *
    *                      issued surprisingly early (meaning,     *
    *                      even though free workfile space is      *
    *                      available).                             *
    *                                                              *
    *                      The problem being corrected has only    *
    *                      been encountered in parallelism, but    *
    *                      theoretically it can happen in cases    *
    *                      other than parallelism.                 *
    ****************************************************************
    * RECOMMENDATION: Apply the fix or issue -STOP then -START on  *
    *                 suspected workfile table space(s)            *
    ****************************************************************
    A workfile table space was marked unavailable after a buffer
    manager extend error even though the error was resolvable. Over
    time, several table spaces ended up being marked unavailable,
    causing the resource unavailable message DSNT501I and SQLCODE
    -904 with reason 00C90084 to be issued against Workfile
    database.
    
    If DSNT501I SQLCODE -904 reason 00C90084 is being experienced,
    the only way to verify that this APAR is a match is if a dump is
    captured (e.g. DSN1SDMP for -904 when 00C90084 is seen, or a
    console dump around that time) along with either LISTCAT output
    of all workfile table spaces or DB2 Statistics trace IFCID 002
    (which tends to be always on in most customer environments), and
    then looked at by IBM Support team (note for Level 2:
    WACTPUNAV(x) = YES on several table space entries). If you do
    not wish to go though the inconvenience of collecting a dump, it
    should be said that the APAR will most likely be a match as long
    as LISTCAT shows low space usage of workfile table spaces or, in
    the case of IFCID 002, if fields QISTWFCU, QISTWF04 and QISTWF32
    show low space usage of workfile table spaces. This would
    indicate that issuing 00C90084 is not consistent with the space.
    use.
    

Problem conclusion

  • Code has been changed to mark workfile table spaces unavailable
    only after unresolvable extend errors.
    
    Additional keywords: SQLCPUP SQLPARALLELISM SQLSYSPLEXP
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PK92163

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-23

  • Closed date

    2009-10-02

  • Last modified date

    2011-05-11

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

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

    UK50740

Modules/Macros

  • DSNISEGF
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R910 PSY UK50740

       UP09/11/03 P F911

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
11 May 2011