DB2 - Problem description
Problem IC65294 | Status: Closed |
SETI INFORMATION IS NOT SENT TO THE SERVER ON THE SECOND AND SUBSEQUENT CONNECTIONS. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
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: | |
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. | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in version 9.7 Fix Pack 2. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.12.2009 07.01.2010 07.01.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |