Security Link SL150 Bedienungsanleitung PDF herunterladen (Seite 22)

Protecting Oracle Database Appliance - Tape Backup with Oracle Secure Backup

Restoring the Database

In the event of a logical database corruption, or a complete disaster, restoration of the database from tape can be

executed. In most instances the Database Administrator (DBA) will be conducting the restoration, and will be

executing the restore job from the machine where the database resides. The DBA will use RMAN to request the

needed backup pieces from the Oracle Secure Backup Media Management Layer. The RMAN backup pieces are

cataloged in the controlfile, or RMAN Catalog if using Recovery Manager with catalog, and Oracle Secure Backup

also knows about the pieces in its own catalog. If a complete disaster has occurred and the Oracle Database

Appliance has been re-imaged, you will also require the DBID of your database to perform the restore.

Restore Demonstration

There are many different restore scenarios available with RMAN, depending on the type of problem encountered

in the database (consult RMAN documentation for complete information). For this example, assume that one or

more controlfiles are damaged and so are some of the data files that under lie the database. Also assume all

archive logs are intact in the Fast Recovery Area (FRA). The basic steps in the RMAN restore process are to

restore the controlfile, restore the database, and then recover the database. After the controlfile is restored, the

database will know which backup pieces are needed based on data contained in the restored controlfile. If the

archive logs are still available in the FRA you can use them to recover up to present or to a specific point in time

(they are available in this example).

Example of steps to restore and recover database:

**From hamms1 execute the following**

[root@hamms1 /]# su - oracle

[oracle@hamms1 ~]$ rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Thu Jul 18 14:38:06 2013

connected to target database: ISR (DBID=2637695581)

RMAN> shutdown immediate;

using target database controlfile instead of recovery catalog

database closed

database dismounted

Oracle instance shut down

** Also login to hamms2 with SQL Plus and execute a shutdown immediate;**

[root@hamms2 /]# su - oracle

[oracle@hamms2 ~]$ sqlplus / as sysdba

SQL> shutdown immediate;

RMAN> startup nomount;

connected to target database (not started)

Oracle instance started

1 2 ... 17 18 19 20 21 22 23 24 25 26 27 ... 30 31

Keine Kommentare

Security Link SL150 Bedienungsanleitung Seite 22