ALTER TABLESPACE REDUCE can fail with EFIBIG as DB2 did not do a
check, if the SMP page requested is really in use.
db2diag.log will show messages like this:
2014-04-14-08.40.27.835137+120 E7436062A520 LEVEL: Info
PID : 19267982 TID : 14137 PROC :
db2sysc 1
INSTANCE: xxxxxx NODE : 001 DB : xxx
APPHDL : 1-3946 APPID: *xx.xxx.xxxxx
AUTHID : xxxxxx HOSTNAME: xxx
EDUID : 14137 EDUNAME: db2agent (xxx) 1
FUNCTION: DB2 UDB, buffer pool services,
sqlbExtentMovementEntryPoint, probe:5401
DATA #1 : <preformatted>
Extent Movement started on table space 20
2014-04-14-08.40.27.836690+120 E7436583A1379 LEVEL: Error
(OS)
PID : 19267982 TID : 14137 PROC :
db2sysc 1
INSTANCE: xxxxxx NODE : 001 DB : xxx
APPHDL : 1-3946 APPID: *xx.xxx.xxxxx
EDUID : 14137 EDUNAME: db2agent (xxx) 1
FUNCTION: DB2 UDB, oper system services, sqloReadBlocks,
probe:60
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
DIA8312C Disk was full.
CALLED : OS, -, pread
OSERR : EFBIG (27) "File too large"
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes
File Handle = 61
File System Block Size = 4096 bytes
File System Type = jfs2
File Handle Flags :
Require Sector Align = No
DIO/CIO Mode = Yes
Raw Block Device = No
Reserved Handle = No
Flush On Close = No
Thread-Level Lock = No
Write-through Mode = Yes
File Not Tracked = Yes
DATA #2 : unsigned integer, 8 bytes
4294966784
DATA #3 : unsigned integer, 8 bytes
1
DATA #4 : unsigned integer, 4 bytes
14
DATA #5 : File Offset, 8 bytes
16384
DATA #6 : File Offset, 8 bytes
70368735789056
DATA #7 : String, 105 bytes
Search for ossError*Analysis probe point after this log entry
for further
self-diagnosis of this problem.
2014-04-14-08.40.27.847281+120 I7437963A3472 LEVEL: Error
(OS)
PID : 19267982 TID : 14137 PROC :
db2sysc 1
INSTANCE: xxxxxx NODE : 001 DB : xxx
APPHDL : 1-3946 APPID: *xx.xxx.xxxxx
AUTHID : xxxxxx HOSTNAME: xxx
EDUID : 14137 EDUNAME: db2agent (xxx) 1
FUNCTION: DB2 Common, OSSe, ossErrorIOAnalysis, probe:100
CALLED : OS, -, pread
OSERR : EFBIG (27) "File too large"
DATA #1 : String, 146 bytes
A total of 5 analysis will be performed :
- User info
- ulimit info
- Target file info
- I/O attempt
- File system
Target file handle = 61
DATA #2 : String, 188 bytes
Real user ID of current process = 1005
Effective user ID of current process = 1005
Real group ID of current process = 1004
Effective group ID of current process = 1004
DATA #3 : String, 379 bytes
Current process limits (unit in bytes except for nofiles) :
mem (S/H) = unlimited / unlimited
core (S/H) = unlimited / unlimited
cpu (S/H) = unlimited / unlimited
data (S/H) = unlimited / unlimited
fsize (S/H) = unlimited / unlimited
nofiles (S/H) = unlimited / unlimited
stack (S/H) = unlimited / unlimited
rss (S/H) = unlimited / unlimited
DATA #4 : String, 41 bytes
current sbrk(0) value: 0x0000000228e07c20
DATA #5 : String, 266 bytes
Target File Information :
Size = 19327352832
Link = No
Reference path = N/A
Type = 0x8000
Permissions = rw-------
UID = 1005
GID = 1004
Last modified time = 1397456624
DATA #6 : String, 33 bytes
I/O attempt not implemented yet.
DATA #7 : String, 401 bytes
File System Information of the target file :
Block size = 4096 bytes
Total size = 1392374710272 bytes
Free size = 518203109376 bytes
Total # of inodes = 112458968
FS name = N/A
Mount point = /xxx/xxx/xxxxxx/NODE0001
FSID (major,minor)= 15, 2
FS type name = jfs2
DIO/CIO mount opt = None
Device type = N/A
FS type = 0x6
The offset here is 70TB, which explains EFBIG. |
