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

CAN NOT RETRIEVE DEFINED VALUES FOR REGISTRY VARIABLES WHEN
"DB2SET" COMMAND IS BEING PERFORMED.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When an application is performing "db2set" command to update 
registry variables, other applications running simultaneously 
might not be able to retrieve defined values for registry 
variables, as if the registry variables have not been set at 
all. 
 
The problem occurs only in a very rare situation. It's most 
likely to happen when registry variables are frequently updated 
by "db2set" command.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 10.1 on Linux, Unix and Windows         * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 10.1 FixPak 1 or higher levels.   * 
****************************************************************
Local-Fix:
Reducing the frequency of updating registry variables.
Lösung
First fixed in DB2 LUW Version 10.1 FixPak 1.
Workaround
Reducing the frequency of updating registry variables.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.06.2012
29.09.2013
29.09.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version