Hi all,
I am getting these errors almost everyday. They generally occur after a scheduled bulk update that happens every night.
here's the error:
2006-06-06-01.16.29.345017-300 E452459A664 LEVEL: Error
PID : 4268212 TID : 1 PROC : db2pfchr 0
INSTANCE: xyz NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbWritePageToDisk, probe:20
MESSAGE : ADM6017E The table space "TEMP16K" (ID "4") is full. Detected on
container "/prod1/sms/tmp/tmp16k" (ID "0"). The underlying
file system is full or the maximum allowed space usage for the file
system has been reached. It is also possible that there are user
limits in place with respect to maximum file size and these limits
have been reached.
2006-06-06-01.16.29.345327-300 I453124A292 LEVEL: Error
PID : 4268212 TID : 1 PROC : db2pfchr 0
INSTANCE: xyz NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbWritePageToDisk, probe:20
MESSAGE : Cont page = 82816 ObjID=5 ObjType=128
2006-06-06-01.16.29.345518-300 E453417A666 LEVEL: Error
PID : 4268212 TID : 1 PROC : db2pfchr 0
INSTANCE: xyz NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloseekwrite64, probe:100
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
DIA8312C Disk was full.
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes
0x0FFFFFFFFFFFD310 : 0000 000E 0000 0000 ........
DATA #2 : unsigned integer, 8 bytes
16384
DATA #3 : signed integer, 8 bytes
1353777152
DATA #4 : unsigned integer, 8 bytes
40
DATA #5 : Hex integer, 4 bytes
0x0000001C
DATA #6 : signed integer, 8 bytes
-1
----------------------------------------------------------
Now the thing is that the location for container mentioned in the error is not full, its just using 2-3% of the space allocated to it.
So I am not understanding where the problem resides. I hope I can get some advice from here.
Also I would like to know the impact of these errors??
Anks