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

UPGRADE DATABASE COMMAND MIGHT FAIL IN SQLPMIGRATEMFH

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
On some occasion, it is possible that UPGRADE DATABASE command 
fails "SQL1042C  An unexpected system error occurred" while 
reporting an error similar to 
 
        2016-11-02-16.29.13.231876-300 I171674A764 
LEVEL: Severe 
        PID     : 22640                TID : 1642           PROC 
: db2sysc 0 
        INSTANCE: xxxxxxxx             NODE : 000           DB 
: xxxxxxxx 
        APPHDL  : 0-2476               APPID: 
*LOCAL.xxxxxxxx.161102212913 
        AUTHID  : xxxxxxxx             HOSTNAME: xxxxxxxx 
        EDUID   : 1642                 EDUNAME: db2agent 
(xxxxxxxx) 0 
        FUNCTION: DB2 UDB, data protection services, 
sqlpMigrateMFH, probe:70 
        MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal 
Logic Error" 
                  DIA8526C A fatal error occurred in data 
protection services. 
        DATA #1 : String, 66 bytes 
        Unable to migrate as MFH records do not have consecutive 
counters. 
        DATA #2 : unsigned integer, 2 bytes 
        0 
        DATA #3 : unsigned integer, 2 bytes 
        65535 
 
        2016-11-02-16.29.13.234006-300 I172439A770 
LEVEL: Severe 
        PID     : 22640                TID : 1642           PROC 
: db2sysc 0 
        INSTANCE: xxxxxxxx             NODE : 000           DB 
: xxxxxxxx 
        APPHDL  : 0-2476               APPID: 
*LOCAL.xxxxxxxx.161102212913 
        AUTHID  : xxxxxxxx             HOSTNAME: xxxxxxxx 
        EDUID   : 1642                 EDUNAME: db2agent 
(xxxxxxxx) 0 
        FUNCTION: DB2 UDB, data protection services, 
sqlpMigrateMFH, probe:70 
        MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal 
Logic Error" 
                  DIA8526C A fatal error occurred in data 
protection services. 
        DATA #1 : String, 26 bytes 
        Unable to migrate MFH file 
        DATA #2 : unsigned integer, 4 bytes 
        1 
        DATA #3 : Hex integer, 4 bytes 
        0x00000D00 
        DATA #4 : Pointer, 8 bytes 
        0x0000000000000000 
 
Despite the message, the counters are consecutive, but we fail 
to detect it correctly.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

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