|
Problem IC64281
|
Status: Closed |
CANCELLING AN IDLE CURSOR OPEN ON A FENCED UDF WHICH ISSUES SQL MAY RESULT IN ABNORMAL TERMINATION OF THE DB2 SERVER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If a cursor that is opened on a fenced UDF is cancelled (using
the WLM_CANCEL_ACTIVITY stored procedure) while idle (that is,
not actively processing an OPEN, FETCH or CLOSE request from
the application), and the udf executes SQL upon receiving a
CLOSE
request, the DB2 server may terminate abnormally. Termination
will occur if the next request issued by the application that
opened the cursor (which was idle) is for any statement other
than the cursor itself. For example, if the next request from
the application is a fetch on the cursor, the server will not
terminate. However, if the next request were an insert, the
server would abnormally terminate. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who make use of fenced UDFs in their environment and *
* who use the WLM_CANCEL_ACTIVITY stored procedure. *
****************************************************************
* PROBLEM DESCRIPTION: *
* An IDLE cursor opened against a fenced UDF is canceled using *
* the WLM_CANCEL_ACTIVITY stored procedure. The next request *
* issued by the application that opened the cursor causes the *
* database server to abnormally terminate. *
* *
* An IDLE cursor is defined here as a cursor that is open on *
* the database server, but is waiting for a client request *
* (e.g. a fetch) to continue processing. The only cursors that *
* may encounter this problem are those opened on fenced UDFs, *
* where the fenced UDF performs one or more SQL statements *
* when it receives a CLOSE request. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
This problem is fixed in DB2 Version 9.7 Fix Pack 2. The fix
does not result in any behavioral changes. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.10.2009
08.04.2010
08.04.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
|
 |
