OS: Solaris
OS Version: Optron 5.10
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 5.0MP3HF2 for VCS Oracle Agent 5.0MP3
===============================================================

 Patch Date:  November, 2009

This README provides information on:
 * BEFORE GETTING STARTED
 * FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH
 * PACKAGES AFFECTED BY THE PATCH
 * INSTALLING THE PATCH
 * UNINSTALLING THE PATCH


BEFORE GETTING STARTED:
----------------------
This patch only applies to:
	VRTSvcsor 5.0MP3 running on Solaris Optron

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


FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH: 
--------------------------------------------
Etrack Incidents: 1543386, 1544263, 1780698

SDR's of Fixed Symantec Incidents:
--------------------------------
Symantec Incident : 1543386
Symptom:
	When an error corresponding to an ORA error, is set in 
	the oraerror.dat file, the agent did not honor the action.
	Instead, it was always failing over the resource.
Defect Description:
	This happenned because, the function call to parse the ORA
	errors and to take the corresponding actions was missing.
Resolution:
	The ORA errors are now populated properly for the Oracle 
	agent's reference. It now performs the corresponding 
	actions mentioned in the oraerror.dat.

Symantec Incident : 1544263
Symptom:
	With different kind of errors, the agent used to take actions
	corresponding to the last received error, ignoring the rest.
Defect Description:
	With this parsing method, Oracle agent may ignore some 
	important actions, specified in oraerror.dat file,
	which could result in inconsistency of the state of the resource.
Resolution:
	The parsing method is updated to prioritize certain actions, 
	when multiple errors occur at a time.

Symantec Incident : 1780698
Symptom:
	Oracle Agent was not able to send SNMP/SMTP notifications 
	in case of any error defined in oraerror.dat file.
Defect Description:
	There was a problem in forming the hanotify(1m) command 
	in Oracle Agent, while sending notifications.
Resolution:
	The problem is now fixed to correctly form the hanotify(1m) 
	command in Oracle Agent, while sending notifications.


PACKAGES AFFECTED BY THE PATCH:
-------------------------------
This patch updates the following VCS package(s) 
	VRTSvcsor from 5.0MP3 to 5.0MP3HF2


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

Stopping VCS Oracle Agent on the cluster node:
---------------------------------------------
Stop Oracle agent using:
	# haagent -stop Oracle -sys [system_name] -force

Installing the Patch:
--------------------
1. Un-compress the downloaded patch from Symantec.
   Change directory to the unzipped patch location. 
   Install the VRTSvcsor 5.0MP3HF1 patch using the following command:
	# patchadd 142626-01

2. Verify that the new patch has been installed:
	# showrev -p | grep  142626-01
   You will find the following output on display with the patch 
   installed properly:
Patch: 142626-01 Obsoletes:  Requires: 128071-03 Incompatibles:  
Packages: VRTSvcsor


Re-starting VCS Oracle Agent on the cluster node:
------------------------------------------------
Re-start Oracle agent using:
	# haagent -start Oracle -sys [system_name]


UNINSTALLING THE PATCH:
-----------------------
The following steps should be run on all nodes in the VCS cluster:

Steps to remove the Patch from a cluster node:
---------------------------------------------
1. Follow the steps provided under 
   "Stopping VCS Oracle Agent on the cluster node" section above, 
   to stop VCS Oracle Agent on the node.

2. Remove the patch by the following command:
	# patchrm 142626-01

3. Verify that the patch has been removed from the system:
	# showrev -p | grep  142626-01
   Nothing will be printed after successful removal of the patch.

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