PM76271: WRONG KEY GENERATED FOR A SPATIAL INDEX AFTER CREATE INDEX

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Wrong key generated for a SPATIAL index after CREATE INDEX.
    When a row for a normal spatial object, ie. polygon, is
    inserted, followed by a row for an empty SPATIAL object, after
    a CREATE INDEX, the keys may contain invalid keys.  There
    should be zero keys generated for the empty spatial object.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
    *                 users of spatial indexes.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Invalid spatial index keys found after  *
    *                      a CREATE INDEX on a spatial column of   *
    *                      a table.                                *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    Multiple rows were inserted into a table with a spatial column
    that included spatial data followed by rows which included
    empty spatial objects.  A subsequent CREATE INDEX was run to
    create a spatial index for that column.  Invalid keys were
    generated for the empty spatial data.
    
    Additional keywords:  INCORROUT SQLINCORR SQLINCORROUT
    DB2INCORR/K DB2INCORR/M
    

Problem conclusion

  • CREATE INDEX has been modified to generate the correct spatial
    index keys.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM76271

  • 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

    2012-10-31

  • Closed date

    2013-01-31

  • Last modified date

    2013-03-04

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

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

    UK91515 UK91516

Modules/Macros

  •    DSNURBXT
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK91515

       UP13/02/28 P F302

  • R910 PSY UK91516

       UP13/02/28 P F302

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

910

Reference #:

PM76271

Modified date:

2013-03-04

Translate my page

Machine Translation

Content navigation