instance recovery time is more manageable in 9i --
mttr_fast_start_target in the init.ora.
For a time, in version 6, Oracle said you HAD to use shutdown abort,
that a shutdown immediate could corrupt the database (that was an
undocumented feature)
I've had cases where the regular, automated
how do we minimize it.
I use shutdown abort to increase availability. If you 'alter system
checkpoint' before you shutdown abort, then automatic crash recovery
is extremely fast, since only a few bytes of redo need to be applied.
On the other hand, if you shutdown immediate, you may be waiting all
Chris,
We hang on shutdown immediate, not startup. That's why I choose to use
shutdown abort.
Joan
Chris Berry wrote:
Schauss, Peter wrote:
I have one Oracle instance which supports an application
server which always maintains a database connection.
The UNIX system
recipients of list ORACLE-L
On Wed, 2 Apr 2003, Chris Berry wrote:
Shutdown abort is pretty drastic, are you sure shutdown immediate
didn't work?
What is drastic about shutdown abort?
Never one to opt out of a shutdown abort thread,
--
Jeremiah Wilton
http://www.speakeasy.net
that had a job in the job queue that ran frequently enough (and
you WANT monitoring software to monitor things!) that we could never
use a shutdown immediate
--- Pardee, Roy E [EMAIL PROTECTED] wrote:
I am certainly not suggesting that recovery can't handle a crash--I'm
just
trying to make sure
PROTECTED]
Sent by: [EMAIL PROTECTED]
03/04/2003 09:14 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
cc:
Subject:RE: dbshut script - shutdown or shutdown
immediate
Suppose you have a database with a sid of mydb
preference. The point I am trying to make is if the
situation demands shutdown abort, then it doesn't make sense jumping through
hoops not to use it.
Regards,
Denny
Quoting Daniel W. Fink [EMAIL PROTECTED]:
Shutdown Immediate v. Shutdown abort (Tastes Great...Less Filling!)
I'll admit
Carmichael [mailto:[EMAIL PROTECTED]
Enviado el: Miércoles, 02 de Abril de 2003 22:34
Para: Multiple recipients of list ORACLE-L
Asunto: RE: dbshut script - shutdown or shutdown immediate
yeah so? are you suggesting that Oracle instance recovery can't handle
a database crash? If so, better pray your
will continue... And on a number of occasions, the Sunday reboot actually took the
server down (and brought it up) on Monday mornings when users complained that they
could not get to databases that were shutdown properly with 'shutdown immediate'.
- Kirti
-Original Message-
Sent
Title: RE: dbshut script - shutdown or shutdown immediate
-Original Message-
From: Jeremiah Wilton [mailto:[EMAIL PROTECTED]]
...
So use your test systems, load them up like production, and try both.
I bet in 9 out of 10 cases, checkpoint+abort+startup will be much
faster
Title: RE: dbshut script - shutdown or shutdown immediate
-Original Message-
From: Pardee, Roy E [mailto:[EMAIL PROTECTED]]
I would
have guessed
that optimally, you'd try immediate first then abort if
immediate takes
too long.
I've read that some people on the list have
Jacques - We have used SHUTDOWN IMMEDIATE for over 5 years now for cold
backups, with zero problems. Weekend before last we had 3 production
databases that didn't go down for backup (all of our databases scheduled for
cold backups). When I checked the following morning they were just hanging
Here's how we do it:
We have 2 cron jobs, one of which runs 10 minutes after the first.
The first does a shutdown immediate. The second checks if oracle is running
and, if so, does a shutdown abort.
-Original Message-
Sent: Thursday, April 03, 2003 2:24 PM
To: Multiple recipients
: dbshut script - shutdown or shutdown immediate
-Original Message-
From: Pardee, Roy E [mailto:[EMAIL PROTECTED]
I would
have guessed
that optimally, you'd try immediate first then abort if
immediate takes
too long.
I've read that some people on the list have done this. I am
StartTime
Dim ImmediateFailed
Const WaitMinutes = 15
Set WinShell = CreateObject(WScript.Shell)
ImmediateFailed = False
StartTime = Now
Set jobImmediate = WinShell.Exec(call to sqlplus w/shutdown immediate
script)
Do While jobImmediate.Status = WSHRunning
WScript.Sleep 5000
If DateDiff(n, StartTime
From: Joan Hsieh [EMAIL PROTECTED]
Chris,
We hang on shutdown immediate, not startup. That's why I choose to use
shutdown abort.
Well, in that case of course you'd use it, but personally, if it was me, I'd
want to find out why it was hanging, and fix that instead. I'm not
suggesting shutdown
.
Looking at $ORACLE_HOME/bin/dbshut, I notice that the input to sqlplus
is
connect internal
shutdown
Should I modify the script to shutdown immediate so that it kills
any connections?
Environment is Oracle 8.1.7 /AIX 4.3.3.
Thanks,
Peter Schauss
Northrop Grumman Corporation
Peter:
One of the first things we do after installing Oracle is
to modify dbshut to 'shutdown immediate'. We have
had no side-effects from this change.
Cheers,
Mike
-Original Message-
Sent: Wednesday, April 02, 2003 7:04 AM
To: Multiple recipients of list ORACLE-L
I have one Oracle
Peter,
I modified to shutdown abort, starup then shutdown immediate.
joan
Schauss, Peter wrote:
I have one Oracle instance which supports an application
server which always maintains a database connection.
The UNIX system administrator tells me that this instance always
hangs when she
Peter,
Shutdown immediate would be a better choice. Might also be a good idea to
have the app server process stopped prior to the database instance being
shutdown.
I have seen apps that have left ghost connections or go nuts when the
database disappeared (bad error handling I guess).
david
We do shutdown abort. But we do checkpoint before shutdown abort i.e,
alter system checkpoint;
shutdown abort;
Then, while bringing up, we do
startup restrict;
shutdown immediate;
startup
Rao
-Original Message-
Sent: Wednesday, April 02, 2003 11:34 AM
To: Multiple recipients
she tries to shut down the system. The other instances,
which do not support a 24x7 process shut down properly.
Looking at $ORACLE_HOME/bin/dbshut, I notice that the input to sqlplus
is
connect internal
shutdown
Should I modify the script to shutdown immediate so that it kills
;
shutdown abort;
Then, while bringing up, we do
startup restrict;
shutdown immediate;
startup
Rao
-Original Message-
Sent: Wednesday, April 02, 2003 11:34 AM
To: Multiple recipients of list ORACLE-L
Peter,
I modified to shutdown abort, starup then shutdown immediate.
joan
We replace the simple shutdown command with:
shutdown immediate
startup restrict
alter system switch logfile;
host sleep 10
shutdown immediate
We recently installed 9.2.0.2-64bit on AIX. As of that release, Oracle is
still shipping dbshut with simply
On Wed, 2 Apr 2003, [EMAIL PROTECTED] wrote:
Then, while bringing up, we do
startup restrict;
shutdown immediate;
startup
Why? Doesn't it start up fine the first time?
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
--
Please see the official ORACLE-L FAQ: http
process shut down properly.
Looking at $ORACLE_HOME/bin/dbshut, I notice that the input to sqlplus
is
connect internal
shutdown
Should I modify the script to shutdown immediate so that it kills
any connections?
Environment is Oracle 8.1.7 /AIX 4.3.3.
From: Joan Hsieh [EMAIL
]
[EMAIL PROTECTED] cc:
om Subject: RE: dbshut script - shutdown or
shutdown immediate
Shutdown abort is pretty drastic, are you sure shutdown immediate didn't
work?
Well said. This topic has been circulating in many DBA forums for a long time.
Shutdown immediate does rollback and will take time if no.of users
is high. On the otherside, shutdown abort simply takes the db down
, May 1 1:00pm - 2:00pm - Automatic Undo Internals
GovindanK wrote:
Shutdown abort is pretty drastic, are you sure shutdown immediate didn't
work?
Well said. This topic has been circulating in many DBA forums for a long time. Shutdown immediate does rollback and will take time
At first, we do shutdown immediate, then startup. But we do have couple
times hang there and couldn't do the cold backup. Since changed to
shutdown abort, startup and shutdown immediate, we don't have any
problem at all. our database is in archive mode. Since our production
database has to refresh
GovindanK wrote:
Shutdown abort is pretty drastic, are you sure shutdown immediate didn't
work?
Well said. This topic has been circulating in many DBA forums for a long time.
Shutdown immediate does rollback and will take time if no.of users
is high. On the otherside, shutdown abort simply takes
://www.optimaldba.com
GovindanK wrote:
Shutdown abort is pretty drastic, are you sure shutdown immediate didn't
work?
Well said. This topic has been circulating in many DBA forums for a long time.
Shutdown immediate does rollback and will take time if no.of users
is high
The scenario you describe would occur regardless of the archive mode. An
active log cannot be archived. This would require that the ARCH process read
the log while LGWR is writing it. Once a log switch occurs (automatic or
manual), the previously active log can be archived.
In this scenario,
not support a 24x7 process shut down properly.
Looking at $ORACLE_HOME/bin/dbshut, I notice that the input to
sqlplus
is
connect internal
shutdown
Should I modify the script to shutdown immediate so that it kills
any connections?
Environment is Oracle 8.1.7
:Re: dbshut script - shutdown or shutdown immediate
Multiplexing redo logs has nothing to do with the archive mode. Logs are
multiplexed so that an error writing to one of the members in a group does
not cause the instance to terminate.
Myth - If you use disk mirroring, you don't need
On Wed, 2 Apr 2003, Stephen Murphy wrote:
We replace the simple shutdown command with:
shutdown immediate
startup restrict
alter system switch logfile;
host sleep 10
shutdown immediate
Why do you do this elaborate dance? Are you trying to get the last
On Wed, 2 Apr 2003, Chris Berry wrote:
Shutdown abort is pretty drastic, are you sure shutdown immediate
didn't work?
What is drastic about shutdown abort?
Never one to opt out of a shutdown abort thread,
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
- Uses shutdown abort exclusively
On Wed, 2 Apr 2003, GovindanK wrote:
Shutdown immediate does rollback and will take time if no.of users
is high.
Number of users is not the largest contributing factor to shutdown
immediate taking a long time. The longest poles in the tent are large
transaction rollback and lazy temp segment
To: Multiple recipients of list ORACLE-L
On Wed, 2 Apr 2003, Chris Berry wrote:
Shutdown abort is pretty drastic, are you sure shutdown immediate
didn't work?
What is drastic about shutdown abort?
Never one to opt out of a shutdown abort thread,
--
Jeremiah Wilton
http://www.speakeasy.net
http://download-west.oracle.com/docs/cd/A81042_01/DOC/server.816/a76956/onlinere.htm#3981
would be nice reference.
What i was trying to communicate was this: If the log is not multiplexed and the only
log member is not avbl for writing then LGWR cannot write and the db instance will go
down.
Agreed. I admit my English needs some improvement. What i wanted to say was about
rollback but used the words no.of.users. Thanks for pointing out.
GovindanK
Jeremiah Wilton [EMAIL PROTECTED] wrote:
On Wed, 2 Apr 2003, GovindanK wrote:
Shutdown immediate does rollback and will take time
From: Jeremiah Wilton [EMAIL PROTECTED]
On Wed, 2 Apr 2003, Chris Berry wrote:
Shutdown abort is pretty drastic, are you sure shutdown immediate
didn't work?
What is drastic about shutdown abort?
Never one to opt out of a shutdown abort thread,
--
Jeremiah Wilton
http://www.speakeasy.net
sure shutdown immediate
didn't work?
What is drastic about shutdown abort?
Never one to opt out of a shutdown abort thread,
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
- Uses shutdown abort exclusively
- successful shutdowns/startups: over 10,000
- problems with shutdown abort: 0
IT
Extension 8487
-Original Message-
Sent: Wednesday, April 02, 2003 2:09 PM
To: Multiple recipients of list ORACLE-L
On Wed, 2 Apr 2003, Chris Berry wrote:
Shutdown abort is pretty drastic, are you sure shutdown immediate
didn't work?
What is drastic about shutdown abort?
Never one to opt
To me it seemed the same as turning off your computer with the power button instead
of the shutdown command or using kill -9, sometimes you have to, but it's not what
you do normally.
Chris Berry
Sounds practical.
GovindanK
--
Shutdown Immediate v. Shutdown abort (Tastes Great...Less Filling!)
I'll admit to being in the Immediate camp. Why? I like the database to come down in a
consistent state except in emergency circumstances. There have been bugs related to
shutdown abort causing database problems.
Do those
wait for db tasks on shutdown immediate or you can wait for
recovery later. It just depends on when you want to wait and the times
are not always the same. Under some circumstances, immediate may cause
a much very long wait and that can be unacceptable. If you need to bring it
down, don't fear
is pretty drastic, are you sure shutdown immediate
didn't work?
What is drastic about shutdown abort?
Never one to opt out of a shutdown abort thread,
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
- Uses shutdown abort exclusively
- successful shutdowns/startups: over 10,000
- shutdown or
shutdown immediate
Sent by:
[EMAIL PROTECTED]
om
script - shutdown or shutdown immediate
Suppose you have a database with a sid of mydb running on unix.
Shutdown abort is like doing the following from the unix command line:
ps -ef | grep mydb | grep -v grep | xargs kill -9. All the processes
that make up the instance or processes
is pretty drastic, are you sure shutdown immediate
didn't work?
What is drastic about shutdown abort?
Never one to opt out of a shutdown abort thread,
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
- Uses shutdown abort exclusively
- successful shutdowns/startups: over 10,000
the shutdown,
use
lsof to trace them back to the client app OR select a list of
sessions
and their respective processes prior to shutdown
5. Forget about shutdown immediate, use shutdown abort.
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
On Sun, 23 Mar 2003, DENNIS WILLIAMS wrote
/rollback prior to
shutdown
4. Look for which processes are still alive during the shutdown, use
lsof to trace them back to the client app OR select a list of sessions
and their respective processes prior to shutdown
5. Forget about shutdown immediate, use shutdown abort.
--
Jeremiah Wilton
http
processes are still alive during
the shutdown, use
lsof to trace them back to the client app OR select
a list of sessions
and their respective processes prior to shutdown
5. Forget about shutdown immediate, use shutdown
abort.
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
On Sun
of sessions
and their respective processes prior to shutdown
5. Forget about shutdown immediate, use shutdown
abort.
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
On Sun, 23 Mar 2003, DENNIS WILLIAMS wrote:
We have been running Oracle 8.1.6 unchanged for
several years. Within
that need commit/rollback prior to
shutdown
4. Look for which processes are still alive during the shutdown, use
lsof to trace them back to the client app OR select a list of sessions
and their respective processes prior to shutdown
5. Forget about shutdown immediate, use shutdown abort.
--
Jeremiah
DENNIS WILLIAMS wrote:
We have been running Oracle 8.1.6 unchanged for several years. Within the
past 3 days, our cold backup scripts have had a shutdown immediate hang. In
the alert log the message is:
Shutting down instance (immediate)
Sun Mar 23 00:09:10 2003
SHUTDOWN: waiting for active
Two things to check:
1. Check dba_jobs to see if any jobs are running like an analyze. I've had
this happen to me. I tried to do a shutdown immediate but database is
waiting for analyze job to finish (several hours).
2. Check if intelligent agent is running. You should shutdown
:)
-
Seán O' Neill
Organon (Ireland) Ltd.
[subscribed: digest mode]
From: Ravi Kulkarni [EMAIL PROTECTED]
Date: Sat, 5 Oct 2002 02:01:58 -0400
Subject: Shutdown Immediate
Gurus,
Solaris8/Oracle 8173-32bit.
Shutdown abort works but Shutdown immediate hangs. Startup Normal is fine.
No special
recipients of list ORACLE-L
Two things to check:
1. Check dba_jobs to see if any jobs are running like an analyze. I've
had
this happen to me. I tried to do a shutdown immediate but database is
waiting for analyze job to finish (several hours).
2. Check if intelligent agent is running. You should
Or, if you don't want all your pagers going off because OEM thinks that all
the instances on that server are down when it loses contact with the IA, on
Unixishes you can:
ps -ef|grep oracle$ORACLE_SID|grep -v grep
...from another session after starting the SHUTDOWN IMMEDIATE. You
Gurus,
Solaris8/Oracle 8173-32bit.
Shutdown abort works but Shutdown immediate hangs. Startup Normal is fine.
No special entries in Alert log regarding smon/pmon
activities-postStartup/During Shutdown. All DB Sessions/connections
cleaned/killed before shutdown. Tried several times.
Any Hints
,
Solaris8/Oracle 8173-32bit.
Shutdown abort works but Shutdown immediate hangs. Startup Normal is
fine.
No special entries in Alert log regarding smon/pmon
activities-postStartup/During Shutdown. All DB Sessions/connections
cleaned/killed before shutdown. Tried several times.
Any Hints?
TIA
Define hang.
In other words, how much time passes before you consider it a hang?
SHUTDOWN IMMEDIATE can take some time.
Our SAP admin got impatient last week and did a SHUTDOWN ABORT
on a database cuz she thought the SHUTDOWN IMMEDIATE was taking
too long.
Files were in need of recovery
Two things to check:
1. Check dba_jobs to see if any jobs are running like an analyze. I've had
this happen to me. I tried to do a shutdown immediate but database is
waiting for analyze job to finish (several hours).
2. Check if intelligent agent is running. You should shutdown intelligent
need to shutdown) to not use shutdown immediate -
because they got the name wrong :-) If you need to
shutdown, I'd just do:
alter system checkpoint;
shutdown abort
hth
connor
--- Steve Perry [EMAIL PROTECTED] wrote:
MessageI hope somebody can help me with this
shutdown problem. There's 2
;
Muthar
Ahmed
DBA
-Original Message-From: Steve Perry
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, August 21, 2002 11:13
PMTo: Multiple recipients of list ORACLE-LSubject:
Shutdown Immediate Hanging
I hope somebody can help me with
this shutdown problem. There's 2 questions
intermittent shutdown
problems.
The shutdown never
completes.
Here's are the steps used to stop the
database
1.) Stop the application
servers
1.) run a kill session script to kill
all remaining sessions except the one running the script
2.) issue shutdown immediate and hope
it shuts down.
At this point
I have Oracle 8.1.7 running on windoze NT 4.0. Every night I have a script
that kicks off a cold backup. Part of the script issues the command
SHUTDOWN IMMEDIATE
which normally works just fine before I actually copy my files. However,
periodically the shutdown immediate command does not work
Dave,
Worth Checking -
Sometimes the OracleSIDAgent service or the OracleSIDDataGatherer
service, if running, will cause the SHUTDOWN IMMEDIATE to hang. Try
shutting such services down by including a 'net stop OracleSIDAgent..'
etc. in your script, just before you issue the SHUTDOWN IMMEDIATE
Dave:
The message in the alert log means that there are uncommitted transactions.
During a shutdown immediate uncommitted transactions are rolled back and
Oracle must wait until this rollback is complete before the db can be
actually shut down.
You could do a shutdown abort, but then you would
Jon,
One correction, shutdown immediate waits till all uncommitted transactions
are committed or rolled back. The client session must do one or the other,
otherwise the shutdown hangs waiting for the end user. This is a good example
of where setting the idle time in user_profiles is a good
Dave,
We've periodically had this problem with various jobs that
were running at the time of the shutdown immediate. I try
to isolate the cause by killing the various processes I still
see running via ps -ef | grep SID.
Sometimes the problem has been our RMAN backup that
is running
On Mon, 10 Sep 2001, [EMAIL PROTECTED] wrote:
One correction, shutdown immediate waits till all uncommitted
transactions are committed or rolled back. The client session must
do one or the other, otherwise the shutdown hangs waiting for the
end user.
No, that's shutdown transactional
Sometimes the instance never shuts down,
BUT the database gets closed. What else could
hang up SVRMGRL ?
TIA
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Leyden, Joseph
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
Joseph
If you are using Novell as your OS then a memory leak that exists in older versions
of Novell might be the problem. The message mixed in with the output messages stated
that a lot of resources were not released. The upgrade to Novell 4.2 appears to have
solved the shutdown problem for
Title: RE: shutdown immediate
I am
at Oracle 8.0.5 AIX 4.3.2
should
I upgrade my Oracle db to get
a good
shutdown immediate?
-Original Message-From: Behar, Rivaldi
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, May 09,
2001 2:46 PMTo: Multiple recipients of list
ORACLE
77 matches
Mail list logo
