Control File restoration scenario 1: rebuilding control File www.2cto.com • You 've experienced a failure and lost all of your control files, and you
Belatedly realizethat you don't have a good binary backup of the control file. • You want to change a database setting that can be modified only
Re-creating the con-trol file. • You are relocating a large number of datafiles, and you find it easier
To re-create the control file with the new names and locations
(Instead of manually renaming the datafiles) solution: rebuilding Control FIles [SQL] SQL> show parameter user_dump_dest NAME TYPE VALUE types -------------------------------------- user_dump_dest string/u01/app/oracle/diag/rdbms/pur ple/purple1/trace skills: naming a trace file Trace file naming rules . Trc, we can identify by setting tracefile_identifier
Do not Trace files. Www.2cto.com SQL> alter session set tracefile_identifier = mytrace Session altered. SQL> select distinct tracefile from v $ process p, v $ session s,
V $ mystat m where p. addr = s. paddr and s. sid = m. sid ;--
View the current TraceFile TRACEFILE examples/u01/app/oracle/diag/rdbms/purple/purple1/trace/purplew.ora _
14669_MYTRACE.trc startup nomount create controlfile reuse database "PURPLE"
Resetlogs archivelog maxlogfiles 192 MAXLOGMEMBERS 3 MAXDATAFILES 1024 MAXINSTANCES 32 MAXLOGHISTORY 292 logfile group 1 '+ DATA/purple/onlinelog/group_1.257.805043621'
SIZE 50 m blocksize 512, GROUP 2' + DATA/purple/onlinelog/group_2.258.805043623'
SIZE 50 mb blocksize 512 -- standby logfile datafile '+ DATA/purple/datafile/system.264.805043525', '+ DATA/purple/datafile/sysaux.262.805043527 ', '+ DATA/purple/datafile/undotbs1.256.805043527', '+ DATA/purple/datafile/users.260.805043527', '+ DATA/purple/datafile/comment' character set ZHS16GBK; startup nomount create controlfile reuse database "PURPLE"
Noresetlogs archivelog maxlogfiles 192 MAXLOGMEMBERS 3 MAXDATAFILES 1024 MAXINSTANCES 32 MAXLOGHISTORY 292 logfile group 1' + DATA/purple/onlinelog/group_1.257.805043621'
SIZE 50 m blocksize 512, GROUP 2' + DATA/purple/onlinelog/group_2.258.805043623'
SIZE 50 m blocksize 512, GROUP 3' + DATA/purple/onlinelog/group_3.271.805043939'
SIZE 50 m blocksize 512, GROUP 4' + DATA/purple/onlinelog/group_4.272.805043941'
SIZE 50 mb blocksize 512 -- standby logfile datafile '+ DATA/purple/datafile/system.264.805043525', '+ DATA/purple/datafile/sysaux.262.805043527 ', '+ DATA/purple/datafile/output',' + DATA/purple/datafile/users.260.805043527 ',' + DATA/purple/datafile/CHARACTER 'character SET ZHS16GBK; Scenario 2: multiplexing Control File restoration [SQL] SQL> startup ORACLE instance started. total System Global Area 16535183 36 bytes Fixed Size 2213896 bytes Variable Size 1090521080 bytes Database Buffers 553648128 bytes Redo Buffers 7135232 bytes ORA-00205: error in identifying control file, check alert log for more info check alter. log ORA-00210 :??????????? ORA-00202 :????: ''+ DATA/purple/controlfile/current03'' ORA-17503: ksfdopn: 2 ?????? + DATA/purple/controlfile/current03 ORA-15173: entry 'current03' does not exist in directory 'controlfile' SQL> alter system set control_files = '+ DATA/purple/controlfile
/Current01 ',' + DATA/purple/controlfile/current02 'scope = spfile
Sid = '*'; -- modify control Files System altered. SQL> startup SQL> shutdown immediate ASMCMD> cp current02 current03 -- copy the control file copying + data/purple/controlfile/current02-> + data/purple
/Controlfile/current03 SQL> startup nomount; SQL> alter system set control_files = '+ DATA/purple
/Controlfile/current01 ',' + DATA/
Purple/controlfile/current02', '+ DATA/purple/controlfile
/Current03 'scope = spfile id = '*'; Scenario 3: Use RMAN to restore Control Files [SQL] RMAN> restore controlfile to '+ DATA/purple/controlfile
/Current04 'from' + DATA/purple/controlfile/current01 '; Starting restore at 22-JAN-2013 11:12:29 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID = 194 instance = purple1 device type = DISK channel ORA_DISK_1: copied control file copy Finished restore at 22-JAN-2013 11:12:33 [SQL]