Patch Name: PHSS_31045

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

Creation Date: 05/01/10

Post Date: 05/01/12

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

Products:
	OmniBackII A.04.10

Filesets:
	OMNIBACK-II.OMNI-DOCS,A.04.10

Automatic Reboot?: No

Status: General Release

Critical:
	Yes
	PHSS_31045: CORRUPTION

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

Symptoms:
	PHSS_31045:
	Change Request: QXCR1000197810
	  Error message is displayed during the automatic
	  configuration of Lotus Notes server using the GUI
	  wizard. Configuration from GUI is impossible.

	Change Request: QXCR1000206849
	  If the "MAXPIECESIZE" RMAN parameter is used during
	  Oracle integration backup, restore fails with corrupt
	  data although backup completed successfully without
	  errors.

	Change Request: QXCR1000212020
	  Backup/restore session is executed even if the command/
	  script set by the "Split pre-exec" EMC Symmetrix option
	  is not executed.

	Change Request: 8606291446
	  Information about user permissions required for SQL
	  Integration restore are missing in the documentation.

	Change Request: 8606292792
	  In HP OpenView OmniBack II EMC Symmetrix/Fastrax
	  Integration Guide, the name of the SPLIT_EXE command for
	  the EMC Integration with Oracle8 is documented
	  incorrectly.

	Change Request: 8606300570
	  Undocumented information about "LUN 0" in the SureStore
	  Virtual Array Integration Guide.

	Change Request: 8606358088
	  References to "filesperset" backup command operand
	  needing to be set to 1 have to be removed from the
	  Windows and UNIX Integration Guides.

	Change Request: 8606359728
	  Incorrect filename for the "libob2oracle8_64bit.so"
	  library is stated in the UNIX Integration Guide.

	Change Request: H555009725
	  When you try to limit the number of devices used in one
	  session by specifying the "MaxMAperSM" global variable
	  in the global options file, limitation is not working
	  (larger number of devices is used anyway).

	Change Request: H555009892
	  A scheduling limitation is not described in
	  Administrator's Guide.

	Change Request: H555009982
	  There is ambiguous information in Administrator's Guide.

	Change Request: H555010278
	  MSSQL 2000 backup session report displays the following
	  error message:

	   "|Warning| From: OB2BAR@<hostname> <object> Time: <time>
	    Error has occurred while executing a SQL statement.
	    Error message: '<Microsoft SQL-DMO (ODBC SQLState:
	    42000)?15  |152:5| bcf|Microsoft||ODBC SQL Server
	    Driver||SQL Server|Backup and file manipulation
	    operations (such as ALTER DATABASE ADD FILE) on a
	    database must be serialized. Reissue the statement
	    after the current backup or file manipulation
	    operation is completed. |Microsoft||ODBC SQL
	    Server Driver||SQL Server|BACKUP LOG is terminating
	    abnormally."

	Change Request: H555010584
	  Incorrect information in UNIX Integration guide,
	  "Integrating Informix and OmniBack II chapter",
	  section "Configuring the Integration as Cluster-Aware",
	  subsection "Installation and Configuration".

	Change Request: H555011080
	  Error in the path of the "man" directory for the MANPATH
	  variable.

	Change Request: H555011093
	  Locations of pre- and post-exec scripts have to be
	  specified more precisely.

	Change Request: H555011098
	  A note in Administrator's guide about the ACS Library is
	  not applicable anymore.

	Change Request: H555011257
	  Limitation about volsers scan is missing
	  in documentation.

	Change Request: H555011342
	  Description of the Oracle Recovery Manager (RMAN)
	  command "delete expired backup" is missing from the UNIX
	  Integration Guide.

	Change Request: H555011462
	  References to Oracle8.x and Oracle8.0 in user guides
	  have to be changed to Oracle8.

	Change Request: H555012157
	  Incorrect information regarding load balancing
	  in Online help and user guides.

	Change Request: H555012319
	  Some errors have been found in the UNIX and Windows
	  Integration Guides, Integrating Oracle8/9 and OmniBack
	  II chapter -> Example of Oracle8/9 Database Restore.

	Change Request: H555012427
	  Users without the "restore as root" user right set are
	  able to restore (overwrite) the data that they
	  otherwise do not have permission to.

	Change Request: H555013536
	  Reporting on backup specifications usage -> objects
	  without backup does not apply for the backup
	  specifications for integrations.

	PHSS_26359:
	Change Request: H555006891
	  Importing clients with reserved keywords in their
	  hostnames fails.

	Change Request: H555006913
	  Wrong path to the "ovpause.lock" file
	  in the UNIX Integration Guide.

	Change Request: H555007271
	  The information on how to upgrade OmniBack II A.03.x
	  Cell Manager to A.04.10 on Microsoft Cluster Server
	  (MSCS) is needed.

	Change Request: 8606221492
	  Pre-exec and post-exec scripts are deleted from
	  <OmniBack_home>\bin directory during the upgrade
	  of OmniBack II A.03.x version to A.04.x version.

	Change Request: 8606227829
	  Wrong pathname is specified for the "detach" utility
	  in the Administrator's Guide.

	Change Request: 8606232193
	  OmniBack II EMC integration does not support two BCVs
	  (Business Continuance Volumes) attached to a backup
	  host.

	Change Request: 8606233576
	  The "#" sign cannot be used in the RMAN script
	  in the Oracle8 backup specification.

	Change Request: B555012727
	  Incorrect VA LUN conversion in the SureStore VA
	  Integration Guide.

	Change Request: B555012924
	  EMC Symmetrix/Fastrax Integration Guide contains
	  a mistake.

	Change Request: B555012982
	  Errors in the UNIX and Windows Integration Guides.

	Change Request: B555013441
	  Wrong filesystem limitation
	  in the Administrator's Guide.

	Change Request: H555010116
	  More information is needed regarding the two values
	  of the SMEXIT variable.

	Change Request: H555010145
	  Administrator's and Concepts Guides contain
	  incorrect information.

	Change Request: H555010232
	  The following error message is reported during
	  a SAP integration backup:

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

	Change Request: 8606262291
	  Error message after the upgrade of OmniBack II A.03.x
	  version to A.04.x version:

	  12:8334" No semicolon after rman command".

