DB2 - Problembeschreibung
Problem IC99076 | Status: Geschlossen |
DB2AIOTHR SEEMS TO STUCK IN THE SOLARIS KERNEL | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 30.01.2014 02.06.2014 02.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |