the (supposedly) limited lifetime of this database.
Regards
David Lord
-Original Message-
From: Connor McDonald [mailto:[EMAIL PROTECTED]]
Sent: 24 July 2002 23:44
To: Multiple recipients of list ORACLE-L
Subject: RE: shutdown abort / startup restrict / shutdown vs. shutdown
imm
/ startup restrict / shutdown vs. shutdown
imm
But if you are concerned that shutdown abort could
corrupt your redo logs, then that is equivalent to
mandating that all servers (that run oracle) must be
on an infinite uninterruptible power supply. An
instance failure (eg loss of power
of this database.
Regards
David Lord
-Original Message-
From: Connor McDonald [mailto:[EMAIL PROTECTED]]
Sent: 24 July 2002 23:44
To: Multiple recipients of list ORACLE-L
Subject: RE: shutdown abort / startup restrict / shutdown vs. shutdown
imm
But if you are concerned
:[EMAIL PROTECTED]]
Sent: 24 July 2002 23:44
To: Multiple recipients of list ORACLE-L
Subject: RE: shutdown abort / startup restrict / shutdown vs. shutdown
imm
But if you are concerned that shutdown abort could
corrupt your redo logs, then that is equivalent to
mandating that all
long response
My opinion that shutdown abort is totally safe is
based on this:
The only thing that matters in the database is redo
logs. Everything else is optional - ie it could be
recovered albeit with difficulty (eg you can recreate
a controlfile from scratch if you really have to, and
, this was on 7.1.4 (don't ask;-)
David
Lord
-Original Message-From: kkennedy
[mailto:[EMAIL PROTECTED]]Sent: 24 July 2002
01:33To: Multiple recipients of list ORACLE-LSubject:
RE: shutdown abort / startup restrict / shutdown vs. shutdown
imm
I
have steel belted radial
That is EXACTLY what happened a week and a half ago. We had to do a
shutdown abort because it wouldn't go down, and when we tried to restart it,
it wouldn't come back... redo log corruption... and this being test... it
isn't in archive log mode (another valid solution but no longer really an
If you don't mind, under what version/os did this take place?
On Wed, Jul 24, 2002 at 07:28:40AM -0800, April Wells wrote:
That is EXACTLY what happened a week and a half ago. We had to do a
shutdown abort because it wouldn't go down, and when we tried to restart it,
it wouldn't come
But if you are concerned that shutdown abort could
corrupt your redo logs, then that is equivalent to
mandating that all servers (that run oracle) must be
on an infinite uninterruptible power supply. An
instance failure (eg loss of power) is effectively a
shutdown abort - so the only way to
I'm not committed to the premise that shutdown abort caused the
corruption... only shutdown abort with a dead EMN0 process, when restarted,
had redo log corruption. I have used shutdown abort in several hundred
circumstances when there is something hanging around out there preventing a
normal
Title: shutdown abort / startup restrict / shutdown vs. shutdown immediate
What I
sometimes use is
alter
system checkpoint
startup force restrict
shutdown normal
-Rich
-Original Message-From: Jacques Kilchoer
[mailto:[EMAIL PROTECTED]]Sent: Monday, July 22, 2002
10:53
Title: shutdown abort / startup restrict / shutdown vs. shutdown immediate
Check
this out too :)
http://www.speakeasy.org/~jwilton/oracle/shutdown-abort-bad.html
-
Kirti
-Original Message-From: kkennedy
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, July 23, 2002 12:14
PMTo:
Title: shutdown abort / startup restrict / shutdown vs. shutdown immediate
I
don't necessarily agree that shutdown immediate is quicker. If you force a
checkpoint prior to the shutdown abort the subsequent crash recovery upon
startup is usually pretty fast. Parallel recovery could be a
Title: shutdown abort / startup restrict / shutdown vs. shutdown immediate
The
differences are
1.shutdown abort - is more drastic, no new
users are allowed to log in, disconnects current sessions without rollback,
recovery however would have to be done when restarted.
2.
shutdown immediate
PROTECTED]]Sent: Tuesday, July 23, 2002 12:09
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
shutdown abort / startup restrict / shutdown vs. shutdown
imm
The
differences are
1.shutdown abort - is more drastic, no
new users are allowed to log in, disconnects current sessions
.
Kevin KennedyFirst Point Energy Corporation
-Original Message-From: Gesler, Rich
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, July 23, 2002 11:14
AMTo: Multiple recipients of list ORACLE-LSubject: RE:
shutdown abort / startup restrict / shutdown vs. shutdown
imm
I
don't
PROTECTED]]Sent: Tuesday, July 23, 2002 1:09
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
shutdown abort / startup restrict / shutdown vs. shutdown
imm
The
differences are
1.shutdown abort - is more drastic, no
new users are allowed to log in, disconnects current sessions
Kevin,
Shutdown immediate must be a preferred option but under some senarios like
distributed databases involving diffrent machines has no option but to use
shutdown abort , startup restrict and shutdown immediate otherwise you will
not be able to shutdown all of your databases in a defined
.
- Rich
-Original Message-From: kkennedy
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, July 23, 2002 3:34
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
shutdown abort / startup restrict / shutdown vs. shutdown
imm
Well.
I'll
agree with you only on the basis
April Wells wrote:
Yes, I WHOLE heartedly agree, and we do a shutdown immediate now, but the
point is... Oracle SUPPORT seems to be of the opinion that rather than trying
to figure out what is 'wrong' we should just do a shutdown abort it 'Is a
valid solution'. I'm guessing there IS a
23, 2002 3:21
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
shutdown abort / startup restrict / shutdown vs. shutdown
imm
You
are assuming that shutdown immediate is a fix amount of time. If there
is a lot to rollback it may take longer to rollback (via shutdown immediate
:
Tuesday, July 23, 2002 1:21 PMTo: Multiple recipients of list
ORACLE-LSubject: RE: shutdown abort / startup restrict / shutdown vs.
shutdown imm
You
are assuming that shutdown immediate is a fix amount of time. If there is
a lot to rollback it may take longer to rollback (via shutdown immediate
Title: shutdown abort / startup restrict / shutdown vs. shutdown immediate
You forgot an option: pressing the power
switch!
Sorry the market is killing
me!
Waleed
Any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the
04
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
shutdown abort / startup restrict / shutdown vs. shutdown
imm
I
would have to agree with Rich ... For years I have been using
startup force restrict, shutdown normal prior to
cold backups with the assumption t
24 matches
Mail list logo
