IBM Support

IT31780: ADM16504E IS GENERATED IN DB2DIAG.LOG IN PURESCALE AFTER DB2STOPIS RUN

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

  • ADM16504E is generated in db2diag.log in pureScale after running
    db2stop.
    
    If this is seen on Db2 11.1.4.5 with pureScale this message can
    be safely ignored.
    
    --------
    2020-01-27-19.30.16.050191+540 E82986A856           LEVEL: Error
    PID     : 15794548             TID : 1              PROC :
    db2rocme 128 [db2inst1]
    INSTANCE: db2inst1              NODE : 128
    HOSTNAME: host1
    EDUID   : 1                    EDUNAME: db2rocme 128 [db2inst1]
    FUNCTION: DB2 UDB, high avail services, sqlhaKillProcesses,
    probe:1633
    MESSAGE : ADM16504E  An attempt to kill a process during a
    CLEANUP failed on
              host: "host1". A host reboot must be manually
    performed.
    CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
      [0] 0x0000000100121928
    sqlhaKillProcesses__FP18SQLHA_PROCESS_INFOUlbT2T3CPb + 0x1BC8
      [1] 0x0000000100130F70 rocmCAKillProcesses + 0xFD0
      [2] 0x0000000100135540 rocmCAStop + 0x7A0
      [3] 0x000000010000473C main + 0x1CFC
      [4] 0x00000001000002F8 __start + 0x70
    

Local fix

  • Set like below explicitly.
    "db2set DB2_ROCM_FORCE_REBOOT_TIMEOUT=120"
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Purescale User                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Set like below explicitly.                                   *
    * "db2set DB2_ROCM_FORCE_REBOOT_TIMEOUT=120"                   *
    ****************************************************************
    

Problem conclusion

  • See description
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31780

  • 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

    2020-02-05

  • Closed date

    2021-03-16

  • Last modified date

    2021-03-16

  • 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:
18 March 2021