DB2 - Problem description
Problem IC84402 | Status: Closed |
DB2 TERMINATES ABNORMALLY DURING EXPLAIN OF A CALL OR A QUERY CONTAINING AN SQL FUNCTION REFERENCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
DB2 will terminate abnormally during explain of a CALL statement that satisfies all of the following conditions: * The routine being called is an SQL procedure; * The procedure contains one or more cursor declarations; * The procedure has been previously invalidated, and has not been revalidated since. DB2 will also terminate abnormally when a query is being explained, and the query contains a reference to at least one compiled SQL function that satisfies the following conditions: * The function contains one or more cursor declarations; * The function has been previously invalidated, and has not been revalidated since. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to v10.1 Fix Pack 1 * **************************************************************** | |
Local Fix: | |
As a workaround, you can force revalidation of procedures or functions before performing the activity that does the explain. The easiest way to do this is using the ADMIN_REVALIDATE_DB_OBJECTS procedure; e.g., db2 "connect to mydb" db2 "call sysproc.admin_revalidate_db_objects('PROCEDURE', NULL, NULL)" db2 "call sysproc.admin_revalidate_db_objects('MODULE', NULL, NULL)" db2 "call sysproc.admin_revalidate_db_objects('FUNCTION', NULL, NULL)" which will revalidate all procedures, module routines, and functions in the connected database. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Fixed in v10.1 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 02.04.2013 02.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |