Datasheet

Using ASM Storage
39
NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ‘C:\ORACLE\ORADATA\11GDB\REDO01.LOG’ SIZE 50M,
GROUP 2 ‘C:\ORACLE\ORADATA\11GDB\REDO02.LOG’ SIZE 50M,
GROUP 3 ‘C:\ORACLE\ORADATA\11GDB\REDO03.LOG’ SIZE 50M
-- STANDBY LOGFILE
DATAFILE
‘C:\ORACLE\ORADATA\11GDB\SYSTEM01.DBF’,
‘C:\ORACLE\ORADATA\11GDB\UNDOTBS01.DBF’,
‘C:\ORACLE\ORADATA\11GDB\SYSAUX01.DBF’,
‘C:\ORACLE\ORADATA\11GDB\USERS01.DBF’,
‘C:\ORACLE\ORADATA\11GDB\EXAMPLE01.DBF’,
‘C:\ORACLE\ORADATA\11GDB\PART_ASM_TBS_01.DBF’,
‘+COOKED_DGROUP1/11GDB/datafile/part_asm_tbs.256.613066047’,
‘+COOKED_DGROUP1/11GDB/datafile/part_asm_tbs.257.613083267’
CHARACTER SET WE8MSWIN1252;
SQL>RECOVER DATABASE;
SQL>ALTER DATABASE OPEN NORESETLOGS;
You can also use RMAN to restore the control file to an ASM disk location, as shown in
this example (this assumes you are connected to a recovery catalog):
SQL> alter system set control_files=’’ scope=SPFILE;
SQL> alter system set
DB_CREATE_FILE_DEST=’+COOKED_DGROUP1’ scope=spfile;
RMAN>shutdown
RMAN>startup nomount
RMAN>restore controlfile;
RMAN>recover database;
RMAN>alter database open resetlogs;
If you are using autobackups, then the process is slightly different:
SQL> alter system set control_files=’’ scope=SPFILE;
SQL> alter system set
DB_CREATE_FILE_DEST=’+COOKED_DGROUP1’ scope=spfile;
95134c01.indd 39 1/28/09 9:43:46 AM