Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2002
    Posts
    2

    Unanswered: DB2 Disk Full Error

    Hello,

    We encounter a problem from time to time with our db2 udb6.1 database. It creates a huge file ( about 15 G) in the directory c:\sqllib\db2\ . The file extension is ".0" (for example 129.0). At about the same time it logs an error message into db2diag.log which has

    2002-02-06-16.49.34.828000 Instance:DB2 Node:000
    PID:105(db2syscs.exe) TID:348 Appid:*LOCAL.DB2.020205113537
    lob_manager sqldx_diskwrite Probe:105 Database:WAS
    DIA3612C Disk was full.

    ZRC=FFFFD60C

    2002-02-06-16.49.35.500000 Instance:DB2 Node:000
    PID:105(db2syscs.exe) TID:348 Appid:*LOCAL.DB2.020205113537
    lob_manager sqldx_diskwrite Probe:105 Database:WAS

    DATA1
    ac10 0200 0100 0000 0400 0000 ...........


    2002-02-06-16.49.36.062000 Instance:DB2 Node:000
    PID:105(db2syscs.exe) TID:348 Appid:*LOCAL.DB2.020205113537
    lob_manager sqldxWriteLobData Probe:30 Database:WAS
    DIA3612C Disk was full.

    ZRC=FFFFD60C

    Can some one please help us with a way out? What is a ".0" file ? why does it get created? Does the error get logged in db2diag.log after ".0" is created and it fills up the hard drive?

    Any help is greatly appreciated.

    Thanks in advance,
    Sri.

  2. #2
    Join Date
    Feb 2002
    Posts
    96

    Re: DB2 Disk Full Error

    Hi,
    This error will happen when, your archive log directory/disk is full.
    Goto the directory(Run DATABASE CONFIGURATION to get the log file path). Delete all the log files or move those files somewhere (Note : Do not delete/move the First Active Log file). Regards.



    Originally posted by sl95
    Hello,

    We encounter a problem from time to time with our db2 udb6.1 database. It creates a huge file ( about 15 G) in the directory c:\sqllib\db2\ . The file extension is ".0" (for example 129.0). At about the same time it logs an error message into db2diag.log which has

    2002-02-06-16.49.34.828000 InstanceB2 Node:000
    PID:105(db2syscs.exe) TID:348 Appid:*LOCAL.DB2.020205113537
    lob_manager sqldx_diskwrite Probe:105 Database:WAS
    DIA3612C Disk was full.

    ZRC=FFFFD60C

    2002-02-06-16.49.35.500000 InstanceB2 Node:000
    PID:105(db2syscs.exe) TID:348 Appid:*LOCAL.DB2.020205113537
    lob_manager sqldx_diskwrite Probe:105 Database:WAS

    DATA1
    ac10 0200 0100 0000 0400 0000 ...........


    2002-02-06-16.49.36.062000 InstanceB2 Node:000
    PID:105(db2syscs.exe) TID:348 Appid:*LOCAL.DB2.020205113537
    lob_manager sqldxWriteLobData Probe:30 Database:WAS
    DIA3612C Disk was full.

    ZRC=FFFFD60C

    Can some one please help us with a way out? What is a ".0" file ? why does it get created? Does the error get logged in db2diag.log after ".0" is created and it fills up the hard drive?

    Any help is greatly appreciated.

    Thanks in advance,
    Sri.

  3. #3
    Join Date
    Feb 2002
    Posts
    33
    Hi. Actually this doesn't look like something related to log files. On NT, depending on the instance name, the diagnostic directory will be
    <drive>:\sqllib\<instance name>.

    It looks like you are hitting a scenario where a dump file is being generated.

    Is that all you see being generated in the db2diag.log? Are there any messages before the diskfull problem? Also, you should check for V6 apars, if I remember correctly there was a fix for finer control of diagnostic filesizes.

  4. #4
    Join Date
    Feb 2002
    Posts
    2
    Thanks for the information. We did find a fix pack and it seems to have fixed the disk full problem for now. But we are still curious as to why this huge dump file is being created. I'm adding the log file as an attachment. Please let us know if you have any ideas as to whats going on!

    Thanks again for your help.

  5. #5
    Join Date
    Feb 2002
    Posts
    33
    Hi, I can't seem to find the attachment... i must be looking for it incorrectly.

Posting Permissions

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