home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC63651 Status: Geschlossen

TRANSFER OWNER FAILS WHEN DEPENDENT OBJECT IS IN AN INVALID STATE

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
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-Zusammenfassung:
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.
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.1 Fix Pack 9
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC63748 IC63749 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.10.2009
16.04.2010
16.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP9
Problem behoben lt. FixList in der Version
9.1.0.9 FixList