Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: ora-1652 - old subject, new twist?

Re: ora-1652 - old subject, new twist?

From: Mike Liu <mike2322_at_hotmail.com>
Date: 23 Jan 2002 13:48:28 -0800
Message-ID: <2262aa8e.0201231348.3e3a9866@posting.google.com>


Ed_Stevens_at_nospam.noway.nohow (Ed Stevens) wrote in message news:<3c4f01cb.193395728_at_ausnews.austin.ibm.com>...
> Platform: Oracle 8.0.5, NT 4
>
> Occasionally I get an ora-1652 against a SYSTEM tablespace. I have double
> checked that all users, including SYS and SYSTEM are set to use a temp ts as
> evidenced by this query:
>
> === begin quote ===
> SQL> select distinct TEMPORARY_TABLESPACE from dba_users;
>
> TEMPORARY_TABLESPACE
> ------------------------------
> NLCTMPTS
> === end quote ===
>
> A Google search of the ng archives turned up this quote from Sybrand:
>
> === begin quote ===
> When an index is created it will initially also show up as a temporary
> segment. This segment, when ready, is renamed behind the scenes to the name
> of the index.
> === end quote ===
>
> In the instances I'm looking at, we were not creating indexes.
>
> Could it be that this "temporary until committed" mechanism is also happening
> during normal index maintenance resulting from inserts and deletes? If not,
> what the heck am I seeing here?
>
> TIA
>
> - Ed Stevens

"Alter index rebuild..." can also cause this error if the default tablespace for the owner of the index is system. Do you have any user whose default tablespace is system?

Regards,
Mike Received on Wed Jan 23 2002 - 15:48:28 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US