Patch Name: PHSS_28725 Patch Description: s700_800 10.X OV OB3.50 patch - CC packet Creation Date: 03/03/24 Post Date: 03/04/04 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.50 Filesets: OMNIBACK-II.OMNI-HPUX-P,A.03.50 OMNIBACK-II.OMNI-OTHUX-P,A.03.50 Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_28725 Symptoms: PHSS_28725: Id = HSLco39486 SR:H555009404 GUI started with "xomni -restore -debug 1-99" ends abnormally when Informix server option in Restore context is selected. Id = HSLco40532 SR:H555009862 When starting "omnir -mssql -barhost <host> -base <basename>", restore ends with: "Set '<basename>:0' not found. Most probably there is a DNS configuration problem or one of the systems is not in the same Cell Manager system." Id = HSLco40537 SR:H555009863 When backing up very large SAP databases with SSEA split mirror, backups can fail with error: "BR280I Time stamp <time> BR296I Split of mirror disks successful BR274E File /<sapdata_path>/system.data1 not found" PHSS_28222: Id = HSLco37193 SR:H555008807 When backing up SAP integration with EMC split mirror functionality, not all the SAP files are backed up. Id = HSLco37723 SR: H555008892 If a Manager-of-Managers Server is also a MC/ServiceGuard virtual node, then the command "omnirpt -report list_sessions -timeframe <start_hours_ago><hours_duration> -multicell -no_multiple" lists the matching sessions from this node twice. PHSS_27595: Id = HSLco31733 SR: H555006893 Additional dates added to periodic backup schedule after 13 months. Id = HSLco35611 SR: H555008476 Restore GUI can not handle two separate Oracle7 databases with the same SID. GUI does not display all objects versions. Id = HSLco35661 SR: H555008490 Filesystem restore summary displays incorrect version of file selected for restore. Id = HSLco36478 SR: H555008657 GUI ends abnormally when trying to perform Informix restore. Id = HSLco36904 SR: H555008730 xomnimm reports "Internal error" when trying to load large media pool or device. Id = JAGad97576 SR: 8606228519 Command Line (CLI) command omnimcopy does not provide error codes. Id = HSLco36916 SR: H555008732 HP-UX GUI corrupts barlists for SSEA backup created using Windows GUI. PHSS_25956: Id = HSLco28793 SR: H555006144 Omnir command starts multiple Database Session Managers. Id = HSLco29971 SR: H555006524 Double-clicking an existing EMC datalist results in the following error: "Unknown object type encountered.". Id = HSLco31433 SR: H555006834 omnir incorrectly parses "-srdf_smmf" option. Id = HSLco31734 SR: H555006894 OmniBack does not select all the objects with the same timestamp. Id = JAGad57038 SR: 8606187829 "Omnidb -filesystem -detail" generates output in which Object Name and Object Type files contents are reversed. PHSS_24660: Id = NSMex03922 Listing of Oracle objects on GUI fails. Id = NSMex03986 Omnir core dumps. Id = NSMex04296 Backup scheduler shows incorrect dates. Id = NSMex04323 Command "omnimm -enter [slot_range]" returns invalid slot error. Id = NSMex04347 Restore to a different host fails with an error: "Can not stat script /usr/omni/bin/(null).". Id = NSMbb39907 Any attempt to change object format in Oracle8 RMAN script using OmniBack II GUI fails with the following error: "[12:1645] Format of RMAN channel names is not correct.". Id = HSLco20414 Device maintenance from command line is not sufficient. Id = NSMex03989 Command "omnirpt -report db_size -html -email <e-address>" works improperly. Id = NSMex04439 omnib command ignores "-encode" option. Id = NSMbb38972 Exchange 2000 backup cannot be started from command line. PHSS_22850: Id = JAGad30352 "EMC Support" tab is not available in "Backup Specification - Options" GUI. Id = JAGad35002 If database integration in a MC/ServiceGuard cluster is backed up, the backup can report an error. Id = NSMex03419 After importing a tape from 2.55 to 3.50 cell some of the files can not be restored. Id = NSMex03475 Restore GUI does not display SAP objects, if two SAP instances with the same name are backed up on different host. Id = NSMex03505 a) When selecting restore of SAP object, message "Cannot browse from root" appears. b) When selecting restore from File System Restore Dialog GUI might core dump. Id = NSMex03658 Exit code of omniminit is incorrect. Id = NSMex03833 The options under Edit button are not accessible even if user has rights. Id = JAGad29457 Ownership incorrectly displayed within restore GUI. Id = JAGad33161 Datalists/barlists with EMC integration are incorrectly created. PHSS_22038: Id = NSMex03503 Users with only "Start Backup" privilege can delete datalists. Id = NSMex03511 "Send external" method always executes external script on Cell Manager system. Defect Description: PHSS_28725: Id = HSLco39486 DbgPlain function is called with wrong string format. Resolution: String format for DbgPlain() is corrected. Id = HSLco40532 The source of <basename> is not parsed. Resolution: The source of <basename> is parsed. Id = HSLco40537 In split mirror environment with very large SAP databases, it can happen that the size of the message buffer that OmniBack II uses is too small to fit in for the complete list of SAP files to be backed up. Resolution: New environment variable is introduced: OB2IPCBUFSIZE. In order to solve this problem, the buffer size can be increased by setting the OB2IPCBUFSIZE environment variable in the .omnirc file on CM, R1 and R2 hosts, specifying the desired amount of memory to be used for the buffer. For determining buffer size please see the Resolution of Id = HSLco37193 below. Part of SSPUX350_088. PHSS_28222: Id = HSLco37193 SR:H555008807 In split mirror environment with huge SAP databases it can happen that the size of the message buffer OmniBack II uses is too small to receive complete list of SAP files to be backed up. Resolution: Setting the OB2IPCBUFSIZE environment variable in the /opt/omni/.omnirc file on Cell Server, R1 and R2 hosts, specifying the desired amount of memory to be used for the buffer solves the described problem. Please read the following instructions and make sure that the patches listed in "Other Dependencies" section (see below) are installed and the environment variable is set on Cell Server, R1 and R2 systems before running the backup! How to determine the buffer size? --------------------------------- N_obj: number of objects (files) N_fs: number of file systems N_lvmvg: number of volume groups N_dg: number of disk groups N_rdsk: number of rawdisks Obj: Object Name ObjBack: Object Backup Name MntPathLen: Path name on backup (R2) host (example: /var/opt/omni/tmp/App_host) fsmnt: File System Mount Point fsdev: File System Device File (example: /dev/dsk/[c0t1d1,lvol1]) vg: Volume group (ex: /dev/vg01) dg: Disk group (VxVM) - dependence on mapfile which is required for creating disk group (example:/dev/vx/dsk/dg01) rdsk: Raw disk file name (example: /dev/rdsk/c1t1d1) AvgLen_<xxx> average length of <xxx> There are two different buffers used: 1. BSM <-> R1 2. R1 <-> R2 Calculating the BSM <-> R1 buffer size -------------------------------------- MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen) Calculating the R1 <-> R2 buffer size ------------------------------------- MsgSize_R1_R2 = N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) + N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+ N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) + N_rdsk*(AvgLen_rdsk*2) Calculating the OB2IPCBUFSIZE value ----------------------------------- OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2) RESTORE NOTE: ------------- If restore is started using the sapbda utility, the variable OB2IPCBUFSIZE must be exported to environment prior to starting sapbda. Known problems: --------------- If the calculated variable OB2IPCBUFSIZE is correctly set, but is still too small for the file list to fit into the message buffer, the session will fail with the following error seen in the report: BR295I Splitting mirror disks... BR280I Time stamp <time> BR279E Return code from '/opt/omni/lbin/ob2smbsplit /<sap_homedir_path>/.<filename>.lst': 2 BR299E Split/resynchronization of mirror disks failed In this case the variable OB2IPCBUFSIZE must be recalculated to appropriate value. See above how to determine it. Part of SSPUX350_080. Id = HSLco37723 Media handling results in IPC error when the buffer size is increased and variable OB2IPCBUFSIZE is set as described in above Resolution for problem HSLco37193. Resolution: Media Session Manager is rebuilt in order to properly include the changes introduced with Resolution for HSLco37193. Part of SSPUX350_085. PHSS_27595: Id = HSLco31733 In next year the same date is not the same day in week. Scheduled dates after one year are just copied, so backups are scheduled on wrong days. Resolution: Days are correctly moved to next year. Id = HSLco35611 GUI does not check on which host Oracle7 database is backed up and all backup versions are appended to the first one found. Resolution: Host matching and object version adding to list is improved. Id = HSLco35661 Restore summary always displays the last version of file selected for restore. Resolution: Restore summary displays file versions as they were selected for restore. Id = HSLco36478 Incorrect pointer handling causes GUI to end ungracefully. Resolution: Pointers are properly handled. Id = HSLco36904 A buffer sent to xomnimm after loading large media pool or device is too big. Resolution: xomnimm reads the buffer size as specified in .omnirc file with OB2IPCBUFSIZE variable. Id = JAGad97576 Omniback II reports the same exit code regardless of success or failure of the command omnimcopy. Resolution: When command omnimcopy fails Omniback II returns exit code 3 = EX_ERR_INTERNAL. Id = HSLco36916 Saving a SSEA barlist with HP-UX GUI corrupts barlist. Resolution: Saving a barlist with HP-UX GUI is not possible. Part of SSPUX350_078. PHSS_25956: Id = HSLco28793 New Database Session Manager instance is started every time when omnir is trying to retrieve object information from the database. Resolution: Omnir reuses existing connections. Part of SSPUX350_051. Id = HSLco29971 Displaying EMC datalists is disabled. Resolution: Displaying EMC datalists is enabled. Part of SSPUX350_055. Id = HSLco31433 When "-rawdisk" option is combined with "-srdf", "-smmf" or "-srdf_smmf", it is recognized only after latter options have been checked. Resolution: Option "-rawdisk" has higher priority. Id = HSLco31734 Restore GUI incorrectly interprets the data obtained from Database Session Manager. Resolution: Restore GUI properly displays the latest versions of restore objects. Id = JAGad57038 The order of putting Object Type and Object FileName into output files is wrong. Resolution: Object Type and Object FileName are displayed in correct order. PHSS_24660: Id = NSMex03922 Incorrect memory usage causes GUI to core dump whilst listing Oracle sessions. Resolution: Memory usage is improved. Id = NSMex03986 The omnir command causes a memory fault and core dumps if it is run with a long list of objects. Resolution: Omnir can handle long list of objects. Id = NSMex04296 Backup scheduler loses months prior to January, 2002. Resolution: Scheduler optimization improved. Id = NSMex04323 When executing "omnimm -enter [slot_range]" command a "0" is appended to slot range. This causes invalid slot error. Resolution: "omnimm -enter [slot_range]" command works properly. Id = NSMex04347 Restore GUI improperly sends empty pre- and post-exec options to Restore Session Manager. Resolution: Fix is implemented in Restore GUI. Id = NSMbb39907 It is impossible to define the object format in an Oracle8 RMAN script using the Omniback II GUI. Resolution: It is possible to change object format in Oracle8 RMAN script using OmniBack II GUI. Part of SSPUX350_031. Id = HSLco20414 Device enabling, disabling and status report can not be performed using OmniBack II command line. Resolution: New options "-disable_device", "-enable_device" and "-device" are added to omnimm, omniupload and omnidownload. To disable/enable specific device and all other devices with the same lockname, run: omnimm -disable_device {device name} omnimm -enable_device {device name} To disable/enable all devices with the same lockname, run: omnimm -disable_lockname {lock name} omnimm -enable_lockname {lock name} To check if specific device is enabled/disabled, run: omnidownload -device {device name} Part of SSPUX350_038. Id = NSMex03989 Command "omnirpt -report db_size -html -email <e-address>" returns HTML code instead of formatted report. Resolution: Missing header is added to HTML report. Id = NSMex04439 omnib command ignores "-encode" option. Resolution: omnib command properly recognizes "-encode" option. Id = NSMbb38972 Exchange 2000 backup cannot be started from command line. Resolution: It is possible to start Exchange 2000 backup from command line. Part of SSPUX350_020. PHSS_22850: Id = JAGad30352 "EMC Support" tab is not available in "Backup Specification - Options" GUI, unless the cell_info entry for the Cell Manager has the "-emc" option. Resolution: xomnibackup now correctly checks cell_info file for "-emc" options. Id = JAGad35002 a )Windows NT GUI supports cluster import which creates additional attributes in the cell info file to mark cluster nodes and virtual servers. MC/SG clusters do not have such support yet. b) Motif GUI does not have any way to import cluster in the cell. Session Manager starts agent on certain machine and expects that the connection will come from that machine or a physical node on a cluster. If additional attributes in the cell info are not set then SM aborts the connection. Resolution: .util shell script has been enhanced to allow import of the cluster using Windows GUI. The script handles messages INFO_CLUS and INFO_CLUS1 which allow the import to happen. Id = NSMex03419 OmniBack II 3.50 objects are case insensitive which is not true for the SAP objects backed up with 2.55 version. Object tape format is changed with 3.50 as well. These changes caused some SAP objects not to be displayed in the Restore GUI after importing the tape with SAP objects from 2.55 to 3.50. Resolution: Names are tape format are converted into OmniBack II 3.50 format after tape import from 2.55. Id = NSMex03475 Restore GUI does not display SAP objects, if two SAP instances with the same name are backed up on different host. Resolution: xomnirestore has been improved to show all object. Id = NSMex03505 a) When selecting restore of SAP object, message "Cannot browse from root" appears. b) Two different structures with the same name were defined. Resolution: xomnirestore has been improved. Id = NSMex03658 Exit code 0 is returned when the medium initialization fails with error: "This medium can be initialized only with force option specified." Resolution: Exit code of omniminit for failed operation is redefined. Id = NSMex03833 User rights are not properly interpreted. Resolution: User rights permissions has been modified. Id = JAGad29457 xomnirestore shows user name and group name for backed up objects. If users on different clients have different UID and GID wrong user will be shown in version browser. Resolution: New option GUIShowUID has to be set in file: /etc/opt/omni/options/global on Cell Manager host. GUIShowUID=<number> where <number> means: - 0, GUI converts UIDs and GIDs to strings - 1, only UIDs and GIDs numbers will be showen Part of SSPUX350_013. Id = JAGad33161 Options for EMC integration are incorrectly saved when datalist/barlist is created with Motif GUI. Resolution: EMC type resolving has been improved. Part of SSPUX350_013. PHSS_22038: Id = NSMex03503 User rights are not properly checked. Resolution: User rights checking is properly improved. Id = NSMex03511 Execution of external script can not be prevented. Resolution: Omnirpt is changed so that the execution of "Send external" method can be controlled by adding a line ExternalScriptMode=<number> in Global Options file, where <number> means: - 0, no checking is performed - 1, script can be executed only in bin directory - 2, executing of external scripts is not allowed. SR: H555009862 H555009592 H555009404 H555009863 H555008927 H555008892 H555008803 H555008807 H555008476 H555008657 H555006893 H555008730 B554000640 B554000632 H555008732 H555008490 8606228519 H555006524 H555006894 H555006834 H555006144 8606187829 H555004942 H555003134 8606179663 H555005709 H555005547 H555005845 H555004369 H555004246 H555004381 8606160131 8606161034 8606163859 B554000788 8606165711 B554000550 H555003728 B554000606 B554000634 Patch Files: /opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/hp/s800/hp-ux-11/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/gpl/i386/linux/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/sco/i386/unixware/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.50/packet.Z /opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.03.50/ packet.Z /opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.50/ packet.Z what(1) Output: /opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/hp/s800/hp-ux-11/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/gpl/i386/linux/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/sco/i386/unixware/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.03.50/ packet.Z: None /opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.50/ packet.Z: None cksum(1) Output: 1535824785 11152455 /opt/omni/databases/vendor/cc/hp/s800/ hp-ux-1020/A.03.50/packet.Z 903497905 11208336 /opt/omni/databases/vendor/cc/hp/s800/ hp-ux-10/A.03.50/packet.Z 2271713999 11147314 /opt/omni/databases/vendor/cc/hp/s800/ hp-ux-11/A.03.50/packet.Z 2055934160 4172467 /opt/omni/databases/vendor/cc/ncr/i386/ mp-ras/A.03.50/packet.Z 3047406478 4949573 /opt/omni/databases/vendor/cc/dec/alpha/ osf1-4/A.03.50/packet.Z 2143153229 8627390 /opt/omni/databases/vendor/cc/gpl/i386/ linux/A.03.50/packet.Z 723479229 4217255 /opt/omni/databases/vendor/cc/ibm/rs6000/ aix-42/A.03.50/packet.Z 3759737747 4028813 /opt/omni/databases/vendor/cc/sco/i386/ sco_sv/A.03.50/packet.Z 3343189653 3941384 /opt/omni/databases/vendor/cc/sco/i386/ unixware/A.03.50/packet.Z 3819542767 4126913 /opt/omni/databases/vendor/cc/sequent/ i386/dynix/A.03.50/packet.Z 1089219669 5022182 /opt/omni/databases/vendor/cc/sgi/mips/ irix/A.03.50/packet.Z 2371282407 5922365 /opt/omni/databases/vendor/cc/sgi/mips/ irix-62/A.03.50/packet.Z 3937653808 4878331 /opt/omni/databases/vendor/cc/siemens/ r400/sinix/A.03.50/packet.Z 1711704483 4578857 /opt/omni/databases/vendor/cc/sun/sparc/ solaris/A.03.50/packet.Z 3292819385 4661017 /opt/omni/databases/vendor/cc/sun/sparc/ solaris-26/A.03.50/packet.Z 2190727103 6980139 /opt/omni/databases/vendor/cc/sun/sparc/ sunos/A.03.50/packet.Z Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: If any newer SSP for the Cell Console is installed on your system, you must re-apply the SSP after installing this Cell Console patch. PHSS_28727: Release date: Available Id = HSLco40537 SR:H555009863 Id = HSLco37193 SR:H555008807 PHSS_28727 is required for these defect fixes. PHSS_28578: Release date: Available Id = HSLco40537 SR:H555009863 PHSS_28578 is required for this defect fix. PHSS_28570: Release date: Available Id = HSLco40537 SR:H555009863 Id = HSLco37193 SR:H555008807 Bad catalog access messages are displayed without PHSS_28570. PHSS_28019: Release Date: Available Id = HSLco37193 SR:H555008807 PHSS_28019 is required for this defect fix. PHSS_28017: Release Date: Available Id = HSLco40537 SR:H555009863 Id = HSLco37193 SR:H555008807 PHSS_28017 is required for these defect fixes. Supersedes: PHSS_22038 PHSS_22850 PHSS_24660 PHSS_25956 PHSS_27595 PHSS_28222 Equivalent Patches: PHSS_28726: s700: 11.00 11.11 11.20 s800: 11.00 11.11 11.20 Patch Package Size: 97360 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_28725 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_28725.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_28725. 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_28725.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_28725.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_28725: NOTE! This Patch has to be installed on the Installation Server host. The User Interface must be redistributed to the client system(s) after the installation of the patch in order to get the fixes into effect. For distribution of the User Interface, refer to the OmniBackII Installation guide. Patch includes the following Site Specific Patches: SSPUX350_013 SSPUX350_020 SSPUX350_031 SSPUX350_038 SSPUX350_051 SSPUX350_055 SSPUX350_078 SSPUX350_080 SSPUX350_085 SSPUX350_088