Patch Name: PHSS_18695

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

Creation Date: 99/08/02

Post Date:  99/08/09

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-HPUX-P OMNIBACK-II.OMNI-OTHUX-P

Automatic Reboot?: No

Status: General Superseded

Critical: No

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

Symptoms:
	PHSS_18695:
	ID = NSMex02288
	    Backups start automatically, although the user
	    excludes specific days in the backup scheduler.

	Id = NSMex02429
	    The xomnirestore GUI coredumps while configuring
	    Oracle restore.

	Id = NSMex02339
	    The xomnimom GUI crashes if any combined license
	    is installed on the cell manager system.

	Id = NSMex02295
	    "omnimm" command incorrectly parses slot range.

	Id = NSMex02181
	    The GUI licensing info shows wrong information when
	    combined licenses are installed.

	Id = NSMbb24161
	    Exit status of 'omnir' command is 0 even if the
	    user has aborted it.

	PHSS_17301:
	Id = NSMex01981, NSMbb22439
	    Oracle restore GUI gives no usefull info when '...'
	    button is clicked for the 'To' field.

	Id = NSMbb21778
	    Connecting to session from CLI fails, if session has
	    been started after 1.1.2000, and short session ID is
	    used, e.g.: 'omniabort -sess 4'.

	Id = HSLco11626
	    Resizing of some dialogs does not work on systems with
	    Japanese locale.

	Id = NSMex01872
	    xomniadmin coredumps during the installation.

	Id = NSMex01933
	    Parallel restore doesn't work, using omnir command.

	Id = NSMbb22764
	    Error message with ITO integration:
	    "Bad Catalog access for message #117 in set 49 !"

	Id = NSMex02191, NSMbb23538
	    Starting 'point in time' restore of Oracle db results
	    in EBU failing with the message:
	    'EBU-530: Date is not in expected format: MM/DD/YYYY'

	Id = NSMex02296
	    Restore with EMC/SRDF TimeFinder integration fails with
	    the message

	    [Major] From: SYMA@host.domain.com ""  Time: <time>
	    [223:327]       SYMA-R2 Could not mount filesystem
	    /dev/vg01 to /mountpoint.

	    [Major] From: SYMA@host.domainc.com ""  Time: <time>
	    [223:363] SYMA-R2 Could not prepare mirror disks of obj
	    /mountpoint
	        for backup.
	        ([22] Invalid argument)
	    [Major] From: SYMA@host.domain.com ""  Time: <time>
	    [223:327]       SYMA-R2 Could not mount filesystem
	    /dev/vg01 to /mountpoint.

	    [Major] From: SYMA@host.domainc.com ""  Time: <time>
	    [223:363] SYMA-R2 Could not prepare mirror disks of obj
	    /mountpoint
	        for backup.
	        ([22] Invalid argument)
	    [Major] From: SYMA@host.domain.com ""  Time: <time>
	    [223:327]       SYMA-R2 Could not mount filesystem
	    /dev/vg01 to /mountpoint.

	    [Major] From: SYMA@host.domainc.com ""  Time: <time>
	    [223:363] SYMA-R2 Could not prepare mirror disks of obj
	    /mountpoint
	        for backup.
	        ([22] Invalid argument)

Defect Description:
	PHSS_18695:
	Id = NSMex02288
	    Dates on which the backups are supposed to be excluded
	    (not started) are incorrectly written to the backup
	    specification. This causes backup to be started even
	    the user explicitly selected days when a backup should
	    not be started.

	Resolution:
	    Scheduling info written correctly into backup
	    specification schedule file.

	Id = NSMex02429
	    The xomnirestore GUI can coredump during the
	    configuration of Oracle restore, if OmniBack II
	    database contains a lot of Oracle objects.

	Resolution:
	    GUI now correctly handles big amount of Oracle objects.

	ID = NSMex02339
	    When combined licenses are installed on the license
	    server in a centralized licensing environment, the
	    xomnimom GUI crashes when user clicks on any cell
	    manager.
	    Part numbers of such licenses are:

	    B6951AA (UNIX Cell Manager + 1 UNIX Single Drive)
	    B6952AA (UNIX Cell Manager + 1 UNIX Multi Drive Server)

	    Part of SSPUX300_069
	Resolution:
	    Combined license handling is improved.

	NSMex02295
	    Incorrect parsing of slot range causes the library to
	    eject/enter wrong media.

	    Part of SSPUX300_065
	Resolution:
	    Slot parsing fixed.

	NSMex02181
	    The xomniadmin GUI doesn't show combined licenses
	    correctly. Part numbers of such licenses are:

	    B6951AA (UNIX Cell Manager + 1 UNIX Single Drive)
	    B6952AA (UNIX Cell Manager + 1 UNIX Multi Drive Server)

	    Part of SSPUX300_050
	Resolution:
	    The xomniadmin GUI now shows detailed list of licenses
	    available.

	Id = NSMbb24161
	    Return status of the omnir command is not updated if
	    user aborts the execution. Exit value is 0, and this
	    gives the impression that the command completed
	    successfuly although it has been interrupted.

	    Part of SSPUX300_074
	Resolution:
	    Return code is set correctly before exiting.

	PHSS_17301:
	Id = NSMex01981
	    An error in the database query results in an empty
	    output when clicking the '...' button for the 'To'
	    field in the Oracle Object Restore GUI.
	    Part of SSPUX300_023.
	Resolution:
	    GUI now passes correct parameters to db query.

	Id = NSMbb21778
	    Any command using short session ID will fail
	    because of ivalid parsing, if session has been
	    started after January 1st 2000. If long session
	    ID is used, the error does not appear.
	Resolution:
	    Session parsing now recognizes short session
	    ID for next centuries too.

	Id = HSLco11626
	    Resizing of popup dialogs does not work correctly on
	    systems with Japanese locale.
	    Part of SSPUX300_004.
	Resolution:
	    The GUI is modified to handle Japanese
	    locales correctly.

	Id = NSMex01872
	    xomniadmin coredumps if one of the hosts is a NT
	    MS Wolfpack Cluster Server.
	    Part of SSPUX300_008.
	Resolution:
	    Parsing of cell_info file is improved.

	Id = NSMex01933
	    "omnir" did not parse options correctly, so that
	     parallel restore didn't work.
	     Part of SSPUX300_020.
	Resolution::
	     Fixed options parsing.

	Id = NSMbb22764
	    Within a c-code switch{} statement, a missing
	    break statement caused execution of additional
	    code which resulted in displaying this superflous
	    message.
	Resolution:
	    A break in the switch statement prevents
	    execution of the superflous code.

	Id = NSMex02191, NSMbb23538
	    The date to which oracle db should be  restored to is
	    sent to EBU in the format 'MM/DD/YY hh:mm:ss', but EBU
	    expects it the format 'MM/DD/YYYY hh:mm:ss'.
	Resolution:
	    GUI now sends the date in correct format.

	Id = NSMex02296
	    If the EMC restore is started using the command omnir,
	    the session will fail as described in Symptoms. The
	    reason is in the omnir command sending misspelled
	    parameters to RSM.
	Resolution:
	    Correct startup option sent to rsm by omnir.

SR:
	5003455857 1653303180 1653287615 B700029256 1653297853

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

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

cksum(1) Output:
	2669197062 10156804 /opt/omni/databases/vendor/cc/hp/s800/
		hp-ux/A.03.00/packet.Z
	4215495723 10340642 /opt/omni/databases/vendor/cc/hp/s800/
		hp-ux-10/A.03.00/packet.Z
	316486976 17340425 /opt/omni/databases/vendor/cc/hp/s800/
		hp-ux-1020/A.03.00/packet.Z
	4271800863 3520343 /opt/omni/databases/vendor/cc/ibm/rs6000/
		aix-42/A.03.00/packet.Z
	1533820908 3447025 /opt/omni/databases/vendor/cc/ibm/rs6000/
		aix/A.03.00/packet.Z
	1972092667 4372371 /opt/omni/databases/vendor/cc/dec/alpha/
		osf1-4/A.03.00/packet.Z
	1056804236 5298581 /opt/omni/databases/vendor/cc/sgi/mips/
		irix-62/A.03.00/packet.Z
	201867760 4357209 /opt/omni/databases/vendor/cc/sgi/mips/
		irix/A.03.00/packet.Z
	274570075 3430851 /opt/omni/databases/vendor/cc/sco/i386/
		sco_sv/A.03.00/packet.Z
	1786290107 4317672 /opt/omni/databases/vendor/cc/siemens/
		r400/sinix/A.03.00/packet.Z
	4282870604 3944567 /opt/omni/databases/vendor/cc/sun/sparc/
		solaris/A.03.00/packet.Z
	964517089 6525014 /opt/omni/databases/vendor/cc/sun/sparc/
		sunos/A.03.00/packet.Z
	2421549513 3938257 /opt/omni/databases/vendor/cc/sequent/
		i386/dynix/A.03.00/packet.Z
	3773431901 3483219 /opt/omni/databases/vendor/cc/ncr/i386/
		mp-ras/A.03.00/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_17301

Equivalent Patches:
	PHSS_18696:
	s700: 11.00
	s800: 11.00

Patch Package Size: 82570 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_18695

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

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

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

Special Installation Instructions:
	PHSS_18695:
	NOTE!
	Patch has to be installed on the Installation Server host.

	"/opt/omni/sbin/omnisv.sh stop" must be executed
	on the cell server before swinstall is run. After
	the swinstall completes, restart OmniBackII using
	"/opt/omni/sbin/omnisv.sh start".

	The Cell Console packets must be redistributed
	to the Cell Manager system and client systems
	afterwards to get the fixes into effect.

	In order to receive proper messages you must install also
	the OMNIBACK II A.03.00 CORE packet patch.
	The latest CORE patch is currently PHSS_17307/PHSS_17308,
	but may be superseded by a newer version in the future.


	Patch includes the following Site Specific Patches:
	SSPUX300_004
	SSPUX300_008
	SSPUX300_020
	SSPUX300_023
	SSPUX300_050
	SSPUX300_065
	SSPUX300_069
	SSPUX300_074