Re: drop user user_name cascade - question

"Tom Miskiewicz" <miskiewicz2_at_no.spam.yahoo.com> wrote in message news:mbfq9.13$CU4.2672_at_news.ecrc.de...
>
> > Then I would pick one segment, and drop that one segment.
> > Then I would repeat for another segment.
> Sorry, but I don't know how to do that.
>

It's not really that difficult. You get the name of the segment from the first query I gave you, and then you issue the command:

drop table fredtbl cascade constraints;
drop index blah;
drop cluster foo;

...or whatever other segment types you have listed.

HJR
> > If individual segment drops are working correctly, then there's a good
> > chance that a particular segment is throwing a wobbly, and that might be
> > because it has a bazillion extents (select segment_name, count(*) from
> > dba_extents group by owner having owner='FRED'; to check).
> This doesn't work on my box too.
> When I do desc dba_extents I get
>
> Your query gives me:
>
> SQL> select segment_name, count(*) from dba_extents
> 2 group by owner having owner='ARADMIN';
> select segment_name, count(*) from dba_extents
> *
> ERROR at line 1:
> ORA-00979: not a GROUP BY expression
>
> > that you're running into trouble performing the recursive SQL needed by
> > Oracle to work out what to drop, and maybe a bigger shared pool might
help
> > that. It could also be half a dozen other things, I'm afraid.
> > I've been known to drop 300 tables individually, successfuly, where a
drop
> > user cascade failed to work.
>
> Thanks
>
> Tom
>
>
Received on Sun Oct 13 2002 - 14:26:58 CDT