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 IC69919 Status: Closed

DATABASE UPGRADE TO 9.7 FAILS WITH SQL1042C DUE TO ERROR SQLB_BPSE
IN SQLBMIGRATEPOOLONDISK

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
An attempt to upgrade a database to the current release results 
in SQL1042C: 
 
db2 upgrade database SAMPLE 
SQL1042C  An unexpected system error occurred.  SQLSTATE=58004 
 
The DB2 diagnostic log will contain messages similar to: 
 
2010-05-21-14.00.58.921136+600 I1713A271          LEVEL: Warning 
PID     : 4571298              TID  : 1           PROC : db2bp 
INSTANCE: db2inst1             NODE : 001 
EDUID   : 1 
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:10 
MESSAGE : Begin engn migration 
 
2010-05-21-14.00.58.955486+600 I1985A579          LEVEL: Error 
PID     : 4366432              TID  : 3086        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 1-100                APPID: *N1.db2inst1.100521040058 
AUTHID  : DB2INST1 
EDUID   : 3086                 EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbMigratePoolOnDisk, 
probe:40 
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
DATA #1 : unsigned integer, 4 bytes 
0 
 
The failure happens due to a zero flavour found in the SQLSPCS.* 
files in the database directory 
 
Zeroed out flavour is a typical symptom of APAR IY95013, where 
during restore on 9.1 we are forgetting to set the flavour to 
the right value for deleted tablespaces. Such an entry can 
survive several releases since typically we do not care about 
this value during runtime. 
 
However, the flavour of zero will cause upgrade to 9.7 to fail 
because we need to upgrade the SPCS entries to the new format, 
and this applies to deleted tablespaces as well. Originally, the 
decision was not to modify the code base with providing a code 
workaround for the APAR, so a standalone tool was created 
("fixtbspflvr"). This tool used to be sent to customers on 
case-by-case basis. A revised decision was made to make 
upgrade to 9.7 more robust from the user's perspective, 
therefore we are now ignoring a zero tablespace flavour.
Problem Summary:
An attempt to upgrade a database to the current release results 
in SQL1042C: 
 
db2 upgrade database SAMPLE 
SQL1042C  An unexpected system error occurred.  SQLSTATE=58004 
 
The DB2 diagnostic log will contain messages similar to: 
 
2010-05-21-14.00.58.921136+600 I1713A271          LEVEL: Warning 
PID     : 4571298              TID  : 1           PROC : db2bp 
INSTANCE: db2inst1             NODE : 001 
EDUID   : 1 
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:10 
MESSAGE : Begin engn migration 
 
2010-05-21-14.00.58.955486+600 I1985A579          LEVEL: Error 
PID     : 4366432              TID  : 3086        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 1-100                APPID: *N1.db2inst1.100521040058 
AUTHID  : DB2INST1 
EDUID   : 3086                 EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbMigratePoolOnDisk, 
probe:40 
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
DATA #1 : unsigned integer, 4 bytes 
0 
 
The failure happens due to a zero flavour found in the SQLSPCS.* 
files in the database directory 
 
Zeroed out flavour is a typical symptom of APAR IY95013, where 
during restore on 9.1 we are forgetting to set the flavour to 
the right value for deleted tablespaces. Such an entry can 
survive several releases since typically we do not care about 
this value during runtime. 
 
However, the flavour of zero will cause upgrade to 9.7 to fail 
because we need to upgrade the SPCS entries to the new format, 
and this applies to deleted tablespaces as well. Originally, the 
decision was not to modify the code base with providing a code 
workaround for the APAR, so a standalone tool was created 
("fixtbspflvr"). This tool used to be sent to customers on 
case-by-case basis. A revised decision was made to make 
upgrade to 9.7 more robust from the user's perspective, 
therefore we are now ignoring a zero tablespace flavour.
Local Fix:
available fix packs:
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 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
Defect   => wsdbu00772858 
Fixed in => v9.7 + FP3 
Module   => engn_sqb
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69967 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.07.2010
24.09.2010
24.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList