DB2 - Problem description
Problem IC61577 | Status: Closed |
SQLO_DERR "DISK ERROR OCCURRED (DOS)" WARNING MESSAGES IN DB2DIAG.LOG AFTER TRYING TO ATTACH TO DB2 INSTANCE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
OS returns EIO error when DB2 tries to attach to the instance, which requires locking of the instance seed file. If the seed file is somehow unavailable, the following db2diag.log message may appear. An example of instance attachment would be ATTACH TO command as well as GET DBM CFG SHOW DETAIL. 2009-02-05-09.06.26.597549-300 E802279E500 LEVEL: Warning (OS) PID : 31700 TID : 183046802080PROC : db2agent (idle) 1 INSTANCE: db2inst1 NODE : 001 APPHDL : 1-1068 APPID: AA123456.1234.0123456789 FUNCTION: DB2 UDB, oper system services, sqloflock, probe:100 MESSAGE : ZRC=0x860F0003=-2045837309=SQLO_DERR "disk error occurred (DOS)" DIA8402C A disk error has occurred. CALLED : OS, -, fcntl OSERR: EIO (5) Please note that this is not a severe error. Databases will function normally, and only the instance attachment may fail. Also, this error message may happen in other normal situations where DB2 was unable to lock a file. The APAR fix will remove the need of seed file locking. | |
Problem Summary: | |
OS returns EIO error when db2 tries to attach to the instance. | |
Local Fix: | |
Try to attach to the instance later. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Fixed in db2 v9.7 FP1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.06.2009 16.12.2009 16.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |