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
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
