Re: Re : undefined object when creating snapshots

Oracle Guy wrote:

> All,
>
> I have exactally the same problem as the below user.
> The sys.obj$ table has a value or 42 for type# :
>
> select * from sys.obj$ where type# = 42
>
> I get the same two objects as if I select:
>
> select * from all_objects where object_type = 'UNDEFINED'
>
> Do any of the oracle guru's out there know how to delete these oddball
> phantom objects from the systems tables?
>
> Oracle Guy
>
> ---
> ynixon_at_bigfoot.com Wrote:
>
> From: ynixon_at_bigfoot.com
> Subject: undefined object when creating snapshots
> Date: 2000/02/01
> Message-ID: <876hjn$a3g$1_at_nnrp1.deja.com>#1/1
> X-Http-Proxy: 1.0 Proxy.Talkline.DE:8080 (Squid/1.1.21), 1.0
> Thetis.Talkline.DE:8080 (Squid/2.1.PATCH2), 1.1 proxy.tli.de (NetCache
> 4.0R3), 1.0 x27.deja.com:80 (Squid/1.1.22) for client unknown,
> unknown,195.252.252.66, 195.252.143.3
> Organization: Deja.com - Before you buy.
> X-Article-Creation-Date: Tue Feb 01 11:55:37 2000 GMT
> X-MyDeja-Info: XMYDJUIDynixon
> Newsgroups: comp.databases.oracle.server,comp.databases.oracle.tools,comp.databases.oracle.misc
> X-Http-User-Agent: Mozilla/4.7 [en] (WinNT; I)
>
> Hi,
>
> I think I have problems with creating snapshots
> that is the meaning of object_type --> undefined
>
> SQL> l
> 1 CREATE SNAPSHOT TACCOUNT_TYPE
> 2 AS
> 3* SELECT * FROM REFWAIT.ACCOUNT_TYPE
> SQL> /
>
> Materialized view created.
>
> SQL> l
> 1* select object_name,object_type,status from obj where object_name
> like '%TACCOUN%'
> SQL> /
>
> OBJECT_NAME OBJECT_TYPE STATUS
> ------------- ----------- -------
> TACCOUNT_TYPE TABLE VALID
> TACCOUNT_TYPE UNDEFINED INVALID
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.

You didn't post your version of Oracle but ...

[Quoted] [Quoted] Look in $ORACLE_HOME/rdbms/admin at the file SQL.BSQ. This file contains the definition of the data dictionary objects and the comments on the field values.

For obj$ (version 8.1.7.3) the valid TYPE# values are: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,19,20,21,22,25,26,27,28,29,30,31,32,33,34, and 35. No 42.

So it does not know how to interpret it.

Daniel Morgan Received on Wed May 15 2002 - 20:20:03 CEST