Patch Name: PHSS_26359 Patch Description: s700_800 10.20 OV OB4.10 patch - DOC packet Creation Date: 03/06/27 Post Date: 03/07/16 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: OmniBackII A.04.10 Filesets: OMNIBACK-II.OMNI-DOCS,A.04.10 Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_26359 Symptoms: PHSS_26359: Id = HSLco31725 SR: H555006891 Importing clients with reserved keywords in their hostnames fails. Id = HSLco31821 SR: H555006913 Wrong path to the "ovpause.lock" file in the UNIX Integration Guide. Id = HSLco33021 SR: H555007271 The information on how to upgrade OmniBack II A.03.x Cell Manager to A.04.10 on Microsoft Cluster Server (MSCS) is needed. Id = JAGad90626 SR: 8606221492 Pre-exec and post-exec scripts are deleted from <OmniBack_home>\bin directory during the upgrade of OmniBack II A.03.x version to A.04.x version. Id = JAGad96889 SR: 8606227829 Wrong pathname is specified for the "detach" utility in the Administrator's Guide. Id = JAGae01429 SR: 8606232193 OmniBack II EMC integration does not support two BCVs (Business Continuance Volumes) attached to a backup host. Id = JAGae02799 SR: 8606233576 The "#" sign cannot be used in the RMAN script in the Oracle8 backup specification. Id = NSMbb43852 SR: B555012727 Incorrect VA LUN conversion in the SureStore VA Integration Guide. Id = NSMbb44126 SR: B555012924 EMC Symmetrix/Fastrax Integration Guide contains a mistake. Id = NSMbb44219 SR: B555012982 Errors in the UNIX and Windows Integration Guides. Id = NSMbb44895 SR: B555013441 Wrong filesystem limitation in the Administrator's Guide. Id = HSLco41047 SR: H555010116 More information is needed regarding the two values of the SMEXIT variable. Id = HSLco41088 SR: H555010145 Administrator's and Concepts Guides contain incorrect information. Id = HSLco41260 SR: H555010232 The following error message is reported during a SAP integration backup: BR301W SQL error -1017 at location BrDbConnect-1 ORA-01017: invalid username/password; logon denied BR310W Connect to database instance UP2 failed Id = JAGae26626 SR: 8606262291 Error message after the upgrade of OmniBack II A.03.x version to A.04.x version: 12:8334" No semicolon after rman command". Defect Description: PHSS_26359: Id = HSLco31725 OmniBack II does not work with clients that have "reserved" keywords in their hostnames (e.g. oracle, exchange, etc.). Resolution: Hostname limitations are added to Release Notes. Id = HSLco31821 Incorrect path to the "ovpause.lock" file is stated for the NNM integration in the UNIX Integration Guide. Resolution: The path to the "ovpause.lock" file is corrected. Id = HSLco33021 The procedure for upgrading OmniBack II A.03.x Cell Manager to A.04.10 on Microsoft Cluster Server (MSCS) is missing. Resolution: The procedure for upgrading OmniBack II A.03.x Cell Manager to A.04.10 on Microsoft Cluster Server (MSCS) is documented. Id = JAGad90626 All files located in the <OmniBack_home>\bin directory are removed during the upgrade from OmniBack II A.03.x version to A.04.10. Resolution: The following important note is added to the Installation and Licensing Guide under Upgrading the Windows Cell Manager and Installation Server section: During the upgrade from OmniBack II A.03.x release, all files in the <OmniBack_home>\bin directory are removed, including non-OmniBack II or customized files, such as Pre-exec and Post-exec scripts. It is recommended that you copy all these files to a different location before you start the upgrade. Id = JAGad96889 On page 221 of OmniBack II A.04.10 Administrator's Guide there is an incorrect pathname specified for the "detach" utility: /opt/omni/bin/utilns/detach However, it should read: /opt/omni/lbin/utilns/detach Resolution: The pathname specified for the "detach" utility is corrected. Id = JAGae01429 Configuration of two BCVs attached to a backup host is not supported and this limitation is not documented. Resolution: EMC/Fastrax Integration Guide documents mentioned limitation. Id = JAGae02799 The important note that the "#" sign must not be used in the RMAN script in the Oracle8 backup specification is missing. Resolution: The important note that the "#" sign must not be used in the RMAN script in the Oracle8 backup specification is added to the UNIX and Windows Integration Guides, chapter Integrating Oracle8/9 and OmniBack II. Id = NSMbb43852 The conversion formula from HP-UX device file to VA LUN number on pages 28 and 35 is incorrect. Resolution: The conversion formula from HP-UX device file to VA LUN number on pages 28 and 35 is corrected. Id = NSMbb44126 There is a mistake in the example for the Oracle8 database offline backup in the EMC Symetrix/Fastrax Guide. Resolution: The example for the Oracle8 database offline backup in the EMC Symetrix/Fastrax Guide is corrected. Id = NSMbb44219 There are some errors found in the Example of Oracle8/9 Database Restore section in the Integrating Oracle8/9 and OmniBack II chapter of the UNIX and Windows Integration Guides. Resolution: Errors in the Example of Oracle8/9 Database Restore section in the Integrating Oracle8/9 and OmniBack II chapter of the UNIX and Windows Integration Guides are fixed. Id = NSMbb44895 There is a wrong filesystem limitation in the Administrator's Guide. Resolution: The filesystem limitation in the Administrator's Guide is corrected. Id = HSLco41047 Values 12 and 13 of the SMEXIT variable need further explanation. Resolution: Values 12 and 13 of the SMEXIT variable are explained in greater detail. Id = HSLco41088 There is incorrect information regarding Cartridge Memory in the Administrator's and Concepts Guides. Resolution: The information regarding Cartridge Memory is corrected in the Administrator's and Concepts Guides. Id = HSLco41260 Note in the UNIX and Windows Integration Guides states that OmniBack II supports all options of SAP brtools that are also supported through backint which is not correct. Resolution: Note in the UNIX and Windows Integration Guides excludes -a and-b options as supported ones. Id = JAGae26626 There are an undocumented limitations when editing RMAN script in the GUI. Resolution: Limitations regarding editing RMAN script in the GUI are documented. SR: H555010116 H555010145 8606227829 B555012924 B555012727 B555012982 H555007271 8606221492 8606232193 8606262291 H555006913 B555013441 8606233576 H555010232 H555006891 Patch Files: /opt/omni/doc/C/Admin.pdf /opt/omni/doc/C/Concepts.pdf /opt/omni/doc/C/Emc.pdf /opt/omni/doc/C/Installation.pdf /opt/omni/doc/C/IntegrationNT.pdf /opt/omni/doc/C/IntegrationUX.pdf /opt/omni/doc/C/VirtualArray.pdf /opt/omni/doc/C/ReleaseNotes.pdf what(1) Output: /opt/omni/doc/C/Admin.pdf: None /opt/omni/doc/C/Concepts.pdf: None /opt/omni/doc/C/Emc.pdf: None /opt/omni/doc/C/Installation.pdf: None /opt/omni/doc/C/IntegrationNT.pdf: None /opt/omni/doc/C/IntegrationUX.pdf: None /opt/omni/doc/C/VirtualArray.pdf: None /opt/omni/doc/C/ReleaseNotes.pdf: None cksum(1) Output: 2089372527 9480549 /opt/omni/doc/C/Admin.pdf 3974858071 5907743 /opt/omni/doc/C/Concepts.pdf 204812951 4337337 /opt/omni/doc/C/Emc.pdf 3581926443 4199947 /opt/omni/doc/C/Installation.pdf 3186534179 8819914 /opt/omni/doc/C/IntegrationNT.pdf 2450189052 7045552 /opt/omni/doc/C/IntegrationUX.pdf 2618484175 2434042 /opt/omni/doc/C/VirtualArray.pdf 3405443831 513217 /opt/omni/doc/C/ReleaseNotes.pdf Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: PHSS_26360: s700: 11.00 11.11 11.20 s800: 11.00 11.11 11.20 Patch Package Size: 24210 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_26359 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_26359.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_26359. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_26359.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_26359.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_26359: NOTE! This patch can only be installed on those systems where documentation package has been previously installed. To check if the documentation is installed on particular system, execute "swlist -l fileset OMNIBACK-II" command and look for OMNI-DOCS. If OMNI-DOCS is present, then this patch can be applied. It is not possible to remotely distribute patched files from this patch.