Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT04014 Status: Closed

PREFETCHING CAUSES DB MARKED BAD WHEN SYSTEM ERROR OCCURS IN SQLOCSEMV

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Failure of msgsnd with EAGAIN will cause prefetcher 
inintialization to fail, resulting in database marked bad. 
 
2013-10-23-19.35.38.562700-240 E12789A534         LEVEL: Error 
(OS) 
PID     : 37945760             TID  : 51917       PROC : db2sysc 
INSTANCE: jefferya             NODE : 000         DB   : FOO 
APPHDL  : 0-183                APPID: 
*LOCAL.jefferya.131023233338 
AUTHID  : JEFFERYA 
EDUID   : 51917                EDUNAME: db2agent (FOO) 
FUNCTION: DB2 UDB, oper system services, sqloCSemV, probe:1 
MESSAGE : ZRC=0x8300000B=-2097151989 
CALLED  : OS, -, unspecified_system_function 
OSERR   : EAGAIN (11) "Resource temporarily unavailable" 
 
2013-10-23-19.35.38.563378-240 I13324A439         LEVEL: Error 
PID     : 37945760             TID  : 51917       PROC : db2sysc 
INSTANCE: jefferya             NODE : 000         DB   : FOO 
APPHDL  : 0-183                APPID: 
*LOCAL.jefferya.131023233338 
AUTHID  : JEFFERYA 
EDUID   : 51917                EDUNAME: db2agent (FOO) 
FUNCTION: DB2 UDB, buffer pool services, sqlbpfTriggerPrefetch, 
probe:1 
MESSAGE : ZRC=0x8300000B=-2097151989 
 
2013-10-23-19.35.38.563814-240 I13764A495         LEVEL: Error 
PID     : 37945760             TID  : 51917       PROC : db2sysc 
INSTANCE: jefferya             NODE : 000         DB   : FOO 
APPHDL  : 0-183                APPID: 
*LOCAL.jefferya.131023233338 
AUTHID  : JEFFERYA 
EDUID   : 51917                EDUNAME: db2agent (FOO) 
FUNCTION: DB2 UDB, buffer pool services, sqlbpfTriggerPrefetch, 
probe:1 
DATA #1 : String, 65 bytes 
sqlbpfTriggerPrefetch : bad rc returned from 
sqlbPFGetFreeRequest 
 
2013-10-23-19.35.38.719140-240 E25922A759         LEVEL: Error 
PID     : 37945760             TID  : 51917       PROC : db2sysc 
INSTANCE: jefferya             NODE : 000         DB   : FOO 
APPHDL  : 0-183                APPID: 
*LOCAL.jefferya.131023233338 
AUTHID  : JEFFERYA 
EDUID   : 51917                EDUNAME: db2agent (FOO) 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:10 
MESSAGE : ADM14005E  The following error occurred: "AppErr". 
First Occurrence 
          Data Capture (FODC) has been invoked in the following 
mode: 
          "Automatic".  Diagnostic information has been recorded 
in the 
          directory named 
 
"/home/jefferya/sqllib/db2dump/FODC_AppErr_2013-10-23-19.35.38.7 
07884 
          _37945760_51917_000/". 
 
2013-10-23-19.35.38.939308-240 E130475A960        LEVEL: 
Critical 
PID     : 37945760             TID  : 51917       PROC : db2sysc 
INSTANCE: jefferya             NODE : 000         DB   : FOO 
APPHDL  : 0-183                APPID: 
*LOCAL.jefferya.131023233338 
AUTHID  : JEFFERYA 
EDUID   : 51917                EDUNAME: db2agent (FOO) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::MarkDBBad, probe:10 
MESSAGE : ADM14001C  An unexpected and critical error has 
occurred: 
          "DBMarkedBad". 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 
 
"/home/jefferya/sqllib/db2dump/FODC_DBMarkedBad_2013-10-23-19.35 
.38.9 
          37140_0000/". Please look in this directory for 
detailed evidence 
          about what happened and contact IBM support if 
necessary to diagnose 
          the problem.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************
Local Fix:
Solution
First fixed in Version 10.1 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.08.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList