IBM Support

PI12731: Information for the xscmd -c showLinkedPrimaries command is missing.

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

  • The xscmd showLinkedPrimaries command shows the current state
    of each link from a primary shard in the local domain to any
    primary shards in foreign domains. When a link is in recovery
    state, it indicates that replication encountered an exception.
    Typically, you review the container server SystemOut or JVM
    logs to find the exception, and to determine the number of
    links in each state, you must count or process the output.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users running with  *
    *                  Multimaster replication (MMR) and using     *
    *                  the xscmd showLinkedPrimaries command.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a link is in recovery state in     *
    *                      the xscmd showLinkedPrimaries output,   *
    *                      additional information is missing.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The xscmd showLinkedPrimaries command is enhanced to show the
    last replication exception encountered for links in recovery
    state. The message column shows the Exception class and the
    exception message. For the full stack, the container server
    SystemOut or JVM logs can be reviewed.
    The xscmd showLinkedPrimaries command also adds the number and
    types of links for each requested data grid and displays the
    results.
    Example:
    Container: server0_C-1, Server: server0, Host:
    host.domainName ***
    Grid Name Map Set Name Partition Domain  Container
    Status   Message
    --------- ------------ --------- ------  ---------
    ------   -------
    inventory aSet         0         domain2 server0_C-0
    recovery org.omg.CORBA.NO_RESPONSE: Request 134 timed out
    inventory aSet         1         domain2 server0_C-0
    recovery org.omg.CORBA.NO_RESPONSE: Request 136 timed out
    Primary shards reporting links that are online: 0
    Primary shards reporting links that are in recovery: 2
    Primary shards reporting links that are pending: 0
    Primary shards reporting no links: 0
    

Problem conclusion

  • Apply the interim fix for additional information from the xscmd
    showLinkedPrimaries command.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI12731

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-28

  • Closed date

    2014-03-17

  • Last modified date

    2014-03-17

  • 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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R850 PSY

       UP

  • R860 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 March 2014