Question

4. Restore and recover whole database

rman target=/

shutdown immediate;

startup mount;

restore database;

recover database;

alter database open;

Show each command you execute and the computer's response (example response:  Database Altered, Tablespace Created, etc.).  If you don't show the commands you execute, then your answer will be counted as wrong.

Format your output as necessary to make it easy to read.  Do not submit for grading anything you would not submit to your boss for review in an actual work environment, i.e. in other words, do not turn in sloppy work that is difficult for me to grade

Answer 1

To restore the server parameter file:

If the database is up at the time of the loss of the SPFILE, connect to the target database. For example, run:

% rman TARGET /

1. If the database is not up when the SPFILE is lost, and you are not using a recovery catalog, then you must set the DBID of the target database. See "Determining your DBID" for details on determining your DBID.

   1. Shut down the instance and restart it without mounting. When the SPFILE is not available, RMAN starts the instance with a dummy parameter file. For example:

      RMAN> STARTUP FORCE NOMOUNT;
      

      Restore the server parameter file. If restoring to the default location, then run:

      RMAN> RESTORE SPFILE FROM AUTOBACKUP; 
      

      If restoring to a nondefault location, then you could run commands as in the following example:

      RMAN> RESTORE SPFILE TO '/tmp/spfileTEMP.ora' FROM AUTOBACKUP;
      

   2. Restart the instance with the restored file. If restarting with a server parameter file in a nondefault location, then create a new client-side initialization parameter file with the single lineSPFILE=new_location, where new_location is the path name of the restored server parameter file. Then, restart the instance with the client-side initialization parameter file.

2. Performing Media Recovery of a Restored Database,

If you are not using a recovery catalog, you must restore your control file from an autobackup. If you want to restore the control file from autobackup, the database must be in a NOMOUNT state. You must first set the DBID for your database, and then use the RESTORE CONTROLFILE FROM AUTOBACKUP command:

RMAN> SET DBID 320066378;

RMAN> RUN 

    SET CONTROLFILE AUTOBACKUP FORMAT 

          FOR DEVICE TYPE DISK TO 'autobackup_format';

    RESTORE CONTROLFILE FROM AUTOBACKUP;

    }

RMAN uses the autobackup format and DBID to determine where to hunt for the control file autobackup. If one is found, RMAN restores the control file from that backup to all of the control file locations listed in theCONTROL_FILES initialization parameter.

Shutting Down with the IMMEDIATE Clause

To shut down a database immediately, use the SHUTDOWN command with the IMMEDIATE clause:

SHUTDOWN IMMEDIATE

an incomplete point-in-time recovery or recovery without a backup control file, it will be necessary to open the database with the OPEN RESETLOGS option as follows:

SQL> alter database open resetlogs;

Without the use of OPEN RESETLOGS, when using the RMAN catalog for future backups, the following command had to be issued to make the RMAN catalog aware of the new incarnation of the database