Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC87918 Status: Closed

EXECUTING DBMS_SQL.EXECUTE_AND_FETCH PROCEDURE WITH 2 PARAMETERS FAILS WITH
SQL0444N RC=4

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Executing DBMS_SQL.EXECUTE_AND_FETCH procedure with 2 parameter 
fails with : 
 
SQL0444N Routine "*ND_FETCH" (specific name 
"DBMS_SQL_EXECUTE_AND_FETCH_2") is implemented with code in 
library or path "...tion\unfenced\db2packlib", function "*" 
which cannot be accessed. Reason code: "4". SQLSTATE=42724 
 
This is because DBMS_SQL.EXECUTE_AND_FETCH is a part of 
db2modlib library
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on DB2 version 10.1 Fix Pack 1 and below               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 2 or higher             * 
****************************************************************
Local Fix:
Call the DBMS_SQL.EXECUTE_AND_FETCH procedure using 3 
parameters.
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 version 10.1 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
29.01.2013
29.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList