IBM Support

IC79893: SETTING CHUNK DOWN FOR MIRRORED DBSPACE ON PRIMARY SERVER WITH ONSPACES WILL NOT BE NOTICED ON THE SDS SECONDARY NODE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When you have a mirrored dbspace defined you can set the primary
    or mirror chunk down with onspaces (for example to relocate the
    device). If you set the chunk of a dbspace down on the primary
    server a connected SDS server will not get an appropriate update
    of the chunk status. This can lead to assertion failures on the
    secondary when the chunk is accessed but the content is not the
    expected, because it will still get accessed by the SDS
    secondary.
    

Local fix

  • To ensure no access till the down chunk is done you can shutdown
    the secondary server, if your usage scenario allows.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Shared Disk Secondaries and mirrored chunks         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When you have a mirrored dbspace defined, you can set the    *
    * primary or mirror chunk down with onspaces (for example to   *
    * relocate the device). If you set the chunk of a dbspace down *
    * on the primary server, a connected SDS server will not get   *
    * an appropriate update of the chunk status. This can lead to  *
    * assertion failures on the secondary when the chunk is        *
    * accessed but the content is not the expected, because it     *
    * will still get accessed by the SDS secondary.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDS 11.50.xC10 when available.                    *
    ****************************************************************
    

Problem conclusion

  • The issue is fixed in IDS 11.50.xC10.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC79893

  • Reported component name

    INFORMIX SERVER

  • Reported component ID

    5725A3900

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-11-18

  • Closed date

    2017-06-15

  • Last modified date

    2017-06-15

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

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

Fix information

  • Fixed component name

    INFORMIX SERVER

  • Fixed component ID

    5725A3900

Applicable component levels

  • RB50 PSY

       UP

  • RB70 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B50","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 June 2017