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 IC81357 Status: Geschlossen

RESTARTING A TABLESPACE ROLLFORWARD AFTER HITTING AN 'OUT OF LOG
SPACE' ERROR MAY CAUSE THE DATABASE TO CRASH.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
If a tablespace rollforward fails in the undo phase due to 
hitting "out of log space" error, the affected tablespace will 
be removed from the tablespace list. But once the rollforward is 
complete, this tablespace will be left in rollforward in 
progress state. This is incorrect, since rollforward on this 
tablespace cannot be resumed (since DB2 no longer has the 
lowtran and minbuff information needed to continue). The 
rollforward on this tablespace must be cancelled, but there is 
no indication given to the customer to do this. If the 
rollforward is not canceled and instead a different set of 
tablespaces are rolled forward, that rollforward will fail with 
SQL4908 (or other errors) due to this tablespace being left in 
rollforward in progress state.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of tablespace rollforward.                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If a tablespace rollforward fails in the undo phase due to   * 
* hitting "out of log space" error, the affected tablespace    * 
* will                                                         * 
* be removed from the tablespace list. But once the            * 
* rollforward is                                               * 
* complete, this tablespace will be left in rollforward in     * 
* progress state. This is incorrect, since rollforward on this * 
* tablespace cannot be resumed (since DB2 no longer has the    * 
* lowtran and minbuff information needed to continue). The     * 
* rollforward on this tablespace must be cancelled, but there  * 
* is                                                           * 
* no indication given to the customer to do this. If the       * 
* rollforward is not canceled and instead a different set of   * 
* tablespaces are rolled forward, that rollforward will fail   * 
* with                                                         * 
* SQL4908 (or other errors) due to this tablespace being left  * 
* in                                                           * 
* rollforward in progress state.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply Version 9.7 Fixpack 6.                                 * 
****************************************************************
Local-Fix:
Cancel the tablespace rollforward that failed due to out of log 
space, before issuing any more tablespace rollfoward commands.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Apply Version 9.7 Fixpack 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.02.2012
04.06.2012
04.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList