Startup force followed by shutdown immediate is what we use. We have not
had any problems with it yet.
-Original Message-
startup force?
What is your experience about it?
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Stephen Lee
INET: [EMAIL
Ok, so I changed my cold backup script lastnight so it does this;
connect internal/amianidiot
shutdown abort
startup restrict
shutdown normal
exit
It then does the abort and the startup and then the shutdown normal but then I get
this and my database hangs;
Shutting down instance (normal)
are entirely my own and not those of my
employer or clients **
-Original Message-
From: Fink, Dan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 8:10 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Debate on rc commands Solaris and Oracle
I know I am going to catch
I'll echo that sentiment.
'shutdown abort', 'startup restrict' was a regular part of my
shutdown scripts beginning in 1994 with 7.0.16, as
'shutdown immediate' wasn't all that reliable, even in situations
where it should have worked.
Jared
On Wednesday 29 January 2003 15:53, John Kanagaraj
I guess I'll go with this method since I have a couple of cold backups that hang on
the SHUTDOWN IMMEDIATE and will remain hung until I rectify the situation. I have had
TAR's on this but this could not be resolved. I'm just more confident to see others
doing this. Does anyone have this
I know I am going to catch major grief for this, but I avoid shutdown abort
when possible. Shutdown immediate can take some time, as it will do
transaction rollback in serial (where recovery at startup can do it in
parallel and as needed). The main reason I avoid it is that there are known
bugs
Title: RE: Debate on rc commands Solaris and Oracle
Okay so Jared - you had scripted the shutdown abort then startup restrict then shutdown immediate even on OLTP's in your rc's without even waiting to see what would happen with a shutdown immediate - right. Well, if it is good enough
I have had a SHUTDOWN IMMEDIATE hang for over 4 days on a test database that had
little if any activity going on it so it could not be doing rollbacks for 4 days. It
is something else that is a feature of 8i. I'm not keen on the SHUTDOWN ABORT
either but I cannot have my database hang
Dan, you won't be running alone. I had a bad corruption experience with 7.3
on NT (who hasn't), that I highly suspect was due to ABORT, but have never
confirmed. Yes, depending on the situation, I have used ABORT with a
followup IMMEDIATE many times without problem since then. My issue with
At 08:10 AM 1/30/2003 -0800, Fink, Dan wrote:
I know I am going to catch major
grief for this, but I avoid shutdown abort
when possible. Shutdown immediate can take some time, as it will do
transaction rollback in serial (where recovery at startup can do it
in
parallel and as needed). The main
I used to see the shutdown immediate hang on OpenVMS (Oracle 7.x)
platforms, never did happen on my Unix machines, and I never did have to support
Oracle on Windoze :). I did notice if I stopped the developers from
submitting jobs via dbms_jobs and forced them to use VMS batch jobsthen
Title: RE: Debate on rc commands Solaris and Oracle
Yes on Solaris, Aix, etc.
-Original Message-
From: Farnsworth, Dave [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 10:21 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Debate on rc commands Solaris and Oracle
Any votes for startup force?
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Stephen Lee
INET: [EMAIL PROTECTED]
Fat City Network Services-- 858-538-5051 http://www.fatcity.com
San Diego, California-- Mailing list and web hosting services
It shouldn't be too hard to split off a process in the shutdown script that
checks for the existence of the smon process 10 minutes or so after the
shutdown immediate, if it sees it it could just go ahead and kill the db
with shutdown abort and sned an email or something. I had some issues
trying
: Debate on rc commands Solaris and Oracle
Any votes for startup force?
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Stephen Lee
INET: [EMAIL PROTECTED]
Fat City Network Services-- 858-538-5051 http://www.fatcity.com
San Diego, California-- Mailing
]
Sent by: [EMAIL PROTECTED]
01/30/2003 09:41 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: Debate on rc commands Solaris and Oracle
Any votes for startup force?
--
Please see the official ORACLE-L
:RE: Debate on rc commands Solaris and Oracle/startup force?
Jared,
startup force?
What is your experience about it?
One time my colleague DBA used it on Production and result was
1)some table corruption
2) Not removing memory segment (ipcs -mb was showing 2 segments of same
SGA
by: [EMAIL PROTECTED]
01/30/2003 01:53 PM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: Debate on rc commands Solaris and
Oracle/startup force?
Jared,
startup force?
What is your experience about
Title: RE: Debate on rc commands Solaris and Oracle
System Administrator says he doesn't trust that the rc commands will stop if the database doesn't want to shutdown and even if it does would want to shutdown with scripts beforehand so that a DBA could connect and resolve the issue. Other
Title: RE: Debate on rc commands Solaris and Oracle
Paula,
Shutdown abort is not recommended as the file
checkpointing is not done during shutdown abort. If you need to perform
shutdown abort, then, it is preferred to bring up the db with startup restrict
(so that the users wouldn't connect
Rao,
And where did you read that 'shutdown abort' is not recommended? This is
another myth that has been busted a while ago. A shutdown abort followed by
a startup restrict and a normal shutdown is the way to go when dealing with
rogue sessions that open a connection and never shutdown. In such
21 matches
Mail list logo
