Re: monitor a drop tablespace

Howard J. Rogers wrote:
>
> That sounds an awfully long time....
>
> Droppng a tablespace (if you mean 'drop tablespace X including contents')
> shouldn't take that long, however big it is. Purely on the grounds that the
> 'drop' command doesn't do much... it removes segments' entries in the data
> dictionary until nothing remains in the tablespace, then it removes the
> pointers to the tablespace contained in the control file. Deletion of
> individual *records* it doesn't do.
>
> The only thing that would cause it to take this long would be if some of
> your tables consisted of thousands upon thousands of extents (then the data
> dictionary deletions would start to take time).
>
> Failing that, I'd suspect it was hung, but you could only tell that really
> by looking at O/S processes/threads and so forth -and you don't mention your
> O/S. If the disk loght is still flashing, good news.
>
> Regards
> HJR
>
> "fabio" <f_vari_at_libero.it> wrote in message
> news:60e08057.0205191035.7980a308_at_posting.google.com...
> > hi,
> > i'm dropping a 800Gb's tablespace
> > How can i monitor this session.
> > It work from 4 Hours and i don't know how many time it spent againg
> >
> > Someone can help me???
> >
> >
> > thanks
> >
> >
> > P.S. Sorry for my english
> >
> >
> > bye Fabio

I haven't looked, but our good friends at Oracle may have instrumented the 'drop tablespace' into v$session_longops (... pessimistic though)

Cheers

-- 
==============================
Connor McDonald

http://www.oracledba.co.uk

"Some days you're the pigeon, some days you're the statue..."