|
Problem IC92253
|
Status: Closed |
PAGE PREFETCH REQUEST MIGHT FAIL WITH ERROR EFBIG "FILE TOO LARGE" |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
A page prefetch request might fail with operating system error
EFBIG.
The page requested by DB2 is wrong and does not exist in the
tablespace.
You will see an entry like the following in the db2diag.log
file:
2013-05-02-17.57.04.517403+120 E7216A1260 LEVEL:
Error (OS)
PID : 10813602 TID : 13880 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000
HOSTNAME: db2host1
EDUID : 13880 EDUNAME: db2pfchr (SAMPLE) 0
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 = 651
File System Block Size = 4096 bytes
File System Type = jfs2
[...]
DATA #6 : File Offset, 8 bytes
17867064049664
DATA #7 : String, 105 bytes
Search for ossError*Analysis probe point after this log entry
for further
self-diagnosis of this problem.
'DATA #6' from the db2diag.log message indicates a file offset
beyond 16TB. This exceeds the file size limit for the JFS2
filesystem and is the reason why the operating system returns
EFBIG when attempting to read from disk.
The subsequent message logged by function ossErrorIOAnalysis
will show the actual mount point at 'DATA #7'.
Checking your table space containers located on that mountpoint
(using 'ls -lR' or 'db2pd -db <DBNAME> -tablespaces' or similar
commands) will show that none of your containers actually
exceeds the size of 16TB. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 FixPack 3. *
**************************************************************** |
| Local Fix: |
- db2set DB2_REDUCED_OPTIMIZATION="DATA_PREFETCHING RA_OFF"
- db2stop
- db2start |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fist fixed in DB2 version 10.1 FixPack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.05.2013
01.10.2013
01.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
