My db2 database crashed last night

HiAll.
My db2 database crashed last night is it to do with the disk full or locking issue;My error log is:

2010-08-18-18.19.13.481000+060 I131553H601        LEVEL: Severe
PID     : 6780                 TID  : 3136        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : CDB
APPHDL  : 0-990                APPID: 192.168.0.35.31236.100814040042
AUTHID  : PCMS_DATA_MANAGER
FUNCTION: DB2 UDB, buffer pool services, sqlbReadPage, probe:1141
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
          DIA8312C Disk was full.
DATA #1 : <preformatted>
Failed to read page from disk on attempt number 2.
Retrying operation. Only subsequent failures will be logged.
 
2010-08-18-18.19.13.497000+060 I132156H387        LEVEL: Error
PID     : 6780                 TID  : 1812        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbClnrAsyncWriteCompletion, probe:40
MESSAGE : ZRC=0x870F000E=-2029060082=SQLO_LOCK "ERROR_LOCK_VIOLATION (DOS)"
          DIA8511C A locked file was encountered.
 
2010-08-18-18.19.13.544000+060 I132545H2385       LEVEL: Severe
PID     : 6780                 TID  : 1812        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbClnrAsyncWriteCompletion, probe:300
DATA #1 : String, 13 bytes
*ioRequest =
DATA #2 : Hexdump, 76 bytes
0x13744A04 : 0301 0000 0000 0000 0080 3900 0000 0000    ..........9.....
0x13744A14 : 0000 0000 0000 0000 947C 576E 6088 900E    .........|Wn`...
0x13744A24 : E049 7413 0000 0000 4431 7413 00C0 F70E    .It.....D1t.....
0x13744A34 : 0010 0000 500F 0000 0000 0000 90E0 7F02    ....P...........
0x13744A44 : 0000 0000 0200 0000 0E00 0F87              ............
LVL 1
hraja77Asked:
Who is Participating?
 
gmarinoCommented:
Sorry - cut-n-past error above...here's what I should have posted:


This could occur when using
a)  Virus Checking software - in  which case you need to make sure the  folder where the database's tablespace containers are defined in is  excluded from the RealTime virus checking  process AND blocked from use  from any other user other than the db2  instance/admin id
-OR-
b) Backup software where the software locks the file while it is taking a back up of the file.

- Greg
0
 
hraja77Author Commented:
can the disk full cause db2 to crash ?
0
 
gmarinoCommented:
This is the same issue you had before that you posted in ID: 26405595

The error suggests that there is another process locking the database files - this time the file is the one that contains your data instead of the file used for Logging.  This could occur when using
a)  Virus Checking software - in which case you need to make sure the  folder defined in LOGPATH is excluded from the RealTime virus checking  process AND blocked from use from any other user other than the db2  instance/admin id
-OR-
b) Backup software where the software locks the file while it is taking a back up of the file.

For more information on this issue and how to resolve it, read this:

http://www-01.ibm.com/support/docview.wss?uid=swg21225179


You obviously need to get this 3rd Party software problem resolved.

- Greg
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
hraja77Author Commented:
thanks greg - i appreciate what your saying its just that the sysadmins did not exclude all the files for o/s backups - they have done that as of today - i just want to check one point before assiging points - can the disk full error message above cause a db crash ?
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
          DIA8312C Disk was full.

thanks
H
0
 
hraja77Author Commented:
i'll assign the points anyway as you have been very helpfull - so thanks for that - but i would appreciate an answer to the comment about the disk full error above

thanks
H
0
 
hraja77Author Commented:
thanks
0
 
gmarinoCommented:
It seems that in THIS case, DB2 crashed.  But that was due to the LACK OF ACCESS to the file, not because the disk was full.  (FILE LOCKED behaves similar to DISK FULL.)

In this case it seems the BufferPool's IO Cleaners (sqlbClnrAsyncWriteCompletion) could not write "dirty" pages (pages with changes to the data on them) out to the tablespace's files/containers.  

I can see how thissituation would cause DB2 to crash - if the Bufferpool's space was needed for another SQL process and those BP pages could not be accessed because they contained data that needed to be first written to disk before they could be reused.

- Greg
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.