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

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
DB2 UDB V9.7 FP5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.09.2011
08.12.2011
08.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList