Patch Name: PHSS_21658

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

Creation Date: 02/01/25

Post Date:  02/02/01

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

Filesets:
	OMNIBACK-II.OMNI-ORA-P,A.03.10

Automatic Reboot?: No

Status: General Release

Critical: No

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

Symptoms:
	PHSS_21658:
	Id = HSLco17699, JAGad00934 SR:B555004087, 8606131784
	    When Oracle7 is configured with multiple parameter
	    files, the configuration fails with the error message:

	      "Oracle Parameter File (alias Oracle init file)
	       specified in the configuration does not exist."

	Id = NSMex02592 SR: B555003386
	    Restoring catalog database with two target databases
	    registered in it can cause that not the latest catalog
	    backup is restored. The catalog database should always
	    be restored from the latest backup and should not
	    depend on target databases.

	Id = HSLco14746 SR: H555002538
	    EBU 2.2 is not supported on AIX 4.3.

	Id = NSMex03408, NSMex03594 SR: B554000539, B554000724
	    Backup and restore session on AIX systems always
	    produce debugs.

Defect Description:
	PHSS_21658:
	Id = HSLco17699, JAGad00934
	    Oracle7 configuration script can only handle one
	    parameter file. If there are more files listed, it
	    cannot parse them correctly.

	Resolution:
	    Parameter file(s) specification is now parsed line
	    by line, and each file existence is checked separately.
	    Part of SSPUX310_023.

	Id = NSMex02592
	   Querying backup objects of catalog database in OB
	   database depends on SID of target database.

	Resolution:
	   Changes in querying OmniBack database for backup
	   objects.

	Id = HSLco14746
	    EBU 2.2 cannot be backed up with OmniBack II on
	    AIX 4.3 platform.

	Resolution:
	    Binaries for AIX 4.3 have been provided in order to
	    enable backup of EBU 2.2 on AIX 4.3. See Special
	    Installation Insctructions for detailed info on how
	    to install and configure the client.

	    Part of SSPUX310_007.

	Id = NSMex03408, NSMex03594
	    Option "-debug" is always added when executing a
	    backup or restore session of Oracle objects on
	    AIX systems.

	Resolution:
	    Debug files are created only when "-debug" option
	    is specified.

SR:
	B554000539 H555002538 8606131784 B555004087 B554000724
	B555003386

Patch Files:
	/opt/omni/databases/vendor/oracle/hp/s800/hp-ux-10/A.03.10/
		require.dat
	/opt/omni/databases/vendor/oracle/hp/s800/hp-ux-10/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/oracle/hp/s800/hp-ux-1020/
		A.03.10/require.dat
	/opt/omni/databases/vendor/oracle/hp/s800/hp-ux-1020/
		A.03.10/packet.Z
	/opt/omni/databases/vendor/oracle/ibm/rs6000/aix-42/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/oracle/ibm/rs6000/aix-42/A.03.10/
		require.dat
	/opt/omni/databases/vendor/oracle/sun/sparc/solaris/A.03.10/
		require.dat
	/opt/omni/databases/vendor/oracle/sun/sparc/solaris/A.03.10/
		packet.Z
	/opt/omni/databases/vendor/oracle/sun/sparc/solaris-26/
		A.03.10/packet.Z
	/opt/omni/databases/vendor/oracle/sun/sparc/solaris-26/
		A.03.10/require.dat

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

cksum(1) Output:
	4114248506 18 /opt/omni/databases/vendor/oracle/hp/s800/
		hp-ux-10/A.03.10/require.dat
	4209142592 1036024 /opt/omni/databases/vendor/oracle/hp/
		s800/hp-ux-10/A.03.10/packet.Z
	3934108962 25 /opt/omni/databases/vendor/oracle/hp/s800/
		hp-ux-1020/A.03.10/require.dat
	2166080169 1070404 /opt/omni/databases/vendor/oracle/hp/
		s800/hp-ux-1020/A.03.10/packet.Z
	944778055 1089643 /opt/omni/databases/vendor/oracle/ibm/
		rs6000/aix-42/A.03.10/packet.Z
	2454992579 17 /opt/omni/databases/vendor/oracle/ibm/rs6000/
		aix-42/A.03.10/require.dat
	3700481286 17 /opt/omni/databases/vendor/oracle/sun/sparc/
		solaris/A.03.10/require.dat
	3642095412 457537 /opt/omni/databases/vendor/oracle/sun/
		sparc/solaris/A.03.10/packet.Z
	124273184 471859 /opt/omni/databases/vendor/oracle/sun/
		sparc/solaris-26/A.03.10/packet.Z
	1968934076 19 /opt/omni/databases/vendor/oracle/sun/sparc/
		solaris-26/A.03.10/require.dat

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes: None

Equivalent Patches:
	PHSS_21659:
	s700: 11.00
	s800: 11.00

Patch Package Size: 4100 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_21658

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

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

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

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

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

	For distribution of the Oracle7 Agent, refer to the
	OmniBackII Installation guide.

	===========================================================
	NOTE!

	The patch introduces support for EBU 2.2 on AIX 4.2. There
	is no automatic client installation available. Instead, use
	the installation procedure described here.

	1. Prerequisite
	---------------
	  'Enterprise Backup Utility' (EBU) module must be
	  installed on the AIX 4.2 Oracle client as described in
	  the Oracle7 documenation. See the documentation
	  included in

	     $ORACLE_HOME/obackup/doc/ADMIN_HTML/


	2. Testing the EBU 2.2 backup functionality
	   with the Oracle7 built-in backup library
	--------------------------------------------
	Before using Omniback II integration to run backups,
	it is recommended to test backup first with the utility
	provided by Oracle. Oracle's utility can manage only
	backups to disk.

	Use the following procedure to test the EBU 2.2 backup:

	a) Go to $ORACLE_HOME/obackup/lib/ directory and check if
	  'libobk.a.DISK' file exist. If not, install (reinstall)
	  Oracle7 EBU module. Make a copy of file 'libobk.a.DISK'
	  into directory $ORACLE_HOME/obackup/lib and rename the
	  file to libobk.a.

	b) Run the following command in the
	   $ORACLE_HOME/obackup/lib/ directory

	   "make -f ins_obackup.mk ORACLE_HOME=/oracle7/ora734 \
	    install"

	   where '/oracle7/ora734' is the ORACLE_HOME directory.

	   Make sure that 'ORACLE_HOME/bin' directory is in $PATH.

	c) Go to the ORACLE_HOME/obackup/bin directory.
	   Create new file (EBU script) containing:

	        BACKUP ONLINE
	        PARALLEL = 3
	        TABLESPACE = "TEMP"
	        ARCHIVELOG = NONE

	   where "TEMP" is one of the tablespaces in the Target
	   database.

	d) Export the following environment variables:

	        export ORACLE_HOME=<ORACLE_HOME>
	        export EBU_HOME=<ORACLE_HOME>/obackup
	        export ORACLE_SID=<ORACLE_SID>
	        export BACKUP_DIR=/tmp

	e) Execute the command "ebu <script>". While backup is
	   running, trace the massages to make sure that there are
	   no errors.

	   This is the message that should appear at the beginning:

	        Tape API: Release 1.1
	        Tape Management Software: Release 9.9.9.9
	        Vendor API: DISK Api (Oracle internal only) \
	                    backing up to /tmp

	   This notifies you that Oracle7 uses its own library to
	   perform backup to disk.

	   If this test backup fails, OmniBack II integration with
	   Oracle7 EBU 2.2 will not function!


	3. Installing the Oracle7 Integration
	--------------------------------------
	Use the Omniback II user interface to install (push) the
	Disk Agent and Media Agent to Oracle7 client. It is
	recommended that the normal Omniback Disk Agent for
	filesystem backup is tested and confirmed to run
	on the Oracle7 client prior to configuring the Oracle7
	backup.

	Integration package is contained in the file packet.Z,
	located on the Installation Server system directory (with
	this patch installed):

	/opt/omni/databases/vendor/oracle/ibm/rs6000/aix-42/A.03.10

	Copy the packet.Z file to a temporary directory on the
	Oracle7 client, and uncompress it using the command
	'compress -d packet.Z'.

	Create a directory '/usr/omni' on the Oracle7 client, and
	copy uncompressed file (named packet) there.

	The file 'packet' now contains tar-ed AIX-42 binaries.
	Untar the file using the command 'tar xvf packet'. Make
	sure that you are in the directory /usr/omni before running
	the tar command.

	When you have finished installing Oracle7 integration
	package, the following directories and files should exist
	on the Oracle7 client system:

	 /usr/omni/lib/libobk.a
	 /usr/omni/bin/utilns/testbar
	 /usr/omni/bin/util_oracle.exe
	 /usr/omni/bin/obackup.sh
	 /usr/omni/bin/cat_e
	 /usr/omni/bin/ob2ebu.exe
	 /usr/omni/bin/ora_tool
	 /usr/omni/bin/cat_d
	 /usr/omni/bin/echo_d
	 /usr/omni/bin/echo_e
	 /usr/omni/bin/obkbackup
	 /usr/omni/bin/test_oracle_integration
	 /usr/omni/bin/obkrestore
	 /usr/omni/config/oracle/oracle.conf
	 /usr/omni/log/oracle.log

	 /usr/omni/config/oracle/bcs
	 /usr/omni/config/oracle/rcs
	 /usr/omni/config/oracle/ccs

	If the above directories /usr/omni/config/oracle/?cs/ were
	not created, make sure to create them before continuing
	with the configuration.

	Now, copy /usr/omni/lib/libobk.a into the directory
	ORACLE_HOME/obackup/lib/.

	Run the following command in the ORACLE_HOME/obackup/lib/
	directory:

	      "make -f ins_obackup.mk ORACLE_HOME=/oracle7/ora734 \
	       install"

	where '/oracle7/ora734' is the ORACLE_HOME directory.

	Make sure that 'ORACLE_HOME/bin' directory is in $PATH
	before executing the above command.

	3. Configuring Oracle7 Integration
	----------------------------------
	Before using GUI to perform configuration of Oracle7 client
	the /usr/omni/config/cell_info file must be edited and the
	Oracle7 client must be added. See the example below:

	Example (must be one line):
	 -host "hostname.domain.si" -os "ibm rs6000 aix-4.2" \
	 -cc A.03.10 -da A.03.10 -ma A.03.10  -oracle A.03.10


	Now start the OmniBack II GUI, and start configuring the
	Oracle7 backup specification. See the 'HP OpenView OmniBack
	II UNIX Integration Guide' to perform Oracle7 configuration.

	============================================================


	NOTE!
	Patch includes the following Site Specific Patches:
	    SSPUX310_007
	    SSPUX310_023