If I try to replace a stored procedure or package body with a new version
while someone is using it, I get a message to the effect that the change
timed out waiting for a lock.

I know how to identify who has a lock on a table or rollback segment (and
even who is waiting for a lock on a table or rollback segment), but can
anyone tell me how to identify which sessions have locks on stored
procedures (and views as well, if possible)?

The first useful answer, provided I haven't figured it out already myself,
wins a couple of gift certificates for Dreyer's/Edy's Grand Ice Cream

Thanks/Regards

Louis Cohen
San Leandro, CA