If you have temporary tablespaces it could mean your default extent sizes
for the TEMP tablespace are too small. When you shutdown SMON will clean up
any temporary segments, if these are in thousands of extents it could easily
take 30 minutes to clean up. Check v$sort_segment and see how many extents
your temporary segments are in and if SMON uses a lot of CPU when shutting
down the instance. Resize the default storage on your TEMP tablespaces if
necessary.
<djuly_at_casema.net> wrote in message
news:378e3b6b.91870501_at_news.casema.net...
> On Thu, 24 Jun 1999 23:29:55 +0800, wanni_at_mbox2.singnet.com.sg (Wanni)
> wrote:
> Maybe you have to kill the dbsnmp proces which is used by the
> enterrprise manager in connection with the database.
> Try this first.
>
> >HI Readers,
> >
> >From what I know, shutdown immediate will terminate all current
> >transactions and does a 'graceful' shutdown down. But when I
> >'hang' at the shutdown immediate command for sometime, and noticing
> >that the disk activity is high, could that mean, it is rollbacking
> >some huge huge active transactions in the rollback segments?
> >
> >We have the shutdown immediate going for about 30mins and it was still
> >running. instead, we did a shutdown abort. the next time the database
> >was brought up, it was ok.
> >
> >When we issue shudown immediate again, the same problem persists.
> >
> >What's the logic explanation here?
> >
> >Thanks for your replies :)
>
Received on Fri Jul 16 1999 - 21:53:39 CDT
