Re: How to deal with objects of type UNDEFINED

Mind you, I don't think I've seen much discussion of the other reasons for 'UNDEFINED' objects appearing other than the 'materialized view' bug.

e.g.
If you create a view that depends on a public synonym, your schema will suddenly contain an object of type UNDEFINED matching the name of the public synonym so that Oracle can do negative dependency checking.

If you drop objects (possibly not all types), then the obj$ row is maintained with a type of UNDEFINED so that Oracle can re-use the same obj# if you create a new object before the next time the database is restarted.

Possibly others I haven't noticed yet.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminars
 UK  July / Sept
 Australia August
 Malaysia September
 USA (MI) November

http://www.jlcomp.demon.co.uk/seminar.html

Daniel Morgan wrote in message <3D2E0EAE.9EA1E132_at_exesolutions.com>...



>You have not discovered anything that has not been discussed numerous

>times in numerous forums, including this one.

>

>And in answer to your question about multiple objects having the same name

>... no it is not possible. Unless, of course, the object consists of

>multiple parts such as a package and package body, or as you have seen.