Integrating SAP R/3 and Data Protector

Troubleshooting

• On other UNIX: /usr/omni/bin/backint -f restore -u

 

<ORACLE_SID> -i <input_file>

 

where the contents of the <input_file> will be restored.

 

If this fails, check if the session was performed successfully and if the

 

restore was started under the appropriate user account.

 

Backint anticipates a list of files in 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>

 

Restore of SAP R/3 Tablespaces Located on Raw Partitions Fails

Problem

When restoring SAP R/3 tablespaces that are located on raw partitions

 

using the Data Protector GUI, the restore fails with a message similar to

 

the following:

 

[Major] From: VRDA@joca.company.com "SAP" Time: 5/9/06

 

3:33:51 PM

 

/dev/sapdata/rsapdata

 

Cannot restore -> rawdisk section !

 

[Warning] From: VRDA@joca.company.com "SAP" Time: 5/9/06

 

3:42:45 PM

 

Nothing restored.

Action

Use SAP R/3 commands (for example, brrestore) to restore these

 

tablespaces.

238

Chapter 2