DB2 - Problem description
Problem IC63748 | Status: Closed |
TRANSFER OWNER FAILS WHEN DEPENDENT OBJECT IS IN AN INVALID STATE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
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. With this APAR fix, we will no longer consider the package's dependencies since it is already an invalid object | |
Problem Summary: | |
**************************************************************** * 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. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.5 Fix Pack 6 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.5 Fix Pack 6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.10.2009 31.08.2010 31.08.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) |