OS: Linux
OS Version: SLES10 (x86_64/i686)
Fixes Applied for Products:
	VRTSvcsor - Veritas High Availability Agent for Oracle by Symantec

Additional Instructions:
Please read the instructions below before installing the patch.

  PATCH VRTSvcsor 5.0MP3RP2HF1 for VCS Oracle Agent 5.0MP3RP2
===============================================================

 Patch Date:  July, 2009

This README provides information on:
 * BEFORE GETTING STARTED
 * CRC AND BYTE COUNT
 * FIXES AND ENHANCEMENTS INCLUDED IN THIS PATCH
 * PACKAGES AFFECTED BY THIS PATCH
 * INSTALLING THE PATCH(S)
 * UNINSTALLING THE PATCH(S)


BEFORE GETTING STARTED:
----------------------
This patches only applies to:
	VRTSvcsor 5.0MP3RP2 running on SLES10 (x86_64/i686)

Ensure that you are running the supported configurations before
installing this patch.


CRC AND BYTE COUNT:
------------------
Ensure that the patch file you have downloaded matches the following
checksum and byte count.

The following command can be used to ascertain this:
For SLES10 (i686/x86_64):
# cksum VRTSvcsor-5.0.30.21-MP3RP2HF1_SLES10.i586.rpm
2824637630	3504968	VRTSvcsor-5.0.30.21-MP3RP2HF1_SLES10.i586.rpm


FIXES AND ENHANCEMENTS INCLUDED IN THIS PATCH: 
---------------------------------------------
Etrack Incidents: 1718459

SDR's of Fixed Symantec Incidents:
--------------------------------
Symantec Incident : 1718459
Symptom:
	When we set an error corresponding to an ORA error in 
	the oraerror.dat file, the agent was not honoring the action. 
	Instead, it was always failing over the resource.
Defect Description:
	This was happening because the function call for parsing 
	the ORA errors and taking the corresponding action was missing.
Resolution:
	We had populated the ORA errors in VCSAgStartUp() function. 
	Once we had these ora errors and its corresponding actions, 
	the agent started performing the corresponding errors.


PACKAGES AFFECTED BY THIS PATCH:
-------------------------------
This patch updates the following VCS packages 
	VRSTvcsor from 5.0.30.20 to 5.0.30.21


INSTALLING THE PATCH(S):
-----------------------
The following steps should be run on all nodes in the VCS cluster:

Stopping the VCS Oracle Agent on a node:
---------------------------------------
Stop Oracle & Netlsnr agents using 
	# haagent -stop Oracle -sys <system_name> -force
	# haagent -stop Netlsnr -sys <system_name> -force

Installing Patch(s):
-------------------
Repeat the below steps on all the nodes:
1. Gunzip the downloaded patch from Symantec.
   Change directory to the unzipped patch location. 
   Install the VRTSvcsor patch using the following command.
	# rpm -Uvh VRTSvcsor-5.0.30.21-MP3RP2HF1_<DIST>.<ARCH>.rpm
   where, DIST is SLES10 and ARCH is i586/i686.

2. Verify that the new patch has been installed:
	# rpm -q VRTSvcsor
   You will find the following output on display with 
   the patch installed properly:
	VRTSvcsor-5.0.30.21-MP3RP2HF1_<DIST>
   where, DIST is SLES10.

Re-starting the VCS Oracle Agent on a node:
------------------------------------------
Start Oracle & Netlsnr agents using 
	# haagent -start Oracle -sys <system_name>
	# haagent -start Netlsnr -sys <system_name>


UNINSTALLING THE PATCH(S):
-------------------------
Removal of the patch will result in removing whole package from 
the system/node. To go back to a previous installed version of 
the package, you may need to re-install the package again. 
Following steps need to be run on all nodes :

Steps to Remove the Patch(s) :
-----------------------------
1. Follow the steps provided under "Stopping the VCS Oracle Agent 
   on a node" section above, to stop VCS Oracle Agent on the node.

2. Remove the patch(s) by the following command:
	# rpm -e VRTSvcsor

3. Verify that the new fileset has been backed out:
	# rpm -qa | grep VRTSvcsor 
   The package VRTSvcsor should not be displayed, which confirms 
   that the package is removed.

4. Restart the node following the steps under 
   "Re-Starting the VCS Oracle Agent on a node" section above.