IBM Support

IT11963: KILL -9 TO A PURESCALE MEMBER RETURNS XAER_RMFAIL UNEXPECTEDLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • While XA applications are running on a 3 members pureScale and
    send kill -9 to one of member's db2sysc may cause xa_commit
    receiving XAER_RMFAIL unexpectedly.
    It should return XAER_RETRY instead of XAER_RMFAIL in this case.
    This is only XA return code problem and no side effect to any
    transaction.
    By the XA Standard it is Transaction Manager's responsibility to
    get the list of indoubt transaction and retry XA operations
    until they are successful to complete the transaction. TM able
    to commit the transaction, by issuing XA_OPEN + XA_COMMIT,
    repeated the steps a few times and eventually successfully able
    to commit the transaction.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 UDB Version 10.5                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Version 11.1 GA or later.                         *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT11963

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-25

  • Closed date

    2017-02-14

  • Last modified date

    2017-02-14

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 June 2020