Restore Problems
6. Try putting the database into the Open state manually after using the Data Protector GUI to recover and restore a backup
session.
If you have used the Data Protector GUI to recover and restore a backup session, 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:
sqlplus/nolog
SQL>connect <user>/<password>@<service> as sysdba SQL>alter database open noresetlogs;
If this does not work try using the following command:
SQL>alter database open resetlogs;
Problem “Binary util_orarest is missing” error message is displayed when browsing Oracle 9i database for restore on Linux
The following error message is displayed when browsing Oracle9i database for restore on Linux:
Binary util_orarest is missing. Cannot get information from the remote host.
Action Start the following command:
/usr/omni/bin/util_orarest.exe -objs0 <DB_NAME>
If the command core dumps, make sure that the libc version is 2.3.2-23 or higher. This should eliminate the problem.
Problem “Binary util_orarest failed” error message is displayed when browsing Oracle 9i database for restore on Linux
The following error message is displayed when browsing Oracle9i 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
1. Rename the util_orarest.exe to util_orarest.exe.orig 2. Rename the util_orarest9.exe to util_orarest.exe
Problem The Recovery Catalog was lost and the control file cannot be restored from Data Protector managed backup
The Recovery Catalog was not used, the RMAN autobackup feature was not used (for Oracle 9i/10g), and the control file cannot be restored from Data Protector managed backup. A valid control file backup exists on tape.
Action • For Oracle 8i, restore the control file from RMAN backupset with the following SQL script:
dbms_backup_restore.restorebackuppiece('<backup piece handle>',done=>done);
END;
For the <backup piece handle> search the Data Protector internal database and session outputs of previous backup sessions.
Use the following RMAN script to copy the control file, mount and restore the database, and perform a database recovery:
run {
allocate channel 'dev_0' type disk;
replicate controlfile from '/tmp/foo.cf';
sql 'alter database mount';
set until time 'MMM DD YY HH24:MM:SS';
restore database;
recover database;
sql 'alter database open resetlogs';
release channel 'dev_0';
}
At this point you must manually register any backups made after the control file backup that was restored. After that, continue with the restore procedure.
• For Oracle 9i/10g, restore the control file from RMAN backup set, mount and restore the database, and perform a database recovery:
run {
allocate channel 'dev_0' type 'sbt_tape';
restore controlfile from '<backup piece handle>';
sql 'alter database mount';
set until time 'MMM DD YY HH24:MM:SS';
restore database;
recover database;
sql 'alter database open resetlogs';
release channel 'dev_0';
}
At this point you must manually register any backups made after the control file backup that was restored. After that, continue with the restore procedure.
For the <backup piece handle> search the Data Protector internal database and session outputs of previous backup sessions.
Problem Shared library that provides thread local storage cannot be loaded
The problem occurs with Oracle8i on HP-UX 11.11.
When, during restore, Data Protector attempts to dynamically load a shared library that provides thread local storage, an error similar to the following is displayed:
Can’t dlopen() a library containing Thread Local Storage:
<ORACLE_HOME>/JRE/lib/PA_RISC/native_threads/libjava.sl The problem occurs when the Radius Authentication Adapter is installed. In this case, libclntsh.sl is dynamically linked with the library libjava.sl that provides thread local storage.
Action Uninstall the Radius Authentication Adapter to remove libjava.sl from the list of dynamic libraries for libclntsh.sl. See
OracleMetaLink, DOC ID: 113395.1 for information on how to uninstall the Radius Authentication Adapter.
Protector
In This Chapter
This chapter explains how to configure and use the Data Protector SAP R/3 integration.
The chapter is organized into the following sections:
“Introduction” on page 145
“Prerequisites and Limitations” on page 147
“Integration Concept” on page 149
“Data Protector SAP R/3 Configuration File” on page 158
“Configuring the Integration” on page 165
“Configuring an SAP R/3 Backup” on page 179
“Backing Up an SAP R/3 Database” on page 197
“Restoring an SAP R/3 Database” on page 204
“Monitoring an SAP R/3 Backup and Restore” on page 212
“Troubleshooting” on page 214
“Examples of SAP R/3 Database Restore” on page 239
Introduction
Data Protector integrates with the SAP R/3 Database Server to offer online backup of your SAP R/3 databases.
If the SAP R/3 system uses an Oracle database, then the Data Protector SAP R/3 integration can be used for backup. If any other database is used by SAP, then the corresponding Data Protector integration of that database (for example, Informix) must be used instead.
Refer to the HP OpenView Storage Data Protector Product Announcements, Software Notes, and References or
http://www.hp.com/support/manuals for up-to-date information about platforms supported by the integration.
The online backup concept is now widely accepted because it addresses the business requirements of high application availability. During backup, the database is online and actively used. The backup is performed quickly and efficiently, with the least possible impact on database performance.
The SAP R/3 part of the integration provides storage management utilities. These utilities communicate with Data Protector via the Data Protector backint executable, which complies with the SAP R/3 backup interface.
Advantages Using Data Protector with the SAP R/3 Database Server offers several advantages over using SAP R/3 alone:
• Central Management for all backup operations
You can manage backup operations from a central point. This is especially important in large business environments.
• Backup Management
Backed up data can be duplicated during or after the backup to increase fault tolerance of backups, to improve data security and availability, or for vaulting purposes.
• Media Management
Data Protector has an advanced media management system that allows you to keep track of all media and the status of each medium, set the protection for stored data, fully automate operations as well as organize and manage devices and media.
• Scheduling
Data Protector has a built-in scheduler that allows you to automate backups to run periodically. With the Data Protector scheduler, the backups you configure run unattended at the periods you specify.
• Local versus Network Backups
When configuring an SAP R/3 backup, the location of devices is completely transparent to the user. They can be connected to the SAP R/3 Database Server or any other Data Protector clients on the network.
• Device Support
Data Protector supports a wide range of devices, from standalone drives to complex multiple drive libraries. Refer to the HP OpenView Storage Data Protector Product Announcements, Software Notes, and References or http://www.hp.com/support/manuals for an up-to-date list of supported devices and other information.
• Reporting
Data Protector has reporting capabilities that allow you to receive information about your backup environment. You can schedule reports to be issued at a specific time or attached to a predefined set of events, such as the end of a backup session or a mount request.
• Monitoring
Data Protector has a feature that allows you to monitor currently running sessions and view finished sessions from any system that has the Data Protector User Interface installed.
All backup sessions are logged in the built-in IDB, providing you with a history of activities that can be queried at a later time.