"FODC is in progress state" is not reset after data collection.
Therefore utilities like INSPECT will not write to db2dump
directory, but to an old FODC directory. If this FODC directory
was previously deleted errors like SQL1143N can occur.
This is the same scenario as described in 9.7 APAR IC74893.
IC74893 fixes an issue where first data capture (FODC) was
triggered by sqlbLogReadAttemptFailure(). Example:
2011-01-23-00.22.22.840571-420 E67029A938 LEVEL: Critical
PID : 2330948 TID : 12150 PROC : db2sysc 3
INSTANCE: db2inst1 NODE : 003 DB : XXXXXX
APPHDL : 3-1123 APPID: nnn
AUTHID : DB2INST1
EDUID : 12150 EDUNAME: db2bm.12339.3 (XXXXXX) 3
FUNCTION: DB2 UDB, buffer pool services,
sqlbLogReadAttemptFailure, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "BadPage".
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
"/db2xxxx/db2dump/FODC_BadPage_2011-01-23-00.22.22.816367/".
Please
look in this directory for detailed evidence about
what happened and
contact IBM support if necessary to diagnose the
problem.
This new APAR will fix situations triggered by:
sqlbDMSMapAndRead()
sqlbSMSDirectRead()
sqlbReorgReadPage()
and make sure that "FODC is in progress" state will be reset
after data is captured.
For example:
2012-10-10-10.36.53.131915+120 I40637326A598 LEVEL: Severe
PID : 23322 TID : 74913 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : XXXXXX
APPHDL : 0-12202 APPID: nnn
AUTHID : DB2INST1
EDUID : 74913 EDUNAME: db2bm.74886.7 (XXXXXX) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapAndRead,
probe:30
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not
exist"
DIA8506C Unexpected end of file was reached.
DATA #1 : <preformatted>
Converting to non-critical read error.
2012-10-10-10.36.53.135000+120 E40637925A938 LEVEL: Critical
PID : 23322 TID : 74913 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : XXXXXX
APPHDL : 0-12202 APPID: nnn
AUTHID : DB2INST1
EDUID : 74913 EDUNAME: db2bm.74886.7 (XXXXXX) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapAndRead,
probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "BadPage".
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
"/db2xxxx/db2dump/FODC_BadPage_2012-10-10-10.36.53.132189_0000/"
.
Please look in this directory for detailed evidence
about what
happened and contact IBM support if necessary to
diagnose the
problem.
As the "FODC in progress" state is not reset here (until
restart), utilities like INSPECT will write their outputs into
this FODC directory. Also any other occurance of a critical
error, will not create a new FODC directory, but will use the
old one. |
