IBM Support

IT31295: "DB2CLUSTER -VERIFY" COMMAND SOMETIMES FAILS IN RDMA PING TEST PHASE WITH DAT API ERROR "unexpected event: 0x4003"

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

  • "db2cluster -verify" command with "-debug" option like
    "db2cluster -debug -verify -req -rdma_ping" logs the following
    error message in /tmp directory.
    
    * /tmp/ibm.db2.cluster_int-2019-11-05-18.26.56.log
    
    18:31:01   Testing rdma ping connection.
    18:31:01   Client Hostname: hosta   Client Netname:
    netnamea
    18:31:01   Server Hostname: host01db03   Server Netname:
    netnameb
    18:33:03   Server exited with an error
    18:33:03   DAT API: dat_evd_wait failed with 0x800F0000. Timeout
    reached while waiting for client to connect.
    
    18:33:03   Client exited with an error
    18:33:03   DAT API: dat_evd_wait failed with 0x40000. Received
    an unexpected event: 0x4003
    
    18:33:03   Udapl ping failed, performed 100 pings out of 100
    
    * /tmp/host01db03/ibm.db2.cluster_int-2019-11-05-18.26.56.trace
    
    2019-11-05-18.31.03.317328+540 I180077A216        LEVEL: Event
    PID     : 23789984             TID : 1
    FUNCTION: DB2 Common, OSSe, ossClusterPingUdaplClient,
    probe:1117
    DATA #1 : String, 20 bytes
    Connecting to Server
    
    2019-11-05-18.31.03.400588+540 I180294A427        LEVEL: Error
    PID     : 23789984             TID : 1
    FUNCTION: DB2 Common, OSSe, ossClusterPingConnectEventWait,
    probe:20
    MESSAGE : ECF=0x9000066B Waiting for an event or response has
    failed
    DATA #1 : Bool, 1 bytes
    false
    DATA #2 : String, 36 bytes
    Received an unexpected event: 0x4003
    DATA #3 : Uint32, 4 bytes
    262144
    DATA #4 : Hex, 4 bytes
    0x4003
    DATA #5 : Hex, 4 bytes
    0x4001
    
    2019-11-05-18.31.03.452468+540 I180722A407        LEVEL: Event
    PID     : 8257992              TID : 1
    FUNCTION: DB2 Common, OSSe, ossClusterPingUdaplServer,
    probe:2008
    DATA #1 : String, 19 bytes
    Delayed Ack feature
    DATA #2 : String, 11 bytes
    Unsupported
    DATA #3 : String, 8 bytes
    Netname:
    DATA #4 : String, 13 bytes
    netnameb
    DATA #5 : String, 18 bytes
    Interface adapter:
    DATA #6 : String, 4 bytes
    hca1
    
    2019-11-05-18.33.03.471822+540 I181130A496        LEVEL: Error
    PID     : 8257992              TID : 1
    FUNCTION: DB2 Common, OSSe, ossClusterPingUdaplServer, probe:180
    DATA #1 : String, 52 bytes
    Timeout reached while waiting for client to connect.
    DATA #2 :
    NULL
    DATA #3 : String, 13 bytes
    netnameb
    DATA #4 : Uint64, 8 bytes
    10
    DATA #5 : Uint64, 8 bytes
    100
    DATA #6 : Uint64, 8 bytes
    53015
    DATA #7 : Uint64, 8 bytes
    1
    DATA #8 : Uint32, 4 bytes
    120000000
    DATA #9 : Uint32, 4 bytes
    2148466688
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Db2 pureScale User                                           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 11.1 Modification 4 FixPack 6 or      *
    * later                                                        *
    ****************************************************************
    

Problem conclusion

  • Fixed in DB2 Version 11.1 Modification 4 FixPack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31295

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-12-15

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

  • 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

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"11.1"}]

Document Information

Modified date:
01 April 2021