Control file is one of Oracle's physical files that records information such as the name of the database, the location of the data file, and so on. The importance of the control file is that once the control file is corrupted, the database will be down. If there are no backup and archive log files for the database, the database cannot be recovered. As a result, we should mirror the control files in multiple ways (multiplex control files) and distribute each mirror's controlled file across different physical disks. Based on experience, the possibility of several control files being broken at the same time is almost zero, after controlling the file multipath image. The focus of control file management is on prevention, not on the mend! Do this today in the test environment to create a Multipath image control file for controlling files! Environment: RHEL6.4 ORACLE 11.2.0.3 RAC1: View current Control file:sql> select * from V$controlfile; STATUS NAME is_ block_size file_size_blks------------------------------------------------------------------------- ---------------------+system/gtsdb/controlfile/current.260.870609283 NO 16384 11282. Modify the control file parameters in SPFile sql> alter system set control_files= ' +system/gtsdb/controlfile/current.260.870609283 ', ' +archive ', ' +data ' scope=spfile; System Altered.3: Stop database srvctl stop database-d GTSDB 4: Boot db instance to Nomount State startup nomount5: Using Rman to restore Controlfile[[email protected] ~]$ rman target/recovery manager:release 11.2.0.3.0-production on Sat Feb 7 11:48:15 2015Copyright (c ) 1982, the Oracle and/or its affiliates. All rights reserved.connected to TARget Database:gtsdb (not mounted) rman> restore controlfile from ' +system/gtsdb/controlfile/current.260.870609283 '; Starting restore at 2015/02/07 11:48:22using target database control file instead of recovery catalogallocated channel:or A_disk_1channel ora_disk_1:sid=1425 instance=gtsdb1 Device type=diskchannel ora_disk_1:copied control file Copyoutput F Ile name=+system/gtsdb/controlfile/current.260.870609283output File name=+archive/gtsdb/controlfile/ Current.259.871040903output file name=+data/gtsdb/controlfile/current.258.871040903finished Restore at 2015/02/07 11:48:26rman> rman> rman> SQL ' ALTER DATABASE mount '; SQL Statement:alter database mountreleased Channel:ora_di sk_1rman> SQL ' ALTER DATABASE open '; SQL Statement:alter database openrman> exitrecovery Manager complete. [[email protected] ~]$ sqlplus/as sysdbasql*plus:release 11.2.0.3.0 Production on Sat Feb 7 11:49:10 2015Copyright (c) 1982, Oracle. All rights reserved. Connected to:oracle DataBase 11g Enterprise Edition Release 11.2.0.3.0-64bit productionwith The partitioning, Real application Clusters, Automat IC Storage Management, Olap,data Mining and Real application testing optionssql> select Open_mode,name from V$database; Open_mode name-----------------------------READ WRITE gtsdbsql> select NAME from V$controlfile; NAME--------------------------------------------------------------------------------+system/gtsdb/controlfile/ current.260.870609283+archive/gtsdb/controlfile/current.259.871040903+data/gtsdb/controlfile/ current.258.8710409036: Start the Node 2 instance!
Oracle 11g Add control files on ASM disk groups