Patch Name: PHSS_30331

Patch Description: s700_800 11.X OV DP5.00 patch - DOC packet

Creation Date: 04/04/28

Post Date: 04/05/04

Hardware Platforms - OS Releases:
	s700: 11.00 11.11
	s800: 11.00 11.11

Products:
	DATA-PROTECTOR A.05.00

Filesets:
	DATA-PROTECTOR.OMNI-DOCS,fr=A.05.00,fa=HP-UX_B.11.00_32/64,v=HP

Automatic Reboot?: No

Status: General Release

Critical: No

Category Tags:
	defect_repair general_release manual_dependencies

Path Name: /hp-ux_patches/s700_800/11.X/PHSS_30331

Symptoms:
	PHSS_30331:
	Change Request: 8606331369
	  Proxy copy backup of an Oracle database with a large
	  number of files can fail due to the maximum number of
	  connections reached. Restore of the proxy copy backup is
	  slow.

	Change Request: H555010495
	  DRTape devices behave exactly the same way as OBDR
	  devices. This has to be reflected in documentation.

	Change Request: H555010792
	  Oracle8i/9i databases cannot be recovered beyond the last
	  backup time (i.e. until now) after instant recovery.
	  Online logs and control files have to be removed
	  from the list of data files and control files
	  of the Production Database in order to avoid resolving
	  of the mirror disks with these files.

	Change Request: H555010793
	  SAP R/3 databases cannot be recovered beyond the last
	  backup time (i.e. until now) after instant recovery.
	  Online logs and control files have to be removed from
	  the list of data files and control files of the
	  Production Database in order to avoid resolving of the
	  mirror disks with these files.

	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 Data
	  Protector 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: H555012746
	  Non-Data Protector problem is not described in Release
	  Notes.

	PHSS_29154:
	Change Request: H555009617
	  There are some errors in Release Notes
	  and Administrator's Guide.

	Change Request: H555009725
	  Insufficient information regarding the "MaxMAperSM"
	  global options variable in the Administrator's Guide
	  and Release Notes.

	Change Request: H555009892
	  Scheduling limitation is not described
	  in the Administrator's Guide.

	Change Request: H555009906
	  Requirements for the Automatic Disaster Recovery
	  are incorrect in the Administrator's Guide.

	Change Request: H555009982
	  There is an ambiguous information
	  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: H555010278
	  MS SQL 2000 backup session report displays a warning
	  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: H555010491
	  There are incorrect limitations in the section
	  3.5.2 of the Release Notes regarding the multiple
	  BC mirrors and Instant recovery.

	Change Request: H555010584
	  Incorrect information in the UNIX Integration Guide,
	  Integrating Informix and Data Protector chapter,
	  section Configuring the Integration as Cluster-Aware,
	  subsection Installation and Configuration.

	Change Request: H555011022
	  Error in the Administrator's Guide and Online Help.

	Change Request: H555011072
	  Mirror/snapshot disk locking mechanism requires
	  a more detailed explanation.

	Change Request: H555011080
	  Error in the path for 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
	  Note in the Administrator's Guide about
	  the ACS Library is not applicable anymore.

	Change Request: 8606291446
	  There is missing information about user permissions
	  required for the SQL Integration restore.

	Change Request: 8606292792
	  Error in the EMC Symmetrix/Fastrax Integration Guide
	  and HP SureStore Disk Array XP Integration Guide.

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

	Change Request: 8606331415
	  More detailed instructions are needed regarding
	  the use of correct templates when doing split
	  mirror/snapshot backup of an Oracle8/8i/9i database.

Defect Description:
	PHSS_30331:
	Change Request: 8606331369
	  Backup agent starts agents for all files at once.
	  Restore of files is performed serially.

	  Resolution:
	  Oracle integration concept is changed extensively.
	  Proxy copy backup and restore performance is enhanced.

	  For more detailed information about changes in the
	  backup concept and backup flow, refer to the Oracle8i/9i
	  chapters of the following disk array guides:

	  -HP OpenView Storage Data Protector HP SureStore Disk
	  Array XP Integration Guide

	  -HP OpenView Storage Data Protector HP SureStore Virtual
	  Array Integration Guide

	  -HP OpenView Storage Data Protector EMC Symmetrix/Fastrax
	  Integration Guide.

	  For more detailed information on changes in the backup
	  specifications, refer to the Oracle chapters of the HP
	  OpenView Storage Data Protector UNIX Integration Guide.

	  Updated versions of these guides are available with the
	  Cell Console (CC) patch DPWIN_00050 and Documentation
	  (DOC) patches PHSS_30331 and DPSOL_00069 or subsequent
	  CC and DOC patches.

	Change Request: H555010495
	  DRTape devices behave exactly as OBDR devices.
	  This has to be reflected in the documentation.

	  Resolution:
	  The following note is added to the Online Help and
	  Administrator's Guide, Disaster Recovery chapter:

	   "OBDR devices include also DRTape devices."

	Change Request: H555010792
	  During an Oracle8i/9i ZDB backup, only replicas
	  of the database data files should be created.

	  Resolution:
	  Oracle8i/9i databases can be recovered after
	  instant recovery. New environment variable
	  ZDB_ORA_INCLUDE_CF_OLF=(0|1) is introduced in the
	  "omnirc" file. When this variable is not present in the
	  environment or it is set to 0, only database data
	  files are resolved/split. In this case, the control
	  files and redo logs can reside on local disks.
	  If set to 1, control files and online redo logs are
	  also resolved/split. Value 1 is to be used only if the
	  user needs to start the database instance on the backup
	  host for other purposes then backup. In both cases,
	  the control files and online redo logs should not
	  reside on the same disks/logical volumes as database
	  data files. If ZDB_ORA_INCLUDE_CF_OLF=1 option is to be
	  used, then control files and online redo logs must also
	  reside on original units (mirrored disks).

	  Prerequisites:
	  If instant recovery is to be performed, the control
	  files and the online redo logs must not reside
	  on the same original units as the data files.
	  IMPORTANT: If the above rule is not followed, data loss
	  may occur (e.g. older version of the redo logs
	  and the control files will overwrite the current
	  versions of these files).

	  For more information, please refer to the:

	  HP OpenView Storage Data Protector HP SureStore Virtual
	  Array Integration Guide, chapter 6 (Integrating Data
	  Protector, HP SureStore Virtual Array and
	  Oracle8/8i/9i) and Appendix.

	  HP OpenView Storage Data Protector HP SureStore Disk
	  Array XP Integration Guide, chapter 5 (Integrating
	  Data Protector, HP SureStore Disk Array XP, and
	  Oracle8/8i/9i) and Appendix.

	  Updated versions of these guides are available with
	  the Cell Console (CC) patch DPWIN_00050, the
	  Documentation (DOC) patch PHSS_30331, and the
	  Documentation (DOC) patch DPSOL_00069 or subsequent
	  CC and DOC patches.

	Change Request: H555010793
	  During a SAP R/3 ZDB backup, only replicas
	  of the database data files should be created.

	  Resolution:
	  SAP R/3 databases can be recovered after
	  instant recovery. New environment variable
	  ZDB_ORA_INCLUDE_CF_OLF=(0|1) is introduced in the
	  "omnirc" file. When this variable is not present in the
	  environment or it is set to 0, only database data
	  files are resolved/split. In this case, the control
	  files and redo logs can reside on local disks.
	  If set to 1, control files and online redo logs are
	  also resolved/split. Value 1 is to be used only if the
	  user needs to start the database instance on the backup
	  host for other purposes then backup. In both cases,
	  the control files and online redo logs should not
	  reside on the same disks/logical volumes as database
	  data files. If ZDB_ORA_INCLUDE_CF_OLF=1 option is to be
	  used, then control files and online redo logs must also
	  reside on original units (mirrored disks).

	  Prerequisites:
	  If instant recovery is to be performed, the control
	  files and the online redo logs must not reside
	  on the same original units as the data files.
	  IMPORTANT: If the above rule is not followed, data loss
	  may occur (e.g. older version of the redo logs
	  and the control files will overwrite the current
	  versions of these files).

	  For more information, please refer to the:

	  HP OpenView Storage Data Protector HP SureStore Virtual
	  Array Integration Guide, chapter 7 (Integrating Data
	  Protector, HP SureStore Virtual Array and SAP R/3) and
	  Appendix.

	  HP OpenView Storage Data Protector HP SureStore Disk
	  Array XP Integration Guide, chapter 6 (Integrating Data
	  Protector, HP SureStore Disk Array XP, and SAP R/3) and
	  Appendix.

	  Updated versions of these guides are available with
	  the Cell Console (CC) patch DPWIN_00050, the
	  Documentation (DOC) patch PHSS_30331, and the
	  Documentation (DOC) patch DPSOL_00069 or subsequent
	  CC and DOC patches.

	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.

	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 Data
	  Protector chapter -> Example of Oracle8/9 Database
	  Restore.

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

	Change Request: H555012427
	  All Data Protector 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: H555012746
	  The problem about the short filenames that are not
	  retained after a tape restore is missing.

	  Resolution:
	  The problem and workaround are described in Release
	  Notes -> Known Problems and Workarounds -> Known
	  Non-Data Protector Problems and Workarounds.

	PHSS_29154:
	Change Request: H555009617
	  "Ob2TapeStatistics" is the global variable and not
	  the omnirc variable. Also, three error statistics are
	  missing from the table in the Medium Quality Statistics
	  section of the Administrator's Guide.

	  Resolution:
	  Errors are corrected.

	Change Request: H555009725
	  Insufficient information regarding the "MaxMAperSM"
	  global options variable in the Adminstrator's Guide
	  and Release Notes.

	  Resolution:
	  Complemented the definition of the "MaxMAperSM"
	  variable in the Administrator's Guide and Release
	  Notes.

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

	  Resolution:
	  Limitation regarding weekly periodic backups
	  is stated in the Administrator's Guide.

	Change Request: H555009906
	  The Automatic Disaster Recovery component does not have
	  to be installed on the Cell Manager as stated in the
	  Administrator's Guide. Automatic Disaster Recovery
	  component must be installed on the host, no matter
	  if it is the Cell Manager or the client, which will be
	  included in the EADR procedure.

	  Resolution:
	  Requirements are corrected
	  in the Administrator's Guide.

	Change Request: H555009982
	  The information about creating a consistent and
	  relevant backup in the 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: 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 Data Protector supports all options of the SAP
	  brtools that are also supported through backint which
	  is incorrect.

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

	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:
	  The description of "Remove inactive entries from
	  transaction log" set of options is removed from the
	  Windows Integration Guide, chapter Integrating MS SQL
	  server 7.0/2000 and Data Protector, section Configuring
	  the Integration. The description is also removed from
	  the Online Help, F1 Help: Object Properties - MS SQL
	  Object.

	Change Request: H555010491
	  Limitations do not exist in the Data Protector 5.0
	  version anymore.

	  Resolution:
	  Limitations are removed from the Release Notes.

	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: H555011022
	  There is an error in the Customizing the Data Protector
	  Environment chapter, section Firewall Support,
	  subsection Examples of Configuring Data Protector
	  in Firewall Environments, Example 4.

	  Resolution:
	  Bulleted sentence "This setup does not allow backup of
	  databases or applications using Application Agents on
	  the clients in the DMZ." is removed from example 4.

	Change Request: H555011072
	  Unlocking mirror/snapshot disks with the omnidbutil
	  command is not described in man pages and guides.

	  Resolution:
	  Two new command-line arguments for the free_locked_devs
	  option of the omnidbutil command are introduced.
	  They are used for unlocking mirror/snapshot disks.
	  The omnidbutil man page and guides are updated
	  accordingly.

	Change Request: H555011080
	  Error in the path for the "man" directory for
	  the MANPATH variable 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.

	Change Request: 8606291446
	  There is missing information about user permissions
	  required for the SQL Integration restore.

	  Resolution:
	  Added the following text to the Windows Integration
	  Guide, chapter 4, page 258:

	   "Make sure that the Data Protector user to be used
	   in the restore session has sufficient permissions
	   granted on the SQL server. Sufficient permissions are
	   the restore permissions default to members of the
	   sysadmin and dbcreator fixed server roles and the
	   owner (dbo) of the database. Fixed database role
	   membership is always checked when restore is
	   performed. When database is damaged or inaccessible,
	   fixed database role membership cannot be checked. In
	   that case, members of the db_owner fixed database role
	   do not have sufficient permissions for restore. Data
	   Protector Inet service must be configured to run under
	   above mentioned user account."

	Change Request: 8606292792
	  Incorrect filename for the "ob2smbsplit" binary
	  is written. "ob2smboracle8_split" binary is incorrect.
	  Correct is "ob2smbsplit".

	  Resolution:
	  Correct filename is written.

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

	  Resolution:
	  The following information was added to the 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 a disk
	   array."

	Change Request: 8606331415
	  More detailed instructions are needed regarding
	  the use of correct templates when doing split
	  mirror/snapshot backup of an Oracle8/8i/9i database.

	  Resolution:
	  More detailed instructions are given regarding the use
	  of correct templates when doing split mirror/snapshot
	  backup of an Oracle8/8i/9i database.

Enhancement:
	No

SR:
	H555012746 H555011257 H555010495 H555012319 H555012157
	8606331369 H555011462 H555012427 H555011342 H555010792
	H555010793 H555011080 H555011072 H555011093 8606291446
	H555009617 8606331415 H555010278 H555009725 H555011098
	H555010491 H555009906 H555010584 H555011022 H555010116
	H555009892 H555009982 8606292792 H555010232 H555010145
	8606300570

Patch Files:
	
	DATA-PROTECTOR.OMNI-DOCS,fr=A.05.00,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/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/ReleaseNotes.pdf
	/opt/omni/doc/C/SureStore.pdf
	/opt/omni/doc/C/VirtualArray.pdf

what(1) Output:
	
	DATA-PROTECTOR.OMNI-DOCS,fr=A.05.00,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/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/ReleaseNotes.pdf:
		None
	/opt/omni/doc/C/SureStore.pdf:
		None
	/opt/omni/doc/C/VirtualArray.pdf:
		None

cksum(1) Output:
	
	DATA-PROTECTOR.OMNI-DOCS,fr=A.05.00,fa=HP-UX_B.11.00_32/64,
		v=HP:
	1463073668 9314870 /opt/omni/doc/C/Admin.pdf
	1716301929 6657213 /opt/omni/doc/C/Concepts.pdf
	4049022024 5596801 /opt/omni/doc/C/Emc.pdf
	1406828965 4491170 /opt/omni/doc/C/Installation.pdf
	3104240549 9126271 /opt/omni/doc/C/IntegrationNT.pdf
	3639799240 7205325 /opt/omni/doc/C/IntegrationUX.pdf
	2859155753 1135883 /opt/omni/doc/C/ReleaseNotes.pdf
	1670130311 5514328 /opt/omni/doc/C/SureStore.pdf
	4076206541 3980360 /opt/omni/doc/C/VirtualArray.pdf

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies:
	Some of the defect fixes contained in this patch
	depend on the following other patches or their
	successors in order to completely resolve the problem:

	PHSS_30338:
	Cell Console (CC) packet patch,
	release date: Late April 2004
	Change Request: 8606331369
	Change Request: H555010495
	Change Request: H555012157
	Change Request: H555012427
	PHSS_30338 is required for these defect fixes.

	PHSS_30341:
	Core packet patch,
	release date: Late April 2004
	Change Request: 8606331369
	Change Request: H555010792
	Change Request: H555010793
	PHSS_30341 is required for these defect fixes.
	Change Request: H555010495
	Bad catalog access message is displayed without PHSS_30341.

	PHSS_30337:
	Cell Server (CS) packet patch,
	release date: Late April 2004
	Change Request: 8606331369
	PHSS_30337 is required for this defect fix.

	PHSS_30333:
	Oracle8 packet patch,
	release date: Late April 2004
	Change Request: 8606331369
	Change Request: H555010792
	PHSS_30333 is required for these defect fixes.

	PHSS_30332:
	SAP packet patch,
	release date: Available
	Change Request: H555010793
	PHSS_30332 is required for this defect fix.

Supersedes:
	PHSS_29154 

Equivalent Patches: None

Patch Package Size: 30510 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_30331

	5. Run swinstall to install the patch:

		swinstall -x autoreboot=true -x patch_match_target=true \
			  -s /tmp/PHSS_30331.depot

	By default swinstall will archive the original software in 
	/var/adm/sw/save/PHSS_30331.  If you do not wish to retain a
	copy of the original software, include the patch_save_files
	option in the swinstall command above:

		-x patch_save_files=false

	WARNING: If patch_save_files is false when a patch is installed,
		 the patch cannot be deinstalled.  Please be careful
		 when using this feature.

	For future reference, the contents of the PHSS_30331.text file is 
	available in the product readme:

		swlist -l product -a readme -d @ /tmp/PHSS_30331.depot

	To put this patch on a magnetic tape and install from the
	tape drive, use the command:

		dd if=/tmp/PHSS_30331.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
	PHSS_30331:
	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 Data Protector
	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.