README VERSION : 1.1 README CREATION DATE : 2014-02-14 PATCH-ID : PVCO_04024 PATCH NAME : VRTSsfcpi601 BASE PACKAGE NAME : VRTSsfcpi601 BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : PVCO_03970 REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : hpux1131 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : PATCH CRITICALITY : RECOMMENDED HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : 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 INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:6.0.500.000 3113795 (3131744) installmp CPI should not enable DMP native support ,it should ask customer if they want to enable it. 3227558 (3243089) During a live upgrade the installation process takes more time than expected. 3228679 (3230218) The Common Product Installer (CPI) based installation fails on Solaris version 11 because the nslookup command is missing. 3294945 (3295841) CPI patches 6.0.1_P4.pl and 6.0.3_P6.pl fails when ssh banner is enabled 3298901 (3304955) The installer blocks upgrading the product to 6.0.1 if Veritas Cluster Server (VCS) is not configured. 3319554 (3432524) For Oracle 12c, the installation of Clusterware's response file fails. 3465678 (3472265) The installvcs script cannot set the heartbeat NIC name to be "L_101". 2821560 (3436227) The VRTSicsco, VRTSobc33, and VRTSpbx files are not removed after upgrading the product from version 50MP2 or 501RP3 to the version 6.0.1. 3419772 (3448674) After upgrading from 5.0MP3RP5 to 6.0.5 using the base_path option, NFSRestart and NFS upper or lower resource cannot come online automatically. SUMMARY OF KNOWN ISSUES: ----------------------------------------- 3437513 (3438634) SFRAC 605 : partial upgrade:inallmr -version detect 'Veritas Storage Foundation - 6.0.5' when vcs 6.0.5 + sf 6.0 installed KNOWN ISSUES : -------------- * INCIDENT NO::3437513 TRACKING ID ::3438634 SYMPTOM:: when a product is partial upgraded(using installer or manually), the ./installmr -version will detect this product as a 6.0.5 product, no matter the upgraded package is a main package or not. partial upgrade means some of the package(s) of a product is upgraded to higher version, but others not. Workaround: There's no workaround for this issue. FIXED INCIDENTS: ---------------- PATCH ID:6.0.500.000 * INCIDENT NO:3113795 TRACKING ID:3131744 SYMPTOM: Timing issue with enabling DMP_native_support interoperability issues with ZFS devices DESCRIPTION: On Solaris 10, for DMP product, If ZFS zpools are configured prior to upgrading 6.0.3, if user previously set tunable dmp_native_support=on, it'll take a long time for installer to enable dmp_native_support after upgrade. RESOLUTION: Installer provide a question asking if user want to enable dmp_native_support after upgrade. * INCIDENT NO:3227558 TRACKING ID:3243089 SYMPTOM: During a live upgrade on SunOS, the rsh or the ssh command use approximately 3 minutes per node to verify if a node is alive. The verification process causes a delay in the installation process. DESCRIPTION: During an installation process, when the rsh or the ssh command is invoked, the command verifies the state of each node to understand if it is alive. In the process of verification, the commands consume more time than expected, which causes a delay in the installation process. The installer also reports error messages during the rsh communication precheck. Some of these error messages are invalid that leads to repeated verification of the ssh or the rsh connection. RESOLUTION: Remove the invalid error messages while CPI verifies the rsh or the ssh commands. CPI executes the rsh or the ssh communication only once regardless of the failure that is observed in the rsh or the ssh verification process. * INCIDENT NO:3228679 TRACKING ID:3230218 SYMPTOM: With Solaris version 11, the Common Product Installer (CPI) based installation process fails during a precheck because the nslookup command is missing. After the failure, the installer reports the following error message: CPI ERROR V-9-30-1446 The following required OS commands are missing on system: /usr/sbin/nslookup: No such file or directory. DESCRIPTION: The Internet Systems Consortium (ISC) has deprecated the use of nslookup command instead has certified to use either the host or dig. The CPI packages contain the nslookup command, which the standard build does not support. During an installation, the Storage Foundation (SF) CPI installer installs the bind packages (pkg:/network/dns/bind) and later removes these bind packages to comply with the ISC's new security guidelines. However, during a precheck when the nslookup command is not found, the installer stops the installation with an error. RESOLUTION: To prevent the installation failure, remove the nslookup command from the preinstallation command checklist. * INCIDENT NO:3294945 TRACKING ID:3295841 SYMPTOM: During an installation process with 6.0.1_P4.pl or 6.0.3_P6.pl, when ssh banner is enabled, an error will be given: Checking system communication CPI ERROR V-9-0-0 1 thread 1 threw error: Can't locate object method "arch_sys" via package "Padv::" (perhaps you forgot to load "Padv::"?) at /opt/VRTSperl/lib/site_perl/UXRT60/EDR/EDR/systems.pm line 102. DESCRIPTION: During an installation process, when the rsh or the ssh command is invoked, the command verifies the state of each node to understand if it is available to conection. If ssh/rsh banner is enabled, the existing diagnostic method for connection will failed. RESOLUTION: Installer will not set $sys->{banner} when testing ssh/rsh connection. * INCIDENT NO:3298901 TRACKING ID:3304955 SYMPTOM: The installer blocks upgrading the product to 6.0.1 if Veritas Cluster Server (VCS) is not configured. DESCRIPTION: Some users have Storage Foundation and High Availability (SFHA) product installed, but only with Dynamic Multi-Pathing (DMP) configured and running. In this case, the installer blocks upgrading the whole product because VCS is not configured. RESOLUTION: Use the hot fix provided to upgrade the whole product. * INCIDENT NO:3319554 TRACKING ID:3432524 SYMPTOM: An error occurs requesting a DISPLAY value When the response file, which the command line generates, is used to install Oracle Clusterware/db. DESCRIPTION: The DISPLAY value in the variable store does not synchronize between the response file and the command line. Thus, the response file fails to generate a variable to store the DISPLAY value. RESOLUTION: The code is modified to synchronize the variable that stores the DISPLAY value between the response file and the command line. * INCIDENT NO:3465678 TRACKING ID:3472265 SYMPTOM: The installvcs script cannot set the heartbeat NIC name to be "L_101". DESCRIPTION: The Symantec product installer assumes the network interface name should not include "_". RESOLUTION: The code is modified to remove the limitation that network interface name should not include "_". * INCIDENT NO:2821560 TRACKING ID:3436227 SYMPTOM: The VRTSicsco, VRTSobc33, and VRTSpbx files are not removed even after upgrading the product from version 50MP2 or 501RP3 to the version 6.0.1. DESCRIPTION: During an upgrade process, the VRTSob package is not removed. As a result some of the obsolete packages that depend on the VRTSob package are available after an upgrade. RESOLUTION: The code is modified to uninstall and reinstall the VRTSob package so that all the obsolete packages are uninstalled after an upgrade. * INCIDENT NO:3419772 TRACKING ID:3448674 SYMPTOM: After upgrading from 5.0MP3RP5 to 6.0.5 using the base_path option, NFSRestart and NFS upper or lower resource cannot come online automatically. DESCRIPTION: Some NFSRestart and NFS lock files are not migrated from /var/VRTSvcs/lock to /var/VRTSvcs/log/volatile during upgrade. Thus, NFSRestart and NFS upper or lower resource cannot come online automatically. RESOLUTION: The upgrade script is modified to migrate the NFSRestart and NFS lock files from /var/VRTSvcs/lock to /var/VRTSvcs/lock/volatile during the upgrade using the base_path option. INCIDENTS FROM OLD PATCHES: --------------------------- NONE