I had this occur once too and it was a corrupt data dict. The way I
found out was I could NOT run catalog or catproc to completion without
fatal error. Might want to try this... I had to restore from WAY back
8=(

HTH,

Mike

>>> "Gillies, Garry" <[Email Address Removed] 08/30/02 05:51AM >>>
Hi Tony,
Wild shot in the dark here, but check to see if any segments contain
a large number of extents (more than a thousand).
In this situation the amount of housekeeping required to shut down
the database takes so long (I've heard of people waiting many hours)
that it appears to have hung.
If I remember correctly, Kevin Loney did a good write up on the
problem.



> -----Original Message-----
> From: Tony [mailto:tony.[Email Address Removed]
> Subject: Unable to shutdown database - any suggestions please?
>
>
> Hi All
>
> I cannot shutdown a database, except by means of using
> "shutdown abort"
>
> This is also the case even if the database is not even open.
>
> I cannot find any obvious reason for this, has naybody else
> got any ideas
> please?
>
> Thanks
>
> Tony

--------
Oracle documentation is here:
http://tahiti.oracle.com/pls/tahiti/tahiti.homepage
To unsubscribe: send a blank email to oracledba-[Email Address Removed] subscribe: send a blank email to oracledba-[Email Address Removed]
Visit the list archive: http://www.LAZYDBA.com/odbareadmail.pl
Tell yer mates about http://www.farAwayJobs.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html

Oracle LazyDBA home page