Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: SQL Statement Shutdown
On Thu, 06 Mar 2003 16:01:12 +0000, Joel Garry wrote:
> "Paul Brewer" <paul_at_paul.brewers.org.uk> wrote in message news:<3e667ff5_2_at_mk-nntp-1.news.uk.worldonline.com>...
>> Joel,
>>
>> I don't want to get contentious here, but it seems to me that according to
>> fundamental principles, one must trust shutdown abort, followed by startup.
>>
>> If not, surely the conclusion must be that Oracle cannot recover from
>> instance failure? And of course it always can, and always does.
>
> Well, I'm one in a million, and I've seen it fail. But that is not
> the point. The point is HJR is advocating abort as a routine, without
> the concommitant bounce afterwards.
Joel, you are -to put it bluntly- a liar.
I don't advocate it as routine. I do say it isn't dangerous. Learn to read.
And I have no idea what a bounce afterwards will do for you, since at the end of a subsequent startup, you are using a recovered and consistent database.
>Why must one trust that, when
> Oracle documents that you shouldn't? To me, that is just asking for
> trouble, especially when presented as advice to novices, and the
> caveat of having some files backed up necessarily brings in the whole
> manual recovery issue (else how do they get restored?).
Learn to read. I said NOTHING, repeat NOTHING, about backing anything up. I spoke about multiplexing your redo logs. That's all.
I'll say it again for the lexigraphically challenged, like Joel. Shutdown abort is no more "dangerous" than shutdown immediate, provided you have multiplexed your redo logs.
HJR Received on Fri Mar 07 2003 - 03:34:19 CST
![]() |
![]() |