IBM Support

LI74173: COMMAND "DB2STOP FORCE" MAY CAUSE A TRAP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Issuing db2stop force command may cause a trap in db2
    v9.5.
    
    The trap occurred immediately after sqleKillNode sent SIGDUMP to
    all processes.  The following messages may appear in the
    db2diag.log:
    
    
    
    
    2009-01-27-12.10.19.234088-300 I32874473E296       LEVEL: Severe
    PID     : 2158                 TID  : 183095683680 PROC :
    db2stop2
    INSTANCE: nyqxt150             NODE : 014
    FUNCTION: DB2 UDB, base sys utilities, sqleKillNode, probe:90
    MESSAGE : Sending sigdump and waiting for 1 min to complete
    
     2009-01-27-12.10.19.302308-300 E32874770E1515      LEVEL:
    Critical
    PID     : 30054                TID  : 183106529632 PROC :
    db2ckpwd 14
    INSTANCE: nyqxt150             NODE : 014
    EDUID   : 1                    EDUNAME: db2sysc 14
    FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
    probe:10
    MESSAGE : ADM14001C  An unexpected and critical error has
    occurred:
    "Trap". The  instance may have been shutdown as a result.
    "Automatic" FODC (First Occurrence Data Capture) has been
    invoked and diagnostic information has been recorded in
    directory <directory name>. Please look in this directory
    for detailed evidence about what happened and contact IBM
    support if necessary to diagnose the problem.
    
    DATA #1 : Signal Number Recieved, 4 bytes              11
    
    
    
    
    A stack trace with the following functions may appear in the
    trap file:
    
    ossDumpStackTraceEx
    OSSTrapFile
    OSSTrapFile
    sqlo_trce
    sqloEDUCodeTrapHandler
    sqloUNIXSignalEDU
    sqloDumpInstanceHandler
    sqlorqueInternal
    sqlorque2
    sqlockpw_daemon_initv
    sqloRunInstance
    sqloEDUMainEntryPcj
    sqloEDUEntry
    

Local fix

  • none
    
    Fixed in FP5.
    

Problem summary

  • Users Affected: All
    
    Problem Description:
    Issuing command db2stop force may cause a trap. The trap
    occurs immediately after sqleKillNode sends SIGDUMP to
    all processes. Messages in the db2diag.log indicate a signal 11
    was received after calling function sqleKillNode.
    
    Problem Summary:
    Instance traps with signal 11 after issuing db2stop force
    command.
    

Problem conclusion

  • Problem is first fixed in Version 9.5 FixPak 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI74173

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-13

  • Closed date

    2010-05-03

  • Last modified date

    2010-05-03

  • 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 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 May 2010