|
Problem IC79087
|
Status: Closed |
NO ERROR RETURNED TO A .NET APPLICATION AFTER A ROLLBACK OF A QUERY DUE TO COMMANDTIMEOUT. |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
Even after a rollback of a query due to CommandTimeout of End
Chain statement in .NET applications or End compound statement
in CLI applications, no error is returned to the application.
On Command Timeout, the CLI sends a SQLCancel() interrupt to the
server.
Irrespective of Interrupt Enabled/Disabled at zOS server, upon
Command Timeout CLI invokes SQlCancel() and rollbacks the
transaction, but CLI rely on the server for interrupt error
(-952). If no error is returned by the server, CLI also fails to
return the error to the application. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 CLI *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* See Error Description *
**************************************************************** |
| Local Fix: |
Increase the 'CommandTimeout' valus in the connection String. |
| available fix packs: |
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 |
See Error Description |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.10.2011
05.06.2012
05.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
