DB2 FOR LUW / DB2FORLUW / A50 - DB2

A SQL procedure that sets an ASSOCIATE RESULT SET LOCATOR inside 
an exception handler could fail with an SQL0480N error ("The 
procedure "<procedure-name>" has not yet been called.") if the 
SQLCODE of the corresponding stored procedure is greater than 
zero. 
 
For example, inside the exception handler the following code 
could cause the stored procedure to fail when executed: 
 
DECLARE EXIT HANDLER FOR SQLEXCEPTION, SQLWARNING 
  BEGIN 
    -- MUST get all of the values in a single call here since 
the values will be reset after each line that is executed 
    SET v_SQLCODE = SQLCODE, v_SQLSTATE=SQLSTATE; 
 
    -- get the result set that is returned by the ADMIN_CMD 
stored procedure 
    ASSOCIATE RESULT SET LOCATORS(result1) WITH PROCEDURE 
SYSPROC.ADMIN_CMD; 
 
    ALLOCATE rsCur CURSOR FOR RESULT SET result1; 
 
    -- read the data from the result set that is returned by the 
LOAD utility 
    FETCH rsCur INTO v_ROWS_READ, v_ROWS_SKIPPED, v_ROWS_LOADED, 
v_ROWS_REJECTED, v_ROWS_DELETED, v_ROWS_COMMITTED, 
          v_ROWS_PARTITIONED, v_NUM_AGENTINFO_ENTRIES, 
v_MSG_RETRIEVAL, v_MSG_REMOVAL; 
 
    SET msg = 'Error while loading data. SQLCODE: ' || v_SQLCODE 
|| ' SQL State: ' || v_SQLSTATE || '. Execute the following SQL 
to view the LOAD utility messages: ' || v_MSG_RETRIEVAL; 
  END;  -- end of error handler

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 Version 10.5 Fix Pack 3.                       * 
****************************************************************

n/a

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

This problem is fixed in DB2 Version 10.5 Fix Pack 3.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

27.08.2013
27.02.2014
27.02.2014