IBM Support

IC87083: STORAGE SYSTEM DETAILS PANEL --> VOLUMES TABLE DATA WILL NOT DISPLAY FOR SOME SVC/STORWIZEV7000/V7000U

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • On the SVC/Storwize  details-->Volumes panel the aggregated
    health data displays however the list table displays the message
    "An error occurred loading table data".  Checking of the TPC &
    TIP logs at the time of the table being brought up will show no
    errors.
    
     However, the actual UI javascript error can be seen in the
    console of a browser debugging tool (such as Firebug for
    Firefox) when the Volumes panel is brought up. The error is:
    "Error: dojox.data.QueryReadStore:  The json data as specified
    by: [../../srm/TPC/curi/StorageVolumes/items] is malformed.
    Items within the list have identifier: [id].  Value collided:
    [61529] ".
    This error shows "value collided" which means an expected unique
    value(s) was duplicated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * V7000/V7000U/SVC users viewing their volume data (only with  *
    * certain configurations)                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The following error is seen when trying to view volume data  *
    * for some V7000/V7000U/SVC storage                            *
    * subsystems.<br/><br/>&quot;An error occurred loading table   *
    * data&quot;.<br/><br/>This has been seen in the following     *
    * panels:<br/>  V7000 details panel--&gt; volumes list         *
    * table<br/>  L2 Volumes table for those who have V7000        *
    * <span><span><span><br/></span></span></span>                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Get customized cleanup script.  Run it and apply patch or    *
    * fix pack.                                                    *
    ****************************************************************
    

Problem conclusion

  • This problem is corrected with TPC 5.1.1.  However, if you have
    already encountered it, you will need to clean up the database
    to resolve the issue.  This can be done by removing the storage
    subsystem experiencing the problem such that the historical
    information for it is removed from the database.  If you cannot
    do this, you must open a PMR to work with support to get a
    script to clean up the incorrect information in your
    database.<br/><br/>Each customer affected needs to
    either:<br/>1) On 5.1.0<br/>   a) remove the offending SS from
    TPC<br/>       Warning:  This will remove historical information
    for the SS.<br/>   b) apply patch<br/>   c) restart device
    service<br/>   d) re-add the SS device to TPC through Configure
    Devices Wizard<br/><br/>2) On 5.1.0 but cannot remove SS from
    TPC<br/>   ** backup DB for safety<br/>   a) open PMR to get
    customized DB cleanup script (supply repocopy)<br/>   b) stop
    data and device service<br/>   c) run customized DB cleanup
    script<br/>   d) restart data service<br/>   e) apply patch<br/>
    f)  restart device service<br/><br/>3) Migrated up to 5.1.1
    (device was added to TPC in 5.1.0)<br/>   a)  remove the
    offending SS from TPC<br/>       Warning:  This will remove
    historical information for the SS.<br/>   b) re-add the SS
    device to TPC through Configure Devices Wizard<br/><br/>4)
    Migrated up to 5.1.1 (device was added to TPC in 5.1.0) but
    cannot remove SS from TPC:<br/>     **backup DB for safety<br/>
    a) open PMR to get customized DB cleanup script (supply
    repocopy)<br/>    b) stop data and device service<br/>    c) run
    customized DB cleanup script<br/>    d) restart data and device
    service<br/><br/>The fix for this APAR is targeted for the
    following maintenance package:<br/><br/>| fix pack |
    5.1.1-TIV-TPC-GA - target December
    2012<br/><br/>http://www-01.ibm.com/support/docview.wss?&amp;uid
    =swg21320822<br/><br/>The target dates for future fix packs do
    not represent a formal <br/>commitment by IBM. The dates are
    subject to change without <br/>notice.<br/>
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC87083

  • Reported component name

    TPC

  • Reported component ID

    5608TPC00

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-09

  • Closed date

    2012-10-23

  • Last modified date

    2012-10-23

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

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

Modules/Macros

  • REPORT
    

Fix information

  • Fixed component name

    TPC

  • Fixed component ID

    5608TPC00

Applicable component levels

  • R510 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
23 March 2022