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

-5055 ERRORS FROM DB2LICM.EXE IN DB2DIAG.LOG DURING UPGRADE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
During product upgrade, db2licm incorrectly attempts to attach 
to an instance.  This triggers messages such as the following to 
be written to the db2diag.log: 
 
2011-02-10-19.14.19.843000-300 I22930H280         LEVEL: Error 
PID     : 5584                 TID  : 5856        PROC : 
db2licm.exe 
INSTANCE: DB2                  NODE : 000 
EDUID   : 5856 
FUNCTION: DB2 UDB, config/install, sqlfcsys, probe:35 
RETCODE : ZRC=0xFFFFEC41=-5055 
 
2011-02-10-19.14.19.843000-300 I23212H387         LEVEL: Error 
PID     : 5584                 TID  : 5856        PROC : 
db2licm.exe 
INSTANCE: DB2                  NODE : 000 
EDUID   : 5856 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
MESSAGE : bytesr 
DATA #1 : Hexdump, 4 bytes 
0x0012FA74 : 0010 0000
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users upgrading to DB2 v9.7                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During product upgrade, db2licm incorrectly attempts to      * 
* attach to an instance triggering -5055 errors in the         * 
* db2diag.log                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* When upgrading to v9.7, use the Fixpack 5 image to avoid the * 
* -5055 messages.                                              * 
****************************************************************
Local-Fix:
The workaround for this issue is to ignore the messages in the 
db2diag.log file.  The license is applied correctly and this 
apar was opened because the messages shouldn't be displayed. 
The fix to this APAR will make these messages not appear.
verfügbare FixPacks:
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

Lösung
First fixed in DB2 v9.7 Fixpack 5
Workaround
The workaround for this issue is to ignore the messages in the 
db2diag.log file.  The license is applied correctly and this 
apar was opened because the messages shouldn't be displayed. 
The fix to this APAR will make these messages not appear.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.02.2011
19.01.2012
19.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.,
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList