home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC82267 Status: Geschlossen

DB2 AGENT HANG IN SQLPGWAITFORLRECONDISK DUE TO MISSING POST.

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
In rare conditions, a db2agent may be stuck in following call 
stacks due to missing post during writing log records into disk. 
 
  sqlpgWaitForLrecOnDisk + 0x330 
  sqlpWriteToLog + 0x7D8 
  sqlpWriteLR + 0x418 
 
The above stacks should be observed in a stack file(use db2pd 
-stack all to generate stack files) for several rounds for a 
long time. 
 
If this db2agent had obtained some latches, then there is a 
chance to hang database due to latch wait cascaded.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All.                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to version 9.1 fixpack 12.                            * 
****************************************************************
Local-Fix:
No known work around.
Lösung
This problem is first fixed in db2 version 9.1 fixpack 12.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC87822 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.03.2012
02.08.2012
02.08.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP12
Problem behoben lt. FixList in der Version
9.1.0.12 FixList