|
Problem IC99076
|
Status: Closed |
DB2AIOTHR SEEMS TO STUCK IN THE SOLARIS KERNEL |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 entered 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: |
****************************************************************
* USERS AFFECTED: *
* Solaris *
****************************************************************
* 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 entered 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. *
****************************************************************
* RECOMMENDATION: *
* Disable ASYNC IO by setting the following registry variable: *
* *
* db2set DB2LIOAIODISABLED=true *
* *
* This requires the instance to be restarted. *
**************************************************************** |
| Local Fix: |
Disable ASYNC IO by setting the following registry variable:
db2set DB2LIOAIODISABLED=true
This requires the instance to be restarted. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.01.2014
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
