Patch Name: PHSS_23109

Patch Description: s700_800 10.X OV OB3.10 patch - CC packet

Creation Date: 01/07/30

Post Date:  01/08/07

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.10

Filesets:
	OMNIBACK-II.OMNI-HPUX-P,A.03.10
	OMNIBACK-II.OMNI-OTHUX-P,A.03.10

Automatic Reboot?: No

Status: General Superseded

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHSS_23109

Symptoms:
	PHSS_23109:
	Id = JAGad01472
	    Exit code of omnimm is incorrect.

	Id = JAGad30352
	    "EMC Support" tab is not available in
	    "Backup Specification - Options" GUI.

	Id = NSMex03475, NSMex03808
	    Restore GUI does not display SAP objects if two
	    SAP instances with the same name are backed up on
	    different hosts.

	Id = NSMex03505
	    a) When selecting restore of SAP object, message
	     "Cannot browse from root" appears.

	    b) Performing tasks in a certain sequence on the File
	     System Restore dialog window can cause GUI to core
	     dump.

	Id = NSMex03658
	    Exit code of omniminit is incorrect.

	Id = NSMex03806
	    Omnir cannot be started with "-r -l" or "-r -p"
	    options.

	Id = NSMex03833
	    The options under Edit button are not accessible even
	    if user has the appropriate rights.

	Id = NSMex03922
	   Listing of Oracle objects on GUI fails.

	Id = NSMex03986
	    Omnir core dumps.

	Id = NSMbb39907, JAGad48886
	    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.

	PHSS_21644:
	Id = NSMbb34280
	    When saving a backup specification template in MoM
	    environment, it is always saved on the Cell Manager,
	    where the xomnibackup GUI has been started from
	    instead of being saved on the MoM server.

	Id = NSMex02757
	    Xomnirestore incorrectly reports the file size.

	Id = NSMex02989
	    Xomnimonitor core dumps when printing all sessions.

	Id = NSMex02991
	    GUI hangs when initializing media.

	Id = NSMex03042
	    Xomnimm dies when configuring 9710 device details.

	Id = NSMex03216
	    If two SAP databases are configured on different hosts,
	    restore GUI doesn't show both host objects for restore.

	Id = NSMex03250
	    Media Management window shows garbage in media
	    location string.

	Id = NSMex03262
	    Scheduling breaks after 12 months have passed.

	Id = NSMex03306
	    Xomnirestore core dumps if Option button is clicked
	    by non-root user.

	Id = NSMex02911
	    Removing a volser results in error message, although
	    the volser has been successfully removed from the
	    database:

	       "Cannot erase in this pool!"

	Id = NSMex02954
	    Clicking the "..." button in Oracle 7 restore window
	    results in listing all sessions for all Databases,
	    including the failed ones, even if the instance name
	    has been provided.

	Id = NSMex03419
	    After importing 2.55 tapes, some SAP files cannot be
	    restored.

	Id = NSMex03503
	    Users with only "Start Backup" privilege can delete
	    datalists.

	Id = NSMex03511
	    "Send external" method always executes external script
	    on Cell Manager system.

	Id = NSMex03238
	    Backup scheduler shows incorrect dates.

Defect Description:
	PHSS_23109:
	Id = JAGad01472
	    Exit code of omnimm is reported as successful when
	    the operation itself is not successful.

	Resolution:
	    Omnimm returns correct exit codes.

	    Part of SSPUX310_041.

	Id = JAGad30352
	    "EMC Support" tab is not available in
	    "Backup Specification - Options" GUI, unless
	    the "-emc" option is manually added to the cell_info
	    file for the Cell Manager.

	Resolution:
	    xomnibackup correctly parses cell_info file and
	    recognizes EMC clients properly.

	Id = NSMex03475, NSMex03808
	    Restore GUI does not show all SAP objects for hosts if
	    two SAP instances are backed up with the same name on
	    two different hosts.

	Resolution:
	    xomnirestore has been improved to shows all object
	    correctly.

	Id = NSMex03505
	    a) When selecting restore of SAP object, message
	    "Cannot browse from root" appears.

	    b) Two different structures with the same name
	    are 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 = NSMex03806
	    Incorrect parsing of appname and bararg arguments.

	Resolution:
	    Omnir has been modified.

	Id = NSMex03833
	    User rights are not properly interpreted.

	Resolution:
	    User right permissions are properly interpreted.

	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 = NSMbb39907, JAGad48886
	    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 SSPUX310_051.

	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.

	    Please see Special Installation Instructions for details
	    about the usage of mentioned options.

	    Part of SSPUX310_055.

	PHSS_21644:
	Id = NSMbb34280
	    The xomnibackup GUI is not aware of the fact that the
	    Cell Manager system is a part of the MoM environment,
	    and saves the backup specification template locally
	    instead of contacting the MoM server.

	Resolution:
	    Xomnibackup now contacts the MoM server for saving
	    the template.


	Id = NSMex02757
	    When trying to restore files bigger than 2 Gb,
	    xomnirestore reports the file size less than 2Gb.

	Resolution
	    Xomnirestore now correctly reports the file size.

	Id = NSMex02989
	    Xomnimonitor core dumps when printing all sessions if
	    there is a backup host with a hostname longer than 80
	    characters to be printed.

	Resolution:
	    Hostname can now be up to 120 character long.

	Id = NSMex02991
	    When initializing media from the CM console, the
	    system hangs if the Actions menu is left open, and
	    the confirmation dialog box is clicked.

	Resolution:
	    Xomnimm has been fixed.

	Id = NSMex03042
	    Uninitialized variable causes the GUI to occasionally
	    coredump when configuring libraries.


	Resolution:
	    All variables are now initialized before displaying.

	Id =  NSMex03216
	    Motif GUI does not show two or more SAP hostnames in
	    restore GUI.

	Resolution:
	    Xomnirestore has been improved.

	Id = NSMex03250
	    Dialog window displays a non-initialized string.

	Resolution:
	    Now all strings are correctly initialized before
	    displaying in the GUI.

	Id = NSMex03262
	    Scheduling breaks after 12 months have passed since
	    the configuration.

	Resolution:
	    Scheduler has been improved.

	Id = NSMex03306
	    If the user does not have admin permissions, the target
	    host text field is not displayed properly, and the
	    xomnirestore GUI coredumps.

	Resolution:
	    Xomnirestore behaviour has been improved.

	Id = NSMex02911
	    An error is reported no matter if the volser remove
	    operation fails or succeeds.

	Resolution:
	    If the remove operation is successful, the error
	    message is not reported.
	    Part of SSPUX310_003.

	Id = NSMex02954
	    List of  the Oracle7 backup sessions has not been
	    filtered properly.

	Resolution:
	    Xomnirestore  has been fixed.
	    Part of SSPUX310_016.

	Id = NSMex03419
	    In pre-3.0 versions file names were stored on the tape
	    in the original upper and lower case letters. Version
	    OBII 3.0 and later store file names always in lower
	    case. At restore time it is assumed that all file names
	    on tape are in lower case. This introduces problems
	    when, for example, a tape from 2.55 system is imported
	    into 3.10 system and a restore is run from such tape.

	Resolution:
	    When comparing names of files which were backed
	    up on the tape, all file names are now converted to
	    lower case, so this doesn't have any effect on new
	    backups (they are already in lower case) but enables
	    restores from pre-3.0 backups.
	    Part of SSPUX310_028.
	    See Special Installation Instructions.

	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.

	Id = NSMex03238
	    Backup scheduler loses months prior to January, 2001.

	Resolution:
	    Scheduler optimization improved.

