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

EVENT MONITOR OUTPUT RETURNS SQL0100W FOR "OPERATION : CLOSE"
FIELD EVENTHOUGH THE SQL COMPLETED SUCCESSFULLY.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
During an early close processing, the server will close the 
cursor implicitly. This is not an error in processing as the 
cursor has already been closed at the server after all the rows 
have been fetched, but the event monitor records incorrectly 
show SQL0100W for the CLOSE operation of the corresponding 
statement.
Problem-Zusammenfassung:
User's Affected : All 
Problem Description : 
  Event monitor output returns SQL0100W for "OPERATION : CLOSE" 
  field eventhough the SQL completed successfully. 
Problem Summary : 
 
During an early close processing, the server will close the 
cursor implicitly. This is not an error in processing as the 
cursor has already been closed at the server after all the rows 
have been fetched, but the event monitor records incorrectly 
show SQL0100W for the CLOSE operation of the corresponding 
statement.
Local-Fix:
verfügbare FixPacks:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in V9.7 Fixpak 5 (s111017)
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.05.2011
18.08.2014
18.08.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.5 FixList