DB2 crashes when function LIO_LISTIO receives OS error ENOTSUP
in Solaris
Example db2diag.log messages encountered:
2014-02-13-05.52.22.060783-480 E15998196A813 LEVEL: Error
(OS)
PID : 8736 TID : 3819 PROC : db2sysc
0
INSTANCE: inst NODE : 000
EDUID : 3819 EDUNAME: db2pclnr (ECMDBP) 0
FUNCTION: DB2 UDB, oper system services, sqloDispatchNBlocks,
probe:100
MESSAGE : ZRC=0x83000030=-2097151952
CALLED : OS, -, lio_listio
OSERR : ENOTSUP (48) "Operation not supported"
DATA #1 : signed integer, 8 bytes
5
DATA #2 : Hex integer, 4 bytes
0x00000002
DATA #3 : signed integer, 4 bytes
11
DATA #4 : unsigned integer, 8 bytes
3
DATA #5 : unsigned integer, 8 bytes
3
DATA #6 : unsigned integer, 4 bytes
2
DATA #7 : signed integer, 4 bytes
11
DATA #8 : unsigned integer, 8 bytes
32768
DATA #9 : unsigned integer, 8 bytes
192282624
DATA #10: signed integer, 8 bytes
0
......................
2014-02-13-05.52.22.311700-480 E16022786A840 LEVEL:
Critical
PID : 8736 TID : 3819 PROC : db2sysc
0
INSTANCE: inst NODE : 000
EDUID : 3819 EDUNAME: db2pclnr (ECMDBP) 0
FUNCTION: DB2 UDB, RAS/PD component, pdStartFODC, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "Panic".
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
"/XXXX/FODC_Panic_2014-02-13-05.52.22
.311204_0000/". Please look in this directory for
detailed evidence
about what happened and contact IBM support if
necessary to diagnose
the problem. |
****************************************************************
* USERS AFFECTED: *
* DB2FORLUW *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 crashes when function LIO_LISTIO receives OS error *
* ENOTSUP *
* in Solaris *
* *
* Example db2diag.log messages encountered: *
* *
* 2014-02-13-05.52.22.060783-480 E15998196A813 LEVEL: *
* Error *
* (OS) *
* PID : 8736 TID : 3819 PROC : *
* db2sysc *
* 0 *
* INSTANCE: inst NODE : 000 *
* EDUID : 3819 EDUNAME: db2pclnr (ECMDBP) 0 *
* FUNCTION: DB2 UDB, oper system services, *
* sqloDispatchNBlocks, *
* probe:100 *
* MESSAGE : ZRC=0x83000030=-2097151952 *
* CALLED : OS, -, lio_listio *
* OSERR : ENOTSUP (48) "Operation not supported" *
* DATA #1 : signed integer, 8 bytes *
* 5 *
* DATA #2 : Hex integer, 4 bytes *
* 0x00000002 *
* DATA #3 : signed integer, 4 bytes *
* 11 *
* DATA #4 : unsigned integer, 8 bytes *
* 3 *
* DATA #5 : unsigned integer, 8 bytes *
* 3 *
* DATA #6 : unsigned integer, 4 bytes *
* 2 *
* DATA #7 : signed integer, 4 bytes *
* 11 *
* DATA #8 : unsigned integer, 8 bytes *
* 32768 *
* DATA #9 : unsigned integer, 8 bytes *
* 192282624 *
* DATA #10: signed integer, 8 bytes *
* 0 *
* *
* ...................... *
* *
* 2014-02-13-05.52.22.311700-480 E16022786A840 LEVEL: *
* Critical *
* PID : 8736 TID : 3819 PROC : *
* db2sysc *
* 0 *
* INSTANCE: inst NODE : 000 *
* EDUID : 3819 EDUNAME: db2pclnr (ECMDBP) 0 *
* FUNCTION: DB2 UDB, RAS/PD component, pdStartFODC, probe:10 *
* MESSAGE : ADM14001C An unexpected and critical error has *
* occurred: "Panic". *
* 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 *
* "/XXXX/FODC_Panic_2014-02-13-05.52.22 *
* .311204_0000/". Please look in this directory for *
* detailed evidence *
* about what happened and contact IBM support if *
* necessary to diagnose *
* the problem. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 fixpack 10 *
**************************************************************** |
