IC92253: PAGE PREFETCH REQUEST MIGHT FAIL WITH ERROR EFBIG "FILE TOO LARGE"

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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.
    

Local fix

  • - db2set DB2_REDUCED_OPTIMIZATION="DATA_PREFETCHING RA_OFF"
    - db2stop
    - db2start
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version 10.1 FixPack 3.                       *
    ****************************************************************
    

Problem conclusion

  • Fist fixed in DB2 version 10.1 FixPack 3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC92253

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-13

  • Closed date

    2013-10-01

  • Last modified date

    2013-10-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.1

Reference #:

IC92253

Modified date:

2013-10-01

Translate my page

Machine Translation

Content navigation