DB2 FOR LUW / DB2FORLUW / A50 - DB2

Description 
After upgrade to v105 FP1 or later, a call of the procedure may 
returns SQL204N while the procedure executes normally before 
upgrading.  "db2rbind dbname -l logname" runs correctly but not 
helpful with the problem. 
 
Cause 
The error of SQL204N is because the table in the procedure is 
dropped and re-created and hence has a newer creation timestamp 
than the EXPLICIT_BIND_TIME of the procedure.  "db2rbind v95db 
-l logfile -r conservative" or" db2rbind v95db -l logfile" will 
not update the EXPLICIT_BIND_TIME and hence will not fix the 
problem. 
 
Workaround 
If the "any" option is used, the EXPLICIT_BIND_TIME will be 
updated and should work around the issue. 
e.g.  db2rbind v95db -l logfile -r any. 
or 
SYSPROC.REBIND_ROUTINE_PACKAGE() can be invoked to more 
selectively rebind only the packages for the routines that fail 
with the SQL204N issue. 
e.g. call sysproc.rebind_routine_package('P','' , '' 
,'<procedure_name_here>, '' );

**************************************************************** 
* USERS AFFECTED:                                              * 
* See Error Description                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Take the workaround in the description                       * 
****************************************************************

not known / see Local fix

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

22.06.2014
16.03.2015
16.03.2015