RMAN Restore and Recovery - Oracle RMAN for Absolute Beginners - page 184

job_queue_processes=10
memory_max_target=300000000
memory_target=300000000
open_cursors=100
os_authent_prefix=''
processes=100
remote_login_passwordfile='EXCLUSIVE'
resource_limit=true
shared_pool_size=80M
sql92_security=TRUE
undo_management='AUTO'
undo_tablespace='UNDOTBS1'
workarea_size_policy='AUTO'

■ If this were an oracle 10g example, you would need to set the parameters background_dump_dest ,
user_dump_dest , core_dump_dest .

Note

Step 6. Create Any Required Directories for Data Files, Control Files, and
Dump/Trace Files
For this example the directories /ora01/dbfile/DEVDB and /ora01/oraredo/DEVDB are created:

$ mkdir -p /ora01/dbfile/DEVDB
$ mkdir -p /ora01/oraredo/DEVDB
$ mkdir -p /ora01/arc/DEVDB

Step 7. Start Up the Database in Nomount Mode
You should now be able to start up the database in nomount mode:

$ rman target /
RMAN> startup nomount;

Step 8. Restore the Control File from the RMAN Backup
Next, restore the control file from the backup that was previously copied; for example,

RMAN> restore controlfile from
'/ora01/rman/DEVDB/rman_ctl_c-3423216220-20130113-06.bk';

The control file will be restored to all locations specified by the CONTROL_FILES initialization parameter. Here is
some sample output:

channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/ora01/dbfile/DEVDB/control01.ctl
output file name=/ora01/dbfile/DEVDB/control02.ctl