home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT03395 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to version 10.1 fixpack 5                             * 
****************************************************************
Local Fix:
Remove the newline character from DB2ENVLIST. Use a space 
character to 
separate values as per the documentation.
Solution
First fixed in version 10.1 fixpack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.07.2014
20.07.2015
20.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList