Date: 2013-03-27 OS: Solaris, AIX, Linux, HPUX Products: All Products The patch fixes the following installer issues: Issue 1: OS: SolSparc, Sol_x64 Products: All Products Etrack Incidents: 2574524 Problem statement: uninstallrp 5.1SP1RP2 does not detect failed patch removals Issue 2: OS: SolSparc, Sol_x64 Products: VCS, SFHA, SFCFS, SVS, SFRAC Etrack Incidents: 2646575 Problem statement: Fencing does not start after reboot after applying 5.1SP1RP2 Issue 3: OS: Solaris, AIX, Linux Products: VCS, SFHA, SFCFS, SVS, SFCFSRAC, SFRAC Etrack Incidents: 2662248 Problem statement: The content of /etc/gabtab is different between each node after rolling upgrade to 5.1SP1RP2. Workaround Steps: Symantec has provided a patch to resolve the above mentioned issues. Issue 4: OS: Solaris, AIX, Linux Products: All products Etrack Incidents: 2832838 Problem statement: Installer starts processes automatically after upgrading to 5.1SP1RP2. But if you have configurations involving terabyte or greater lun sizes, starting Volume Manager 5.1SP1RP2 processes may potentially cause diskgroup import failures and lead to potential data loss. Installer provides a new option "-nostart" in this hot-fix. If "-nostart" option is used, installer will not start any processes after upgrading to 5.1SP1RP2. Issue 5: OS: HPUX Products: All products Etrack Incidents: 3133259 Problem statement: During reboot requirement checking for VRTS packages and patches, CPI uses 'swlist -s $ppdir -a blah' to determine. But this may end up like 'swlist -s -a blah' when $ppdir is null. Workaround steps: Symantec has provided a patch to resolve the above mentioned issue. Usage: 1. Copy the hot-fix CPI_5.1SP1RP2_P5.pl to /tmp 2. Run RP script or RP rollback script with the hot-fix Example: ./installrp -require /tmp/CPI_5.1SP1RP2_P5.pl ./uninstallrp -require /tmp/CPI_5.1SP1RP2_P5.pl If you do not want installrp to start processes after installing 5.1SP1RP2, run installrp script with the "-nostart" option: Example: ./installrp -require /tmp/CPI_5.1SP1RP2_P5.pl -nostart