IBM Support

IT06746: DB2 MAY CRASH WITH SIGNAL #11(SIGSEGV) AFTER UPGRADING TO V97FP10 FROM BELLOW FIXPACK LEVEL

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • DB2 may crash after upgrading to V97fp10 from below fixpack
    level due to the changes made in statistical/activity monitor
    tables. If you have Statistics/Activity monitor defined from
    fixpacks below v97fp10 and then upgrade to v97fp10,DB2 may
    crash.
    
    Trap file will have Signal info as bellow:
    
    </Siginfo_t>
    Signal #11 (SIGSEGV): si_addr is 0x0000000000000000, si_code is
    0x00000080 (SI_KERNEL:Send by kernel.)
    </SignalDetails>
    
    Stack in trap will be as bellow:
    Stack #1             Signal #11        Timestamp
    2015-01-14-06.40.01.039691
    0 > ossDumpStackTraceEx
    1 > OSSTrapFile::dumpEx
    2 > sqlo_trce
    3 > sqloEDUCodeTrapHandler
    4 > _IO_ftrylockfile
    5 > sqmRequestMetrics::populateOldEvmonMetricsDvalues
    6 > sqm_evmon_ttarget::write_data
    7 > sqm_evmon_target::prepAndWriteData
    8 > sqmEvmonBuffer::write_data
    9 > sqmEvmonWriter::evmonWriter
    10 >-- sqmEvmonWriter::startMeUp
    11 >-- sqlm_bds_start_monitor_hdl
    12 >-- sqleSubRequestRouter
    13 >-- sqleProcessSubRequest
    14 >-- sqeAgent::RunEDU
    15 >-- sqzEDUObj::EDUDriver
    16 >-- sqlzRunEDU
    17 >-- sqloEDUEntry
    18 >-- __deallocate_stack
    19 >-- __clone
    
    You will see similar error logs in db2diag.log:
    
    2015-01-14-06.40.01.115961+000 I9575182E571        LEVEL: Severe
    PID     : 1894                 TID  : 46912854026560PROC :
    db2sysc 39
    INSTANCE: bculinux             NODE : 039          DB   :
    BDWLP01
    APPHDL  : 0-75                 APPID: *N0.DB2.150114063059
    AUTHID  : BCULINUX
    EDUID   : 102                  EDUNAME: db2evmtp (DB2STATISTICS)
    39
    FUNCTION: DB2 UDB, RAS/PD component,
    pdResilienceIsSafeToSustain, probe:800
    DATA #1 : String, 37 bytes
    Trap Sustainability Criteria Checking
    DATA #2 : Hex integer, 8 bytes
    0x2000000000021009
    DATA #3 : Boolean, 1 bytes
    false
    

Local fix

  • Drop and Recreate the event monitor tables to avoid further
    crashes.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 11.                      *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 9.7 Fix Pack 11.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT06746

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-26

  • Closed date

    2015-10-06

  • Last modified date

    2015-10-06

  • 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

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT06746

Modified date: 06 October 2015