Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC81357 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
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.
Problem Summary:
**************************************************************** 
* 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.
available fix packs:
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

Solution
Apply Version 9.7 Fixpack 6.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.02.2012
04.06.2012
04.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.