Re: Non-existing objects? (sys.obj$.type# = 10)

'Non-existent' objects exist to handle
'negative dependency' tracking.

Say you have a view

    create or replace view v1 as
    select * from t1;

but T1 is actually a public synonym to a table in someone else's schema. The validity of this view is dependent on the fact that there is no object named T1 in your schema; so
Oracle creates a 'non-existent' object in your schema that the view can depend on.

Then, when you create an object called T1 in your schema, this causes the elimination of the 'non-existent' object, which automatically causes the invalidation and recompilation of the view to use your table.

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

tashepkov_at_my-dejanews.com wrote in message <7h7m62$n3o$1_at_nnrp1.deja.com>...
>Hello,
>
>Does anybody know what object with type 10 means in Oracle?
>
>It is a long story to tell why I am asking about it.
>But, in short, we are running Oracle Parallel Server 8.0.5.1.1 on
>OSF1 v4.0 and I think that Oracle data dictionary is corrupted.
>(sometimes server dumps core with code ORA-0600 -- internal error).
>
>I looked at the source of sys.all_objects view and noticed that
>objects with type 10 is just skipped in output of that view:
>
>...
>
> and (o.type# not in (1 /* INDEX - handled below */,
> 10 /* NON-EXISTENT */)
>...
>
Received on Tue May 11 1999 - 14:58:49 CDT