my own and not those of my
employer or clients **
> -Original Message-
> From: Jeremiah Wilton [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 07, 2003 1:59 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: re SHUTDOWN ABORT -- was RE: Debate on rc
> comm
online redologs and stop until a checkpoint does complete!
> > >
> > > Forcing a checkpoint is a great idea -- for speeding up instance
> > > recovery -- but it doesn't make ABORT any more or less safe.
> > >
> > > My motto is: Shutdown abort is not
at
there are no user sessions operating on the database.
Cheers!
RF
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Behalf Of Jamadagni, Rajendra
Sent: Monday, February 03, 2003 9:01 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: re SHUTDOWN ABORT --
; any given time. If you haven't, the database will soon run out of
> > online redologs and stop until a checkpoint does complete!
> >
> > Forcing a checkpoint is a great idea -- for speeding up instance
> > recovery -- but it doesn't make ABORT any more or less safe.
&
it doesn't make ABORT any more or less safe.
>
> My motto is: Shutdown abort is not shutdown abhorrent!
>
> :-)
>
> --
> Jeremiah "Shutdown Abort" Wilton
> http://www.speakeasy.net/~jwilton
>
> On Thu, 6 Feb 2003, Robert Freeman wrote:
>
> > RE: re SHUTDOWN ABOR
Feb 2003, Robert Freeman wrote:
> RE: re SHUTDOWN ABORT -- was RE: Debate on rc commands Solaris andLet me
> throw in my 2 cents worth on this topic. There are two problems with
> SHUTDOWN ABORT that I have experienced in the past.
>
> 1. Before 9i (it appears to be fixed in 9i) if yo
got it
Thanks,
Dave
-Original Message-
Sent: Friday, February 07, 2003 11:30 AM
To: Multiple recipients of list ORACLE-L
an
Dave
Just add one more line before to shutdown abort...
alter system checkpoint;
SHUTDOWN ABORT
STARTUP RESTRICT
SHUTDOWN IMMEDIATE
Regards
Rafiq
Reply-T
Dave
Just add one more line before to shutdown abort...
alter system checkpoint;
SHUTDOWN ABORT
STARTUP RESTRICT
SHUTDOWN IMMEDIATE
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
Date: Fri, 07 Feb 2003 07:28:43 -0800
I do my cold bac
Title: RE: re SHUTDOWN ABORT -- was RE: Debate on rc commands Solaris and
I do
my cold backups at a time when the system is not being used. In the future
I want to learn RMAN for hot backups but for now I do the
following;
SHUTDOWN ABORT
STARTUP RESTRICT
SHUTDOWN IMMEDIATE
You
mention
Title: RE: re SHUTDOWN ABORT -- was RE: Debate on rc commands Solaris an
Thanks Robert,
I wasn't aware of that issue. Plus now that we have all instances on 9202, we hope it won't bite us. As for adding tablespaces dynamically, no chance. We *require* that development team reques
Let me throw in my 2 cents worth on this topic. There are two problems with
SHUTDOWN ABORT that I have experienced in the past.
1. Before 9i (it appears to be fixed in 9i) if you inserted data in a table,
then did a shutdown abort, if after restarting the database, you tried to
truncate the table
Title: RE: re SHUTDOWN ABORT -- was RE: Debate on rc commands Solaris and
Let me
throw in my 2 cents worth on this topic. There are two problems with SHUTDOWN
ABORT that I have experienced in the past.
1.
Before 9i (it appears to be fixed in 9i) if you inserted data in a table, then
did a
Title: RE: re SHUTDOWN ABORT -- was RE: Debate on rc commands Solaris and
When we do cold backups, our script issues 'shutdown immediate', if within 3 minutes the db is not shut down, we cancel and issue 'shutdown abort'. In either case, we (again issue) startup/shutd
Rajesh,
There are unknowns with every feature. ABORT is a feature just as
IMMEDIATE is. In version 7, I encountered a bug with IMMEDIATE that
required recovery from a backup, and eventually manual BBED'ing of the
SYSTEM datafile by Oracle BDE. SO maybe we shouldn't use immediate
either. I'll j
I totally agree
I am witness of one of these untested combination resulting in "true disaster" .
And the combination was shutdown immediate to an extremely busy database (with no
response), followed by shutdown abort and all the data files got corrupted. We could
not recover tha
I have to say that I still have an emotional
response to 'shutdown abort', despite knowing
that logically it ought to be perfectly safe.
The reason for this is the lack of stress testing
that goes on at Oracle Corp. In most (if not
all) cases, the only blanket stress test that
the software gets
...kind of a side story on the virtues of ALTER SYSTEM CHECKPOINT...
About 6-7 years ago, I was teaching Oracle Education's "Backup and Recovery
Workshop", which was a 3 day class. The first 2 days are blabber/lecture
and the last day is all lab. In that last day, students spend the morning
desi
You're absolutely correct - I have neglected the
acknowledge many of the various places I've seen
proposing the 'alter system checkpoint / shutdown
abort' model, including your web site.
Apologies.
Cheers
Connor
--- Jeremiah Wilton <[EMAIL PROTECTED]> wrote: >
Alter system checkpoint... You don
I began using 'shutdown abort' on a regular basis in 7.x
( whenever shutdown immediate became available )
because that was the *only* way to guarantee a shutdown.
Jared
On Sunday 02 February 2003 01:23, Jeremiah Wilton wrote:
> Alter system checkpoint... You don't say...
>
> Hey, this is the fir
Alter system checkpoint... You don't say...
Hey, this is the first time this thread has concluded without the
usual "you guys better watch out b/c yer gonna break your database!"
post.
I'd say this universal support for ABORT over IMMEDIATE represents a
dramatic change in the prevailing DBA attit
Agreed. All that matters is the redo logs. If Oracle
had named the shutdown options more accurately, that
is
shutdown abort => shutdown fast
shutdown immediate => shutdown hopefully
shutdown transactional => shutdown when hell freezes
over
shutdown normal => shutdown never
then I'm pretty sure I
21 matches
Mail list logo
