Welcome Guest ( Log In | Register )


 
 
 
 
 
 

 
Oracle performance tuning 

software
 
Oracle 

performance Tuning 10g reference poster
 
Oracle training in Linux 

commands
 
Oracle training 

Excel
 
Easy Oracle Jumpstart
 
Oracle training & performance tuning books
 
Burleson Consulting Remote DB Administration
 
 
 
Reply to this topicStart new topic
> Upgrade To 9.2.0.6
shay_b
post Aug 9 2006, 10:03 AM
Post #1


Advanced Member
***

Group: Members
Posts: 181
Joined: 20-July 05
Member No.: 2,545



Hi
ineed to do Upgrade to my database from 8.1.7.4 to 9.2.0.6 i can do this in ONLINE ?

i can"t shutdown the database is need to be in ONLINE 24H * 7 DAY .
Go to the top of the page
 
+Quote Post
dave
post Aug 9 2006, 10:06 AM
Post #2


Advanced Member
***

Group: Members
Posts: 5,028
Joined: 8-October 04
Member No.: 785



no you cannot do it online (think about it)

you need downtime
Go to the top of the page
 
+Quote Post
herod
post Aug 9 2006, 12:22 PM
Post #3


Advanced Member
***

Group: Members
Posts: 54
Joined: 20-July 06
Member No.: 4,611



QUOTE (shay_b @ Aug 9 2006, 03:04 PM) *
Hi
ineed to do Upgrade to my database from 8.1.7.4 to 9.2.0.6 i can do this in ONLINE ?

i can"t shutdown the database is need to be in ONLINE 24H * 7 DAY .


You need downtime.

I have done this for one of our 24*7 systems, and this was my approach - others will have a different approach. Possibly better. we went 8 to 10g

1.) We rented similar hardware to what the production DB was working on. We bought a duplicate set of drives.
2.) We got a copy of the production DB running on the rental, made sure it was all good (days of work).
We made sure that the mount points etc were all the same as on prod - an exact as possible duplicate.
3.) Had downtime, unmounted the drives (external bays) from the prod machine, put those drives in place on the rental. Brought everything back up. Total downtime was 19 minutes and worked like a charm. put the new drives on the prod box
4.) We upgraded the prod database on the prod machine, tested did our work, took weeks while everything ran on the rental. We built refresh scripts that converted data that needed converted, we also kept the 10g DB as refreshed as possible from the prod DB, only about 1 hour behind using manual scripts.
6.) we scheduled downtime on the rental, refreshed the data, and remounted the drives. Took under an hour. Brought the prod machine back up and decomissioned the rental as soon as we got user sign off a day or two later.


We took the time to add 2 CPU's and some RAM to the production machine as well in the time the rental was running. It was just barely over an hour total downtime spread weeks apart. management was happy and since we scheduled the work for 3am our time, nobody really cared from the users. And those that did - we apologized for the scheduled maintenance.

Costly as we had to pay for the rental and an entire duplicate set of disks. But we used the extra disks on other servers once we were done with them.


This was on HPUX


--------------------
Go to the top of the page
 
+Quote Post
burleson
post Aug 9 2006, 05:56 PM
Post #4


Advanced Member
***

Group: Members
Posts: 7,973
Joined: 26-January 04
Member No.: 13



Hi Herod,

Wow. Great tip, I'm impressed.

Thanks for sharing . . .

Also, one of my consutants (Steve Karam, OCM) has another low-downtime upgrade approach:

http://www.dba-oracle.com/t_rolling_upgrades.htm


--------------------
Hope this helps. . .

Donald K. Burleson
Oracle Press author
Author of Oracle Tuning: The Definitive Reference
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version Time is now: 8th September 2010 - 03:27 PM