IBM Support

IZ16696: TIMING ISSUE WITH CRASHING FMP CAN LEAD TO INSTANCE SHUTDOWN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A timing issue exists such that if an FMP crashes soon enough on
    start-up,
    the system controller can mistakenly fail to identify it as an
    FMP and as a
    consequence shut down the instance.
    
    In the db2diag.log you can see this :
    
    
    2008-02-26-12.56.07.614831-300 I1293360A350       LEVEL: Severe
    PID     : 12155                TID  : 1           PROC : db2sysc
    INSTANCE: dbguest5             NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler,
    probe:15
    DATA #1 : Hexdump, 15 bytes
    0x4000000000007900 : 416E 2045 4455 2063 7261 7368 6564 2E
    An EDU crashed.
    
    2008-02-26-12.56.07.615324-300 I1294389A338       LEVEL: Severe
    PID     : 12155                TID  : 1           PROC : db2sysc
    INSTANCE: dbguest5             NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler,
    probe:18
    DATA #1 : Hexdump, 4 bytes
    0x9FFFFFFFFFFFDE9C : FFFF FFFF
    ....
    
    2008-02-26-12.56.07.615546-300 I1294728A338       LEVEL: Severe
    PID     : 12155                TID  : 1           PROC : db2sysc
    INSTANCE: dbguest5             NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler,
    probe:19
    DATA #1 : Hexdump, 4 bytes
    0x9FFFFFFFFFFFDE94 : FFFF FC88
    ....
    
    Where the system controller has performed a SIGKILL on the
    db2fmp but
    believes it to be a normal EDU and so crashes the instance.
    

Local fix

Problem summary

  • Summary :
    
    A timing issue exists such that if an FMP crashes soon enough on
    start-up,
    the system controller can mistakenly fail to identify it as an
    FMP and as a
    consequence shut down the instance.
    
    
    Users affected :
    
    Users using fenced stored procedures which crash.
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ16696

  • Reported component name

    DB2 UDB ESE HP-

  • Reported component ID

    5765F4103

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-03-05

  • Closed date

    2008-11-11

  • Last modified date

    2008-11-11

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

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

    IZ16818

Fix information

  • Fixed component name

    DB2 UDB ESE HP-

  • Fixed component ID

    5765F4103

Applicable component levels

  • R910 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
04 October 2021