Patch Name: PHSS_28017

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

Creation Date: 03/01/16

Post Date:  03/01/23

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-SAP-P,A.03.50

Automatic Reboot?: No

Status: General Release

Critical: No

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

Symptoms:
	PHSS_28017:
	Id = HSLco35966  SR: H555008565
	    "util_sap -APP" displays connection strings.

	Id = HSLco36404  SR: H555008642
	    SAP BR tools 6.10 (44) reports:

	       "BR247E No Backup utility ID or ID longer than 16
	       characters".

	Id = HSLco37193  SR: H555008807
	    When backing up SAP integration with EMC split mirror
	    functionality, not all the SAP files are backed up.

	PHSS_26879:
	Id = HSLco33261  SR:H555007380
	    SAP integration on UNIX clients automatically passes
	    "-u" option.

	Id = HSLco33948  SR:H555007650
	    a) After OmniBack II upgrade from A.03.10 to A.03.50,
	       SAP backup fails with Memory fault.

	    b) SAP objects restore GUI browser fails with the
	       error message:
	        "Cannot browse from root.
	         Please specify starting point."

	PHSS_24988:
	Id = HSLco27737  SR:H555005741
	    Omniback II does not support SAP integration on Linux.

	Id = JAGad82658  SR:8606213466
	    SAP on Oracle 8.1.6 64 bit configuration fails with:

	      "/usr/lib/pa20_64/dld.sl: Unable to find library
	      'libwtc8.sl'".

	Id = HSLco26047 HSLco28867 SR:H555005128 SR:H555006178
	    Although brarhive exit code is not 0, Omniback II
	    reports "Session completed successfully".

	Id = HSLco30814  SR:H555006710
	    Session ends as failed because Omniback II tries
	    to back up non existent SAP redo logs.

	PHSS_22912:
	Id = NSMex03392
	    Brbackup output contains duplicated messages.

	Id = NSMex03419
	    After importing a tape from 2.55, some of the SAP
	    files can not be restored.

	Id = NSMex03601, NSMex03617
	    SAP backup fails with

	      "Brbackup doesn't respond".

	Id = NSMex03690
	    Disk balancing on EMC Symmetrix fails.

Defect Description:
	PHSS_28017:
	Id = HSLco35966
	    Connection string in printed in plain text format.

	Resolution:
	    Connection string is encrypted before it is passed
	    to GUI.

	    Part of SSPUX350_079.

	Id = HSLco36404
	    Set ID number searching is not strict enough and gets
	    confused by new SAP BR tools format.

	Resolution:
	    Stricter checking is applied to see if it really is
	    backint ID.

	    Part of SSPUX350_081.

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

	PHSS_26879:
	Id = HSLco33261
	    brbackup/brarchive is always started with "-u" option
	    which displays logon information.

	Resolution:
	    brbackup/brarchive options are passed in a file.

	    Part of SSPUX350_073.

	Id = HSLco33948
	    Variable ARG_FILELIST is not set to 0.

	Resolution:
	    ARG_FILELIST is set to 0, in order to properly set
	    ARG_FILELIST's MALLOC.

	PHSS_24988:
	Id = HSLco27737
	    Omniback II does not support SAP integration on Linux.

	Resolution:
	    Omniback II supports SAP integration on Linux.

	Id = JAGad82658
	    Error occurs because omnisap.exe and SAP_template
	    search for 64 bit shared library in wrong path.

	Resolution:
	    Path for ${ORA_HOME}/lib64 is added.

	Id = HSLco26047 HSLco28867
	    Omnisap.exe script on Unix does not exit with
	    brarchive exit code.

	Resolution:
	    Omnisap.exe is changed.

	    Part of SSPUX350_047.

	Id = HSLco30814
	    By design, Omniback II ends session as 'Failed' if
	    there are no objects to back up.

	Resolution:
	    Two new global variables have been introduced:

	      1) SessSucessfullWhenNoObjectsBackedUp=0
	      By setting this variable to 1 user can change the
	      Omniback II behavior in order to end the session
	      as successful when there are no objects backed up.

	      2) TreatScriptReturnAsNormal=<script return>
	      Setting this variable to a certain number instructs
	      Omniback II to treat all the script returns equal
	      to the specified number as normal.

	    Part of SSPUX350_062.

	PHSS_22912:
	Id = NSMex03392
	    Brbackup utility puts empty lines into communication
	    file. Sapback sends these lines to backint which after
	    getting an empty line dumps its previous content to
	    session output.

	Resolution:
	    Fix implemented in sapback and backint prevents
	    duplicating of messages in session output.

	Id = NSMex03419
	    In pre-3.0 versions of OmniBack II file names were
	    stored on the tape in the original case. OBII 3.0
	    and later store file names in lower case and because
	    of that, during restore it assumes 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.50 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 of SAP.

	Id = NSMex03601, NSMex03617
	    If brbackup response time is too long for some
	    reason, session will fail with the error:

	      "Brbackup doesn't respond.".

	Resolution:
	    Timeout for brbackup is implemented. OmniBack II
	    reports a warning after waiting for brbackup response
	    for 30 minutes and aborts the session after 2 hours.

	Id = NSMex03690
	    EMC Symmetrix disk balancing for SAP backup is not
	    properly implemented.

	Resolution:
	    Disk balancing is improved.

SR:
	H555008642 H555008807 H555008565 H555007650 H555007380
	H555005741 8606213466 H555006710 H555006178 H555005128
	B554000819 B554000747 B554000550 B554000523 B554000732

Patch Files:
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-10/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-11/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/sap/sun/sparc/solaris/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/sap/sun/sparc/solaris-26/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/sap/gpl/i386/linux/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/sap/gpl/i386/linux/A.03.50/
		require.dat

what(1) Output:
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.03.50/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-10/A.03.50/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/hp/s800/hp-ux-11/A.03.50/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.03.50/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/sun/sparc/solaris/A.03.50/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/sun/sparc/solaris-26/A.03.50/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/gpl/i386/linux/A.03.50/
		packet.Z:
		None
	/opt/omni/databases/vendor/sap/gpl/i386/linux/A.03.50/
		require.dat:
		None

cksum(1) Output:
	2040216157 967481 /opt/omni/databases/vendor/sap/hp/s800/
		hp-ux-1020/A.03.50/packet.Z
	689697014 950763 /opt/omni/databases/vendor/sap/hp/s800/
		hp-ux-10/A.03.50/packet.Z
	1696371913 968137 /opt/omni/databases/vendor/sap/hp/s800/
		hp-ux-11/A.03.50/packet.Z
	3986034704 802917 /opt/omni/databases/vendor/sap/ibm/rs6000/
		aix-42/A.03.50/packet.Z
	2609729354 1007911 /opt/omni/databases/vendor/sap/sun/sparc/
		solaris/A.03.50/packet.Z
	3548452470 1043883 /opt/omni/databases/vendor/sap/sun/sparc/
		solaris-26/A.03.50/packet.Z
	3835548504 1299009 /opt/omni/databases/vendor/sap/gpl/i386/
		linux/A.03.50/packet.Z
	2538349776 17 /opt/omni/databases/vendor/sap/gpl/i386/linux/
		A.03.50/require.dat

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies:
	If any newer SSP for the SAP is installed
	on your system, you must re-apply the SSP after
	installing this SAP patch.

	PHSS_28222:
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	PHSS_28222 is required for this defect fix.

	PHSS_28021:
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	PHSS_28021 is required for this defect fix.

	PHSS_28019:
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	PHSS_28019 is required for this defect fix.

Supersedes:
	PHSS_22912 PHSS_24988 PHSS_26879

Equivalent Patches:
	PHSS_28018:
	s700: 11.00 11.11 11.20
	s800: 11.00 11.11 11.20

Patch Package Size: 6950 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_28017

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

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

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

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

	The OB2 SAP agent must be redistributed to the SAP
	client system(s) after the installation of the patch
	in order to get the fixes into effect.

	For distribution of the SAP agent, refer to
	the OmniBackII Installation guide.

	NOTE!
	Instructions for manual installation of non HP-UX patches:

	1. Rename the patch:

	   mv PHSS_<number> PHSS_<number>.shar

	2. Then unshar the patch:

	   sh PHSS_<number>.shar.

	During unshar operation an error message will occur due to
	using non HP-UX platform for unshar although everything
	will be done. When the patch is unshared, there will be
	PHSS_<number>.depot and PHSS_<number>.text.

	3. Depot file is a tar package, which should be untared:

	   tar -xvf PHSS_<number>.depot

	There is whole directory structure stored in the package,
	so this tree structure will be created under current
	directory.

	4. Create a temporary directory /tmp/omni_tmp and copy
	appropriate packet.Z from expanded depot file.
	Use packet.Z from OMNI-SAP-P/<OS_TYPE>/A.03.50
	directory, where "OS_TYPE" is one of:

	  dec/alpha/osf1-4, gpl/i386/linux, ibm/rs6000/aix-42,
	  ncr/i386/mp-ras, sco/i386/sco_sv, sco/i386/unixware,
	  sequent/i386/dynix, sgi/mips/irix-62, siemens/r400/sinix,
	  sun/sparc/solaris-26, sun/sparc/sunos.

	5. In the next step one has to copy utils.tar package from
	the OmniBack II installation CD to a temporary directory
	on the non HP-UX machine (for example: /tmp/omni_tmp).
	The utils.tar file can be found on the installation CD
	on the following location:

	/OMNIBACK-II/OMNI-CORE-IS/opt/omni/databases/utils/ \
	<OS_TYPE>/utils.tar

	6. Un-tar the utils.tar package and find the omni_rinst.sh
	installation script. Install the patch locally on the
	non-HP-UX client using this script:

	./omni_rinst.sh <tempdir>/packet.Z <package> <version> \
	 <OS_TYPE> /usr/omni <Cell Server>

	where:
	 <tempdir> - temporary directory where the packet.Z is
	    stored (for example /tmp/omni_tmp)
	 <package> - name of the component (for example SAP)
	 <Cell Server> - one can see this parameter in the
	    /usr/omni/config/cell/cell_server file. Be careful to
	    set the same name as written in cell_server file.

	Following the procedure written above the patch should be
	successfully installed.


	Patch includes the following Site Specific Patches:
	   SSPUX350_047
	   SSPUX350_062
	   SSPUX350_073
	   SSPUX350_079
	   SSPUX350_080
	   SSPUX350_081