Re: Unable to shutdown the database
Date: Fri, 02 Nov 2012 20:27:31 +0100
Message-ID: <afil54FnidsU1_at_mid.individual.net>
On 11/02/2012 06:17 PM, Kai Rode wrote:
>>> 1. shutdown abort
>>> 2. startup
>>> 3. shutdown immediate
>
>> Why are you doing that? Why are you shutting down your database, then
>> starting it and shutting down again when you only want to shut down?
>> And why are you using "shutdown abort"?
>
> Actually this is not completely nonsensical. If you "shutdown immediate",
> pending transactions will do a normal rollback. If you do it the way the
> original poster describes, the database will do a fast parallel rollback in
> step 2 so it *could* be faster.
But that would be done on next startup anyway. Why do it here? For a cold backup? Also, "faster" is not the only goal. Especially with databases reliability is high on the list as well. So I'd probably rather pick the _possibly_ slower operation and stick to the regular procedure.
> Plus I remember a conversation with oracle support I once had while working
> on a priority 1 ticket: Them: "Now do a shutdown abort". Me: "Do you mean
> shutdown immediate?". Them: "If you have that much time..." :-)
Well, I have also seen support personnel of a telco provider to suggest switching off the Windows firewall (which resulted in a virus infection of a friend's PC) so I usually take advice from support with a grain of salt - especially when it seems to contradict the documentation so drastically.
Kind regards
robert Received on Fri Nov 02 2012 - 20:27:31 CET