RE: Rolling Upgrade of Oracle on a 24*7 implementation

Someone at MetaToke must have pried their lips off the crack pipe, because I was able to hobble through a small query.

Despite the fact that i remember specifically reading oracle documentation on OPS ( 73? 80? not 8i...) that *allowed* rolling upgrades, the current word is that it is NOT recommended.  Certainly, as Greg notes, with the new "helpful" features of the installer pushing code and such, you don't have a real rolling upgrade going. <shrug>

Maybe that's what happened to our friends at MetaBLink. They tried to do a rolling upgrade. ;-)

Yours in Data,

"Don't help, ok Wally?",

Ross

-----Original Message-----
From: Nelson, Greg [mailto:GNelson_at_banknorth.com] Sent: Thursday, February 22, 2001 4:30 PM To: Multiple recipients of list ORACLE-L Subject: RE: Rolling Upgrade of Oracle on a 24*7 implementation

I've run OPS on OpenVMS and HPUX and you can't do a rolling upgrade without contortions.  The actual database files are shared by the nodes so you usually wouldn't want different versions of Oracle sharing the files.  When you install Oracle software on HPUX the software is pushed to the other nodes from the one you are on by Oracle's installer.  Not sure if Oracle on VMS also pushes the software now as it has been over two years since I worked with it. It didn't with Oracle 7.
 

However, you could break apart the cluster, run the databases without OPS (unless you have 3 or more nodes), install a different version of Oracle, test it, install it on the other node(s) when ready, and put back the cluster.  This obviously adds complexity to your and the Sys Admin's life but can be done.
 

To have a true 24*7 implementation you would have to add another piece such as a standby database.
 

Greg Nelson
gnelson_at_banknorth.com <mailto:gnelson_at_banknorth.com>
 
 -----Original Message-----

Sent: Thursday, February 22, 2001 3:17 PM To: Multiple recipients of list ORACLE-L

Gary,
 

i wish i knew the answers to those good questions.
 

Consider though, that until recently the DLM was the job of the OS vendor NOT the dbms vendor and so a dbms version tick changed nothing in that regard.
 

as for DD upgrades...<shrug>...praps the init.ora parameter compatible is not set
to the newest version until the latest upgrade is in place? Just a guess.
 

For a real answer, you'd have to open an iTar, and head to Tibet to meditate yourself into Perfect SelfTranscendence before getting an answer from the hamster
running MetaStink.
 
 

-----Original Message-----
Sent: Thursday, February 22, 2001 2:56 PM To: Multiple recipients of list ORACLE-L

So, when freshly upgraded box comes online, lock manager doesn't have a problem with different versions? And on related note, at what point is the data dictionary upgraded? Having never done this, I'm rather curious....
 

-----Original Message-----
Sent: Thursday, February 22, 2001 2:26 PM To: Multiple recipients of list ORACLE-L

You can do rolling upgrades on OPS, yes.

For quite some time, now....not a "new feature" either.

-----Original Message-----
Sent: Thursday, February 22, 2001 2:04 PM To: Multiple recipients of list ORACLE-L

Not 100% sure, but I don't believe you can do a "rolling" upgrade in OPS configuration. All or nothing deal it seems. I can't imagine DLM capable of operating with different Oracle versions in multiple instances. My guess is,

you could upgrade one box in the cluster at a time, but you would need to have a black out for the last box. Again, this is only a guess.

Gary

-----Original Message-----
Vallath
Sent: Thursday, February 22, 2001 1:41 PM To: Multiple recipients of list ORACLE-L

Any body have ideas on how a Oracle Upgrade is done in a 24*7 installation for a very large database specifically using OPS.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Nelson, Greg


  INET: GNelson_at_banknorth.com



Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).