Restore an Oracle database

Restore a database using the management console

Restoring to the original database replaces the original production application data with the specified point-in-time image. This restoration results in the loss of all current application data as the application is restored to its status at the point-in-time when the image was created. This operation cannot be undone. The amount of time required to complete a restore operation depends on the amount of data involved. You can also restore a database to another target .

Use these instructions to restore an Oracle database using RMAN automatically from the management console, overwriting the original production database.

Open the management console to the App Managerand enter the database application name or use the filters to find the database image that you need.
Right-click the application and select Access.
On the Accesspage, select an image and click Restoreunder the Mountmenu.
On the Restorepage, select Traditional(not Mount and Migrate).
Use the Restore Rangeslider to a select a specific point in time to restore the database. Slide the slider tool all the way to the left to restore only the database with no logs applied.
At Usernameenter the Oracle software owner on the selected target server.
For Number of Channels, specify the number of RMAN channels to configure parallelism for database restore.
Click Submit.
A warning dialog appears. Read it and enter DATA LOSS to confirm.
The job is queued for the next available job slot. You can view progress from the Jobs Monitor.

Note: The backup plan options ( Run Schedule, Expire Data) of the database are disabled.

Restore a database to any target using the management console

Use these instructions to restore an Oracle database to a new target, using RMAN from the management console.

From the App Manager> Applicationslist, right-click the database and select Access.
Select the backup image to recover and choose Restore.
On the Restore page, select Traditional.
- Target: For all configurations, all eligible Oracle database servers are available to choose from the drop-down. Select the target server for the restore from the drop-down.
- Replace Original Application identity: This option is only available when restoring to a new server on the same appliance where the backup was originally generated.
- Yes: This replaces the original application and has the same application ID, job history, backup images, and backup plan as the original application.
- No: This does not replace the original application. The new database will be discovered as a new application as part of the Restore job.
- Rollforward time: Choose a date and time for a database protected with logs to recover to the required point in time.
- Application Options:
  - DATABASESID: This is pre-populated with the protected database SID name and is immutable.
  - USERNAME: This is pre-populated with source database Oracle software owner. Update the USERNAMEif the Oracle software owner on the selected target server is different.
  - ORAHOME: This is pre-populated with source database Oracle Home path. Update the Oracle Home directory if the Oracle home is different on the selected target server.
  - Advanced Options: This is pre-populated and displays all the database parameter settings (from pfile) at the source at backup time. Make sure the parameter value is correct for the target database server (source or new target) for restore.
Note: Make sure to verify that path-specific parameters (audit file dest, db create file dest) are available on the target server.
Mapping Options:
- Target Database Type: Select the database target type (ASM diskgroup or file system) for the database from the drop-down list. File system target type is not supported for backup images in ASM format.
  
  Source Database Backup image format Restore Target
  
  ASM
  ASM ASM
  
  ASM
  File system ASM
  
  File system
  File system File system
- Select target ASM diskgroup and file system mappings for three file types: the data files, the control files and the redo files for the database from the drop-down list.
Click Pre-Flight Check. If the pre-flight check fails, fix the issue and run the pre-flight check again.
Click Submitto submit the restore job.

Source Database	Backup image format	Restore Target
ASM	ASM	ASM
ASM	File system	ASM
File system	File system	File system

Recover an Oracle database manually using RMAN

To manually recover an Oracle database, refer to these procedures.

Non-RAC, Non-ASM, File System

Recover an Oracle database with data file on file system and protected under file-based staging disk format

Mount the image from the protected source database.

In the Mountwindow, Mapping Options, provide a mount location for the image, for example: /acttestdb . For instructions on how to mount a database image, see Mount an Oracle database image protected Under a file system for data access .

The database backup image is mounted at: /acttestdb

The protected archive log is mounted at: /acttestdb_Log
Set the Oracle environment and use sqlplus to shut down the database:
```
 sqlplus / as sysdba
sql> shutdown immediate; 
```
Verify the database is shut down. End any remaining processes for the database.
```
 ps -ef | grep database sid 
 
```
Start the database in nomount state using the backup parameter file from the mounted volume. The backup parameter file is under top mounted folder, for example /acttestdb

Set the Oracle environment and use sqlplus to start the database:

 sqlplus / as sysdba
sql> startup nomount pfile='/acttestdb/ database sid 
___backup.ora';

Create a new spfile from the existing pfile and restart the database.

