README VERSION		: 1.0
README Creation Date	: 2011-09-14
Patch-ID 		: 145452-03 
Patch Name		: VRTSdbac 5.1SP1RP2-sol10-x86
BASE PACKAGE NAME	: Veritas Oracle Real Application Cluster Support Package by Symantec
BASE PACKAGE VERSION	: VRTSdbac 51SP1
Obsolete Patches	: NONE
Superseded Patches	: NONE
Required Patches	: NONE
Incompatible Patches	: NONE
Supported PADV		: sol10_sparc
(P-Platform , A-Architecture , D-Distribution , V-Version)
Patch Category		:  CORE ,  MEMORYLEAK
Reboot Required		: YES


KNOWN ISSUES : 


FIXED INCIDENTS: 
----------------


 Patch Id::145452-03

 * Incident no::2374970	 Tracking ID ::2210343

 Symptom::CRSResource agent does not support Oracle 11gR2.

 Description::CRSResource agent support for Oracle 11gR2.

 Resolution::CRSResource agent support for Oracle 11gR2.

 * Incident no::2374977	 Tracking ID ::2231603

 Symptom::If a node running SFRAC crashes and comes back online, Oracle instance on any
other existing in the live cluster might crash throwing the IPC errors in the
error logs.

 Description::As per the IPC implementation, if a node running SFRAC crashes and comes back
online, Oracle instance on any other existing in the live cluster might crash
throwing the IPC errors in the error logs.

 Resolution::Perform the cancellation of inprogress rqhs for VSND rqhs too in vcsipc_destwr()
to avoid memory corruption issues during flow-control and peer node death.

 * Incident no::2380469	 Tracking ID ::2551431

 Symptom::SFRAC does not have support for Solaris local zones.

 Description::SFRAC cannot run in Solaris local zone environments where SFRAC is
installed and configured on global zones while Oracle RAC is installed inside
local zones.

 Resolution::Now SFRAC can run in Solaris local zone environments where SFRAC is
installed and configured on global zones while Oracle RAC is installed inside
local zones.

* Incident no::2390892   Tracking ID ::2390967

 Symptom::Starting VCSMM driver on one or more nodes in the cluster causes a memory
leak in the vcsmm_set_cluster_proto function during memory allocation.

  Description::If VCSMM driver is started on one or more nodes in the cluster, it causes memory
leaks. The amount of memory leak depends on the number of nodes in the cluster.
Once the nodes join the cluster, starting VCSMM on any node in the cluster
causes a further increase in the memory leak.

 Resolution::The vcsmm_set_cluster_proto function is now updated to allocate memory only if
 there is no current allocation.

 * Incident no::2429449	 Tracking ID ::2511099

 Symptom::Monitor script for cssd agent (ie. cssd-monitor) uses hard-coded name for cssd
resource and due to this, if resource name used in main.cf is not "cssd", weird 
behavior is shown.

 Description::If cssd resource name in main.cf is not given as "cssd", cssd-monitor script fails
to provide expected behavior.

 Resolution::Monitor script for cssd resource agent (ie. cssd-monitor) now handles the case
where name of the resource is different. It retrieves the name and uses that
instead of the hard-coded string "cssd".

Incidents from old Patches:
---------------------------
NONE