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

sqldReplaceRow reports SQLD_BADPAGE during roll forward

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
After upgrading to DB2 V10, a rollforward may fail with 
SQLD_BADPAGE on internal meta-data pages due to 
incorrect page space management. 
 
This only happens on object table pages, where the reserved 
space was incorrectly set to a value other than 0 during a DB2 
V9.7 rollforward. DB2 V10 does not expect values other than 0 
for 
reserved space on object table pages. 
 
Please note that DB2 V10 does not set or update the 
reserved space value for object table pages during rollforward. 
The inconsistency is introduced by DB2 V9.7 rollforward only and 
can lead to problems after an upgrade of such a system to DB2 
V10 
and later releases. 
 
The following relevant messages will be written to the 
db2diag.log file: 
 
2014-02-06-01.30.57.616659+000 I47564905A532        LEVEL: 
Severe 
PID     : 25690288             TID : 9511           PROC : 
db2sysc 0 
INSTANCE: xxxx               NODE : 000           DB   : yyy 
APPHDL  : 0-9                  APPID: *LOCAL.DB2.140206012857 
HOSTNAME: zzzz 
EDUID   : 9511                 EDUNAME: db2redow (yyy) 0 
FUNCTION: DB2 UDB, data management, sqldReplaceRow, probe:435 
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data 
Page" 
... 
2014-02-06-01.30.57.617868+000 I47566001A545        LEVEL: 
Severe 
PID     : 25690288             TID : 9511           PROC : 
db2sysc 0 
INSTANCE: xxxx               NODE : 000           DB   : yyy 
APPHDL  : 0-9                  APPID: *LOCAL.DB2.140206012857 
HOSTNAME: zzzz 
EDUID   : 9511                 EDUNAME: db2redow (yyy) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging function), probe:30 
MESSAGE : PAGE OBJECT IDENTIFIERS: 
DATA #1 : String, 54 bytes 
Tablespace ID = 7, Object ID = 65535, Object Type = 0 
... 
2014-02-06-01.30.57.620403+000 I47569512A560        LEVEL: 
Severe 
PID     : 25690288             TID : 9511           PROC : 
db2sysc 0 
INSTANCE: xxxx               NODE : 000           DB   : yyy 
APPHDL  : 0-9                  APPID: *LOCAL.DB2.140206012857 
HOSTNAME: zzzz 
EDUID   : 9511                 EDUNAME: db2redow (yyy) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging function), probe:30 
MESSAGE : SPACE MANAGEMENT: 
DATA #1 : String, 76 bytes 
Free = 7404, Reserved = 7558, Young Reserve = 0, Young TID = 
0000 2191 0CDF 
 
The key elements here are "Object ID = 65535" which identifies 
this 
as an object table page, and "Free = 7404, Reserved = 7558" 
which 
shows the reserved space has been incremented above the free 
space.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4.                      * 
****************************************************************
Local-Fix:
Restore a newer backup and do rollforward from there.
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.5 Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
31.03.2014
06.11.2014
06.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList