|
Problem IC76109
|
Status: Closed |
EVENT MONITOR OUTPUT RETURNS SQL0100W FOR "OPERATION : CLOSE" FIELD EVENTHOUGH THE SQL COMPLETED SUCCESSFULLY. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
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: |
|
| available fix packs: |
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
|
| Solution |
Problem was first fixed in V9.7 Fixpak 5 (s111017) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.05.2011
18.08.2014
18.08.2014 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