Create an spfile from the pfile:

 create spfile='$ORACLE_HOME/dbs/spfile_ database sid 
.ora' from pfile='/acttestdb/ database sid 
___backup.ora';

Restart the database with spfile in nomount state:

 shutdown immediate;
startup nomount;

Restore the control file using RMAN from the Backup and DR mounted archive log image. Use the latest control file from the log mounted image, for example:

 /acttestdb_Log/cf D_ sid 
-id_ Target SID 
.ctl

or if there is more than one log image:

/acttestdb_Log_1/cf-D_ sid -id_ Target SID .ctl

   
 rman 
  
 target 
  
 / 
  
 restore 
  
 controlfile 
  
 from 
  
 '/acttestdb_Log_1/cf-D_<var>sid</var>-id_<var>id</var>.ctl' 
  
 ;

Mount the database:
```
 alter database mount; 
```

Catalog the datafile and archivelog folder from Backup and DR mounted database image and archive log image to RMAN:

 run {
     catalog start with '+acttestdg/ db_name 
/datafile' noprompt;
     catalog start with '+acttestdg/ db_name 
archivelog' noprompt;
     catalog start with ' mountpoint_log 
' noprompt;
     }

Restore and recover the database:

 run { restore database ; recover database; }

For a specific point in time recovery using the format yyyymmddhh24mi:

 run
    {
    restore database;
    recover database until time "to_date(' timestamp 
',' yyyymmddhh24mi 
')";
    }

Open the database with the reset log option.
- For primary database recovery:
```
 alter database open resetlogs; 
```
- For Data Guard standby database recovery, start the Data Guard managed recovery process:
```
 alter database recover managed standby database nodelay disconnect; 
```
The database is available for read and write.

RAC or Standalone ASM, File System

Recover an Oracle database with data file on ASM disk group and protected under file-based staging disk format

Mount the image from the protected source database.

In the Mount window under Mapping Options, provide a mount location for the image, for example: /acttestdb . For instructions on how to mount a database image, see Mounting an Oracle Database Image Protected Under a File System for Data Access .

The database backup image is mounted at the mount location: /acttestdb

The protected archive log is mounted at: /acttestdb_Log
Shut down the Oracle database. From node 1, su to Oracle OS user:

su - oracle

Set the Oracle environment and use srvctl to stop the database across all nodes:

srvctl stop database -d <var>database_name</var>

Verify the database is shutdown (all nodes). End any remaining processes for the database.

ps -ef | grep <var>database_name</var>
Start the database in no-mount state using the backup parameter file from the mounted volume. The backup parameter file is under the top mounted folder, for example at /acttestdb

Set the Oracle environment and use sqlplus to start the database:

  sqlplus 
  
 / 
  
 as 
  
 sysdba 
 startup 
  
 nomount 
  
 pfile 
 = 
 '/acttestdb/<var>database_name</var>___backup.ora' 
 ;

Create a new spfile and restart the database.

To get the path of original spfile under disk group:

cat $ORACLE_HOME/dbs/init{database sid}.ora

For example: spfile=+{preferred disk group}/ db_name /spfile db_name .ora`

   
 create 
  
 spfile 
 = 
 '+{preferred disk group}/{db name}/spfile<var>db_name</var>.ora' 
  
 from 
  
 pfile 
 = 
 '/acttestdb/<var>db_name</var>___backup.ora' 
 ;

Restart the database with spfile in nomount state:

   
 shutdown 
  
 immediate 
 ; 
  
 startup 
  
 nomount 
 ;

Restore the control file using RMAN from the Backup and DR mounted archive log image. Use the latest control file from the log mounted image, for example:

  / 
 acttestdb_Log 
 / 
 cf 
 - 
 D_<var>db_name 
< / 
 var 
> - 
 id_<var>db_id 
< / 
 var 
> . 
 ctl

or if you have more than one log image:

  / 
 acttestdb_Log_1 
 / 
 cf 
 - 
 D_<var>db_name 
< / 
 var 
> - 
 id_<var>db_id 
< / 
 var 
> . 
 ctl

   
 target 
  
 / 
  
 restore 
  
 controlfile 
  
 from 
  
 '/acttestdb_Log_1/cf-D_<var>db_name</var>-id_<var>db_id</var>.ctl' 
  
 ; 
  
 ```

Mount the database:
```
 alter database mount; 
```

Catalog the datafile and archivelog folder from Backup and DR mounted database image and archive log image to RMAN:

 run { catalog start with '/acttestdb/datafile' noprompt;
 catalog start with '/acttestdb/archivelog' noprompt;
 catalog start with '/acttestdb_Log' noprompt;}

Restore and recover the database:

 run { restore database ; recover database; }

For a specific point in time recovery using the format yyyymmddhh24mi:

   
 run 
  
 { 
  
 restore 
  
 database 
 ; 
  
 recover 
  
 database 
  
 until 
  
 time 
  
 "to_date('<var>timestamp</var>','yyyymmddhh24mi')" 
 ; 
  
 }

Open the database with the reset log option.

For primary database recovery:

 alter database open resetlogs;

RAC config requires another step after reset log: Shut down the database on node 1 and start the database across all nodes.

Use sqlplus to shut down the database:

   
 sqlplus 
  
 / 
  
 as 
  
 sysdba 
  
 shutdown 
  
 immediate 
 ; 
  
 ``` 
 Use 
  
 srvctl 
  
 to 
  
 start 
  
 the 
  
 database 
  
 across 
  
 all 
  
 nodes 
 : 
  
 ``` 
 srvctl 
  
 srvctl 
  
 start 
  
 database 
  
 - 
 d 
  
< var>database_name 
< / 
 var 
>  
 ``` 
 + 
  
 For 
  
 Data 
  
 Guard 
  
 standby 
  
 database 
  
 recovery 
 : 
  
 + 
  
 For 
  
 non 
 - 
 RAC 
  
 config 
 : 
  
 Start 
  
 the 
  
 Data 
  
 Guard 
  
 managed 
  
 recovery 
  
 process 
  
 ``` 
 rman 
  
 alter 
  
 database 
  
 recover 
  
 managed 
  
 standby 
  
 database 
  
 nodelay 
  
 disconnect 
 ; 
  
 ``` 
  
 + 
  
 For 
  
 RAC 
  
 config 
 : 
  
 Shut 
  
 down 
  
 the 
  
 database 
  
 on 
  
 node 
  
 1 
  
 and 
  
 start 
  
 the 
  
 database 
  
 in 
  
 mounted 
  
 state 
  
 across 
  
 all 
  
 nodes 
 . 
  
 1. 
  
 Use 
  
 sqlplus 
  
 to 
  
 shut 
  
 down 
  
 the 
  
 database 
 : 
  
 ``` 
 sqlplus 
  
 / 
  
 as 
  
 sysdba 
  
 shutdown 
  
 immediate 
 ; 
  
 ``` 
  
 1. 
  
 Use 
  
 srvctl 
  
 to 
  
 start 
  
 the 
  
 database 
  
 in 
  
 a 
  
 mount 
  
 state 
  
 across 
  
 all 
  
 nodes 
 : 
  
 ``` 
 srvctl 
  
 srvctl 
  
 start 
  
 database 
  
 - 
 d 
  
< var>database_name 
< / 
 var 
>  
 - 
 o 
  
 mount 
  
 ``` 
  
 1. 
  
 Start 
  
 the 
  
 Data 
  
 Guard 
  
 managed 
  
 recovery 
  
 process 
 : 
  
 ``` 
 rman 
  
 alter 
  
 database 
  
 recover 
  
 managed 
  
 standby 
  
 database 
  
 nodelay 
  
 disconnect 
 ; 
  
 ```

The database is available for read and write.

RAC or Standalone ASM, ASM Disk Group

Recover an Oracle database with data file on ASM disk group and protected under ASM disk group staging disk format

Mount the image from the protected source database. In the Mount window, provide a preferred disk group for the image mount under ASM on RAC Node 1. For details on how to mount a database image, see Mounting an Oracle Database Image Protected Under an ASM Disk Group for Data Access .

Note: OnVault pools pointing to backup vaults don't support mount operations.

For example, on the mount screen:
- Select Host: RAC node 1 database server
- Preferred disk group: acttestdg
- RAC node list: IP of RAC node 1
  
  The backup parameter file is copied under /act/touch/<var>preferred_disk_group</var>/ , for example:
  
  /act/touch/acttestdg/<var>database_name</var>___backup.ora

Shut down the Oracle database.

From node 1, su to Oracle OS user:

 su - oracle

Set the Oracle environment. Use srvctl to stop database across all nodes:

   
 srvctl 
  
 stop 
  
 database 
  
 - 
 d 
  
< var>database_name 
< / 
 var 
>

Verify the database is shut down (on all nodes). End any remaining processes for the database.

  ps 
  
 - 
 ef 
  
 | 
  
 grep 
  
< var>db_name 
< / 
 var 
>

Start the database in nomount state using the backup parameter file copied under /act/touch/acttestdg.

Set the Oracle environment. Use sqlplus to start the database:

  ``` 
 sqlplus 
 / 
  
 as 
  
 sysdba 
 startup 
  
 nomount 
  
 pfile 
 = 
 '/act/touch/acttestdg/<var>db_name</var>___backup.ora' 
 ; 
 ```

Create a new spfile and restart the database.

To get the path of original spfile under disk group:

 ```sqlplus
 cat $ORACLE_HOME/dbs/init(database sid).ora
 ```

For example: spfile=+ preferred disk group / db_name /spfile db_name .ora

   
 create 
  
 spfile 
 = 
 '+<var>preferred disk group</var>/<var>db_name</var>/spfile<var>db_name</var>.ora' 
  
 from 
  
 pfile 
 = 
 '/act/touch/acttestdg/<var>db_name</var>___backup.ora' 
 ;

Restart the database with spfile in nomount state:

 ```sql
 shutdown immediate;
 startup nomount;
 ```

Restore control file using RMAN from the Backup and DR mounted archive log image. Use the latest control file from Log mounted image, for example:
/acttestdb_Log/cf-D_<var>db_name</var>-id_<var>db_id</var>.ctl or if more than one log image exists:
/acttestdb_Log_1/cf-D_<var>db_name</var>-id_<var>db_id</var>.ctl
```
   
 ``` 
 rman 
  
 rman 
  
 target 
  
 / 
  
 restore 
  
 controlfile 
  
 from 
  
 '/acttestdg_Log_1/cf-D_<var>db_name</var>-id_<var>db_id</var>.ctl' 
  
 ; 
  
 ``` 
 
```
Mount the database:
```
 ```rman
 alter database mount;
 ``` 
```

Catalog the datafile and archivelog folder from Backup and DR mounted database image and archive log image to RMAN:

   
 ``` 
 rman 
  
 run 
  
 { 
  
 catalog 
  
 start 
  
 with 
  
 '+acttestdg/<var>db_name</var>/datafile' 
  
 noprompt 
 ; 
  
 catalog 
  
 start 
  
 with 
  
 '+acttestdg/<var>db_name</var>/archivelog' 
  
 noprompt 
 ; 
  
 catalog 
  
 start 
  
 with 
  
 '/acttestdg_Log' 
  
 noprompt 
 ;} 
  
 ```

Restore and recover the database:

 ```rman
 run { restore database ; recover database ; }
 ```

For a specific point in time recovery run the recover command as under:

   
 ``` 
 rman 
  
 run 
  
 { 
  
 restore 
  
 database 
 ; 
  
 recover 
  
 database 
  
 until 
  
 time 
  
 "to_date('<var>timestamp</var>','yyyymmddhh24mi')" 
 ; 
  
 } 
  
 ```

Open the database with the reset log option.
- For primary database recovery:
```
 alter database open resetlogs; 
```
  RAC config requires another step: After reset log, shut down the database on node 1 and start the database across all nodes. Use sqlplus to shut down the database:
```
 / as sysdba
 shutdown immediate; 
```
  Use srvctl to start database across all nodes:
```
   
 start 
  
 database 
  
 - 
 d 
  
< var>database_name 
< / 
 var 
> 
```
- For Data Guard standby database recovery:
  - For non-RAC config: Start the Data Guard managed recovery process:
```
 alter database recover managed standby database nodelay disconnect; 
