|
Problem IC72741
|
Status: Closed |
SUBSEQUENT DROP TABLESPACE/RESTORE WITH REBUILD OPTION FOR AUTOMATIC STORAGE TABLESPACE MAY CRASH THE INSTANCE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When the database is dropped or when database is restored on
different server using restore with rebuild option you may
notice this issue. The instance may crash when you restore
automatic storage tablespace or drop the tablespace after
successfully restoring syscatspace.
Simple repro:
db2 terminate
db2 drop db SAMPLE
rm -rf logdir logdir.backup backup1 backup2 backup3
$HOME/sqllib/db2dump/*
mkdir logdir backup1 backup2 backup3
db2sampl
db2 update db cfg for SAMPLE using LOGRETAIN ON TRACKMOD ON
NEWLOGPATH $PWD/logdir
db2 backup db SAMPLE to /dev/null
db2 backup db SAMPLE tablespace (SYSCATSPACE) online to
$PWD/backup1 compress include logs
db2 backup db SAMPLE tablespace (USERSPACE1) online incremental
delta to $PWD/backup2 compress include logs
db2 backup db SAMPLE online to $PWD/backup3 compress include
logs
cp -R logdir logdir.backup
db2 drop db SAMPLE
db2 restore db SAMPLE rebuild with all tablespaces in image from
$PWD/backup1
db2 rollforward db SAMPLE to end of logs overflow log path
($PWD/logdir.backup)
db2 rollforward db SAMPLE complete overflow log path
($PWD/logdir.backup)
db2 connect to sample
db2 drop tablespace userspace1
SQL1224N The database manager is not able to accept new
requests, has
terminated all requests in progress, or has terminated the
specified request
because of an error or a forced interrupt. SQLSTATE=00000
Crash with following stacks:
0 sqlbAdjustPathsForReleasedContainers
1 sqlbDMSFreePoolContainers
2 sqlbDMSDropPool
3 sqlbDropPoolAct
4 storMgrAction
5 sqldmpnd
6 sqlptppl
7 sqlpxcm1
8 sqlrrcom_dps
9 sqlrrcom
10 sqlrr_commit
11 sqljs_ddm_rdbcmm
12 sqljsParseRdbAccessed
13 sqljsParse
14 sqljsSqlam
15 sqljsDriveRequests
16 sqljsDrdaAsInnerDriver
17 sqljsDrdaAsDriver
18 sqeAgent::RunEDU
19 sqzEDUObj::EDUDriver
20 sqlzRunEDU
21 sqloEDUEntry
or
db2 "restore db sample tablespace (USERSPACE1) online
incremental automatic from $PWD/backup2"
SQL1224N The database manager is not able to accept new
requests, has
terminated all requests in progress, or has terminated the
specified request
because of an error or a forced interrupt. SQLSTATE=00000
Crash with following stacks:
0 sqlbAdjustPathsForReleasedContainers
1 sqlbDMSFreePoolContainers
2 sqlbEmptyOrRemovePoolI
3 sqlbRemovePool
4 sqlbRestorePoolDef
5 sqludProcessSPCS
6 sqludBMInit
7 sqludbuf
8 sqloEDUEntry
The reason for failure is at the time of restoring USERSPACE1
tablespace is still not fully set up, more specifically its
containers are still not defined. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using automatic storage tablespace. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Database may crash during restore with rebuild option if the *
* tablespace is created as Automatic storage. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 fix Pack 4. *
**************************************************************** |
| Local Fix: |
Restoring all the required tablespaces in the first restore
rebuild option does not crash the instance. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 |
First fixed in DB2 Version 9.7 fix Pack 4. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC72898
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.11.2010
14.01.2013
14.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
