Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT06716 Status: Geschlossen

A PURESCALE MEMBER MIGHT TRAP IN MON_GET_UNIT_OF_WORK PROCESSING WHILE
ANOTHER MEMBER IS STOPPING

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In purescale environment, a member might trap and restart in 
MON_GET_UNIT_OF_WORK, MON_GET_CONNECTION, MON_GET_PKG_CACHE_STMT 
or PD_GET_DIAG_HIST UDF processing while another member is 
stopping.   When this case occurs, the following logs can be 
seen in db2diag.log: 
 
2014-12-04-16.07.03.845117+540 I4201485A587         LEVEL: Info 
PID     : 3671426              TID : 288566         PROC : 
db2sysc 0 
INSTANCE: *****             NODE : 000           DB   : ***** 
APPHDL  : 0-35690              APPID: *N0.*****.141211032904 
AUTHID  : *****             HOSTNAME: ***** 
EDUID   : 288566               EDUNAME: db2agent (*******) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrkrpc_nl, probe:2368 
DATA #1 : String, 42 bytes 
RPC was re-sent because of DB deactivation 
DATA #2 : String, 10 bytes 
numRetries 
DATA #3 : unsigned integer, 8 bytes 
1 
... 
 
2014-12-04-16.07.23.314785+540 E4307950A1306        LEVEL: 
Severe 
PID     : 3671426              TID : 288566         PROC : 
db2sysc 0 
INSTANCE: *****             NODE : 000           DB   : ***** 
APPHDL  : 0-35690              APPID: *N0.*****.141211032904 
AUTHID  : *****               HOSTNAME: ***** 
EDUID   : 288566               EDUNAME: db2agent (*****) 0 
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, 
probe:90 
MESSAGE : ADM14011C  A critical failure has caused the following 
type of error: 
          "Trap". The DB2 database manager cannot recover from 
the failure. 
          First Occurrence Data Capture (FODC) was invoked in 
the following 
          mode: "Automatic". FODC diagnostic information is 
located in the 
          following directory: 
 
"/db2/*****/dump/DIAG0000/FODC_AppErr_2014-12-04-16.07.06.432309 
_ 
          3671426_288566_000/". 
DATA #1 : Signal Number Recieved, 4 bytes 
11 
DATA #2 : Siginfo, 64 bytes 
0x0A0000012940EDC0 : 0000 000B 0000 0000 0000 0032 0000 0000 
...........2.... 
0x0A0000012940EDD0 : 0000 0000 0000 0000 5449 4442 5641 4C31 
........******* 
0x0A0000012940EDE0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0A0000012940EDF0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
 
2014-12-04-16.07.23.321243+540 I4309257A808         LEVEL: Event 
PID     : 3671426              TID : 288566         PROC : 
db2sysc 0 
INSTANCE: *****             NODE : 000           DB   : ***** 
APPHDL  : 0-35690              APPID: *N0.*****.141211032904 
AUTHID  : *****             HOSTNAME: ***** 
EDUID   : 288566               EDUNAME: db2agent (*******) 0 
FUNCTION: DB2 UDB, oper system services, 
sqloPGRPRegisterOneCrash, probe:2158 
MESSAGE : lastCrashCount 
DATA #1 : unsigned integer, 8 bytes 
0 
DATA #2 : String, 10 bytes 
inRecovery 
DATA #3 : Boolean, 1 bytes 
false 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x0900000035566AFC sqloPGRPRegisterOneCrash + 0x1D4 
  [1] 0x09000000355677B0 sqloEDUCodeTrapHandler + 0xB50 
 
In a trap file, stacktraces can be shown as following: 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000035E13548 
sqlkdDispatchRequest__FP23SQLKD_RQST_REPLY_FORMATP14sqeApplicati 
on + 0x2C0 
0x090000003529C198 
sqlrkrpc_nl__FP8sqlrr_cbiN22PCsP15SQLR_RPCMESSAGEP13SQLO_MEM_POO 
LP18SQLR_RPC_REPLY_HDRPbPlUlP17SQLR_WLM_BDSREPLY + 0x31BC 
0x09000000352983E8 
sqlrkrpc_all__FP8sqlrr_cbiP15SQLR_RPCMESSAGEP13SQLO_MEM_POOLPP18 
SQLR_RPC_REPLY_HDRT2UlP17SQLR_WLM_BDSREPLY + 0x785C 
0x09000000359B6B00 sqlerTrustedRtnCallbackRouter__FUiPPv + 
0x2E134 
0x09000000125FBE78 wlmGetNextBuffer + 0xF8 
0x09000000125FBE78 wlmGetNextBuffer + 0xF8 
0x090000001261CFD8 
monGetUnitOfWorkCommon__FP5sqlcaPFUiPPv_iR13uowParameters24sqlmM 
etricOutputFunctionPcN35P17sqludf_scratchpadP16sqludf_call_type 
+ 0x2F8 
0x090000001261CB54 monGetUnitOfWork_v105fp4 + 0x1CD4 
0x090000001261E7EC monGetUnitOfWork + 0x16AC
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fixpack 7.                       * 
****************************************************************
Local-Fix:
Lösung
First fixed in Version 10.5 Fixpack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.01.2015
26.01.2016
26.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList