Patch Name: PHSS_24431

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

Creation Date: 01/08/20

Post Date:  01/10/05

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,A.03.00
	OMNIBACK-II.OMNI-OTHUX-P,A.03.00

Automatic Reboot?: No

Status: General Release

Critical: No

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

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

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

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

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

	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.

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

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

	PHSS_21331:
	Id = NSMbb23888, NSMbb33864
	    Restore of the SAP backup is not possible if there are
	    two or more equal Oracle SID's on different systems.

	Id = NSMbb23993
	    MoM GUI fails to start with the message:

	      "Can not access the Manager of Managers server".

	Id = NSMbb34111
	    Windows NT registry restore from incremental backup
	    fails.

	Id = NSMbb34280
	    MoM server does not save backup templates on client
	    cell server.

	Id = NSMex02374
	    Dragging host from ITO Node bank and dropping it in
	    Backup nodes results in an error:

	      "Backups will not start because there are no Cell
	       Manager licenses available".

	Id = NSMex02387
	    At the end of restore object stays as "Pending" instead
	    of "Completed".

	Id = NSMex02539, HSLco14279
	    MoM GUI reports duplicate medium barcodes.

	Id = NSMex02757
	    Object size displayed in the Restore GUI is incorrect.

	Id = NSMex02837, NSMex02840, NSMex02841, NSMex02916,
	     NSMex02447, NSMex02393
	    Various scheduler problems.

	Id = NSMex02954, HSLco14573
	    Selecting "..." in "To" field of Oracle 7
	    Restore GUI shows all the session for all
	    Oracle databases.

	Id = NSMex02989
	    Monitor GUI core dumps when printing all
	    sessions.

	Id = NSMex02991
	    GUI hangs when initializing media.

	Id = NSMex02504
	    omnib command periodically fails if it is started
	    with Maestro scheduler.

	Id = NSMex02530
	    When configuring a SAP barlist the message about
	    missing EMC licenses pops up even when there is no
	    EMC system in the cell.

	Id = NSMex02424
	    "All Media Available" in Media Management GUI does
	    not work correctly.

	Id = NSMex02716
	    Parameter file is not loaded in xomnibackup.

	Id = NSMex02773
	    After upgrade from 2.55 to 3.00, objects with capital
	    hostnames are not accessible with omnir and omnidb
	    commands, even if the option "noexpand" is used.

	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_24431:
	Id = JAGad01472
	    Exit code of omnimm is reported as successful when
	    the operation itself is not successful.

	Resolution:
	    Omnimm returns correct exit codes.

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

	Id = NSMex03587, 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 = 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 omniinit 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.

	PHSS_22036:
	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.

	PHSS_21331:
	Id = NSMbb23888, NSMbb33864
	    Restore GUI shows only one Oracle SID when there are
	    two or more equal Oracle SID's on different systems.

	Resolution:
	    Fix is implemented in xomnirestore.

	Id = NSMbb23993
	    MoM GUI can not be started if a user does not have
	    Admin Access rights.

	Resolution:
	    Any user with OmniBack II Access rights can start MoM
	    GUI. The limitations are that "Backup All" and
	    "Installation Administration (Install, Import, Export)"
	    can be started only by root:sys on MoM server.

	    Part of the SSPUX300_079.

	Id = NSMbb34111
	    Windows NT registry restore from incremental backup
	    fails.

	Resolution:
	    Windows NT registry from an incremetal backup is
	    successfully restored.

	Id = NSMbb34280
	    Backup template created in MoM environment is always
	    saved on the host from which the GUI was started.

	Resolution:
	    Backup templates are now saved on the specified host.

	Id = NSMex02374
	    Starting xomnibackup with the "datalist" option reports
	    the following error:

	      "Backups will not start because there are no Cell
	       Manager licenses available".

	Resolution:
	    Fix is implemented in xomnibackup.

	Id = NSMex02387
	    If "List from media" restore is executed, the status
	    of the object at the end of restore is "Pending"
	    instead of "Completed".

	Resolution:
	    Fix is implemented in Restore GUI.

	Id = NSMex02539, HSLco14279
	    Changing media location for at least two media results
	    in duplicated media barcodes.

	Resolution:
	    Fix is implemented in MoM GUI.

	Id = NSMex02757
	    Restore GUI reports incorrect size of the object,
	    if the objects are bigger than 4Gb.

	Resolution:
	    Object size calculation improved.

	Id = NSMex02837, NSMex02840, NSMex02841, NSMex02916,
	     NSMex02447, NSMex02393
	    Various scheduler problems.

	Resolution:
	    Scheduler fixed.

	    Part of the SSPUX300_081.

	Id = NSMex02954, HSLco14573
	    Selecting "..." in "To" field of Oracle 7
	    Restore GUI shows all the session for all
	    Oracle databases.

	Resolution:
	    Fix is implemented in Restore GUI.

	Id = NSMex02989
	    Monitor GUI core dumps when printing all sessions
	    if there is a backup host is more than 80
	    characters long.

	Resolution:
	    Hostname can be up to 120 characters long.

	Id = NSMex02991
	    When initializing media is done from Cell server
	    console, GUI hangs right after the confirmation
	    in the dialog box is clicked if the Actions menu
	    is opened.

	Resolution:
	    Fix is implemented in xomnimm.

	Id = NSMex02504
	    omnib command does not handle Interrupt signal
	    correctly.

	Resolution:
	    If command is not started from tty, interrupt
	    signal is ignored.

	    Part of the SSPUX300_080.

	Id = NSMex02530
	    After installing permanent licenses any attempt to
	    save a SAP barlist fails with a message:

	      "The Symmetrix or Time Finder Integration backup will
	       not start because the EMC SRDF Time Finder extension
	       license is not available"

	    even if there is no EMC system in the cell.

	Resolution:
	    GUI shows this message only when EMC Integration is
	    installed and there are no licenses for this
	    integration.

	    Part of the SSPUX300_082.

	Id = NSMex02424
	    "All Media Available" in Media Management GUI does not
	    display the right values.

	Resolution:
	    Fix is implemented in xomnimm.

	    Part of the SSPUX300_087.

	Id = NSMex02716
	    If EMC/SAP configuration is used, xomnibackup does not
	    read SAP parameter file correctly.

	Resolution:
	    Fix is implemented in xomnibackup.

	    Part of the SSPUX300_087.

	Id = NSMex02773
	    OmniBack II 3.00 internally uses lower case hostnames,
	    and when running a backup of a upper case hostname,
	    object names are converted to lower case in the OB2
	    database. Since this was not a case in OmniBack II 2.55
	    the objects that contain upper case letters and are
	    backed up with 2.55 are not recognized and the error:

	      "Cannot browse from root. Please specify starting
	       point"

	    is reported.

	Resolution:
	    Fix is implemented in omnir and omnidb commands.

	    Part of the SSPUX300_090.

	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 and NSMbb22439
	    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:
	H555005554 B554000550 8606132323 H555003728 H555003665
	8606161034 B554000716 5003457317 5003459081 8606107308
	5003463505 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:
	2287649809 10157339 /opt/omni/databases/vendor/cc/hp/s800/
		hp-ux/A.03.00/packet.Z
	2701850050 10354868 /opt/omni/databases/vendor/cc/hp/s800/
		hp-ux-10/A.03.00/packet.Z
	4118643446 12936719 /opt/omni/databases/vendor/cc/hp/s800/
		hp-ux-1020/A.03.00/packet.Z
	3343976239 3456913 /opt/omni/databases/vendor/cc/ibm/rs6000/
		aix-42/A.03.00/packet.Z
	940270868 3362457 /opt/omni/databases/vendor/cc/ibm/rs6000/
		aix/A.03.00/packet.Z
	2603126240 4261677 /opt/omni/databases/vendor/cc/dec/alpha/
		osf1-4/A.03.00/packet.Z
	4087630626 5162215 /opt/omni/databases/vendor/cc/sgi/mips/
		irix-62/A.03.00/packet.Z
	1177164897 4254339 /opt/omni/databases/vendor/cc/sgi/mips/
		irix/A.03.00/packet.Z
	339962317 3363447 /opt/omni/databases/vendor/cc/sco/i386/
		sco_sv/A.03.00/packet.Z
	2679982976 4203807 /opt/omni/databases/vendor/cc/siemens/
		r400/sinix/A.03.00/packet.Z
	2397323895 3864913 /opt/omni/databases/vendor/cc/sun/sparc/
		solaris/A.03.00/packet.Z
	1069802535 6273497 /opt/omni/databases/vendor/cc/sun/sparc/
		sunos/A.03.00/packet.Z
	3584579088 3959591 /opt/omni/databases/vendor/cc/sequent/
		i386/dynix/A.03.00/packet.Z
	1654616029 3509959 /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 PHSS_18695 PHSS_21331 PHSS_22036

Equivalent Patches:
	PHSS_24432:
	s700: 11.00
	s800: 11.00

Patch Package Size: 77340 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_24431

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

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

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

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

	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_20843/PHSS_20844,
	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
	SSPUX300_079
	SSPUX300_080
	SSPUX300_081
	SSPUX300_082
	SSPUX300_087
	SSPUX300_090