|
Problem IC71454
|
Status: Closed |
DB2 INSTANCE ON SOLARIS CAN BECOME INACCESSIBLE AND ENTER A HUNG STATE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
DB2 instance on solaris can become inaccessible and
enter a hung state.
After a period of activity a DB2 instance became inaccessible
and entrered a hung state.
Looking at the DB2 threads they can been seen to be on async I/O
requests. However the Solaris async I/O worker threads all
appear to be idle and waiting on requests.
This can be due to a solaris defect 6972029 close(-1) cancels
all aio for all open file descriptors. |
| Problem Summary: |
DB2 instance on solaris can become inaccessible and
enter a hung state. |
| Local Fix: |
Disable ASYNC IO
db2set DB2LIOAIODISABLED=true
then db2stop & db2start instance. |
| Solution |
First Fixed in v9.8FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.09.2010
11.02.2011
11.02.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
