IBM Support

PI21134: MODIFY STATISTICS FAILING ON A USER-DEFINED INDEX ON A CATALOG TABLE. "DSNUGMAP - INDEXSPACE DSNDB06.SYSDBAUT NOT FOUND"

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MODIFY STATISTICS Failing on a user-defined index on a catalog
    table using 'SYSDBAUT' as index space name.
    Fails with the message
    "DSNUGMAP - INDEXSPACE DSNDB06.SYSDBAUT NOT FOUND"
    

Local fix

  • work around - Do not use 'SYSDBAUT' as an index space name for
    user defined indexes.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
    *                 users of the MODIFY STATISTICS utility.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The MODIFY STATISTICS utility failed    *
    *                      when run on a user-defined index on     *
    *                      a DB2 catalog table. The user-defined   *
    *                      index did exist but MODIFY STATISTICS   *
    *                      failed with RC8 and the following       *
    *                      DSNU104I message being issued:          *
    *                                                              *
    *                      DSNU1014I DSNUGMAP - INDEXSPACE         *
    *                           DSNDB06.SYSDBAUT NOT FOUND         *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    A user-defined index called SYSDBAUTH was created on the
    SYSDBAUTH catalog table in DB2 10 for z/OS. When created, this
    index had a SYSINDEXES.INDEXSPACE column value of 'SYSDBAUT'
    which came from DB2 using the first eight characters of the
    index name.
    
    This 'SYSDBAUT' index space name is identical to a catalog table
    space name that existed until it was dropped during the
    DB2 10 for z/OS ENFM process.
    
    The MODIFY STATISTICS INDEXSPACE utility was run specifying
    the 'SYSDBAUT' INDEXSPACE name. DB2 utility processing tried
    to validate that the index space name exists. Since it was an
    index on a DB2 catalog object we first tried to validate the
    name using internal catalog object name tables. DB2 utility
    processing found a match on the 'SYSDBAUT' name but the entry
    located was for the dropped SYSDBAUT table space and not the
    user-defined index whose index space name was also 'SYSDBAUT'.
    Since the entry located was not for an index space the
    MODIFY STATISTICS INDEXSPACE utility incorrectly determined
    that the index space did not exist and it failed with a RC8
    with the following DSNU1014I message appearing in the job
    output:
    
      DSNU1014I -DB2A DSNUGMAP - INDEXSPACE DSNDB06.SYSDBAUT
          NOT FOUND
    
    
    Additional keyword: MSGDSNU1014I
    

Problem conclusion

  • DB2 CREATE INDEX code has been modified so that user-defined
    indexes on DB2 catalog tables will not be given index space
    names that are the same as other DB2 object names.
    
    If indexes already exist where the index space names match
    another catalog object name then do the following:
    
    1 - Apply the PTF for this APAR.
    
    2 - Drop the index.
    
    3 - Recreate the index. This will create the same index with an
       index space name that doesn't conflict with any other
       catalog object name.
    
    While the reported problem involved the MODIFY STATISTICS
    INDEXSPACE utility, other utilities that take index space
    names as input would also have problems similar to the
    reported failure.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI21134

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-01

  • Closed date

    2014-09-22

  • Last modified date

    2014-11-04

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

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

    UI21565 UI21566

Modules/Macros

  • DSNXCATL DSNXICX3
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI21565

       UP14/10/08 P F410

  • RB10 PSY UI21566

       UP14/10/08 P F410

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":"10.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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 November 2014