DB2 FOR LUW / DB2FORLUW / 970 - DB2

seti information is not sent to the server on the second and 
 
subsequent connections. 
 
This may cause missing information for 
client application information when monitored on the server. For 
example, client application name and/or client account may be 
missing for all but the first connections/threads.

Users Affected: All Users 
 
Problem Description: 
SETI INFORMATION IS NOT SENT TO THE SERVER ON THE SECOND AND 
SUBSEQUENT CONNECTIONS. 
 
This may cause missing information for 
client application information when monitored on the server. For 
example, client application name and/or client account may be 
missing for all but the first connections/threads. 
 
Problem Summary: 
SETI INFORMATION IS NOT SENT TO THE SERVER ON THE SECOND AND 
SUBSEQUENT CONNECTIONS. 
 
This may cause missing information for 
client application information when monitored on the server. Fo 
example, client application name and/or client account may be 
missing for all but the first connections/threads.

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in version 9.7 Fix Pack 2.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

22.12.2009
07.01.2010
07.01.2010

9.7.FP2