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

MIGRATION TO V9.7 MAY HANG TRYING TO SCAN CATALOG TABLE
SYSIBM.SYSTABLESPACES IF ITS INDEXES ARE MARKED INVALID.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When migrating to v9.7, the root page of an index is also 
migrated. If db2 does not find enough space on the root page to 
migrate it, it will mark the index invalid.  These indexes are 
rebuilt in the later part of the migration. 
. 
. 
Similarly, When there isn't enough space on the root page of the 
indexes on SYSIBM.SYSTABLESPACES, we mark the indexes invalid. 
You will see following db2diag.log entry: 
. 
. 
FUNCTION: DB2 UDB, index manager, sqliMigrateRootPage, 
probe:8796043655424 
DATA #1 : <preformatted> 
Index will be marked to be rebuilt and migration will 
continue. 
Root page=5 index IID= 4 
TableSpaceID=0 TableId=16 Index_TableSpaceId=0 
Index_ObjectId=16 
. 
. 
In this case tableid=16, tablespaceid=0 refers to table 
SYSIBM.SYSTABLESPACES. 
. 
. 
Later in the migration where we try to scan the catalog table 
with the bad index, we get stuck into a loop with the following 
entries repeating in the db2diag.log: 
. 
. 
FUNCTION: DB2 UDB, data management, sqldLoadTCB, probe:7390^M 
MESSAGE : ADM5572I  One or more indexes on table 
"TBSPACEID=0.TABLEID=16" are marked invalid and require 
rebuilding. 
.
Problem-Zusammenfassung:
When migrating to v9.7, the root page of an index is also 
migrated. If db2 does not find enough space on the root page to 
migrate it, it will mark the index invalid.  These indexes are 
rebuilt in the later part of the migration. 
. 
. 
Similarly, When there isn't enough space on the root page of the 
indexes on SYSIBM.SYSTABLESPACES, we mark the indexes invalid. 
You will see following db2diag.log entry: 
. 
. 
FUNCTION: DB2 UDB, index manager, sqliMigrateRootPage, 
probe:8796043655424 
DATA #1 : <preformatted> 
Index will be marked to be rebuilt and migration will 
continue. 
Root page=5 index IID= 4 
TableSpaceID=0 TableId=16 Index_TableSpaceId=0 
Index_ObjectId=16 
. 
. 
In this case tableid=16, tablespaceid=0 refers to table 
SYSIBM.SYSTABLESPACES. 
. 
. 
Later in the migration where we try to scan the catalog table 
with the bad index, we get stuck into a loop with the following 
entries repeating in the db2diag.log: 
. 
. 
FUNCTION: DB2 UDB, data management, sqldLoadTCB, probe:7390^M 
MESSAGE : ADM5572I  One or more indexes on table 
"TBSPACEID=0.TABLEID=16" are marked invalid and require 
rebuilding.
Local-Fix:
REORG or recreate indexes on SYSIBM.SYSTABLESPACES before the 
migration.  This will create enough space on the root page to 
allow the migration or the root page. Hence, the index will not 
be marked invalid.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
Defect   => wsdbu00604952 
Fixed in => V9.7 + FP2 
Module   => ENGN_SQRL
Workaround
REORG or recreate indexes on SYSIBM.SYSTABLESPACES before the 
migration.  This will create enough space on the root page to 
allow the migration or the root page. Hence, the index will not 
be marked invalid.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.12.2009
10.06.2010
10.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.2 FixList