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

DATABASE UPGRADE FAILS

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Database upgrade fails when moving from a lower version DB2 to a 
newer versions due to a tablespace issue. The DB2 diag log will 
show something similar to: 
 
2015-01-28-00.11.45.571417-300 I63108585E667         LEVEL: 
Error 
PID     : 29895                TID : 46913067936064  PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-8                  APPID: 
*LOCAL.db2inst1.123456789123 
AUTHID  : db2inst1             HOSTNAME: sample 
EDUID   : 18                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, buffer pool services, sqlbMigrateFiles, 
probe:100 
MESSAGE : ZRC=0x870201A8=-2029911640=SQLB_INV_SG_ID 
          "Invalid storage group identified found." 
DATA #1 : unsigned integer, 4 bytes 
2 
DATA #2 : File name, 53 bytes 
/home/db2inst1/db2inst1/NODE0000/SQL00001/MEMBER0000/ 
 
2015-01-28-00.11.45.571799-300 I63109253E508         LEVEL: 
Warning 
PID     : 29895                TID : 46913067936064  PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-8                  APPID: 
*LOCAL.db2inst1.123456789123 
AUTHID  : db2inst1             HOSTNAME: sample 
EDUID   : 18                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, base sys utilities, sqle_remap_errors, 
probe:100 
DATA #1 : <preformatted> 
ZRC 0x800208ab remapped to SQLCODE -1704 
 
2015-01-28-00.11.45.722959-300 I63109762E584         LEVEL: 
Severe 
PID     : 29895                TID : 46913067936064  PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-8                  APPID: 
*LOCAL.db2inst1.123456789123 
AUTHID  : db2inst1             HOSTNAME: sample 
EDUID   : 18                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::FirstConnect, probe:7889 
RETCODE : 
ZRC=0x800208AB=-2147350357=SQLB_UPGRADE_INVALID_TABLESPACE_STATE 
          "Table space state is invalid for upgrade." 
 
Steps to recreate the problem: 
 
1.) Create a database under an older version of DB2. 
2.) Create STOREGROUP for that new database: 
db2 "CREATE STOGROUP HIGHEND ON '/tmp/spcs/'" 
3.) Create tablespace under that new STOREGROUP: 
db2 "CREATE TABLESPACE USERSPACE4 MANAGED BY DATABASE USING 
(FILE '/tmp/spcs/file1' 1 M)"; 
4.) Create another tablespace under that same path: 
db2 "CREATE TABLESPACE USERSPACE5 MANAGED BY DATABASE USING 
(FILE '/tmp/spcs/file1' 1 M)"; 
5.) Drop the older tablesspace (not the newer one) 
db2 drop tablespace USERSPACE4 
6.) Drop the storage group 
db2 drop STOGROUP HIGHEND 
7.) Disconnect from the database and stop DB2, and upgrade the 
database and instance. 
8.) Upgrade will fail due to the tablespace issue.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DATABASE UPGRADE FAILS                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First fixed in fix pack 7 of v10.5                           * 
****************************************************************
Local-Fix:
Lösung
First fixed in fix pack 7 of v10.5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.01.2015
21.01.2016
21.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList