HP (Hewlett-Packard) B6960-96008 Garage Door Opener User Manual


 
Integrating SAP R/3 and Data Protector
Troubleshooting
Chapter 2 233
To get the error description, start the command:
/opt/omni/lbin/omnigetmsg 12 <Error_number> (HP-UX and
Solaris systems) or
/usr/omni/bin/omnigetmsg 12 <Error_number> (other UNIX
systems)
The *RETVAL*0 indicates successful configuration.
2. 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 SAP R/3 Database Server. Check the
/etc/opt/omni/client/cell_server (HP-UX and Solaris systems)
or /usr/omni/config/cell/cell_server (other UNIX systems) file,
which contains the name of the Cell Manager system. Then run the
following command:
/opt/omni/bin/utilns/testbar2 -type:SAP
-appname:<ORACLE_SID> -bar:<backup_specification_name>
-perform:backup (HP-UX and Solaris systems)
/usr/omni/bin/utilns/testbar2 -type:SAP
-appname:<ORACLE_SID> -bar:<backup_specification_name>
-perform:backup (other UNIX systems)
Examine the errors reported by the testbar2 utility by clicking the
Details button in the Data Protector Monitor context.
If the messages indicate problems concerning the Data Protector side
of the integration, proceed as follows:
a. Check that the owner of the backup specification is the SAP R/3
backup owner as described in the “Configuring an SAP R/3 User in
Data Protector (UNIX Systems Only)” on page 165 and that this
user belongs to the Data Protector operator or admin group.
b. Check that the respective Data Protector user group has the See
private objects user right enabled.
c. Create an SAP R/3 backup specification to back up to a null or file
device. If the backup succeeds, the problem may be related to the
backup devices.
Refer to the HP OpenView Storage Data Protector Troubleshooting
Guide for instructions on troubleshooting devices.