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 a
Alas, I'm until recently a prisoner of windows & so I can't speak to shell
scripts. On windows I'd probably try a windows script host vbscript like
so:
Option Explicit
Dim WinShell
Dim jobImmediate
Dim StartTime
Dim ImmediateFa
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: RE: dbshut script - shutdown or shutdown immediate
> -Original Message-
> From: Pardee, Roy E [mailto:[EMAIL PROTECTED]
>
> I would
> have guessed
> tha
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 of lis
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.
The p
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.
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
Precisely.
I am trying to propose the abort option, but I am not the majority around this place I
call work.. :)
On a more than dozen times in the last few months, I had to kill oracle processes to
get the database to shutdown (with immediate), so the scheduled reboot of the machine
will conti
inal-
De: Rachel 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
Using immediate or abort is a matter of personal preference. Use whichever
option that works for you. But I would not agree that using shutdown abort is
risky or should be avoided. (I don't know of any bugs with shutdown abort.
There could be, but then a lot of other things also could go wro
"Nelson, Allan" <[EMAIL 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
the problem is, if immediate hangs and you have automated the
process... nothing happens. it doesn't time out so you sit. and sit and
sit. and hope that whatever is keeping the database active will
eventually end.
In version 7 (7.3.2) I found that while using a third party monitoring
package that
I am certainly not suggesting that recovery can't handle a crash--I'm just
trying to make sure that I understand what shutdown abort does. Some posts
have implied that it's no big deal, which is counter-intuitive to me. To
me, crashing a program on purpose seems like a drastic measure. No doubt
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.
> > > > > Th
Mark has hit on the crux of the issue. Most of us have expectations
from users and management that we will have the databases available as
much as possible. Downtime costs money and should be avoided.
That said, we will eventually need downtime for one reason or another.
The question becomes how
Rachel
>
> Carmichael To: Multiple recipients
> of list ORACLE-L <[EMAIL PROTECTED]>
> <[EMAIL PROTECTED] cc:
Oracle crash??? What's that :)??? Isn't that a bug in SQL Server only ?
-Mensaje original-
De: Rachel 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 o
cc:
Subject: RE: dbshut 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 u
Subject: RE: dbshut script - shutdown or
shutdown immediate
Sent by:
[EMAIL PROTECTED]
yeah so? are you suggesting that Oracle instance recovery can't handle
a database crash? If so, better pray your server never crashes.
--- "Pardee, Roy E" <[EMAIL PROTECTED]> wrote:
> Well... my official oracle instructor in dba larva school said that
> it's
> tantamount to crashing the db--or so
On Wed, Apr 02, 2003 at 03:43:43PM -0800, Darrell Landrum wrote:
> - Drives to work on busy streets exclusively
> - successful trips to work: over 14,000
> - accidents during trips to work: 0
> - still, I drive carefully
--
I've always taken Jeremiah's modivation on this to be functionality.
You
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 in the
>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
--
|X
- Uses shutdown abort exclusively
- successful shutdowns/startups: over 10,000
- problems with shutdown abort: 0
- versions used: 7.3.2.3 - 10.0 (yes I have a pre-beta)
- still employed!
- Drives to work on busy streets exclusively
- successful trips to work: over 14,000
- accidents during trips
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 that are connected to that
instance are killed. The da
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/~jw
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
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. How
Well... my official oracle instructor in dba larva school said that it's
tantamount to crashing the db--or so I recall anyway. This isn't so?
Peace,
-Roy
Roy Pardee
Programmer/Analyst
SWFPAC Lockheed Martin IT
Extension 8487
-Original Message-
Sent: Wednesday, April 02, 2003 2:09 PM
To
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
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, 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
L PROTECTED]>
cc:
Subject: 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 us
> > >"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 tries to shut down the system. The other instances,
> >
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, yo
What does this have to do with archivelog mode? In the bizarre
scenario in which you lose a log between the time you shut down and
started up, you are screwed with or without archivelog mode.
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
On Wed, 2 Apr 2003, GovindanK wrote:
> This topic
This topic is getting interesting once more. Lets contribute.
>>Multiplexing redo logs has nothing to do with the archive mode.
Take a situation wherein the db is in NOARCH mode with only one member per group
(default setup). The dba gives shutdown abort and upon starting for some reason the
a
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
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 to multiplex your redo logs.
Reality - Mirroring only prote
>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 an
PROTECTED]
[EMAIL PROTECTED] cc:
om Subject: RE: dbshut script - shutdown or
shutdown
>"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 tries to shut down the system. The other instances,
> which do not support
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://www.oraf
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 shutdo
I also started doing this a couple months ago and have not had a shutdown hang since.
Dave
-Original Message-
Sent: Wednesday, April 02, 2003 11:04 AM
To: Multiple recipients of list ORACLE-L
We do shutdown abort. But we do checkpoint before shutdown abort i.e,
alter system checkpoint;
Yes, that should be a standard practice any time you perform an new Oracle install.
Otherwise, that database will problably always hang waiting for all sessions to
disconnect before completing the shutdown.
I believe the latest versions of Oracle have corrected that issue in the dbshut
script.
--
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 of li
From: "Schauss, Peter" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
Subject: dbshut script - shutdown or shutdown immediate
Date: Wed, 02 Apr 2003 07:03:38 -0800
I have one Oracle instance which supports an ap
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 s
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 in
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 tries to shut down the system. The other instances,
which do not support a 24x7 process shut down properly.
51 matches
Mail list logo
