home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC78854 Status: Closed

PANIC IN SQLBALTERPOOLACT WHILE DMS -> AS CONVERSION LOG RECORD WAS
REPLAYED FOR A TABLESPACE DURING DB ROLLFORWARD AND THE TABL

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If a DMS tablespace was converted to AS during redirected 
database restore and was subsequently DMS -> AS conversion log 
record was replayed for it during database rollforward then we 
panic. 
 
Here is the quick repro for this problem: 
db2 -v "connect to x" 
db2 -v "create tablespace as1" 
db2 -v "create tablespace dms1 managed by database using (file 
'file1' 1M)" 
tbsp_id=`db2 -x +n "select tbspaceid from sysibm.systablespaces 
where tbspace='DMS1'"` 
db2 -v "terminate" 
 
db2 -v "backup db x" 
db2 -v terminate 
 
db2 -v "connect to x" 
db2 -v "alter tablespace dms1 managed by automatic storage" 
db2 -v terminate 
 
db2 -v "restore db x redirect without prompting" 
db2 -v "set tablespace containers for 3 using automatic storage" 
db2 -v "restore db x continue" 
db2 -v "rollforward db x to end of logs and stop"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB V9.7, all platforms                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If a DMS tablespace was converted to AS during redirected    * 
*                                                              * 
* database restore and was subsequently DMS -> AS conversion   * 
* log                                                          * 
* record was replayed for it during database rollforward then  * 
* we                                                           * 
* panic.                                                       * 
*                                                              * 
* Here is the quick repro for this problem:                    * 
*                                                              * 
* db2 -v "connect to x"                                        * 
*                                                              * 
* db2 -v "create tablespace as1"                               * 
*                                                              * 
* db2 -v "create tablespace dms1 managed by database using     * 
* (file                                                        * 
* 'file1' 1M)"                                                 * 
*                                                              * 
* tbsp_id=`db2 -x +n "select tbspaceid from                    * 
* sysibm.systablespaces                                        * 
* where tbspace='DMS1'"`                                       * 
*                                                              * 
* db2 -v "terminate"                                           * 
*                                                              * 
*                                                              * 
*                                                              * 
* db2 -v "backup db x"                                         * 
*                                                              * 
* db2 -v terminate                                             * 
*                                                              * 
*                                                              * 
*                                                              * 
* db2 -v "connect to x"                                        * 
*                                                              * 
* db2 -v "alter tablespace dms1 managed by automatic storage"  * 
*                                                              * 
* db2 -v terminate                                             * 
*                                                              * 
*                                                              * 
*                                                              * 
* db2 -v "restore db x redirect without prompting"             * 
*                                                              * 
* db2 -v "set tablespace containers for 3 using automatic      * 
* storage"                                                     * 
* db2 -v "restore db x continue"                               * 
*                                                              * 
* db2 -v "rollforward db x to end of logs and stop"            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB V9.7 FP5                                  * 
****************************************************************
Local Fix:
available fix packs:
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
DB2 UDB V9.7 FP5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.09.2011
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList