Look again at step 5. The sequence is:
alter system checkpoint;
shutdown abort;
startup;
shutdown immediate;
The theory is that the checkpoint may take awhile but the database is still
available. Then the shutdown abort - startup - shutdown immediate sequence
get's us to a consistent state as re
Patrick <[EMAIL PROTECTED]>
> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> Sent: Thursday, February 08, 2001 4:15 PM
> Subject: RE: Applying patches - minimizing database down time
>
>
> > Do you have a test instance to apply the patches to? Check
; >
> > I have not actually done this, but in theory it should work. Look into
> > the
> > documentation for logminer.
> >
> > > -Original Message-
> > > From: Molina, Gerardo [SMTP:[EMAIL PROTECTED]]
> > > Sent: Thursday, February 08, 2001
, 2001 2:45 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Applying patches - minimizing database down time
>
> Yeah, I like the theory but putting the theory into practice is another
> story. Maybe I'll try it another day. I thought Oracle supported 24X7
> Inter
-Original Message-
> From: Molina, Gerardo [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, February 08, 2001 12:56 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Applying patches - minimizing database down time
>
> (Not a sales pitch)
>
> Talk to your Qu
logminer.
> -Original Message-
> From: Molina, Gerardo [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, February 08, 2001 12:56 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Applying patches - minimizing database down time
>
> (Not a sales pitch)
>
(Not a sales pitch)
Talk to your Quest rep about a product they are working on or is already
available which will allow you to do upgrades/patches with no or minimal
downtime. It involves a kind of replication. The way I see it is you must
have some kind of replication if you want to make upgra
Attention all installation gurus/hacks...
I'm looking for suggestions, experiences, and best practices on safely
applying Oracle patches and minimizing database down time. By way of example
let's say we're going from server version 8.1.6.0.0 to 8.1.6.3.0. Let's also
say we're going to apply the 8
