Patch Name: PHSS_17305 Patch Description: s700_800 10.X OV OB3.00 patch - EMC packet Creation Date: 99/01/29 Post Date: 99/02/19 Hardware Platforms - OS Releases: s700: 10.00 10.01 10.10 10.20 s800: 10.00 10.01 10.10 10.20 Products: OmniBackII A.03.00 Filesets: OMNIBACK-II.OMNI-EMC-P Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_17305 Symptoms: PHSS_17305: Id = NSMex01888 EMC integration doesn't work if backup specification is resolved to more than 50 physical devices on the system. Id = NSMbb21387 Mount of the filesystem on the backup host fails. Id = NSMbb22580 Syma dies after executing symlv command. Id = NSMbb22461 Oracle 8.0.3 EMC online integration does not backup control file. Defect Description: PHSS_17305: Id = NSMex01888 When reallocating space for physical devices in EMC integration, some pointers are not updated. This results in an internal error during the backup session. Part of SSP30_10. Resolution: Fix implemented in syma. Id = NSMbb21387 On HP-UX platform the mount of the filesystems on the backup host fails when the OB2 Symmetrix agent (syma) tries to mount these filesystems in read-only mode in order to allow backups through this backup (R2) host. This happens in case: - the root filesystem type is hfs and - the filesystem which needs to be mounted is vxfs Part of SSP30_01. Resolution: Fix implemented in syma. Id = NSMbb22580 Syma dies after executing symlv command if the output of the command: symlv -g -collapse show contains the same physical device more than once. Part of SSP30_28. Resolution: Fix implemented in syma. Id = NSMbb22461 The issue surfaces when the EMC Integration is used to perform the on-line database backup, using a backup control file. When an attempt is made to use "restore controlfile to", RMAN complains that neither a original or backup control can be found even though the "controlfile" used for the backup session can be seen w/SQLPLUS queries of the recovery catalog. Attempting to use "include current controlfile" in the backup specification, RMAN again complains that the control file that is open is a "backup" control file, which in actuality it is. Resolution: The manuals were appropriately changed. Please read also in the Special Installation Instructions below. SR: 0000000000 Patch Files: /opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.03.00/ packet.Z what(1) Output: /opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.03.00/ packet.Z: None cksum(1) Output: 2633747026 807601 /opt/omni/databases/vendor/emc/hp/s800/ hp-ux-1020/A.03.00/packet.Z Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: PHSS_17306: s700: 11.00 s800: 11.00 Patch Package Size: 850 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_17305 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_17305.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_17305.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_17305. 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_17305.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_17305.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_17305: NOTE! Patch has to be installed on the Installation Server host. The EMC packet needs to be redistributed to the appropriate systems, where the EMC Clients are installed, from within the "Cell Administration - Install" window of the OmnibackII graphical user interface before the patch modifications take effect. NOTE! Be sure that no EMC Backup / Restore is running while you distribute the packet to the EMC client. IMPORTANT! Special instructions for users who are using ORACLE 8 / EMC / Omniback II Integration! ============================================ NOTE: During Oracle8 EMC backup, the database is mounted on the backup system with backup control file. The Recovery Manager does not backup the control file with the command 'backup database' in case that the database is mounted with backup control file! Follow the instructions how to specify Recovery Manager script in your Oracle8 EMC backup specification. The command has to be added into Recovery Manager script: controlfilecopy CONTROL_FILE_LOCATION/ctrlORACLE_SID.ctl; INSTRUCTIONS: Creating an OmniBack II Oracle8 Backup Specification You need two backup specifications to start a backup from OmniBack II. See the HP OpenView OmniBack II Integration Guide for information on how to create backup specification. Proceed as follows: 1.Create a backup specification for the backup of database files on the Application (R1) System using the Symmetrix TimeFinder, SRDF or Combined (SRDF + TimeFinder) facility. When you enter the Recovery Manager script, you specify for backup also the control file. The command is: controlfilecopy FullPathOfTheBackupControlfile; The script looks like as follows: run { allocate channel dev_1 type sbt_tape; allocate channel dev_2 type sbt_tape; backup incremental level 0 filesperset 1 format BACKUP_SPECIFICATION_NAME.dbf database controlfilecopy CONTROL_FILE_LOCATION/ctrlORACLE_SID.ctl; release channel dev_1; release channel dev_2; } where BACKUP_SPECIFICATION_NAME is the name of the Oracle8 backup specification, ORACLE_SID is the name of the database instances and CONTROL_FILE_LOCATION is pathname of the directory on the mirrored Symmetrix Devices on the Application (R1) System to which OmniBack II copies the Oracle8 control file. The owner of the backup specification should be the Oracle8 backup owner from the Application (R1) system. Specify EMC Symmetrix options. Refer to Symmetrix Options on page 46 of Chapter 3 for description of Symmetrix backup options. You can define an online split mirror backup of datafiles. WARNING: If you create backup specification from GUI, you should add the following lines to the field Post-backup: backup incremental level 0 filesperset 1 controlfilecopy CONTROL_FILE_LOCATION/ctrlORACLE_SID.ctl \ format 'BACKUP_SPEC_NAME .dbf' Example: backup incremental level 0 filesperset 1 controlfilecopy '/TF2/oracle8/CF/oradata/KIWI/ctrlKIWI.ctl' \ format 'KIWI-Database-EMC.dbf' 2. Create a backup specification for the backup of the archived log files on the Application (R1) System without the use of Symmetrix facilities. For both backup specifications, specify the Application (R1) System as an OmniBack II client. The patch includes the following Site Specific Patches: SSP30_01 SSP30_10 SSP30_28