DB2 FOR LUW / DB2FORLUW / A10 - DB2

Within the same connection, if there are multiple identical 
references to a function or procedure of the form 
(<module-name>.<routine-name>), DB2 may fail to 
re-resolve the schema name despite a schema change. 
 
Example: 
 
Assuming the existence of procedures M.Proc1  (where M is the 
name of a module or PL/SQL package) in both schema A and schema 
B. 
 
set current schema = A; 
set current path = A, sysproc, sysfun, sysibm; 
 
call M.Proc1 (); 
 
set current schema = B; 
set current path = B, sysproc, sysfun, sysibm; 
 
--  A.M.Proc1, instead of B.M.proc1, may be incorrectly invoked. 
call M.Proc1 ();

**************************************************************** 
* USERS AFFECTED:                                              * 
* User prior to DB2 v10                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v101fp1                                       * 
****************************************************************

Add a "flush package cache dynamic" statement after changing 
current schema.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 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
 

not known / see Local fix

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

14.06.2012
03.12.2012
03.12.2012