When I run db2rbind, I check the result log and I am getting a number of failed rebinds for an old user on my system for not having the required auth or privilege. I do not want to have add or change an old user that doesn't exist anymore. He is listed as the Owner and Binder of the packages in question, however when I check ALL tables, indexes, views, functions and procedures I cannot find ANY objects that exist with such a schema.

How can I trace these apparent Orphaned Packages to what they are, what they do and more importantly, how do I get rid of them ? If I list the application.objects and packages from Control Center, there is no drop option.

I've tried any number of system tables trying to track the package name of SYSIBMADM.P4212532 but I cannot find any reference to culprits other than the below.

If I perform the following query:

SELECT * FROM SYSCAT.PACKAGEDEP WHERE PKGNAME = 'P4212532';

F SYSCAT SYSCAT_COLLATIONNAME
V SYSCAT TABLES
I SYSIBM INDTABLES01
T SYSIBM SYSAUDITPOLICIES
T SYSIBM SYSCOLLATIONS
T SYSIBM SYSTABLES
m SYSIBMADM UTL_DIR
F SYSIBMADM UTL_DIR UTL_DIR_INIT

I get listed the above 2 functions, 3 tables, 1 index and 1 view for this package name SYSIBMADM.P4212532 but I still do not know what it actually is.

SELECT * FROM SYSCAT.PACKAGES WHERE OWNER = 'X' gives me 52 packages owned by said user most with a package name of Pxxxxxx but the following package names also appear:

STADMH03
DB2COMMO
DB2MOVE
DB2L2H00
DB2L0H00
DB2UPDV

Any bright ideas, any help would be greatly appreciated ?

On Jul 8, 4:39*pm, Fin <tdavi... (AT) hotmail (DOT) com> wrote:
Seems like that particular USER held DBADM or SYSADM at some point.
That user might have run db2updv8 or db2updv9, db2move...etc
commands.
DB2L2H00 i think, belongs to DB2LOOK
See if You can drop these packages

Cheers
Shashi Mannepalli