|
Problem IC73648
|
Status: Closed |
Input Output(AIO) error occurred in DB2 PAGECLEANER thread/process may crash the db2 instance |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In IBM DB2 product, page cleaning mechanism depends on the
Operating System's sub-system - Asynchronous Input Output (AIO).
Any error at that AIO layer in Operating System will cause
errors in page cleaners of DB2.
Many times the AIO errors are so transient and reproduced very
rarely that it become tough for the Support analysts to
efficiently find the root cause of the AIO errors.
The fix of this APAR will retry the failed Asynchronous
operation again with a Synchronous one. So if it's a pure
Asynchronous IO transient issue, it will not cause DB2 to crash
with Panic.
This issue can be diagnosed by Error- EIO (5) in db2diag log
messages.
One of the example on Linux platform could be similar to :
2010-09-08-06.17.39.724804-300 E1487E845 LEVEL:
Error(OS)
PID : 11118 TID : 47963275520320PROC :db2sysc
0
INSTANCE: <inst_name> NODE : 000
EDUID : 218 EDUNAME: db2pclnr (<db_name>) 0
FUNCTION: DB2 UDB, oper system services,
sqloLioAIOCollect,probe:100
MESSAGE : ZRC=0x860F0003=-2045837309=SQLO_DERR "disk error
occurred (DOS)"
DIA8402C A disk error has occurred.
CALLED : OS, -, aio_return OSERR: EIO (5)
<=== |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* It can happen in any DB2 database setup as the issue is *
* faced in page cleaner mechanism of DB2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* The problem is experienced by users as a Panic in the *
* database due to a failed operation in page cleaning. *
* And, it will show a Operating System error number in the *
* db2diag.log while performing AIO at Operating System *
* level *
****************************************************************
* RECOMMENDATION: *
* To avoid experiencing this issue users can upgrade to DB2 *
* Version V9.7 fix pak 4 at the minimum. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in DB2 Version V9.7 fix pak 4
After the fix the end users will not find any difference in the
functioning. Only it will not Panic in case of any AIO error
experienced at the Operating System level |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.01.2011
09.05.2011
09.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
