Re: ORA-00376: what are my options?

Originally posted by Mar
> This is what I've done:
>
> - deleted all index-related constraints, but I left "NOT NULL"
> and CHECK
> constraints
>
> - tried ALTER TABLESPACE INDX OFFLINE but I got 01191 and 01110
>
> - tried DROP TABLESPACE INDX INCLUDING CONTENTS but I got
> 00604 and 02429 (and CPU usage jumped to 90% for oracle.exe)
>
> - tried DROP TABLESPACE INDX INCLUDING CONTENTS CASCADE
> CONSTRAINTS but got again 00604 and 02429 (CPU usage jumped to
> 90% for oracle.exe again)
>
> After these actions, oracle.exe stayed at 50% for no apparent reason
> (it's Sunday, no connected users).
>
> - then, dropped absolutely all constraints
>
> - after 5 minutes, oracle.exe still at 50% for no apparent reason
>
> - DROP TABLESPACE INDX INCLUDING CONTENTS CASCADE
> CONSTRAINTS but got again 00604 and 02429 (CPU usage jumped to
> 90% for oracle.exe again)
>
>
>
> So looks like I can't drop tablespace INDX. Any suggestions?
>

The ORA-02429 indicates that there is still a constraint out there using an index. Please re-verify that all unique and primary key constraints have been dropped. You earlier mentioned that you had only thirty tables. Are there other schemas that also use the INDX tablespace? Maybe there is something in there you don't know about.

HTH,
Patrick

--
Posted via http://dbforums.com