SAP Knowledge Base Article - Preview

2499080 - How to check db2fmp messages in the db2diag.log

Symptom

  • There are frequent db2fmp messages in the db2diag.log.
  • You want to confirm if they are actual errors or just warnings.
     
    A typical example of db2fmp warnings in the db2diag.log is as follows

    2017-06-29-19.10.45           LEVEL: Event

    PID : 123456 TID : PROC : db2sysc 0
    INSTANCE: db2    NODE : 000 DB : P20
    APPHDL : 0-0000 APPID: *LOCAL.db2p20.170629165927
    AUTHID : DB2TST HOSTNAME: xxxxxx
    0000 EDUNAME: db2agent (000) 0
    FUNCTION: DB2 UDB, oper system services, sqlossig, probe:10
    MESSAGE : Sending SIGKILL to the following process id
    DATA #1 : signed integer, 4 bytes
    123456
    CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
    [0] 0x00007FFFF03F0357 sqlossig + 0x167
    [1] 0x00007FFFEF693735 _Z20sqlerReturnFmpToPoolccP14sqlerFmpHandleP8sqeAgent + 0xD35
    [2] 0x00007FFFF0858F69 _Z28sqlri_close_udf_ufob_cleanupP10sqlri_ufobP5sqlcaP8sqlrr_cb + 0x589
    [3] 0x00007FFFF0858709 _Z19sqlri_close_udf_eosP25sqlra_sql_context_siblingiP8sqlrr_cb + 0xB9
    [4] 0x00007FFFF087B754 _Z16sqlricls_complexP8sqlrr_cbilll + 0x4A74
    [5] 0x00007FFFF34CD672 _Z29sqlrr_process_execute_requestP8sqlrr_cbib + 0x2252
    [6] 0x00007FFFF34C9E6C _Z13sqlrr_executeP14db2UCinterfaceP9UCstpInfo + 0x26C
    [7] 0x00007FFFF34101E6 _Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject + 0x4C6
    [8] 0x00007FFFF340F76E _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCinterface + 0x7E
    [9] 0x00007FFFEF78C5AB _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 0x36B
    [10] 0x00007FFFEF786BAF /db2/db2p20/sqllib/lib64/libdb2e.so.1 + 0x347DBAF
    [11] 0x00007FFFEF78502C /db2/db2p20/sqllib/lib64/libdb2e.so.1 + 0x347C02C
    [12] 0x00007FFFEF782079 /db2/db2p20/sqllib/lib64/libdb2e.so.1 + 0x3479079
    [13] 0x00007FFFEF781C6B _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xEB
    [14] 0x00007FFFEF47F5EF _ZN8sqeAgent6RunEDUEv + 0xACF
    [15] 0x00007FFFF0CB4AA7 _ZN9sqzEDUObj9EDUDriverEv + 0xF7
    [16] 0x00007FFFF0466DA3 sqloEDUEntry + 0x303
    [17] 0x00007FFFF7BC7806 /lib64/libpthread.so.0 + 0x7806
    [18] 0x00007FFFEB0DD67D clone + 0x6D

    2017-06-29-19.10.46.006056+120 E86962329E437 LEVEL: Error
    PID : 123456  TID :                         PROC : db2wdog 0 [db2p20]
    INSTANCE: db2   NODE : 000
    HOSTNAME: xxxxxxxx
    EDUID : 2 EDUNAME: db2wdog 0 [db2p20]
    FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:7918
    DATA #1 : <preformatted>
    Beginning cleanup of Process id: 123456 OSS term code: 0x102, signal: 9

    2017-06-29-19.10.46.            Error
    PID : 123456 TID :                            PROC : db2sysc 0
    INSTANCE: db2   NODE : 000
    HOSTNAME: xxxxxxx
    EDUID : 1 EDUNAME: db2sysc 0
    FUNCTION: DB2 UDB, base sys utilities, sqleCleanupFmp, probe:776
    DATA #1 : <preformatted>
    A 64-bit fenced mode process crashed. Process id: 123456

    2017-06-29-19.10.46.                  LEVEL: Warning
    PID : 123456 TID :                  PROC : db2sysc 0
    INSTANCE: db2tst NODE : 000
    HOSTNAME: xxxxxxx
    EDUID : 1 EDUNAME: db2sysc 0
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:999
    DATA #1 : String, 34 bytes
    Removing FMP from pool FMP handle:


Read more...

Environment

DB2 LUW (Unix, Linux and Windows)

Product

SAP NetWeaver 7.4

Keywords

crash, SQL, Java, KEEPFENCED, SYSIBM.SQL, SQL0464W, exiting, fenced user, db2 stored procedure , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.