procedure for upgrading oracle in vcs

book

Article ID: 100019477

calendar_today

Updated On:

Resolution


procedure upgrading oracle vcs
******************************

customer has SF 5.0 and his oracle DB in vcs (No RAC).
he wanted to perform the oracle upgrade and wanted to know how to do that so that oracle should not failover to the failover node when they shutdown the data base.

provided the following methods for getting oracle out side of the VCS control:

Method One=>
----------

1- make vcs config read/writeable
#haconf -makerw
2- modify the oracle resource to "non critical"
#hares -modify Critical 0
#hares -modify Critical 0

3- make the vcs readable only
#haconf -dump -makero

4- Offline the oracle and Listener as its non critical it won't failover
#hares -offline -sys
#hares -offline -sys

Method Two:=>

In this method you can freeze the oracle SG so that vcs no longer monitors it by using the any of the following commands:

1- hagrp -freeze - persistent OR
2- hastop -force [ it will stop the vcs keeping apps online]

Now the SG is out side of the vcs and the oracle can be upgraded if you followed the method one then you have to restart the oracle as it has been offlined from VCS. follow the oracle upgrade procedure for the upgrade.


Once the upgrade is done you have to modify the vcs config for the new changes took place during upgrade

1- go to the read/write mode of vcs
#haconf -makerw

2- follow the following command to modify the new HOME/TNSAdmin and pfile values:

#hares -modify Oracle-name Home "/orlog/oracle/product/"
#hares -modify Oracle-name Pfile ""
#hares -modify Listener-name Home "/orlog/oracle/product/"
#hares -modify Listener-name TnsAdmin "/orlog/oracle/product//network/admin"
#haconf -dump -makero


Issue/Introduction

procedure for upgrading oracle in vcs