Troubleshooting checklist for

Data Protector and Oracle on

UNIX systems

Copyright 2004

Page 1 of 1

Table of Contents
Page
Introduction
1. Checking the Oracle8/9 Side of the Integration.
1.1. Verify that you can access the Oracle8/9 Target Database.
1.2. Verify that you can access the recovery catalog.
1.3. Verify that the TNS listener is correctly configured for the Oracle8/9 Target Database and
for the recovery catalog database.
1.4. Check if your Oracle network path configuration is exported correctly.
1.5. Assign any special (non-default) Oracle environment settings.
1.6. Verify that the Oracle8/9 Target & Recovery database are configured to allow remote
connections with system privileges.
1.7. If you are using the recovery catalog database, verify that the Target Database is registered
in the recovery catalog.
1.8. Verify backup and restore directly to disk using a Recovery Manager channel type disk.
1.9. Test the oracle side of the configuration.
2. Configuration Problems.
2.1. Verify that the Data Protector software has been installed properly.
2.2. Verify that the Data Protector Database Library is linked with the Oracle8/9 executable.
2.3. Verify permissions of the Oracle home directory.
2.4. Verify the ownership of the Oracle binary.
2.5. Verify the permissions of the current user account.
2.6. Examine the system errors.
3. Backup Problems.
3.1. Perform a filesystem backup of the Oracle8/9 Server system.
3.2. Check your Oracle8/9 Server configuration.
3.3. Verify Data Protector internal data transfer using the testbar2 utility.
3.4. Start an Oracle backup directly to disk, using Recovery Manager channel type disk.
3.5. Check if the target database is in archivelog mode (required for online backup).
3.6. Known backup problems.
4. Restore Problems.
4.1. Verify that an object exists on the backup media.
4.2. Simulate a restore session.
4.3. Ensure that the database is in the correct state.
4.4. Check your environment variables.
4.5. Try using the RMAN CLI to restore the database items.
4.6. For Zero Downtime or Standalone Backup sessions, try to put the database into the Open state
manually.
4.7. Known restore problems.
4.8. Examples of an Oracle8/9 Database Restore.
Supported versions

Copyright 2004

Page 2 of 2

Introduction
This document will help you in identifying the problem area in the Oracle8/9 integration in Data Protector, and it will help
you troubleshooting the problem.
Before starting your troubleshooting, be sure to consider the following:
Ensure that all the Data Protector II official patches are installed. A list of the latest patches is available
on the Web at HP Services and Support Center.
Refer to the HP OpenView Data Protector Software Release Notes for a description of general Data
Protector limitations, problems and workarounds as well as the list of available Data
Protector Patches.

IMPORTANT
When you plan to use Oracle8/9 after you have removed the Data Protector Oracle8/9 Integration, then take note of the
following:
After uninstalling the Data Protector Oracle8/9 integration on an Oracle8/9 server system, the Oracle8/9 server software
is still linked to the Data Protector Database Library. You must rebuild (Oracle8.x) or relink (Oracle8i or Oracle9i) the
Oracle8/9 binary to remove this link. If this is not done, the Oracle8/9 server cannot be started after the integration has
been removed.
Please refer to Using Oracle8/9 After Removing the Data Protector Oracle8/9 Integration in the Unix integration guide
for more info.

Setting Up the Environment Variables

If you need to export some variables before starting the Oracle8 Server Manager or Oracle9i SQL Plus, TNS listener, or
Recovery Manager, these variables must be exported as described in the Unix integration guide in paragraph Setting,
Retrieving and Listing Data Protector Oracle8/9 Configuration Files Parameters Using the CLI .

Note
Whenever RMAN is run outside of Data Protector, which is currently true for restores, always set the two variables
appropriately prior to running the command :
export OB2APPNAME=<ORACLE_SID>
export OB2BARLIST=<OmniBack II barlist>
Depending on the Oracle version running, the exporting of the above variables might not work and thus it is crucial to use
the parms option on the allocate channel command in the RMAN run command to pass the variables into the environment
as in the following example :
allocate channel dev_1 type sbt_tape
parms
ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=<ORACLE_SID>,OB2BARLIST=<OmniBack II barlist>);

Copyright 2004

Page 3 of 3

1. Checking Prerequisites Related to the Oracle8/9 Side of the

Integration
For more detailed information about how to perform any of the following procedures, refer to the Oracle8/9
documentation.
1.1.Verify that you can access the Oracle8/9 Target Database (and that it is opened as follows)
Export <ORACLE_HOME > and <ORACLE_SID> as follows:
if you are using an sh - like shell, enter the following commands:
ORACLE_HOME=<ORACLE_HOME>
export ORACLE_HOME
ORACLE_SID=<ORACLE_SID>
export ORACLE_SID
if you are using a csh - like shell, enter the following commands:
setenv ORACLE_HOME <ORACLE_HOME>
setenv ORACLE_SID <ORACLE_SID>
Start the Server Manager (Oracle8) or SQL Plus (Oracle9i) from the <ORACLE_HOME> directory:
For Oracle8:
bin/svrmgrl
For Oracle 9i: bin/sqlplus /nolog
At the SVRMGR (Oracle8) or SQL (Oracle9i) prompt type:
connect internal
select tablespace_name, status from dba_tablespaces;
exit
This will give you a list of the current status of all tablespaces in the database.
Example of the command output:

TABLESPACE_NAME
STATUS
---------------------------------------------------SYSTEM
ONLINE
RBS
ONLINE
TEMP
ONLINE
TOOLS
ONLINE
USERS
ONLINE

If this fails, you need to open the Oracle8/9 Target Database.

Copyright 2004

Page 4 of 4

1.2.Verify that you can access the recovery catalog (if used).

Export <ORACLE_HOME > and <ORACLE_SID> as described in 1.1.

Start the Server Manager (Oracle8) or SQL Plus (Oracle9i) from the <ORACLE_HOME> directory:
For Oracle8:
bin/svrmgrl
For Oracle 9i: bin/sqlplus /nolog
At the SVRMGR (Oracle8) or SQL (Oracle9i) prompt type:
connect <Recovery_Catalog_Login>
select * from rcver;
exit
If this fails, you need to open the recovery catalog.

1.3.Verify that the TNS listener is correctly configured for the Oracle8/9 Target Database and for
the recovery catalog database (This is required for properly establishing network).
Export <ORACLE_HOME> as described in 1.1.
Start the listener from the <ORACLE_HOME> directory:
bin/lsnrctl80 status <service>
exit
Example of the command output:

LSNRCTL for HPUX: Version 8.0.4.0.0 - Production on 17-JUN-99 15:26:57

(c) Copyright 1997 Oracle Corporation. All rights reserved.
Connecting to
(ADDRESS=(COMMUNITY=TCP.world)(PROTOCOL=TCP)(Host=farma.hermes.si)(Port=1528))
STATUS of the LISTENER
-----------------------Alias TOP
Version TNSLSNR for HPUX: Version 8.0.4.0.0 - Production
Start Date 07-JUN-99 14:07:16
Uptime 10 days 1 hr. 19 min. 43 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File
/applications/ORA8/app/oracle/product/8.0.4/network/admin/listener.ora
Listener Log File
/applications/ORA8/app/oracle/product

Note that with Oracle8i and Oracle9i, the lsnrctl and not the lsnrctl80 command is used.
If it fails, start up the TNS listener process and refer to the Oracle documentation for instructions on how
to create a TNS configuration file (LISTENER.ORA).

Copyright 2004

Page 5 of 5

Export <ORACLE_HOME> as described in 1.1.

Start the Server Manager (Oracle8) or SQL Plus (Oracle9i) from the <ORACLE_HOME> directory:
For Oracle8:
bin/svrmgrl
For Oracle 9i: bin/sqlplus /nolog
At the SVRMGR (Oracle8) or SQL (Oracle9i) prompt type:
connect <Target_Database_Login>
exit
and then
connect <Recovery_Catalog_Login>
exit
If this fails, refer to the Oracle8/9 documentation for instructions on how to create a TNS configuration
file (TNSNAMES.ORA).

1.4.Check if your Oracle network path configuration is exported correctly.

If your Oracle8 Net8 network configuration is not in the default directory,
<ORACLE_HOME>/network/admin, then you have to export the TNS_ADMIN shell variable to the
/etc/opt/omni/oracle8/<ORACLE_SID>/.profile (for HPUX) or
/usr/omni/config/oracle8/<ORACLE_SID>/.profile (for non HP-UX) file.

1.5.Assign any special (non-default) Oracle environment settings.

Register them in the following file:
For HP-UX and Solaris systems:
/etc/opt/omni/oracle8/<ORACLE_SID>/.profile
For HP-UX and Solaris systems:
/usr/omni/config/oracle8/<ORACLE_SID>/.profile

1.6.Verify that the Oracle8/9 Target and Recovery catalog database are configured to allow
remote connections with system privileges.
Export <ORACLE_HOME > as described in 1.1.
Start the Server Manager (Oracle8) or SQL Plus (Oracle9i) from the <ORACLE_HOME> directory:
For Oracle8:
bin/svrmgrl
For Oracle 9i: bin/sqlplus /nolog

Copyright 2004

Page 6 of 6

At the SVRMGR (Oracle8) or SQL (Oracle9i) prompt type:

connect <Target_Database_Login> as SYSDBA
exit
and
bin/svrmgrl connect <Recovery_Catalog_Login> as SYSDBA (For Oracle8)
bin/sqlplus connect <Recovery_Catalog_Login> as SYSDBA (For Oracle9i)
exit
Repeat the procedure using SYSOPER instead of SYSDBA.
If this fails, refer to the Oracle8/9 documentation for instructions about how to set up the password file
and any relevant parameters in the init<ORACLE_SID>.ora file.

1.7.If you are using the recovery catalog database, verify that the Target Database is registered
in the recovery catalog:
Export <ORACLE_HOME> as described in 1.1 and start the Oracle8 Server Manager or Oracle9i SQL
Plus:
For Oracle8:
bin/svrmgrl
For Oracle 9i: bin/sqlplus /nolog
At the SVRMGR (Oracle8) or SQL (Oracle9i) prompt, type:
connect <Recovery_Catalog_Login>;
select * from db;
exit
If this fails, start the configuration using Data Protector or refer to the Oracle8/9 documentation for details
about how to register an Oracle8/9 Target Database in the recovery catalog database.

1.8.Verify backup and restore directly to disk using a Recovery Manager channel type disk.
If you are using the recovery catalog, export <ORACLE_HOME> as described in 1.1 and start Recovery
Manager as follows:
bin/rman target <Target_Database_Login> rcvcat \
<Recovery_Catalog_Login> cmd_file=rman_script
If you are not using the recovery catalog, export <ORACLE_HOME> as described in 1.1 and start
Recovery Manager as follows:
bin/rman target <Target_Database_Login> nocatalog \
cmd_file=rman_script
An example of the RMAN script is presented below:
run {allocate channel dev0 type disk;
backup tablespace <tablespace_name>
format <ORACLE_HOME>/tmp/<datafile_name>;}

Copyright 2004

Page 7 of 7

After a successful backup, try to restore the backed up tablespace by running the following restore script:
run {
allocate channel dev0 type disk;
sql alter tablespace <tablespace_name> offline immediate;
restore tablespace <tablespace_name>;
recover tablespace <tablespace_name>;
sql alter tablespace <tablespace_name> online
release channel dev0;
}
If this fails, refer to the Oracle8/9 documentation for details about how to execute a backup and restore
directly to disk using the Recovery Manager.

1.9.Test the oracle side of the configuration.

To test the Oracle8 part of the configuration, start the configuration procedure directly from Recovery
Manager (RMAN) as follows;
Log in as root to the Oracle system and export <ORACLE_HOME> as described in 1.1.
Start the Recovery Manager.
Register the Database in a Recovery Catalog using the register database command.
Refresh the Recovery Catalog using the Recovery Manager resync catalog comand.
Example:

$ cd /applications/ORA8/app/oracle/product/8.0.4
$ export
ORACLE_HOME=/applications/ORA8/app/oracle/product/8.0.4
$ bin/rman target sys/manager@TOP rcvcat rman/rman@TCAT;
Recovery Manager: Release 8.0.4.0.0 - Production
RMAN-06005: connected to target database: TOP
RMAN-06008: connected to recovery catalog database
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::;::
RMAN> resync catalog;
RMAN-03022: compiling command: resync
RMAN-03023: executing command: resync
RMAN-08002: starting full resync of recovery catalog
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

1.10. Check the following Oracle files for error descriptions.

Oracle8 log file:
$ORACLE_HOME/rdbms/log/ sbtio.log
or
<Oracle8 user dump directory>/ sbtio.log

Copyright 2004

Page 8 of 8

RMAN debug files:

$ bin/rman sys/manager@TFDR rcvcat rman/rman@TCAT cmdfile
rman_command_script debug | tee /DEBUGS/RMAN.txt
Oracle log files (cdump and bdump) (from dir <ORACLE_BASE>/cdump
<ORACLE_BASE>/bdump or check conf<ORACLE_SID>.ora for location)

1.11. Use the Oracle error reporting tool.

Use the following command to invoke oerr at the UNIX command line:
$ oerr error_facility error_number
(error facility = ora, rman)
Example:

$ bin/oerr ora 19602

19602, 00000, "cannot backup or copy active file in NOARCHIVELOG
mode"
// *Cause: You tried to copy or backup a file that was not closed
//cleanly,
//and the database was in NOARCHIVELOG mode. This is not allowed
//because when restored, the file will require redo application
//before it is usable, and redo is not currently being saved
//beyond the contents of the online redo logs.
// *Action: Take the tablespace offline clean or close the database and
//retry
//the copy or backup.
$ bin/oerr rman 10032

1.12. Run a backup and restore without Data Protector.

Remove the Data Protector shared library from Oracle (/opt/omni/lib/libob2oracle8.sl).
Logon as the Oracle user and shutdown all Oracle instances.
cd $ORACLE_HOME/rdbms/lib
Make sure that you uncomment out any lines you previously commented in the
$ORACLE_HOME/rdbms/lib/env_rdbms.mk file.
Type the following command:
make -f ins_rdbms.mk ioracle
Check that the Data Protector shared library is no longer included.
You can check this with the chats/ldd command. See the Oracle linking technical white paper, this can be
found at Location to be included when known.

Copyright 2004

Page 9 of 9

Example:

$ chatr oracle
oracle:
shared executable
shared library dynamic path search:
SHLIB_PATH disabled second
embedded path disabled first Not Defined
shared library list:
dynamic /usr/lib/librt.2
dynamic /usr/lib/libnss_dns.1
dynamic /usr/lib/libdld.2
static /usr/lib/libc.2
shared library binding:
immediate nonfatal
static branch prediction disabled
kernel assisted branch prediction enabled
lazy swap allocation disabled
text segment locking disabled
data segment locking disabled
data page size: D (default)
instruction page size: D (default)

Start backup using RMAN.

Start backup.
Create backup script
Start backup
Example:

$ vi rman_command_script
run {
allocate channel dev_1 type disk;
allocate channel dev_2 type disk;
full
filesperset 1
(database format
'/app/oracle/tmpbc/TOP_%s:%t.dbf');
}
$ bin/rman sys/manager@TOP nocatalog cmdfile
rman_command_script
Recovery Manager: Release 8.0.4.0.0 - Production
RMAN> run {
2> allocate channel dev_1 type disk;
3> allocate channel dev_2 type disk;
(Refer to Oracle manuals for further instruction)

Copyright 2004

Page 10 of 10

Start restore.
Create restore script
Start restore
Example:

$ vi rman_command_script
run {
allocate channel dev_1 type disk;
allocate channel dev_2 type disk;
restore database;
release channel dev_1;
release channel dev_2;
}
$ bin/rman sys/manager@TOP nocatalog cmdfile rman_command_script

2. Configuration Problems
IMPORTANT
If you have encountered any errors up to this point when performing the procedures described in the previous
section, please contact Oracle8/9 support. The respective tests must be done before you even start checking the
Data Protector Oracle8/9 configuration.
2.1.Verify that the Data Protector software has been installed properly.
Prequisite when doing an upgrade/ installation:
You need to shut down any running Oracle8 databases on the Oracle8 servers to be integrated before
upgrading or installing the Data Protector Oracle8 integration, and restart them after the upgrade or
installation is complete.
When performing an upgrade:
The Oracle 8/9 integration is upgraded automatically during the client upgrade. After the upgrade
procedure has completed, some additional steps have to be performed manually to finish the upgrade.
For the upgrade procedure, refer to Upgrading to Data Protector A.05.10 in the HP OpenView Storage
Data Protector Installation and Licensing Guide.
When performing an installation:
Install the Data Protector Oracle8/9 integration software on your Oracle8/9 Server system either locally,
from the CD-ROM, or remotely, using the Data Protector GUI. You must install the following Data Protector
software components on the Oracle8/9 server system:
Oracle8 Integration
Disk Agent
Media Agent (if you have devices connected to the system)

Copyright 2004

Page 11 of 11

It is recommended that you also install:

User Interface
Refer to the HP OpenView Storage Data Protector Installation and Licensing Guide for details about the
installation.
Verifying the Upgrade/Installation
Once the installation has completed, you can verify it. For the procedure, refer to Verifying Data
Protector Installation in the HP OpenView Storage Data Protector Installation and Licensing Guide.

2.2.Verify that the Data Protector Database Library is linked with the Oracle8/9 Executable.
Refer to the Oracle linking whitepaper:
Oracle with Omniback/Data Protector on UNIX systems
This whitepaper can be found on http://support.openview.hp.com/dataprotector_docs.jsp .

2.3.Verify permissions of the Oracle home directory.

Check the permissions for the Oracle8 home directory. The right permissions are 755.
Verify the ownership of the Oracle binary.
2.4.Verify the ownership of the Oracle binary.
Check that the switch ownership(s) bit of the oracle binary is set and that the
owner of the commands is the Oracle8 backup owner.

2.5.Verify the permissions of the current user account.

Your user account should enable you to perform an Oracle8/9 backup or restore with Data Protector.
For a backup:
Check that the owner of the backup specification is the Oracle8 backup owner, and that they
are in the Data Protector operator or admin group
For a restore:
Verify that the user specified for the restore session is the Oracle backup owner, and that it is in
the Data Protector operator group.
In the Data Protector GUI, Users, check the user rights for the group operator. It should include See private
objects.
Test if the Oracle8 backup owner has the right privileges in Data Protector.
Log in as the Oracle8 backup owner, for example, as user oracle and run the following command:

Copyright 2004

Page 12 of 12

Use the testbar2 utility to check the permissions:

For HP-UX and Solaris systems:
/opt/omni/bin/testbar2 -perform:checkuser
For other UNIX systems:
/usr/omni/bin/testbar2 -perform:checkuser
Example of the command output:

====================
Parsing options:
'-perform:checkuser' :OPT_PERFORM: 'CHECKUSER'
=======================
[Normal] Parsing environment options.
[Normal] Performing common initialisation.
[Normal] Getting cell server host from config file.
[Normal] Performing cell server connection initialisation.
[Normal] Getting current user information.
[Normal] Testing if user can see private BAR objects.
[Normal] Testing if user can perform restore.
[Normal] Check user successfully finished.
-----------------------------------------OmniBackII testbar finished.
------------------------------------------

If the user account holds all required permissions, you will receive only NORMAL messages displayed on
the screen.
For example, if user dizdar, on Oracle8 client system.com, is not in the operator or
admin group, you get the following error:
[Critical] From: [email protected] "" Time: 08/06/98 17:35:37
[131:53] User "[email protected]" is not allowed to perform a restore.
Refer to the HP OpenView Storage Data Protector UNIX Integration Guide for additional information
about right privileges.

2.6.Examine the system errors.

The system errors are reported in the /var/opt/omni/log/debug.log (HP-UX and Solaris systems) or
/usr/omni/log/debug.log (other UNIX systems) file on the Oracle8/9 Server system.

Copyright 2004

Page 13 of 13

3. Backup Problems
At this stage, you should have performed all the verification steps described in the previous sections. After this,
proceed as follows:

3.1.Perform a filesystem backup of the Oracle8/9 Server system.

Perform a filesystem backup of the Oracle8/9 Server system so that you can eliminate any potential
communication problems between the Oracle8/9 Server and the Data Protector Cell Manager system.
IMPORTANT
Do not start troubleshooting an online database backup unless you have
successfully completed a filesystem backup of the Oracle8/9 Server system.
Refer to the HP OpenView Storage Data Protector Administrators Guide for details about how to
do a filesystem backup.

3.2.Check your Oracle8/9 Server configuration.

To check the Oracle8/9 Server configuration, login as an Oracle8/9 group dba user to the Oracle8/9
server system and start the following command on the Oracle8/9 Server system:
For HP-UX and Solaris systems:
/opt/omni/lbin/util_oracle8.exe -CHKCONF <ORACLE_SID>
For other UNIX systems:
/usr/omni/bin/util_oracle8.exe -CHKCONF <ORACLE_SID>
In case of an error, the error number is displayed in the form:
*RETVAL*<Error_number>.
To get the error description, start the command:
omnigetmsg <set_number> <Error_number>
For HP-UX and Solaris systems:
/opt/omni/lbin/omnigetmsg 12 <Error_number>
For other UNIX systems:
/usr/omni/bin/omnigetmsg 12 <Error_number>

The *RETVAL*0 indicates successful configuration.

If this fails, then the configuration needs to be troubleshooted.

IMPORTANT
It is possible to receive a *RETVAL*0 even though the backup still fails. This can happen
due to the fact that the backup owner is not the Oracle dba user.

Copyright 2004

Page 14 of 14

3.3.Verify Data Protector internal data transfer using the testbar2 utility.
Before you run the testbar2 utility, verify that the Cell Manager name is correctly defined on the
Oracle8/9 Server system. Check the name of the Cell Manager system in the file.
For HP-UX and Solaris systems, this file can be found at:
/etc/opt/omni/cell/cell_server
For other UNIX systems, this file can be found at:
/usr/omni/config/cell/cell_server
Then run the following command:
For HP-UX and Solaris systems:
/opt/omni/bin/testbar2 -type:Oracle8 -appname:<ORACLE_SID> \
-bar:<backup_specification_name> -perform:backup
For other UNIX systems:
/usr/omni/bin/testbar2 -type:Oracle8 -appname:<ORACLE_SID> \
-bar:<backup_specification_name> -perform:backup
Switch to the Data Protector Manager and examine the errors reported by the testbar2 utility by clicking
the Details button in the Data Protector Monitor context.
If the messages indicate problems on the Data Protector side of the integration, proceed as follows:
Create an Oracle8/9 backup specification to back up to a null device or file. If the backup
succeeds, the problem may be related to the backup devices. Refer to the HP OpenView Storage
Data Protector Administrators Guide for instructions on troubleshooting devices.

3.4.Start an Oracle backup directly to disk, using Recovery Manager channel type disk.
If this test fails, then it may not be a Data Protector problem.
Example:
Logon as the Oracle user.
Start backup to disk using RMAN.
Create rman backup command script:
$ vi bkp_command_script
run {
allocate channel dev_1 type disk;
allocate channel dev_2 type disk;
full
filesperset 1
(database format '/app/oracle/tmpbc/TOP_%s:%t.dbf');
}
$ bin/rman sys/manager@TOP nocatalog cmdfile rman_command_script
Start restore to disk using RMAN.

Copyright 2004

Page 15 of 15

Create rman restore command script:

$ vi rman_command_script
run {
allocate channel dev_1 type disk;
allocate channel dev_2 type disk;
restore database;
release channel dev_1;
release channel dev_2;
}
$ bin/rman sys/manager@TOP nocatalog cmdfile rman_command_script
Refer to Oracle8 manuals for further instructions.

3.5.Check if the target database is in archivelog mode (required for online backup).
logon as the Oracle user
export ORACLE_SID of target database as described in 1.1.
start Server Manager and connect internal
type "archive log list;" in order to get archivelog status of target database.
SVRMGR> archive log list;
Example:

Database log mode

Automatic archival
Archive destination
Oldest online log sequence
Current log sequence

No Archive Mode
Disabled
/applications/ORA8/app/oracle/admin \
/TOP/arch
270
272

Refer to Oracle8 documentation on how to put database in the archivelog

3.6.Known backup problems:

Data Protector reports Export of the Recovery Catalog Database Failed when backing up Oracle 9i .
Problem
The following errors are listed in the Data Protector monitor:
EXP-00008: ORACLE error 6550 encountered
ORA-06550: line 1, column 13:
PLS-00201: identifier 'SYS.LT_EXPORT_PKG' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
EXP-00083: The previous problem occurred when calling
SYS.LT_EXPORT_PKG.schema_info_exp
exporting statistics

Copyright 2004

Page 16 of 16

Export terminated successfully with warnings.

[Major] From: ob2rman.exe@machine "MAKI" Time: 10/01/01 16:07:53
Export of the Recovery Catalog Database failed.
Action
Log in to Oracle9i SQL Plus and grant the execute permission to the Oracle9i
LT_EXPORT_PKG as follows (make sure that the user sys has the SYSDBA permission
granted beforehand):
sqlplus sys/<password>@CDB as sysdba
SQL> grant execute on sys.lt_export_pkg to public;
Restart the failed backup session.

Data Protector reports Cannot allocate/attach shared memory

Problem
Backup fails and the following error message is displayed:
Cannot allocate/attach shared memory (IPC Cannot Allocate Shared Memory Segment)
System error: [13] Permission denied) => aborting
Action
Set the OB2SHMEM_IPCGLOBAL omnirc option in /opt/omni/.omnirc file to 1 in order
to use the memory windowing properly, and restart the failed backup session. Refer to
the HP OpenView Storage Data Protector Administrators Guide for details on using
omnirc options.

Backup Fails after a Point in Time Restore and Recovery

Problem
Backup fails after a Point in time restore and recovery was performed and the following
error is displayed:
RMAN-06004: ORACLE error from recovery catalog database:
RMAN-20003: target database incarnation not found in recovery catalog
Action
Connect to the target and recovery catalog database using RMAN and reset the
database:
rman target <Target_Database_Login> rcvcat <Recovery_Catalog_Login>RMAN> RESET
DATABASE;
RMAN> exit

Copyright 2004

Page 17 of 17

4. Restore problems
You should have performed all the verification steps described in the previous sections. Proceed with the points below.
If youre not sure what or how to restore an Oracle database, then do check the chapter 4.8 Examples of an
Oracle8/9 Database Restore first. This will give some examples of how you should perform a restore.

4.1.Perform a filesystem restore of the Oracle8/9 Server system.

Ensure that a filesystem restore of the problematic client works. It is much easier to troubleshoot a
filesystem backup and restore.
If a filesystem restore fails as well, then you need to troubleshoot this first. This way you can eliminate any
potential communication problems between the Oracle server and the Data Protector Cell Manager
system.

4.2.Verify that an object exists on the backup media.

This can be done by executing the following command on the Oracle8/9 Server system:
For HP-UX and Solaris systems:
/opt/omni/bin/omnidb -oracle8 <object_name> session <Session_ID> media
For other UNIX systems:
/usr/omni/bin/omnidb -oracle8 <object_name> session <Session_ID> -media
The output of the command lists detailed information about the specified Oracle8/9 object, as well as the
session IDs of the backup sessions containing this object and a list of the media used. For detailed syntax
of the omnidb command, run: man omnidb

4.3.Verify Data Protector internal data transfer using the testbar2 utility.
Once you know the information about the object to be restored, you can simulate a restore using the Data
Protector testbar2 utility.
Before you run the testbar2 utility, verify that the Cell Manager name is correctly defined on the
Oracle8/9 Server system.
Check the name of the Cell Manager system in the cell_server file.
For HP-UX and Solaris systems:
/etc/opt/omni/cell/cell_server
For other UNIX systems
/usr/omni/config/cell/cell_server

Copyright 2004

Page 18 of 18

Test Data Protector internal data transfer using the testbar2 utility:
For HP-UX and Solaris systems:
/opt/omni/bin/testbar2 \
-type:Oracle8 \
-appname:<ORACLE_SID> \
-perform:restore
-object:<object_name> \
-version:<object_version> \
-bar:<backup_specification_name>
For other UNIX systems:
/usr/omni/bin/testbar2 \
-type:Oracle8 \
-appname:<ORACLE_SID> \
-perform:restore \
-object:<object_name> \
-version:<object_version> \
-bar:<backup_specification_name>
IMPORTANT
The hostname should not be specified in the object option. It is automatically provided by testbar2. You
should see only NORMAL messages displayed on your screen, otherwise examine the errors reported by
the testbar2 utility by clicking the Details button in the Data Protector Monitor context.
If the messages indicate problems on the Data Protector side of the integration, proceed as follows:
Run the omnidb command to view the objects in the database.

4.4.Ensure that the database is in the correct state.

If you are trying to restore a database item using the Data Protector Restore GUI for Oracle and the GUI
hangs try one of the following:
If you are restoring the control file the database should be in the NoMount state.
Open a command window and enter the following:
sqlplus/nolog
SQL>connect/as sysdba
SQL>shutdown immediate
SQL>startup nomount
If you are restoring datafiles the database should be in the Mount state.
Open a command window and enter the following:
sqlplus/nolog
SQL>connect/as sysdba
SQL>shutdown immediate
SQL>startup mount

4.5.Check your environment variables.

The message below sometimes appears when you are restoring database items to a new host:
Binary util_orarest is missing. Cannot get information from the remote host.

Copyright 2004

Page 19 of 19

To resolve this problem do as follows:

a. Close Data Protector.
b. Set the environment variable on the system where the Cell Manager resides:
OB2_ORARESTHOSTNAME = <target Oracle host>
c. Restart Data Protector and try to restore the database items again.
d. When the restore is complete, close Data Protector and re-set the following environment variable:
OB2_ORARESTHOSTNAME = <empty>
e. Restart Data Protector.

4.6.Try using the RMAN CLI to restore the database items.

If there is a problem you cannot resolve while you are trying to restore a database item using the Data
Protector Restore GUI for Oracle try using the RMAN CLI to restore the database items. For information
about using the CLI and Restoring Oracle8/9 Using RMAN, see the HP OpenView Storage Data
ProtectorUNIX Integration Guide.

4.7.For Zero Downtime or Standalone Backup sessions, try to put the database into the Open
state manually (after using the Data Protector Restore GUI for Oracle to recover and restore).
If you have used the Data Protector Restore GUI for Oracle to recover and restore a Zero Downtime
Backup (ZDB) session or a standalone backup, and you see the following error message:
Oracle Error: ORA-1589: must use RESETLOGS or NORESETLOGS option for database open.
Open a SQLplus window and use the following command:
SQL>sqlplus/nolog
SQL>connect as sysdba
SQL>alter database open no resetlogs/resetlogs;
If this does not work try using the following command:
SQL>alter database open resetlogs;

4.8.Known restore problems:

Binary util_orarest failed error message is displayed when browsing Oracle9 database for restore on
Linux.
Problem
The following error message is displayed when browsing Oracle9 database for restore on Linux:
Binary util_orarest failed. Cannot get information from the remote host.
Action
Replace the util_orarest.exe utility with the new util_orarest9.exe (both located in the /usr/omni/bin
directory on Linux):
1. Rename the util_orarest.exe to util_orarest.exe.orig
2. Rename the util_orarest9.exe to util_orarest.exe

Copyright 2004

Page 20 of 20

4.9.Examples of an Oracle8/9 Database Restore.

This section describes some examples of how you can restore an Oracle8/9 database.
The following examples of restore are given:
Full database restore
Point-in-time restore
Tablespace restore
Datafile restore
Archive log restore
Control files restore
IMPORTANT
The restore of an Oracle8/9 database is performed using the RMAN utility, which is not a part of Data
Protector. This section only describes examples of how you can perform a restore. The examples
provided do not apply to all situations where a restore is needed. For additional information on how you
can restore an Oracle8/9 database using the RMAN utility, refer to the Oracle documentation.
Preparing the Oracle8/9 Database for Restore.
The restore of an Oracle8/9 database can be performed when the database is in a mount (quiescent)
mode. However, when you are performing the restore of tablespaces or datafiles, only a part of the
Oracle8/9 database can be put offline.
Prerequisites
The following requirements must be met before you start a restore of an Oracle8/9 database:
If you are using a recovery catalog database, make sure that the database is running. If the recovery
catalog database cannot be brought online, you will probably need to restore the database. Refer to the
HP Openview Storage Data Protector UNIX Integration Guide, chapter Restoring Oracle8/9
Databases on page 66 for details on how to restore the recovery catalog database.
If you are using control files, they must be accessible in order to perform the restore. If the control files
are not available, you will probably need to restore them. Refer to the HP Openview Storage Data
Protector UNIX Integration Guide, chapter Control File Restore on page 115 for details on how to
restore the control files.
If you have to perform a restore of the recovery catalog database or control files, you must perform this
restore first. Only then can you perform a restore of other parts of the Oracle8/9 database. When you
are sure that the recovery catalog database or control files are in place, start the recovery catalog
database and the listener.
Make sure that the following environment variables are set:
ORACLE_BASE
ORACLE_HOME
ORACLE_TERM
ORACLE_SID
PATH
NLS_LANG
NLS_DATE_FORMAT

Copyright 2004

Page 21 of 21

Example of Environment Variables:

ORACLE_BASE=/opt/oracle
ORACLE_HOME=/opt/oracle/product/8.1.6
ORACLE_TERM=hp
ORACLE_SID=PROD
PATH=$PATH:/opt/oracle/product/8.1.6/bin
NLS_LANG=american
NLS_DATE_FORMAT=Mon DD YYYY HH24:MI:SS
Check that the /etc/oratab file has the following line:
PROD:/opt/oracle/product/8.1.6:N
The last letter determines whether the database will automatically start upon bootup (Y) or not (N).
Examples of Oracle8/9 Database Restore
In the examples below, the following connection strings are used:
Target connection string for target database:
sys/manager@PROD
Where sys is the username, manager is the password and PROD is the name of the Oracle8/9
database.
Recovery catalog connection string for recovery catalog database:
rman/rman@CATAL
Where rman is the username and password and CATAL is the name of the Oracle8/9 database.

Full Database Restore

To perform a full database recovery, you also need to restore and apply all the archive logs. To perform
a full database restore, follow the steps below:
1. Log in to the Oracle 8/9 RMAN:
a. If you are using the recovery catalog database, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat rman/rman@CATAL
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD nocatalog
2. Start the full database restore:
run{
allocate channel <dev1> type <sbt_tape> parms
ENV=(OB2BARTYPE=Oracle8, \
OB2APPNAME=<ORACLE_SID>);
restore database;
recover database;
sql alter database open;
release channel <dev1>;
}

Copyright 2004

Page 22 of 22

You can also save the script into a file and perform a full database restore using the saved files.
The procedure in such cases is as follows:
1. Create a file restore_database in the /var/opt/omni/tmp directory.
2. Start the full database restore.
a. If you are using the recovery catalog database, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat \
rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_datafile
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD \
nocatalog cmdfile=/var/opt/omni/tmp/restore_datafile

Point-in-Time Restore
To perform a point-in-time restore, you also need to restore and apply the archive logs to the specified
point in time. To perform a point-in-time database restore, follow the steps below:
1. Log in to the Oracle 8/9 RMAN:
a. If you are using the recovery catalog database, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat \ rman/rman@CATAL
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD nocatalog
2. Start the point-in-time restore:
run{
allocate channel <dev1> type <sbt_tape> parms
ENV=(OB2BARTYPE=Oracle8 \
OB2APPNAME=<ORACLE_SID>);
set until time Mar 14 2001 11:40:00;
restore database;
recover database;
sql alter database open;
release channel <dev1>;
}
3. After you have performed a point-in-time restore, reset the database in the Recovery Catalog.
You can also save the script into a file and perform a point-in-time restore using the saved files.
Follow the steps below:
1. Create a file restore_PIT in the /var/opt/omni/tmp directory.
2. Start the point-in-time restore.
a. If you are using the recovery catalog database, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat \
rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_PIT
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD \
nocatalog cmdfile=/var/opt/omni/tmp/restore_PIT

Copyright 2004

Page 23 of 23

Tablespace Restore
If a table is missing or corrupted, you need to perform a restore of the entire tablespace. To restore a
tablespace, you may take only a part of the database offline, so that the database does not have to be in
the mount mode. You can use either a recovery catalog database or control files to perform a tablespace
restore. Follow the steps below:
1. Log in to the Oracle 8/9 RMAN:
a. If you are using the recovery catalog database, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat \
rman/rman@CATAL
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD nocatalog
2. Start the tablespace restore.
a. If the database is in the open state, the script to restore the tablespace should have the
following format:
run{
allocate channel <dev1> type <sbt_tape> parms
ENV=(OB2BARTYPE=Oracle8, \
OB2APPNAME=<ORACLE_SID>);
sql alter tablespace TEMP offline immediate;
restore tablespace TEMP;
recover tablespace TEMP;
sql alter tablespace TEMP online;
release channel <dev1>;
}
b. If the database is in the mount state, the script to restore the tablespace should have the
following format:
run{
allocate channel <dev1> type <sbt_tape> parms
ENV=(OB2BARTYPE=Oracle8, \
OB2APPNAME=<ORACLE_SID>);
restore tablespace TEMP;
recover tablespace TEMP;
release channel <dev1>;
}
You can also save the script into a file and perform a tablespace restore using the saved
files. The procedure in such cases is as follows:
1. Create a file restore_TAB in the /var/opt/omni/tmp directory.
2. Start the tablespace restore.
a. If you are using the recovery catalog database, run the following
command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat \
rman/rman@CATAL cmdfile=/var/opt/omni/log/restore_TAB

Copyright 2004

Page 24 of 24

b. If you are using control files, run the following command:

<ORACLE_HOME>/bin/rman target sys/manager@PROD \
nocatalog cmdfile=/var/opt/omni/log/restore_TAB
Datafile Restore
To restore a datafile, you may take only a part of the database offline. To perform a datafile restore,
follow the steps below:
1. Log in to the Oracle 8/9 RMAN:
a. If you are using the recovery catalog database, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat rman/rman@CATAL
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD nocatalog
2. Start the datafile restore:
a. If the database is in an open state, the script to restore the datafile should have the
following format:
run{
allocate channel <dev1> type <sbt_tape> parms
ENV=(OB2BARTYPE=Oracle8, \
OB2APPNAME=<ORACLE_SID>);
sql alter database datafile
/opt/oracle/data/oradata/DATA/temp01.dbf offline;
restore datafile
/opt/oracle/data/oradata/DATA/temp01.dbf;
recover datafile
/opt/oracle/data/oradata/DATA/temp01.dbf;
sql alter database datafile
/opt/oracle/data/oradata/DATA/temp01.dbf online;
release channel <dev1>;
}
b. If the database is in a mount state, the script to restore the datafile should have the
following format:
run{
allocate channel <dev1> type <sbt_tape> parms
ENV=(OB2BARTYPE=Oracle8, \
OB2APPNAME=<ORACLE_SID>);
restore datafile
/opt/oracle/data/oradata/DATA/temp01.dbf;
recover datafile
/opt/oracle/data/oradata/DATA/temp01.dbf;
release channel <dev1>;
}
You can also save the script into a file and perform a datafile restore using the saved files.
The procedure in such cases is as follows:
1. Create a file restore_dbf in the /var/opt/omni/tmp directory.

Copyright 2004

Page 25 of 25

2. Start the datafile restore.

a. If you are using the recovery catalog database, run the following
command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat \
rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_dbf
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD \
nocatalog cmdfile=/var/opt/omni/tmp/restore_dbf

Archive Log Restore

To restore an archive log, follow the steps below:
1. Login to the Oracle 8/9 RMAN:
a. If you are using the recovery catalog database, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat rman/rman@CATAL
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD nocatalog
2. Start the archive log restore:
run{
allocate channel <dev1> type <sbt_tape> parms
ENV=(OB2BARTYPE=Oracle8, \
OB2APPNAME=<ORACLE_SID>);
restore archivelog all;
release channel <dev1>;
}
You can also save the script into a file and perform an archive log restore using the saved files.
The procedure in such cases is as follows:
1. Create a file restore_arch in the /var/opt/omni/tmp directory.
2. Start the archive log restore.
a. If you are using the recovery catalog database, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD rcvcat \
rman/rman@CATAL cmdfile=/var/opt/omni/tmp/restore_arch
b. If you are using control files, run the following command:
<ORACLE_HOME>/bin/rman target sys/manager@PROD \
nocatalog cmdfile=/var/opt/omni/tmp/restore_arch

Control File Restore

The restore and recovery procedure of Oracle 8/9 control files is a very delicate operation, which
depends on whether you are using the recovery catalog or control file as a central repository and on the
version of the Oracle database you are using. For detailed steps to perform the restore of control files,
please refer to the Recovery Manager Users Guide and Reference.

Copyright 2004

Page 26 of 26

Supported Versions

OD/DP version

Oracle type

Omniback 3.5

Oracle (32 bit)

(Including Oracle Parallel
Server)

Oracle (64 bit)

(Including Oracle Parallel
Server)

Oracle Version

Oracle 7.3.4 / EBU

2.2

HP-UX 10.20 (32 bit)

HP-UX 11.0 (32 & 64 bit)
Windows NT 4.0
Solaris 2.5, 2.6 (32 bit)
AIX 4.3.x

Oracle 8.0.x /
Recovery Manager

HP-UX 10.20 (32 bit)

HP-UX 11.0 (32 & 64 bit)
Windows NT 4.0
Solaris 2.6 (32 bit), 7 (32 & 64 bit)
AIX 4.3.x

Oracle 8.1.x /
Recovery Manager

HP-UX 11.0 (32 & 64 bit)

HP-UX 11.11 (32 & 64 bit)
Solaris 7, 8(1) (32 & 64 bit)
AIX 4.3.x
Windows NT 4.0
Linux Red Hat Dist. 6.x

Oracle 8.1.6

Windows 2000

Oracle 8.0.x /
Recovery Manager

HP-UX 11.0 (64 bit) (3)

Oracle 8.1.x /
Recovery Manager

Omniback 4.1

Copyright 2004

Oracle (32 bit)

(Including Oracle Parallel
Server and RAC)

Operating System

HP-UX 11.0 (64 bit)

HP-UX 11.11 (64 bit)
Solaris 7 & 8 (64 bit) (2)

Oracle 7.3.4 / EBU

2.2

HP-UX 10.20 (32 bit)

HP-UX 11.0 (32 & 64 bit)
Windows NT 4.0
Solaris 2.6 (32 bit)
AIX 4.3.x

Oracle 8.0.x /
Recovery Manager

HP-UX 10.20 (32 bit)

HP-UX 11.0 (32 & 64 bit)
Windows NT 4.0
Solaris 2.6 (32 bit)
Solaris 7 (32 & 64 bit)
AIX 4.3.x

Page 27 of 27

Oracle (64 bit)

(Including Oracle Parallel
Server and RAC)

Data Protector 5.0

Copyright 2004

Oracle (32 bit)

(Including Oracle Parallel
Server and RAC) (7)

Oracle 8.1.x /
Recovery Manager

HP-UX 11.0 (32 & 64 bit)

HP-UX 11.11 (32 & 64 bit)
Solaris 7, 8(1) (32 & 64 bit)
AIX 4.3.x, 5.1 (4), 5.2 (4,5)
Windows NT 4.0, 2000
Linux Red Hat Dist. 6.x, 7.x
Linux SuSE 7.x

Oracle 9i / Recovery
Manager (6)

Solaris 7 & 8 (32 bit)

Linux Red Hat 7.x, 8.x (4)
Linux SuSE 7.x, 8.x (4)
WindowsNT 4.0, 2000

Oracle 8.0.x /
Recovery Manager

HP-UX 11.0 (64 bit)

Oracle 8.0.1 /
Recovery Manager

HP-UX 11.0 (64 bit)

HP-UX 11.11 (64 bit)
Solaris 7 & 8 (64 bit)

Oracle 7.3.4 / EBU

2.2 (8)

HP-UX 10.20 (32 bit)

HP-UX 11.0 (32 & 64 bit)
Windows NT 4.0
Solaris 2.6 (32 bit)
AIX 4.3.x

Oracle 8.0.x /
Recovery Manager

HP-UX 10.20 (32 bit)

HP-UX 11.0 (32 & 64 bit)
Windows NT 4.0
Solaris 2.6 (32 bit)
Solaris 7 (32 & 64 bit)
AIX 4.3.x

Oracle 8.1.x /
Recovery Manager

HP-UX 11.0 (32 & 64 bit)

HP-UX 11.11 (32 & 64 bit)
Solaris 7, 8(1) (32 & 64 bit)
AIX 4.3.x
Windows NT 4.0, 2000
Linux (32 bit) Red Hat 6.x, 7.x
Linux (32 bit) SuSE 8.x

Oracle 9i / Recovery
Manager (6)

Solaris 7, 8 & 9 (32 & 64

bit)
Linux (32 bit) Red Hat 7.x, 8.x
Linux (32 bit) Red Hat
Advanced Server 2.1
Linux (32 bit) SuSE 7.x, 8.x (9)
Windows NT 4.0, 2000

Page 28 of 28

Oracle (64 bit)

(Including Oracle Parallel
Server and RAC) (7)

Data Protector 5.1

Oracle (32 bit)

(Including Oracle Parallel
Server and RAC) (7,11)

Oracle 8.0.x /
Recovery Manager

HP-UX 11.0 (64 bit)

Oracle 8.0.1 /
Recovery Manager

HP-UX 11.0 (64 bit)

HP-UX 11.11 (64 bit)
Solaris 7,8 & 9 (64 bit)
AIX 4.3.3 (64 bit),
5.1 (64 bit) (9)
5.2 (64 bit) (9,10)
Tru64 5.xx

Oracle 8.0.x /
Recovery Manager

HP-UX 11.0 (32 & 64 bit)

Windows NT 4.0
Solaris 2.6 (32 bit),
7 (32 & 64 bit)
AIX 4.3.x

Oracle 8.1.x /
Recovery Manager

HP-UX 11.0 (32 & 64 bit)

HP-UX 11.11 (32 & 64 bit)
Solaris 7, 8(1) (32 & 64 bit)
AIX 4.3.x, 5.1, 5.2
Windows NT 4.0, 2000
Linux (32 bit) Red Hat 6.x, 7.x
Linux (32 bit) SuSE 8.x

Oracle 9i / Recovery
Manager (6)

Oracle (64 bit)

(Including Oracle Parallel
Server and RAC) (7,11)

Copyright 2004

Solaris 7, 8 & 9 (32 & 64

bit)
Linux (32 bit) Red Hat 7.x, 8.x
Linux (32 bit) Red Hat
Advanced Server 2.1 (12)
Linux (32 bit) SuSE 7.x, 8.x
Windows NT 4.0, 2000,
2003 (32 bit)

Oracle 8.0.x /
Recovery Manager

HP-UX 11.0 (64 bit)

Oracle 8.0.1 /
Recovery Manager

HP-UX 11.0 (64 bit)

HP-UX 11.11 (64 bit)
Solaris 7,8 & 9 (64 bit)
AIX 4.3.3 (64 bit),
5.1 (64 bit)
5.2 (64 bit)
Tru64 5.xx

Page 29 of 29

Oracle 9i / Recovery
Manager

HP-UX 11.0 (64 bit)

HP-UX 11.11 (64 bit)
HP-UX 11.22 (64 bit)
HP-UX 11.23 (64 bit) (13)
Solaris 7,8 & 9 (64 bit)
Windows 2003 (64 bit)
AIX 4.3.3 (64 bit),
5.1 (64 bit)
5.2 (64 bit)
Tru64 5.xx

(1) To utilize Solaris 8 a patch is required:

Patch PHSS_22434 for Installation Server on HP-UX 10.x
Patch PHSS_22435 for Installation Server on HP-UX 11.0 or 11.11
(2) To utilize Oracle 8.1.x (64-bit) on Solaris 7 & 8 (64-bit) the patch PHSS_22439 is required.
Oracle Parallel Server option is not supported.
(3) Oracle 8.0.6 (64-bit) on HP-UX 11.0 (64-bit) is not supported.
(4) To utilize this feature the patch PHSS_28582 is required
(5) To utilize this feature, the patch PHSS_28584 is required
(6) Oracle 9i includes all released versions of Oracle 9.x.x.x
(7) FILEPERSET=1 limitation has been removed.
Oracle 9i covers all released versions of Oracle 9.x.x.x
(8) Only supported if the Customer has a valid support contract with Oracle for the database.
(9) To utilize this feature, the following patches are required:
PHSS_28337 for a HPUX Installation Server
DPSOL_00014 for a Solaris Installation Server
(10) To utilize this feature, the patch PHSS_28735 is required
(11) This is true for the platforms on which Data Protector has Cluster support. The whitepaper for the procedure for
Installing/Configuring Data Protector in a Oracle 9i RAC on HP-UX is available at the following location:
http://www.openview.hp.com/sso/searchdocs?prod=DATAPRO&ct=TWP
(12) Includes support for Red Hat Enterprise Linux Advanced Workstation and Enterprise Server
(13) To utilize this feature the following patches are required:
PHSS_29139 (for HP-UX Cell Manager)/ DPSOL_00023 (for Solaris Cell Manager)

2003 Hewlett-Packard Development Company, L.P. The information

contained herein is subject to change without notice. The only warranties for
HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed
as constituting an additional warranty. HP shall not be liable for technical or
editorial errors or omissions contained herein.
OV-ENXXXXXX, 01/2004

Copyright 2004

Page 30 of 30