DB2 FOR LUW / DB2FORLUW / 910 - DB2

Transfer owner can fail when a dependent object is an invalid 
state.   For example: 
 
Consider an SQL procedure that references a table X.T1.    If 
X.T1 is dropped, then the underlying db2 package is invalidated. 
If a TRANSFER is attempted on the SQL procedure to another user, 
this transfer will fail when evaluating privileges on dependent 
objects held by the transferee.   Since the table that the 
package depends on no longer exists, this lack of privilege will 
block the transfer. 
 
With this APAR fix, we will no longer consider the package's 
dependencies since it is already an invalid object

Users Affected: ALL 
 
Problem Description: Transfer owner can fail when a dependent 
object is an invalid state 
 For example: 
Consider an SQL procedure that references a table X.T1.    If 
X.T1 is dropped, then the underlying db2 package is invalidated. 
If a TRANSFER is attempted on the SQL procedure to another user, 
this transfer will fail when evaluating privileges on dependent 
objects held by the transferee.  Since the table that the 
package depends on no longer exists, this lack of privilege will 
block the transfer.

DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 

Problem was first fixed in Version 9.1 Fix Pack 9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC63748 IC63749 
follow-up : 

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

08.10.2009
16.04.2010
16.04.2010

9.1.FP9