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

MANY TCPIP SOCKET MAY REMAIN OPEN WHILE DEBUGGING A STORED PROCEDURE WITH
OPTIM DEVELOPMENT STUDIO.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When a stored procedure is debugged with Optim Development 
Studio. 
TCPIP socket may not be closed correctly by DB2 Server. 
The following kind of error are repeated for many times in 
db2diag.log while this issue happens. 
 
2012-02-08-16.43.39.216622+540 I22634260A559      LEVEL: Error 
PID     : 6193174              TID  : 11568       PROC : db2sysc 
0 
INSTANCE: instname               NODE : 000         DB   : 
P92253 
APPHDL  : 0-25                 APPID: 
9.189.215.199.4584.120208073604 
AUTHID  : E34229 
EDUID   : 11568                EDUNAME: db2agent (dbname) 0 
FUNCTION: DB2 UDB, runtime interpreter, 
sqlriOneTimeInitRtn1Trusted, probe:25 
MESSAGE : Error calling openHandle. rc = 
DATA #1 : Hexdump, 4 bytes 
0x0700000004FF1F80 : FFFF FBAA
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* User using Optim Development Studio                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 Fix Pack 1.                                 * 
****************************************************************
Local-Fix:
Not Available
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 1.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
01.11.2012
01.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList