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

DB2 CACHES GROUP MEMBERSHIP OF LOCALSYSTEM (SYSTEM) UNTIL NEXT INSTANCE
RECYCLING.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The DB2 server enumerates and saves the groups that the 
LocalSystem (SYSTEM) account is a member of, but unlike other 
accounts, the cache is never refreshed. This creates a problem 
when users attempt to grant SYSTEM additional privileges by 
adding SYSTEM to groups that have DB2 privileges after the DB2 
server has started.   Once DB2 has populated the cache, it will 
not be aware of group membership changes to SYSTEM afterwards. 
To remedy, restart DB2 after making the group membership change.
Problem-Zusammenfassung:
The DB2 server enumerates and saves the groups that the 
LocalSystem (SYSTEM) account is a member of, but unlike other 
accounts, the cache is never refreshed. This creates a problem 
when users attempt to grant SYSTEM additional privileges by 
adding SYSTEM to groups that have DB2 privileges after the DB2 
server has started.   Once DB2 has populated the cache, it will 
not be aware of group membership changes to SYSTEM afterwards. 
To remedy, restart DB2 after making the group membership change.
Local-Fix:
Restart the db2 instance.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.1 Fix Pack 4.
Workaround
Restart the db2 instance.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC98911 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.01.2014
22.07.2014
22.07.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList