DB2 - Problem description
Problem IT03990 | Status: Closed |
DB2INSPECT FAILS WITH SQL1143N ERROR BECAUSE A FILE ERROR OCCURED, MISSING FODC DIRECTORY. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Example: db2 "inspect check database indexdata results keep node44.inspectdb.out ON DBPARTITIONNUM (44)" SQL1143N The operation cannot complete because a file error occurred for the file "node44.inspectdb.out". "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 and IC87297. Following errors will be reported in the db2diag.log: 2014-08-07-10.28.31.391058+000 I248060A490 LEVEL: Severe PID : 12845298 TID : 9289 PROC : db2sysc 44 INSTANCE: db2xxxx NODE : 044 EDUID : 9289 EDUNAME: db2pfchr (xxxxx) 44 FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapAndRead, probe:30 MESSAGE : ZRC=0x860F0003=-2045837309=SQLO_DERR "disk error occurred (DOS)" DIA8402C A disk error has occurred. DATA #1 : <preformatted> Converting to non-critical read error. 2014-08-07-10.28.31.392201+000 E248551A852 LEVEL: Critical PID : 12845298 TID : 9289 PROC : db2sysc 44 INSTANCE: db2xxxx NODE : 044 EDUID : 9289 EDUNAME: db2pfchr (xxxxx) 44 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 **** Following DB2 trace collection can be used to capture diagnostics on partition where db2inspect fails: db2 connect to <database>; db2trc on -m "*.*.DART.*.*"; db2 "INSPECT CHECK DATABASE RESULTS KEEP db2_inspect.log ON DBPARTITIONNUM (44)"; db2trc dmp trc.dmp; db2trc off; db2trc fmt -c trc.dmp trc.fmtc; db2trc fmt trc.dmp trc.fmt; db2trc flw -t -wc trc.dmp trc.flw; From the db2 trace collected above in trc.fmt file, it shows db2 inspect is trying to create the output file here: /db2fs/db2edwp1/NODE0044/db2dump/FODC_BadPage_2014-08-07-10.28.3 1.391243_0044 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7 version Fixpack 10. * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.08.2014 01.12.2014 01.12.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |