Patch Name: PHSS_29415

Patch Description: s700_800 10.20 OV OB4.10 patch - SAP packet

Creation Date: 03/09/08

Post Date: 03/09/18

Hardware Platforms - OS Releases:
	s700: 10.20
	s800: 10.20

Products:
	OmniBackII A.04.10

Filesets:
	OMNIBACK-II.OMNI-SAP-P,A.04.10

Automatic Reboot?: No

Status: General Superseded

Critical: No

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

Symptoms:
	PHSS_29415:
	Id = HSLco35983  SR: H555008572
	    Backup takes a lot of time to finish.

	Id = HSLco42398  SR: H555010594
	    During SAP integration backup with brarchive the
	    following is reported in the session report:

	     "BR301W SQL error -1017 at location BrDbConnect-1
	      ORA-01017: invalid username/password; logon denied
	      BR310W Connect to database instance UP2 failed"

	Id = HSLco42535  SR: H555010652
	    Configuration checking "util_sap.exe" sometimes fails
	    and in such cases environment setting troubleshooting
	    is not possible.

	PHSS_29405:
	Id = HSLco41136  SR: H555010162
	    After executing pre-exec script the subsequent popen
	    or pclose calls fail to get return code of executed
	    process.

	Id = HSLco42093  SR: H555010476
	    During SAP raw disk backup of read-only disk the
	    following is reported in the session report and the
	    disk is not backed up:

	      "Error: Cannot open object (|30| Read-only file
	      system)."

	PHSS_28723:
	Id = HSLco39882  SR: H555009563
	    Data Protector SAP R/3 integration does not work on
	    SAP R/3 system with Oracle 9i.

	Id = HSLco40709  SR: H555009941
	    Restore of SAP tablespace on raw disk bigger than the
	    one backed up falls into loop. Restore agent is then
	    aborted due to inactivity by session manager.

	Id = HSLco40764  SR: H555009971
	    During a SAP backup session, debug.log file is being
	    filled with "Unknown state" messages.

	PHSS_28343:
	Id = HSLco36193  SR: H555008621
	    Errors are reported in debug.log for files of size 0 and
	    for missing function entry statements.

	Id = HSLco36404  SR: H555008642
	    SAP BR tools 6.10 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.

	Id = HSLco37210  SR: H555008812
	    During raw device SAP restore following error is
	    reported:

	      "|Minor| From: OB2BAR_SAPREST@<host> ""  Time:<time>
	       Error: Cannot open object <raw disk path>
	       |20| Not a directory)."

	Id = HSLco37773  SR: H555008906
	    During some backint queries following error is reported:

	      "|Critical| From: OB2BAR@<host> ""  Time:<time>
	       Failed to allocate memory.
	       System error: |12| Not enough space"

	Id = HSLco37783  SR: H555008908
	    When OmniBack II tries to backup nonexistent SAP redo
	    logs, session ends as failed.

	Id = HSLco39552  SR: H555009439
	    SAP backup on Linux, reports the following error:

	    "Cannot get information on file
	     '/sapmnt/SID/exe/brarchive ...' Error: 22."

	PHSS_27452:
	Id = HSLco35628  SR: H555008480
	    Raw partition backup is not restored even though
	    OmniBack II states that restore session is completed
	    successfully.

	Id = HSLco35646  SR: H555008483
	    Aborting SAP backup session results in executing new
	    session.

	Id = JAGae25124  SR: 8606260802
	    Session log files contains improper information when
	    SAP backup fails.

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

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

	Id = HSLco33795  SR: H555007605
	    OmniBack II SAP integration is not supported on
	    Compaq Tru64 operating system.

Defect Description:
	PHSS_29415:
	Id = HSLco35983
	    There is approximately 20 sec delay between backup
	    of stage files in SAP Database.

	Resolution:
	    "ErhMark" is removed from "CheckSize" function.

	Id = HSLco42398
	    Notes in UNIX and Windows Integration Guides state that
	    OmniBack II supports all options of SAP "brtools" that
	    are also supported through backint which is not correct.

	Resolution:
	    By setting "OB2NOBRTSECU" variable in "omnirc" file, a
	    part of code that is responsible for hiding
	    username/password for "brtools" is excluded, and backup
	    with command "brarchive -b" is possible.

	Id = HSLco42535
	    Environment is not written to debugs.

	Resolution:
	    Values of environment variables are logged into debugs.

	PHSS_29405:
	Id = HSLco41136
	    Default handling of child processes is set to discard
	    the child return code after script execution.

	Resolution:
	    After script is executed handling of the child
	    processes is restored to initial state.

	    Part of SSPUX410_069.

	Id = HSLco42093
	    Raw disks are opened for check in read-write mode.

	Resolution:
	    During backup disks are opened in read-only mode.

	    Part of SSPUX410_075.

	PHSS_28723:
	Id = HSLco39882
	    Oracle Server Manager (svrmgrl) is obsoleted with
	    Oracle 9i. sqlplus needs to be used instead.

	Resolution:
	    Data Protector SAP R/3 integration works on SAP R/3
	    system with Oracle 9i.

	    Part of SSPUX410_067.

	Id = HSLco40709
	    Size of data to be restored is mistakenly overwritten
	    by disk size checking function.

	Resolution:
	    Disk size checking function is changed in a manner that
	    it properly calculates destination directory properties.

	    Part of SSPUX410_064.

	Id = HSLco40764
	    All information messages in switch.log, except #SUCCESS
	    and #ERROR, are being treated as serious error.

	Resolution:
	    Status of information messages is lowered from "error"
	    to normal.

	PHSS_28343:
	Id = HSLco36193
	    CheckFile checks marked error if parameter is null.
	    Debugs are initialized after function entry is marked.

	Resolution:
	    Error messages are not written to the debug.log file.

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

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

	Id = HSLco37210
	    OmniBack II ignores the following caution in the SAP
	    specification:

	      "Caution:By restoring raw partition to a different
	      one, the <dest_dir> means directly the new raw
	      partition, not the directory containing the special
	      file."

	Resolution:
	    Destination directory forming procedure is changed.

	Id = HSLco37773
	    Some parts of structures for query are allocated but
	    not released.

	Resolution:
	    All allocated structures are released.

	Id = HSLco37783
	    By design, whenever there are no objects backed up,
	    OmniBack II ends session as failed.

	Resolution:
	    Two new global variables have been introduced:

	    a) 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.
	    b) TreatScriptReturnAsNormal=<script return>
	    By setting this variable to a certain number instructs
	    OmniBack II to treat all the script returns equal to
	    the specified number as normal.

	Id = HSLco39552
	    'brbackup' and 'brarchive' are called with wrong
	    parameters.

	Resolution:
	    Parameters for 'brarchive' and 'brbackup' calls are
	    corrected.

	    Part of SSPUX410_050.

	PHSS_27452:
	Id = HSLco35628
	    Incorrect function is used for raw partition restore.

	Resolution:
	    Raw partition restore uses proper function.

	    Part of SSPUX410_027.

	Id = HSLco35646
	    Abort mechanism is implemented incorrectly.

	Resolution:
	    Sapback aborts all the objects upon abort request from
	    OmniBack II user.

	Id = JAGae25124
	    Session log files contains improper information when
	    SAP backup fails.

	Resolution:
	    Log files contain proper information.

	    Part of SSPUX410_023.

	Id = HSLco35966
	    Connection string in printed in plain text format.

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

	    Part of SSPUX410_025.

	PHSS_26887:
	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 SSPUX410_014.

	Id = HSLco33795  SR: H555007605
	    OmniBack II SAP integration is not supported on
	    Compaq Tru64 operating system.

	Resolution:
	    OmniBack II SAP integration is supported on
	    Compaq Tru64 operating system.

SR:
	H555010594 H555010652 H555008572 H555010476 H555010162
	H555009971 H555009941 H555009563 H555008908 H555009439
	8606207021 H555008621 H555008812 H555008642 H555008643
	H555008906 H555008807 H555008480 8606244527 8606260802
	H555008483 H555008565 H555007605 H555007380

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

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

cksum(1) Output:
	1261112550 968600 /opt/omni/databases/vendor/sap/gpl/i386/
		linux-60/A.04.10/packet.Z
	2652885644 1370367 /opt/omni/databases/vendor/sap/hp/s800/
		hp-ux-1020/A.04.10/packet.Z
	1250503032 1371319 /opt/omni/databases/vendor/sap/hp/s800/
		hp-ux-11/A.04.10/packet.Z
	1185831527 1189526 /opt/omni/databases/vendor/sap/ibm/
		rs6000/aix-42/A.04.10/packet.Z
	1893972187 1240949 /opt/omni/databases/vendor/sap/sun/sparc/
		solaris-26/A.04.10/packet.Z
	1146700958 1875293 /opt/omni/databases/vendor/sap/dec/alpha/
		osf1-4/A.04.10/packet.Z
	1650591381 18 /opt/omni/databases/vendor/sap/dec/alpha/
		osf1-4/A.04.10/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_29409:
	Core packet patch,
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	Id = HSLco33795  SR:H555007605
	Bad catalog access messages are displayed without
	PHSS_29409.

	PHSS_28740:
	Cell Server (CS) packet patch,
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	Id = HSLco37783  SR:H555008908
	PHSS_28740 is required for these defect fixes.

	PHSS_28738:
	Cell Console (CC) packet patch,
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	PHSS_28738 is required for this defect fix.

	PHSS_28341:
	EMC packet patch,
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	PHSS_28341 is required for this defect fix.

Supersedes:
	PHSS_26887 PHSS_27452 PHSS_28343 PHSS_28723 PHSS_29405

Equivalent Patches:
	PHSS_29416:
	s700: 11.00 11.11
	s800: 11.00 11.11

Patch Package Size: 7570 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_29415

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

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

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

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


	Patch includes the following Site Specific Patches:
	   SSPUX410_014
	   SSPUX410_023
	   SSPUX410_025
	   SSPUX410_027
	   SSPUX410_033
	   SSPUX410_036
	   SSPUX410_050
	   SSPUX410_064
	   SSPUX410_067
	   SSPUX410_069
	   SSPUX410_075