Defect Description:
	PHSS_31045:
	Change Request: QXCR1000197810
	  Data Protector searches for all clients in the cell
	  with Lotus Notes integration installed and if any of
	  them is not configured properly, the error message is
	  displayed and automatic Lotus Notes integration
	  configuration from GUI fails.

	  Resolution:
	  The following text has been added to the UNIX
	  Integration guide /
	  Integrating Lotus Domino R5 Server and Data Protector /
	  Troubleshooting / Configuration Problems:

	  5.) Make sure there are no misconfigured Lotus Notes
	  servers in your cell (for example, if the paths are not
	  set or not set correctly) otherwise the following
	  error message will be displayed for each misconfigured
	  client in your cell: No Domino Server found on the
	  system or path is not set correctly. If you receive
	  this error message, configure the problematic clients
	  properly or remove them from the cell.

	Change Request: QXCR1000206849
	  Restore of multiple backup pieces created during a
	  backup is not possible using the Omniback Oracle
	  integration.

	  Resolution:
	  A limitation has been added to UNIX and Windows
	  Integration guides.

	Change Request: QXCR1000212020
	  This is the design of Data Protector and not a bug, but
	  the documentation does not mention what happens if the
	  "Split pre-exec" is not executed.

	  Resolution:
	  The documentation has been enhanced: Backup/restore
	  session is not aborted if the command set by the "Split
	  pre-exec" option is not executed.

	Change Request: 8606291446
	  Information about user permissions required for SQL
	  Integration restore are wanting.

	  Resolution:
	  Information about user permissions required for SQL
	  Integration restore are added to the Integration guide.

	Change Request: 8606292792
	  The documentation refers to a non-existing file
	  "/opt/omni/lbin/ob2smboracle8_split". The correct file
	  name is "ob2smbsplit".

	  Resolution:
	  The documentation is corrected.

	Change Request: 8606300570
	  Information about configuration and proper use of LUN 0
	  is not documented.

	  Resolution:
	  The following information is added into SureStore
	  Virtual Array Integration Guide:

	   "Limit the size of LUN 0 to 10 MB and do not use it for
	  storing data, as LUN 0 is used as a command device and
	  is accessed by all hosts connected to the disk array."

	Change Request: 8606358088
	  References to "filesperset" backup command operand
	  needing to be set to 1 have to be removed from the
	  Windows and UNIX Integration Guides.

	  Resolution:
	  References to "filesperset" backup command operand
	  needing to be set to 1 are removed from the Windows and
	  UNIX Integration Guides.

	Change Request: 8606359728
	  It should read "libob2oracle8_64bit.so" instead of
	  "libob2oracle8_64.so".

	  Resolution:
	  Filename is corrected in the UNIX Integration Guide.

	Change Request: H555009725
	  Global variable "MaxMAperSM" is not handled correctly.

	  Resolution:
	  When the "MaxMAperSM" global variable is less then
	  maximum number of devices specified in the backup
	  specification (load balancing), the "MaxMAperSM" value
	  is used.

	Change Request: H555009892
	  The limitation regarding weekly periodic backups is not
	  stated in the Administrator's Guide.

	  Resolution:
	  The limitation regarding weekly periodic backups is
	  added into the Administrator's Guide, Chapter 5; section
	  "Scheduling Unattended Backups":

	  "Weekly periodic backups can be configured only if time
	  between two reoccurring backups is at most four weeks."

	Change Request: H555009982
	  The information about creating a consistent and relevant
	  backup in Administrator's Guide, "Chapter 10: Disaster
	  Recovery", section "Preparing for a Disaster Recovery"
	  is not clear enough.

	  Resolution:
	  The information about creating a consistent and relevant
	  backup is clarified.

	Change Request: H555010278
	  Log file(s) truncation process should not be started
	  manually. It is an automatic process which is started
	  after each transactional backup by an SQL server.

	  Resolution:
	  SQL ignores such options if they are already written to
	  the backup specification. OmniBack II disables/removes
	  those options from the graphical user interface (GUI) in
	  a way that those options could not be written to the
	  backup specification anymore.

	Change Request: H555010584
	  The following paragraph is incorrect:"Append the
	  following file to the same file on the same position on
	  all other nodes: /etc/opt/omni/informix/SERVERLIST".

	  Resolution:
	  Incorrect paragraph is removed.

	Change Request: H555011080
	  The path of the "man" directory for the MANPATH variable
	  is wrong in the Installation and UNIX Integration Guides.

	  Resolution:
	  Error is corrected.

	Change Request: H555011093
	  Locations of pre- and post-exec scripts have to be
	  specified more precisely.

	  Resolution:
	  Locations of pre- and post-exec scripts are specified
	  more precisely.

	Change Request: H555011098
	  Note about the ACS Library is not applicable anymore and
	  should be removed from the Administrator's guide.

	  Resolution:
	  The note is removed from the Administrator's guide.

	Change Request: H555011257
	  Volsers scan may not complete successfully if the
	  ADIC/GRAU library is configured with more than 3970
	  volsers in a repository.

	  Resolution:
	  The following limitation is added to the Administrator's
	  Guide:

	   "Volsers scan may not complete successfully if the
	    ADIC/GRAU library is configured with more than 3970
	    volsers in a repository. A workaround for this problem
	    is to configure multiple logical ADIC/GRAU libraries
	    in order to separate the slots from the large
	    repository into several smaller repositories."

	Change Request: H555011342
	  RMAN command "delete expired backup" removes all expired
	  backup objects from the recovery catalog database.

	  Resolution:
	  Description of the "Delete expired backup" command is
	  added to the UNIX Integration Guide.

	Change Request: H555011462
	  References to Oracle8.x and Oracle8.0 in user guides
	  have to be changed to Oracle8.

	  Resolution:
	  References to Oracle8.x and Oracle8.0 are changed to
	  Oracle8 in the UNIX Integration Guide, HP SureStore Disk
	  Array XP Integration Guide and HP SureStore Virtual
	  Array Integration Guide.

	Change Request: H555012157
	  Incorrect information about the role
	  of an object size in load balancing.

	  Resolution:
	  Correct information is given regarding the role
	  of an object size in load balancing.

	Change Request: H555012319
	  Some errors have been found in the UNIX and Windows
	  Integration Guides, Integrating Oracle8/9 and OmniBack
	  II chapter -> Example of Oracle8/9 Database Restore.

	  Resolution:
	  Errors have been corrected in the UNIX and Windows
	  Integration Guides, Integrating Oracle8/9 and OmniBack
	  II chapter -> Example of Oracle8/9 Database Restore.

	Change Request: H555012427
	  All OmniBack II processes started by the "OmniInet"
	  and run under its account have its permissions. When
	  the data is being restored, the operating system does
	  not control whose data is being restored/overwritten
	  and whether the user performing the restore has
	  sufficient permissions to overwrite the data on the
	  destination.

	  Resolution:
	  "Restore to new location", "Keep most recent" and
	  "Overwrite" options are disabled for users that do not
	  have "Restore as root" user right set. This is
	  described in the Administrator's Guide -> Configuring
	  Users and User Groups -> Data Protector User Rights ->
	  Restore as root and Online Help.

	Change Request: H555013536
	  Reporting on backup specifications usage -> objects
	  without backup does not apply for the backup
	  specifications for integrations.

	  Resolution:
	  A note is written in the Administrator's Guide and
	  Online Help stating that reporting on objects without
	  backup does not apply for the backup specifications for
	  integrations.

	PHSS_26359:
	Change Request: H555006891
	  OmniBack II does not work with clients that have
	  "reserved" keywords in their hostnames (e.g. oracle,
	  exchange, etc.).

	  Resolution:
	  Hostname limitations are added to Release Notes.

	Change Request: H555006913
	  Incorrect path to the "ovpause.lock" file is stated
	  for the NNM integration in the UNIX Integration Guide.

	  Resolution:
	  The path to the "ovpause.lock" file is corrected.

	Change Request: H555007271
	  The procedure for upgrading OmniBack II A.03.x Cell
	  Manager to A.04.10 on Microsoft Cluster Server (MSCS)
	  is missing.

	  Resolution:
	  The procedure for upgrading OmniBack II A.03.x Cell
	  Manager to A.04.10 on Microsoft Cluster Server (MSCS)
	  is documented.

	Change Request: 8606221492
	  All files located in the <OmniBack_home>\bin directory
	  are removed during the upgrade from OmniBack II A.03.x
	  version to A.04.10.

	  Resolution:
	  The following important note is added
	  to the Installation and Licensing Guide
	  under Upgrading the Windows Cell Manager
	  and Installation Server section:

	  During the upgrade from OmniBack II A.03.x release,
	  all files in the <OmniBack_home>\bin directory are
	  removed, including non-OmniBack II or customized files,
	  such as Pre-exec and Post-exec scripts.
	  It is recommended that you copy all these files
	  to a different location before you start the upgrade.

	Change Request: 8606227829
	  On page 221 of OmniBack II A.04.10 Administrator's
	  Guide there is an incorrect pathname specified for
	  the "detach" utility:
	  /opt/omni/bin/utilns/detach

	  However, it should read:
	  /opt/omni/lbin/utilns/detach

	  Resolution:
	  The pathname specified for the "detach" utility is
	  corrected.

	Change Request: 8606232193
	  Configuration of two BCVs attached to a backup host
	  is not supported and this limitation is not documented.

	  Resolution:
	  EMC/Fastrax Integration Guide documents mentioned
	  limitation.

	Change Request: 8606233576
	  The important note that the "#" sign must not be used
	  in the RMAN script in the Oracle8 backup specification
	  is missing.

	  Resolution:
	  The important note that the "#" sign must not be used
	  in the RMAN script in the Oracle8 backup specification
	  is added to the UNIX and Windows Integration Guides,
	  chapter Integrating Oracle8/9 and OmniBack II.

	Change Request: B555012727
	  The conversion formula from HP-UX device file to VA LUN
	  number on pages 28 and 35 is incorrect.

	  Resolution:
	  The conversion formula from HP-UX device file to VA LUN
	  number on pages 28 and 35 is corrected.

	Change Request: B555012924
	  There is a mistake in the example for the Oracle8
	  database offline backup in the EMC Symetrix/Fastrax
	  Guide.

	  Resolution:
	  The example for the Oracle8 database offline backup
	  in the EMC Symetrix/Fastrax Guide is corrected.

	Change Request: B555012982
	  There are some errors found in the Example of Oracle8/9
	  Database Restore section in the Integrating Oracle8/9
	  and OmniBack II chapter of the UNIX and Windows
	  Integration Guides.

	  Resolution:
	  Errors in the Example of Oracle8/9 Database Restore
	  section in the Integrating Oracle8/9 and OmniBack II
	  chapter of the UNIX and Windows Integration Guides
	  are fixed.

	Change Request: B555013441
	  There is a wrong filesystem limitation
	  in the Administrator's Guide.

	  Resolution:
	  The filesystem limitation in the Administrator's Guide
	  is corrected.

	Change Request: H555010116
	  Values 12 and 13 of the SMEXIT variable need further
	  explanation.

	  Resolution:
	  Values 12 and 13 of the SMEXIT variable are explained
	  in greater detail.

	Change Request: H555010145
	  There is incorrect information regarding Cartridge
	  Memory in the Administrator's and Concepts Guides.

	  Resolution:
	  The information regarding Cartridge Memory is
	  corrected in the Administrator's and Concepts Guides.

	Change Request: H555010232
	  Note in the UNIX and Windows Integration Guides states
	  that OmniBack II supports all options of SAP brtools
	  that are also supported through backint which is not
	  correct.

	  Resolution:
	  Note in the UNIX and Windows Integration Guides
	  excludes -a and-b options as supported ones.

	Change Request: 8606262291
	  There are an undocumented limitations when editing
	  RMAN script in the GUI.

	  Resolution:
	  Limitations regarding editing RMAN script in the GUI
	  are documented.

SR:
	QXCR1000212020 8606359728 H555011080 H555011342
	H555011093 8606291446 H555011257 H555012319
	H555012157 H555010278 H555009725 H555011462
	H555011098 QXCR1000197810 H555012427 QXCR1000206849
	H555010584 8606358088 H555013536 H555009892
	8606292792 H555009982 8606300570 H555006913
	B555013441 B555012982 8606227829 H555010116
	H555007271 B555012727 8606221492 8606233576
	8606262291 H555010232 H555006891 8606232193
	B555012924 H555010145

Patch Files:
	/opt/omni/doc/C/Admin.pdf
	/opt/omni/doc/C/Concepts.pdf
	/opt/omni/doc/C/Emc.pdf
	/opt/omni/doc/C/Installation.pdf
	/opt/omni/doc/C/IntegrationNT.pdf
	/opt/omni/doc/C/IntegrationUX.pdf
	/opt/omni/doc/C/VirtualArray.pdf
	/opt/omni/doc/C/ReleaseNotes.pdf
	/opt/omni/doc/C/SureStore.pdf

what(1) Output:
	/opt/omni/doc/C/Admin.pdf:
		None
	/opt/omni/doc/C/Concepts.pdf:
		None
	/opt/omni/doc/C/Emc.pdf:
		None
	/opt/omni/doc/C/Installation.pdf:
		None
	/opt/omni/doc/C/IntegrationNT.pdf:
		None
	/opt/omni/doc/C/IntegrationUX.pdf:
		None
	/opt/omni/doc/C/VirtualArray.pdf:
		None
	/opt/omni/doc/C/ReleaseNotes.pdf:
		None
	/opt/omni/doc/C/SureStore.pdf:
		None

cksum(1) Output:
	415268127 9659235 /opt/omni/doc/C/Admin.pdf
	3171624764 6121557 /opt/omni/doc/C/Concepts.pdf
	3850122560 4529281 /opt/omni/doc/C/Emc.pdf
	1120861043 4264506 /opt/omni/doc/C/Installation.pdf
	1615727616 8947464 /opt/omni/doc/C/IntegrationNT.pdf
	453851941 7238884 /opt/omni/doc/C/IntegrationUX.pdf
	4271933604 2531444 /opt/omni/doc/C/VirtualArray.pdf
	3405443831 513217 /opt/omni/doc/C/ReleaseNotes.pdf
	3360411302 4510113 /opt/omni/doc/C/SureStore.pdf

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_26359

Equivalent Patches:
	PHSS_31046:
	s700: 11.00 11.11
	s800: 11.00 11.11

Patch Package Size: 27060 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_31045

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

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

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

Special Installation Instructions:
	PHSS_31045:
	NOTE!

	This patch can be installed locally only on systems
	where the documentation packet has been previously
	installed. Typically this is Cell Server or
	Installation Server system.
	It is not possible to remotely distribute patched
	files from this patch.

	
	Patch includes no Site Specific Patches.

	
	A Site Specific Patch is a temporary hotfix that
	you might have received from HP Support if you
	have encountered a problem with OmniBack II
	for which no General Release patch was or is
	available yet.

	If any newer Site Specific Patch - that is
	one with a higher number - for the Documentation
	is installed on your system, then you
	must re-apply this SSP after installing
	this Documentation patch.