|
Problem IT37149
|
Status: Closed |
SYSTEM TEMP TABLESPACE CAN BE LEFT IN SQLB_REORG_IN_PROGRESS IF REORGS WERE STARTED, BUT NOT COMPLETED BEFORE CRASH RECOVERY
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
A CLASSIC REORG using a system temporary tablespace that was
started, but not completed, before crash recovery can leave the
tablespace in SQLB_REORG_IN_PROGRESS state after crash recovery
completes.
During crash recovery, the reorg in progress state is not reset.
If the connection to the database is maintained after crash
recovery eg through `RESTART DB `, the tablespace state
is not reset.
After the database is restarted, if the database is deactivated
and reactivated, the tablespace state will be reset. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.1.4.7 *
**************************************************************** |
| Local Fix: |
Deactivate and reactivate the database after crash recovery
completes |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.1.4.7 *
**************************************************************** |
| Comment |
Upgrade to 11.1.4.7 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.06.2021
17.04.2022
17.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
