README VERSION : 1.1 README CREATION DATE : 2015-12-01 PATCH-ID : VRTSvcs-7.0.1.000 PATCH NAME : VRTSvcs 7.0.1.000 BASE PACKAGE NAME : VRTSvcs BASE PACKAGE VERSION : 7.0.0.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol11_sparc (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : CORE , HANG PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : YES PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Install Guide for install instructions and Release Notes for other information. PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Install Guide for uninstall instructions and Release Notes for other information. SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:VRTSvcs-7.0.1.000 3747487 (3668853) The halog(1M) command becomes unresponsive when VCS is in the REMOTE_BUILD state. 3846445 (3835428) On forced reboot, the VCS configuration files (main.cf and/or types.cf) size becomes zero. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:VRTSvcs-7.0.1.000 * INCIDENT NO:3747487 TRACKING ID:3668853 SYMPTOM: The halog(1M) command becomes unresponsive when VCS is in the REMOTE_BUILD state. DESCRIPTION: When VCS is in the REMOTE_BUILD state, it rejects all messages from VCS commands since it is busy receiving a snapshot. However, VCS does not share this information with the halog(1M) CLI. As a result, the halog(1M) command becomes unresponsive while waiting for a response from the VCS daemon process. RESOLUTION: The code is modified such that VCS rejects the halog(1M) command when it is in the REMOTE_BUILD state. * INCIDENT NO:3846445 TRACKING ID:3835428 SYMPTOM: In case of an ungraceful reboot or a system panic, the hacf dump operation fails to write contents of the configuration files to the disk. This leads to empty VCS configuration files (main.cf and/or types.cf). DESCRIPTION: If the system reboots during the dump operation, sometimes the in-memory data does not get flushed onto the disk This leads to empty VCS configuration files (main.cf and/or types.cf). RESOLUTION: The HA daemon program is modified so that either the contents from the new configuration files are completely written to the disk or the old configuration is retained. INCIDENTS FROM OLD PATCHES: --------------------------- NONE