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

EXTEND DB2START FUNCTIONALITY TO REMOVE OBSOLETE ENTRIES IN GLOBAL.REG
AND PROFILES.REG

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Currently, in DB2 9, db2start creates global.reg and 
profiles.reg, and adds the entry for the instance, if it does 
not exist. 
With this APAR, we will extend this functionality, so 
that db2start will also remove the entry from a previous 
version, if exists. 
Both DB2 9 and 9.5 will be changed. 
This functionality is to provide a better migration support 
especially for a multiple partition environment as well as DB2 
on HACMP installation. 
 
To benefit from this APAR, all partitions in a multiple 
partition environment (or all members in HACMP clusters) must 
run db2start during migration.
Problem-Zusammenfassung:
USERS AFFECTED: All 
 
PROBLEM DESCRIPTION: 
 
Currently, in DB2 9, db2start creates global.reg and 
profiles.reg, and adds the entry for the instance, if it does 
not exist. 
With this APAR, we will extend this functionality, so 
that db2start will also remove the entry from a previous 
version, if exists. 
Both DB2 9 and 9.5 will be changed. 
This functionality is to provide a better migration support 
especially for a multiple partition environment as well as DB2 
on HACMP installation. 
 
To benefit from this APAR, all partitions in a multiple 
partition environment (or all members in HACMP clusters) must 
run db2start during migration. 
 
PROBLEM SUMMARY: 
 
see problem description.
Local-Fix:
remove old entries manually
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
The complete fix for this problem first appears in DB2 UDB 
Version 9.5 FixPak 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.10.2009
15.12.2009
15.12.2009
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version
9.7.0.1 FixList