IBM Support

PH58324: MISSING CHECK CONDITION DATAREPEATFACTORF=0 FOR DSN_VIRTUAL_INDEXES.DATAREPEATFACTORF

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DSN_VIRTUAL_INDEXES is defined with the following
    check constraint on the column DATAREPEATFACTORF
    .
      CHECK("DATAREPEATFACTORF" = -1
         OR "DATAREPEATFACTORF" >= 1)
    .
    instead of
    .
      CHECK("DATAREPEATFACTORF" = -1
         OR "DATAREPEATFACTORF" = 0
         OR "DATAREPEATFACTORF" >= 1)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS and Db2 13 for z/OS                      *
    * users of the following:                                      *
    * o Db2 EXPLAIN table DSN_VIRTUAL_INDEXES                      *
    * o Db2-supplied stored procedure                              *
    *   - SYSPROC.ADMIN_EXPLAIN_MAINT                              *
    * o Db2-supplied REXX execs:                                   *
    *   - DSNTXTA (Job DSNTIJXA)                                   *
    *   - DSNTXTB (Job DSNTIJXB)                                   *
    * o Db2 sample job DSNTESC                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The EXPLAIN table DSN_VIRTUAL_INDEXES                        *
    * is currently defined with the                                *
    * following check constraint on the                            *
    * column DATAREPEATFACTORF                                     *
    *   CHECK("DATAREPEATFACTORF" = -1                             *
    *      OR "DATAREPEATFACTORF" >= 1)                            *
    * instead of                                                   *
    *   CHECK("DATAREPEATFACTORF" = -1                             *
    *      OR "DATAREPEATFACTORF" = 0                              *
    *      OR "DATAREPEATFACTORF" >= 1)                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    The Db2-supplied stored procedure SYSPROC.ADMIN_EXPLAIN_MAINT,
    the Db2 REXX execs DSNTXTA and DSNTXTB, and the Db2 sample
    job DSNTESC all specified the incorrect check constraint on
    the DATAREPEATFACTORF column of the EXPLAIN table
    DSN_VIRTUAL_INDEXES.
    

Problem conclusion

  • This APAR provides the following fixes to ensure that the
    correct check constraint is specified on
    DSN_VIRTUAL_INDEXES.DATAREPEATFACTORF:
    o Db2-supplied stored procedure SYSPROC.ADMIN_EXPLAIN_MAINT:
      - Specify the correct check constraint on column
        DATAREPEATFACTORF when performing the following actions:
        o Create table DSN_VIRTUAL_INDEXES.
        o Add missing column DATAREPEATFACTORF to an existing
          DSN_VIRTUAL_INDEXES table.
        o Add missing check constraint on
          DSN_VIRTUAL_INDEXES.DATAREPEATFACTORF.
    o Db2-supplied REXX exec DSNTXTA (job DSNTIJXA):
      - Specify the correct check constraint on column
        DATAREPEATFACTORF when performing the following actions:
        o Add missing column DATAREPEATFACTORF to an existing
          DSN_VIRTUAL_INDEXES table.
        o Add missing check constraint on
          DSN_VIRTUAL_INDEXES.DATAREPEATFACTORF.
    o Db2-supplied REXX exec DSNTXTB (job DSNTIJXB):
      - Specify the correct check constraint on column
        DATAREPEATFACTORF when performing the following actions:
        o Create table DSN_VIRTUAL_INDEXES in UNICODE.
    o Db2 sample job DSNTESC:
      - Specify the correct check constraint on column
        DATAREPEATFACTORF in the
        CREATE TABLE DSN8!!0.DSN_VIRTUAL_INDEXES statement.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH58324

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-11-22

  • Closed date

    2023-12-21

  • Last modified date

    2024-01-02

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

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

    UI95033 UI95034

Modules/Macros

  • DSNADMEM DSN@DMEM DSNTESC  DSNTXTA  DSNTXTB
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI95033

       UP23/12/29 P F312

  • RD10 PSY UI95034

       UP23/12/29 P F312

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 January 2024