SR:
	H555003134 8606132323 8606161034 8606179663 B554000606
	B554000634 B554000788

Patch Files:
	/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/gpl/i386/linux/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.10/packet.Z
	/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.10/
		packet.Z

what(1) Output:
	/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/gpl/i386/linux/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.03.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.10/
		packet.Z:
		None

cksum(1) Output:
	2827308708 14582101 /opt/omni/databases/vendor/cc/hp/s800/
		hp-ux-1020/A.03.10/packet.Z
	357775364 11071024 /opt/omni/databases/vendor/cc/hp/s800/
		hp-ux-10/A.03.10/packet.Z
	2289614035 4130051 /opt/omni/databases/vendor/cc/ncr/i386/
		mp-ras/A.03.10/packet.Z
	3394929000 4877241 /opt/omni/databases/vendor/cc/dec/alpha/
		osf1-4/A.03.10/packet.Z
	3385655115 6796836 /opt/omni/databases/vendor/cc/gpl/i386/
		linux/A.03.10/packet.Z
	819084938 4186445 /opt/omni/databases/vendor/cc/ibm/rs6000/
		aix-42/A.03.10/packet.Z
	1906344340 3988537 /opt/omni/databases/vendor/cc/sco/i386/
		sco_sv/A.03.10/packet.Z
	2173542553 4057633 /opt/omni/databases/vendor/cc/sequent/
		i386/dynix/A.03.10/packet.Z
	383965649 4986458 /opt/omni/databases/vendor/cc/sgi/mips/
		irix/A.03.10/packet.Z
	2072292031 5777896 /opt/omni/databases/vendor/cc/sgi/mips/
		irix-62/A.03.10/packet.Z
	3340462006 4838628 /opt/omni/databases/vendor/cc/siemens/
		r400/sinix/A.03.10/packet.Z
	2053401217 4536467 /opt/omni/databases/vendor/cc/sun/sparc/
		solaris/A.03.10/packet.Z
	305493359 4616139 /opt/omni/databases/vendor/cc/sun/sparc/
		solaris-26/A.03.10/packet.Z
	216976711 6939519 /opt/omni/databases/vendor/cc/sun/sparc/
		sunos/A.03.10/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_21644

Equivalent Patches:
	PHSS_23110:
	s700: 11.00
	s800: 11.00

Patch Package Size: 83460 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_23109

	5a. For a standalone system, run swinstall to install the
	    patch:

		swinstall -x autoreboot=true -x match_target=true \
			-s /tmp/PHSS_23109.depot

	By default swinstall will archive the original software in
	/var/adm/sw/patch/PHSS_23109.  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_23109.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_23109.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
	PHSS_23109:
	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.


	NOTE!
	Fix for HSLco20414 introduces new options for device
	maintenance. The usage of new options is listed below:

	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}

	To obtain complete functionality one has to install
	PHSS_24423/PHSS_24424 (CORE) and PHSS_23689/PHSS_23690
	(Cell Server) or later patches as well.


	NOTE!

	Fix NSMex03419 is also part of the Windows NT
	(OMNIBACK_00014) and Cell Server (PHSS_22166/PHSS_22167)
	general release patch. Its functionality will be fully
	available when the mentioned patches that include this
	fix are released.


	Patch includes the following Site Specific Patches:
	   SSPUX310_003
	   SSPUX310_016
	   SSPUX310_028
	   SSPUX310_041
	   SSPUX310_051
	   SSPUX310_055