Results 1 to 9 of 9
  1. #1
    Join Date
    Jul 2009
    Location
    USA
    Posts
    53

    Unanswered: error in db2diag.log and crash

    We have DB2 v8.2 on AIX. Getting following error in the db2diag.log and the instance comes down.

    FUNCTION: DB2 UDB, oper system services, sqloseekwrite64, probe:40
    MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
    DIA8312C Disk was full.
    CALLED : OS, -, unspecified_system_function
    OSERR : EFBIG (27) "File too large"


    Has anyone encountered this error before?

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Jul 2009
    Location
    USA
    Posts
    53
    I checked this link. Our filesystem is JFS2 and ulimit is unlimitted.

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by db2aix
    I checked this link. Our filesystem is JFS2 and ulimit is unlimitted.
    ...and it was created with large file support, right?
    ---
    "It does not work" is not a valid problem statement.

  5. #5
    Join Date
    Jul 2009
    Location
    USA
    Posts
    53
    According to our AIX SA, large file support is for JFS only. JFS2 don't need this to be set.

  6. #6
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    Do you see some more information on the specific file that shall be accessed? Maybe it is for log files and not data containers or something else altogether?
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  7. #7
    Join Date
    Jul 2009
    Location
    USA
    Posts
    53
    db2diag.log doesn't show the specific file name. This is what I see after EFBIG error:

    CALLED : OS, -, unspecified_system_function
    OSERR : EFBIG (27) "File too large"
    DATA #1 : Device number, 8 bytes
    9223372221538369537
    DATA #2 : Inode number, 8 bytes
    611
    DATA #3 : File mode, 4 bytes
    33152
    DATA #4 : User id, 4 bytes
    5100
    DATA #5 : User id, 4 bytes
    5100
    DATA #6 : File size, 8 bytes
    63963136000
    DATA #7 : soft file resource limit, 8 bytes
    1073741312
    DATA #8 : hard file resource limit, 8 bytes
    1073741312


    I'll increase the diaglevel.

  8. #8
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by db2aix
    DATA #4 : User id, 4 bytes
    5100
    DATA #5 : User id, 4 bytes
    5100
    DATA #6 : File size, 8 bytes
    63963136000
    DATA #7 : soft file resource limit, 8 bytes
    1073741312
    DATA #8 : hard file resource limit, 8 bytes
    1073741312
    I think the above tells you everything you need to know.

    The ulimit does not seem to be "unlimited", after all.
    ---
    "It does not work" is not a valid problem statement.

  9. #9
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    ulimit may be set to unlimited but that is not what was in effect when the error occured. Please check the following technote:
    IBM - Why are the instance owner ulimits ignored when the instance is started with the DB2 fault monitor?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •