DB2 - Problembeschreibung
Problem IC96500 | Status: Geschlossen |
INSTANCE CRASH DURING CRASH RECOVERY IF INFLIGHT ONLINE REORG WORKLOAD AND TABLE SPACE IS INACCESSIBLE. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
At the time of a database crash, if there is an online reorg in progress and before the ensuing database crash recovery the table space in which the reorg is taking place in becomes inaccessible, the crash recovery may crash the DB2 instance attempting to compensate the online reorg transaction with the follow stack: sqldOLRTerminate <unknown> sqldomUndo sqldmund sqlptudo sqlprudm sqlprbck sqlprDbBackwardPhase sqlprecm sqlpresr | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * At the time of a database crash, if there is an online reorg * * in progress and before the ensuing database crash recovery * * the table space in which the reorg is taking place in * * becomes inaccessible, the crash recovery may crash the DB2 * * instance attempting to compensate the online reorg * * transaction with the follow stack: * * * * sqldOLRTerminate * * <unknown> * * sqldomUndo * * sqldmund * * sqlptudo * * sqlprudm * * sqlprbck * * sqlprDbBackwardPhase * * sqlprecm * * sqlpresr * **************************************************************** * RECOMMENDATION: * * To resolve the problem, either try the work around of fixing * * the table space issue before the database crash recovery or * * upgrade to Version 10.5 Fix Pack 3. * **************************************************************** | |
Local-Fix: | |
A work around would be to solve the table space issue first before doing database crash recovery. | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 10.5 Fix Pack 3. At a minimum, this fix should be applied on the server. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC97849 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 30.09.2013 02.10.2013 02.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |