Error SQL1143N is returned when running inspect utility and
outputting to a log.
$ db2 INSPECT CHECK DATABASE RESULTS KEEP db2_inspect.log
SQL1143N The operation cannot complete because a file error
occurred
for the
file "db2_inspect.log".
This is due to trying to access a FODC directory that was not
created.
Sample of db2diag.log when this occurs.
2014-10-06-17.38.26.106149-240 E77810A783 LEVEL: Error
(OS)
PID : 21037166 TID : 1 PROC :
db2support
INSTANCE: db2inst1 NODE : 000
EDUID : 1
FUNCTION: DB2 UDB, oper system services, sqlochdir, probe:10
MESSAGE : ZRC=0x870F0011=-2029060079=SQLO_PATH "an invalid path"
DIA8514C An invalid file path, "", was specified.
CALLED : OS, -, chdir
OSERR : ENOTDIR (20) "Not a directory"
DATA #1 : String, 0 bytes
Object not dumped: Address: 0x0000000000000000 Size: 0 Reason:
Address is NULL
DATA #2 : String, 76 bytes
/db2inst1/db2dump/FODC_Hang_2014-10-04-23.12.02.114937/DB2CONFIG
/db2nodes.cfg
DATA #3 : String, 105 bytes
Search for ossError*Analysis probe point after this log entry
for further
self-diagnosis of this problem.
.
.
.
2014-10-04-23.12.02.141038-240 E4003A641 LEVEL: Warning
PID : ********** TID : 1 PROC :
db2fodc
INSTANCE: db2inst1 NODE : 000
EDUID : 1
FUNCTION: DB2 UDB, RAS/PD component, pdDb2FODCMain, probe:30
MESSAGE : ADM14003W FODC has been invoked by the user from
db2fodc tool for
symptom "hang" and diagnostic information has been
recorded in
directory
"/pajyaz0/db2dump/FODC_Hang_2014-10-04-23.12.02.114937".
Please look in this directory for detailed evidence
about what
happened and contact IBM support if necessary to
diagnose the
problem. |