```
  - For RAC config: Shut down the database on node 1 and start the database in mounted state across all nodes.
    1. Use sqlplus to shut down the database:
      as sysdba shutdown immediate;
    2. Use srvctl to start the database in a mount state across all nodes:
      start database - d < var>database_name < / var > - o mount
    3. Start the Data Guard managed recovery process:
      alter database recover managed standby database nodelay disconnect;
The database is available for read and write.

Recover Oracle tablespace and data files

To recover a single tablespace data file, for example, due to data corruption:

Mount the latest database snapshot from the backup/recovery appliance back to the Oracle server.

Note: OnVault pools pointing to backup vaults don't support mount operations.
Catalog the database backup snapshot to RMAN.
Restore and recover the tablespace using the backup snapshot as detailed here.

Recover a single tablespace of a production database on an ASM Disk Group

To recover a single tablespace of a production database to the primary node:

Mount the database point-in-time snapshot as detailed in Mount an Oracle database as a standard mount .
In the Mount window under Mapping Options, provide a mount location for the image. For example, for an image under ASM disk group provide a disk group name under Preferred Disk Group and for image under file system provide a mount location such as /acttestdb .

Note: OnVault pools pointing to backup vaults don't support mount operations.
- For instructions on how to mount a database image protected under file system, see Mount an Oracle database image protected under a file system for data access .
- For details on how to mount a database image protected under ASM Disk Group, see Mount an Oracle database image protected under an ASM disk group for data access .
From the primary node, log into the database server as Oracle OS user.
Set the database environment and log into RMAN:
```
 rman target / 
```

At the RMAN prompt, catalog the backup data file and archive log folder:

Example: A database image protected under ASM Disk Group: (Mounted ASM Disk Group name " + acttestdg"):

  ``` 
 rman 
 catalog 
  
 start 
  
 with 
  
 '+acttestdg/<var>db_name</var>/datafile' 
  
 noprompt 
 ; 
 catalog 
  
 start 
  
 with 
  
 '+acttestdg/<var>db_name</var>/archivelog' 
  
 noprompt 
 ; 
 catalog 
  
 start 
  
 with 
  
& #8216;/<var>mountpoint_log</var>'; noprompt; 
 ( 
 If 
  
 archivelogs 
  
 are 
  
 protected 
  
 by 
  
 Backup 
  
 and 
  
 DR 
 ) 
 ```

Example: A database image protected under file system (mounted file system name "/acttestdb"):

 ```rman
catalog start with '/acttestdb/datafile' noprompt;
catalog start with '/acttestdb/archivelog'
noprompt;
catalog start with '/acttestdb_log/archivelog' noprompt;
```

(If archivelogs are protected by Backup and DR)

Now you can run all RMAN recovery commands, such as:

Recover a tablespace
Recover a datafile
Recover a corrupt database block
Recover lost control files
Recover an Oracle pluggable database

When finished, unmount and delete the image.

Recover a tablespace

To recover a tablespace:

   
 ``` 
 rman 
  
 restore 
  
 tablespace 
  
< var>tablespace 
  
 name 
< / 
 var 
> ; 
  
 recover 
  
 tablespace 
  
< var>tablespace 
  
 name 
< / 
 var 
> ; 
  
 ```

Recover a datafile

To recover a datafile:

   
 ``` 
 rman 
  
 restore 
  
 datafile 
  
< var>file 
 #</var>; 
  
 recover 
  
 datafile 
  
< var>file 
 #</var>; 
  
 ```

Recover a corrupt database block

To recover a corrupt database block:

Mount the database point-in-time snapshot as detailed in Mount an Oracle database as a standard mount .
In the Mountwindow, Mapping Options, provide a mount location for the image. For example, for an image in an ASM disk group provide a disk group name under Preferred Disk Group and for image in a file system provide a mount location ex: /acttestdb.
- For instructions on how to mount a database image protected under file system, see Mount an Oracle database image protected under file system for data access .
- For details on how to mount a database image protected under an ASM Disk Group, see Mount an Oracle database image protected under an ASM disk group for data access .
From the primary node, log into the database server as Oracle OS user.
Set the database environment and log into sqlplus, then query v$database_block_corruption to check the corrupt blocks:
```
 ```sh
sqlplus / as sysdba
sql> SELECT * FROM V$DATABASE_BLOCK_CORRUPTION;
``` 
```
Login to RMAN to recover all corrupted blocks:
```
 ```rman
rman target /
RECOVER CORRUPTION LIST;
``` 
```
After the blocks are recovered, the database removes them from V$DATABASE_BLOCK_CORRUPTION.
To recover an individual corrupt block (for example: datafile 8 and block 13):

From RMAN prompt
```
 ```rman
recover datafile 8 block 13;
``` 
```

Recover lost control files

To recover lost control files:

Mount the database point-in-time snapshot as detailed in Mount an Oracle database as a standard mount .
In the Mountwindow, Mapping Options, provide a mount location for the image. For example, for an image under ASM disk group provide a disk group name under Preferred Disk Group and for an image under file system provide a mount location such as /acttestdb .
- For instructions on how to mount a database image protected under file system, see Mount an Oracle database image protected under a file system for data access .
- For details on how to mount a database image protected under ASM Disk Group: see Mounting an Oracle Database Image Protected Under an ASM Disk Group for Data Access .
From the primary node, log into the database server as Oracle OS user.

Set the database environment and log into sqlplus, then shut down the database and start in nomount state:

For standalone database:

 ```sql
sqlplus / as sysdba
sql> shutdown immediate;
sql> startup nomount;
```

For RAC database from the mounted image node shutdown the database across all nodes:

  ``` 
 sh 
 srvctl 
  
 stop 
  
 database 
  
 - 
 d 
  
< var>db_name 
< / 
 var 
> sql 
>  
 startup 
  
 nomount 
 ; 
 ```

Restore the control file from Backup and DR mounted image.

For example: /acttestdb (file system) and +acttestdg (for ASM)

  ``` 
 rman 
 rman 
  
 target 
  
 / 
 restore 
  
 controlfile 
 from 
  
 '/acttestdb/cf-D_<var>db_name</var>-id_<var>db_id</var>.ctl' 
  
 ; 
  
 ( 
 Filesystem 
 mount 
 ) 
 restore 
  
 controlfile 
 from 
  
 '+acttestdb/cf-D_<var>db_name</var>-id_<var>db_id</var>.ctl' 
  
 ; 
  
 ( 
 ASM 
 mount 
 ) 
 ```

Mount and open the database from sqlplus:

 ```sql
sqlplus / as sysdba
sql> alter database mount;
sql> recover database until cancel;
sql> alter database open resetlogs;
```

Recover an Oracle pluggable database

To recover an Oracle 12c or later pluggable database (PDB):

Mount the image from the source database server to recover. In the Mountwindow, provide a preferred disk group for the image mount under ASM on RAC Node 1. For details on how to mount a database image, see Mount an Oracle database image protected under ASM Disk Group for data access .

Note: OnVault pools pointing to backup vaults don't support mount operations.

Close the pluggable database:

From Node 1, su to Oracle User
```
 su  
-  
oracle 
```

Set the Oracle environment. Connect to the Oracle database as "sysdba" user:

   
 / 
  
 as 
  
 sysdba 
  
 alter 
  
 pluggable 
  
 database 
  
< var>pluggable_db_name 
< / 
 var 
>  
 close 
 ;

Catalog the datafile and archivelog folder from Backup and DR mounted database image and archive log image to RMAN:

   
run  
 { 
  
catalog  
start  
with  
 '+acttestdg/<var>db_name</var>/datafile' 
  
noprompt ; 
  
catalog  
start  
with  
 '+acttestdg/<var>db_name</var>/archivelog' 
  
noprompt ; 
  
catalog  
start  
with  
 '/acttestdg_Log' 
  
noprompt ; 
  
 }

Restore and recover the pluggable database
```
   
run  
 { 
  
restore  
pluggable  
database  
<var>pluggable_db_name</var> ; 
  
recover  
pluggable  
database  
<var>pluggable_db_name</var>  
 until 
  
 time 
  
 "to_date('<var>required time stamp</var>>';,';yyyymmddhh24mi')" 
 ; 
  
 } 
 
```
Note: These steps are applicable only for Oracle 12.1.0.2 version and later. If Oracle version is 12.1.0.1 or earlier 12.1.0.2, then recovery of all datafiles belonging to the pluggable database must be performed before you open the pluggable database in the next step. For example: rman> recover datafile <PDB datafile number>;

Open the pluggable database:

   
alter  
pluggable  
database  
<var>pluggable_db_name</var>  
open ;

The pluggable database is open for read and write.

Restore an Oracle database Stay organized with collections Save and categorize content based on your preferences.

Restore a database using the management console

Restore a database to any target using the management console

Recover an Oracle database manually using RMAN

Non-RAC, Non-ASM, File System

RAC or Standalone ASM, File System

RAC or Standalone ASM, ASM Disk Group

Recover Oracle tablespace and data files

Recover a single tablespace of a production database on an ASM Disk Group

Recover a tablespace

Recover a datafile

Recover a corrupt database block

Recover lost control files

Recover an Oracle pluggable database

The Oracle DBA guide

Restore an Oracle database