HP Data Protector A.06.11 Integration Manual page 230

For oracle and sap
Hide thumbs Also See for Data Protector A.06.11:
Table of Contents

Advertisement

2.
Verify that a backup object exists on the backup media and in the IDB:
This can be done by executing the command
/opt/omni/bin/omnidb -SAP "object_name" -session
"Session_ID" -media (HP-UX, Solaris, and Linux systems) or
/usr/omni/bin/omnidb -SAP "object_name" -session
"Session_ID" -media (other UNIX systems)
on the SAP Database Server system.
The output of the command lists detailed information about the specified backup
object, session IDs of the backup sessions containing this object, and a list of
the media used.
For detailed syntax of the omnidb command, run:
/opt/omni/bin/omnidb -help (HP-UX, Solaris, and Linux systems)
/usr/omni/bin/omnidb -help (other UNIX systems)
You can also do this using the SAP tools:
Use backint, so that SAP tools will also use this command to query:
/opt/omni/lbin/backint -f inquiry -u ORACLE_SID -i
input_file (HP-UX, Solaris, and Linux systems)
/usr/omni/bin/backint -f inquiry -u ORACLE_SID -i
input_file (other UNIX systems)
where the specified input_file is queried.
If this fails, check if the backup session was performed successfully and if the
query was started under the appropriate user account.
Backint anticipates a list of files of the following format:
backup_ID_1 pathName_1 [targetDirectory_1]
backup_ID_2 pathName_2 [targetDirectory_2]
backup_ID_3 pathName_3 [targetDirectory_3]
To retrieve the backup_ID numbers, enter the following command:
echo "#NULL #NULL" | backint –f inquiry –u ORACLE_SID
or, alternatively, you can just specify #NULL as backup_ID_1 in the
input_file. In this case, the latest backup session for the file is used for the
restore.
230
Integrating SAP R/3 and Data Protector

Advertisement

Table of Contents
loading

Table of Contents