Patch Name: PHSS_16713

Patch Description: s700_800 10.X OV OB2.55 patch - SAP packet

Creation Date: 98/12/02

Post Date:  98/12/15

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

Filesets:
	OMNIBACK-II.OMNI-SAP-P

Automatic Reboot?: No

Status: General Superseded

Critical: No

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

Symptoms:
	PHSS_16713:
	Id = NSMex01373
	    SAP backup reports '#ERROR <filename>' if a file
	    is bigger than 2 GB.

	Id = NSMex01445
	    Backup of some SAP files fails with an error
	    "Brbackup doesn't respond."

	Id = NSMex01638
	    SAP restore query via backint is very slow.

	Id = NSMex01735
	    SAP Restore fails with the error message:
	    "ABORT request from RSM (ERR: Bar object not
	    found in the database.)"

	Id = NSMbb22035
	    Sparse files corrupted after restore.

	PHSS_14347:
	Id = NSMex01145
	    Restore of archive logs failed with
	    Query incomplete/failed (Object not found.).

	Id = NSMex01140
	    SAP restore to the host different than the backed
	    up host failed.

	Id = NSMex00831
	    SAP backup failed with:
	    "No Backup utility ID or ID longer than 16 characters."

Defect Description:
	PHSS_16713:
	Id = NSMex01373
	    On systems that support files bigger than 2Gb,
	    the SAP integration backup reports an error for
	    each file bigger than 2 GB. As a result these files
	    are not backed up.
	    Part of SSP255_67.

	Id = NSMex01445
	     Backup of some SAP files fails with an error
	     "Brbackup doesn't respond." This happens due to
	     long response time from brbackup (10 minutes).
	     This time-out is now increased to 1 hour.
	     Now, if brbackup does not respond within 30 minutes,
	     the sapback process will report the following warning:
	        "Sapback hasn't got confirmation from
	          brbackup for file %s for 30 minutes"
	     After 1 hour the backup will skip this file
	     and continue with the next file.
	     Part of SSP255_72.

	|Id = NSMex01638
	     Backint queries for all 256 SAP sets instead of
	     checking for the number of needed queries.
	     This causes the SAP restore to be very slow.
	     Part of SSP255_100.

	Id = NSMex01735
	     SAP restore of a file from the first set of backed
	     up files failed with an error: "Bar object not
	     found in the database."
	     Part of SSP255_102.

	Id = NSMbb22035
	     Restore of sparse files produces corrupted files.
	     Although the files are backed up correctly, restore
	     will cause sparse files corruption (data changed,
	     size of file reduced signifficantly).

	PHSS_14347:
	Id = NSMex01145
	    SAP restore of archive logs failed because
	    session was not found in the OmniBack II DB if
	    during backup there was more than one backint started.
	    Part of SSP255_28.

	Id = NSMex01140
	    SAP restore failed if the hostname of the target
	    host was different than the backed up hostname while
	    the object name was the same. The problem has been
	    observed in the Service Guard environment.
	    Part of SSP255_33.

	Id = NSMex00831
	    SAP backup failed with:
	    "No Backup utility ID or ID longer than 16 characters."
	    The problem appeared if parallelism was bigger than 25.
	    Part of SSP255_47.

SR:
	5003399097 5003437921

Patch Files:
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux/A.02.55/
		packet.Z
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-10/A.02.55/
		packet.Z
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.02.55/
		packet.Z
	/opt/omni/databases/vendor/sap/ibm/rs6000/aix/A.02.55/
		packet.Z
	/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.02.55/
		packet.Z

what(1) Output:
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux/A.02.55/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-10/A.02.55/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.02.55/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/ibm/rs6000/aix/A.02.55/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.02.55/
		packet.Z:
		None

cksum(1) Output:
	3869601673 756885 /opt/omni/databases/vendor/sap/hp/s800/
		hp-ux/A.02.55/packet.Z
	2619915989 823912 /opt/omni/databases/vendor/sap/hp/s800/
		hp-ux-10/A.02.55/packet.Z
	528135834 810763 /opt/omni/databases/vendor/sap/hp/s800/
		hp-ux-1020/A.02.55/packet.Z
	2481971153 672353 /opt/omni/databases/vendor/sap/ibm/rs6000/
		aix/A.02.55/packet.Z
	3968459836 676326 /opt/omni/databases/vendor/sap/ibm/rs6000/
		aix-42/A.02.55/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_14347

Equivalent Patches:
	PHSS_16714:
	s700: 11.00
	s800: 11.00

Patch Package Size: 3720 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_16713

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

		swinstall -x autoreboot=true -x match_target=true \
			-s /tmp/PHSS_16713.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_16713.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_16713.  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_16713.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_16713.depot of=/dev/rmt/0m bs=2k

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

	The SAP-R3 packet needs to be redistributed to the
	appropriate systems, where the SAP-R3 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 SAP-R3 backup or restore is running
	while you distribute the packet to the SAP-R3 client.

	The patch includes the following Site Specific Patches:
	   SSP255_28
	   SSP255_33
	   SSP255_47
	   SSP255_67
	   SSP255_72
	   SSP255_100
	   SSP255_102