README VERSION : 1.1 README CREATION DATE : 2012-09-18 PATCH-ID : 5.1.133.000 PATCH NAME : VRTSdbac 5.1 SP1RP3 BASE PACKAGE NAME : Veritas Oracle Real Application Cluster Support Package by Symantec BASE PACKAGE VERSION : VRTSdbac 5.1SP1 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : rhel5_x86_64,rhel6_x86_64,sles10_x86_64,sles11_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer the release notes for installation instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer the release notes for un-installation instructions. SPECIAL INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 2734745 (2853860) PrivNIC resource state goes to FAULTED state after setting UseVirtualIP to 1. 2740150 (2933837) SFRAC CPI does not set OfflineWaitLimit attribute for CSSD agent resource. 2749412 (2853857) When usevirtualIP=1, it overwrites the IP on virtual interface of some nodes of the cluster. SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:5.1.133.000 * INCIDENT NO:2734745 TRACKING ID:2853860 SYMPTOM: PrivNIC resource state goes to FAULTED state after setting UseVirtualIP to 1. DESCRIPTION: Code trying to plumb the IP without checking if it is already plumbed on base interface. RESOLUTION: If IP is already plumbed on base interface and UseVirtualIp=1 we do nothing. * INCIDENT NO:2740150 TRACKING ID:2933837 SYMPTOM: When CPI configures the CSSD resource, CSSD resource goes in ONLINE|UNABLE TO OFFLINE state after first monitor interval cycle. DESCRIPTION: When CPI configures the CSSD resource, CPI does not set OfflineWaitLimit=3 during modifying the CSSD resource attributes RESOLUTION: CPI will set OfflineWaitLimit=3 during configuring the CSSD resource by >>hares -override cssd_resname OfflineWaitLimit >>hares -modify cssd_resname OfflineWaitLimit 3. * INCIDENT NO:2749412 TRACKING ID:2853857 SYMPTOM: When usevirtualIP=1, it overwrites the IP on virtual interface of some nodes of the cluster. DESCRIPTION: Virtual interface alias calculation logic was incorrect. RESOLUTION: Symantec has fixed the code. Now IP on other nodes doesn't get overwritten. INCIDENTS FROM OLD PATCHES: --------------------------- Patch Id::5.1.132.000 * 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::2374987 Tracking ID ::2374985 Symptom::PrivNIC/MultiPrivNIC agents fail to remove IP address during failover operation. Description::During failover operation PrivNIC/MultiPrivNIC agents check if active interface is down. If active interface is down, they do not take any action on active device leaving IP address plumbed on active device. They later plumb the same IP address on winner device. Resolution::Along with check of active device down, we now also check if given IP address is plumbed on the active interface. If IP address is plumbed on active device, we delete the IP address from active device and subsequently plumb IP on the winner device. * 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".