Re: Shutdown immediate taking a very long time (hour plus) after upgrade of

MAYBE THERE ARE SUBMIT JOBS STILL RUNNING. CHECK IT AND SOLVE
Paul <paul_at_dbforums.com> wrote:

>We have a DSS system roughly arounf the same size on (8.17 on NT 4.0)
>and we waited over 3 hours for it to shutdown following the upgrade.
>Since then it takes anywhere between 10 and 45 minutes :(
 

>Oracle couldn't really give me a definite reason other than it was
>cleaning up and maybe I have dodgy data dictionary entry and a few other
>non-specific possibilities.
 

>I've since learnt to live with it as it only shuts down for weekly
>backup on a Saturday and I'm not around to worry if it's hung :)

>Sharon wrote:
> > We are upgrading our database from 8.0.5 to 8.1.6, and everything so far
> > has gone smoothly. However, after all steps have taken place and we
> > issue the shutdown immediate command, it's taking a verrrryyy long time
> > to shut down. The last command in the alert log is ALTER DATABASE
> > DISMOUNT, and all background processes are still running. Of course we
> > can't get to it now either since it's in shutdown mode -- just want to
> > make sure it SHOULD be taking so long, as I know Oracle supposedly needs
> > to do some housecleaning.
> > Our database is roughly 250GB
> > thnx

>--
>Posted via dBforums, http://dbforums.com
Received on Fri May 18 2001 - 01:11:18 CDT