Re: Unable to shutdown the database
From: Robert Klemme <shortcutter_at_googlemail.com>
Date: Fri, 02 Nov 2012 18:13:33 +0100
Message-ID: <afid9uFllvfU1_at_mid.individual.net>
On 02.11.2012 15:53, epokopac_at_gmail.com wrote:
> Perhaps it was "stuck" doing the "canceling, etc." for some odd
> reason. 30 minutes for a shutdown is not normal. Makes even less
> sense since it appears your startup was successful.
Date: Fri, 02 Nov 2012 18:13:33 +0100
Message-ID: <afid9uFllvfU1_at_mid.individual.net>
On 02.11.2012 15:53, epokopac_at_gmail.com wrote:
> Perhaps it was "stuck" doing the "canceling, etc." for some odd
> reason. 30 minutes for a shutdown is not normal. Makes even less
> sense since it appears your startup was successful.
Couldn't it also be the instance recovery triggered by the "startup" after "shutdown abort" not having been finished?
Cheers
robert
-- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/Received on Fri Nov 02 2012 - 18:13:33 CET