IBM Support

LI73828: ADDING A NEW PARTITION TO A MULTI-PARTITIONED DATABASE FAILS WITH -1031 IF THE DATABASE DIRECTORY CONTAINS SYMBOLIC LINKS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Suppose a database that uses automatic storage exists in a
    multi-paritition instance with multiple physical partitions.
    Furthermore, the local database directory contains symbolic
    links to different physical paths on each machine.
    When a new partition needs to be added, the ADD DBPARTITIONNUM
    command fails with SQLCODE -1031 because
    the storage path from a non-catalog partition cannot be resolved
    on the catalog partition.
    

Local fix

Problem summary

  • Users Affected: All Users
    Problem Description:
    ADDING A NEW PARTITION TO A MULTI-PARTITIONED DATABASE FAILS
    WITH -1031 IF THE DATABASE DIRECTORY CONTAINS SYMBOLIC LINKS
    
    Suppose a database that uses automatic storage exists in a
    multi-paritition instance with multiple physical partitions.
    Furthermore, the local database directory contains symbolic
    links to different physical paths on each machine.
    When a new partition needs to be added, the ADD DBPARTITIONNUM
    command fails with SQLCODE -1031 because
    the storage path from a non-catalog partition cannot be resolved
    on the catalog partition.
    
    Problem Summary:
    ADDING A NEW PARTITION TO A MULTI-PARTITIONED DATABASE FAILS
    WITH -1031 IF THE DATABASE DIRECTORY CONTAINS SYMBOLIC LINKS
    
    Suppose a database that uses automatic storage exists in a
    multi-paritition instance with multiple physical partitions.
    Furthermore, the local database directory contains symbolic
    links to different physical paths on each machine.
    When a new partition needs to be added, the ADD DBPARTITIONNUM
    command fails with SQLCODE -1031 because
    the storage path from a non-catalog partition cannot be resolved
    on the catalog partition.
    

Problem conclusion

  • Problem  was first fixed in Version 9.1 Fix Pack 7
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI73828

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-10-15

  • Closed date

    2009-04-20

  • Last modified date

    2009-04-20

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

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

    LI73829

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 October 2021