DB2 - Problembeschreibung
Problem IC70546 | Status: Geschlossen |
DB2 INSTANCE ON SOLARIS CAN BECOME INACCESSIBLE AND ENTER A HUNG STATE. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - 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 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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Solaris * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 instance on solaris can become inaccessible andenter a * * hung state.After a period of activity a DB2 instance * * becameinaccessibleand entered a hung state.Looking at the * * DB2 threads they can been seen to be on asyncI/Orequests. * * However the Solaris async I/O worker threads allappear to be * * idle and waiting on requests.This can be due to a solaris * * defect 6972029 close(-1)cancelsall aio for all open file * * descriptors. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.5 Fixpak 7 or higher * **************************************************************** | |
Local-Fix: | |
Disable ASYNC IO db2set DB2LIOAIODISABLED=true then db2stop & db2start instance. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in DB2 v9.5 Fixpak 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC70549 IC71454 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.08.2010 15.11.2010 15.11.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5. | |
Problem behoben lt. FixList in der Version | |
9.1.0.7 | |
9.5.0.7 |