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 IT08455 Status: Closed

LEAK IN FILE DESCRIPTORS CAN CAUSE "TOO MANY OPEN FILES" ERROR
FROM IBM SECURE SHELL SERVICE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When the IBM Secure Shell for Windows service has been activate 
for a long time, jobs submitted through Database Web Console 
might be hanged and no new jobs can be added.  Studying the 
event log on the Windows Server will show "Too many open files" 
error. 
New Jobs can only be added after refreshing the IBM Secure Shell 
For Windows service. 
 
This is due to a leak in the file descriptors for each SSH 
connection.  When the leak reached the internal file descriptor 
limit, new SSH connection 
cannot be received.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of Data Studio Web Concolse                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 5 or higher.                    * 
****************************************************************
Local Fix:
None, must restart IBM Secure Shell service.
Solution
Problem first fixed in DB2 10.1 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2015
14.07.2015
14.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