Re: ORA-00376: what are my options?

Well, you're getting lots of good advice from others now, but I couldn't resist: I *told* you it was harder to drop indexes than it looks!

I suspect there is still something lurking in INDX. Have a poke around in dba_segments where tablespace_name='INDX' and see what pops up.

Regards
HJR "mar" <mar_at_foo.com> wrote in message
news:ba803q$piroj$1_at_ID-174077.news.dfncis.de...
> 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?
>
>
Received on Sun May 18 2003 - 14:24:55 CDT