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

A newline character in DB2ENVLIST will result in an infinite loop when
accessed by the REG_VARIABLES view causing high cpu.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When the value of DB2ENVLIST contains a newline character the 
processing 
of it for the REG_VARIABLES view will enter a infinite loop 
driving up 
CPU usage for the db2fmp process handling the request. 
 
As it is an infinite loop, the accessing statement will never 
complete 
and will have to be interrupted. The db2fmp process will need to 
be 
identified and terminated using db2fmpterm <process-ID>. 
 
For example, executing: 
 
SELECT * FROM SYSIBMADM.REG_VARIABLES 
 
With: 
 
$ db2set -all 
[e] DB2ENVLIST=VAR_A 
VAR_B 
[i] DB2COMM=tcpip 
... 
 
active at the time the instance was started, will result in this 
issue.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Remove the newline character from DB2ENVLIST. Use a space 
character to 
separate values as per the documentation.
Lösung
First fixed in Version 10.5 Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.07.2014
15.03.2015
15.03.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList