Oracle 11g adds a control file to the ASM disk, 11 gasm

Oracle 11g adds a control file to the ASM disk, 11 gasm

A Control File is one of Oracle physical files. It records the database name, data File location, and other information. The importance of the control file is that the database will go down once the control file is corrupted. The database cannot be recovered without the backup and archiving log files of the database. Therefore, we should use Multiplex Control Files to distribute the Control Files of each image on different physical disks. Based on experience, after multi-channel image control files are controlled, the possibility of several control files being damaged at the same time is almost zero. The focus of controlling file management is to focus on prevention, rather than making up for it!

Create a multi-path image control file for the control file in the test environment today!

Environment: RHEL6.4 ORACLE 11.2.0.3 RAC

1: view the current control file:

SQL> select * from V $ CONTROLFILE; STATUS NAME IS _ BLOCK_SIZE FILE_SIZE_BLKS

----------------------------------------------------------------------------------------------

+ SYSTEM/gtsdb/controlfile/current.260.870609283 NO 16384 1128

2. 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: Start the database instance to the nomount status startup nomount

5: Use rman to restore controlfile

SQL> startup nomount
ORACLE instance started.


Total System Global Area 3323752448 bytes
Fixed Size 2232920 bytes
Variable Size 838864296 bytes
Database Buffers 2466250752 bytes
Redo Buffers 16404480 bytes


[Oracle @ gtsdb1 ~] $ Rman target/


Recovery Manager: Release 11.2.0.3.0-Production on Sat Feb 7 11:48:15 2015


Copyright (c) 1982,201 1, 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:22
Using target database control file instead of recovery catalog
Allocated channel: ORA_DISK_1
Channel ORA_DISK_1: SID = 1425 instance = gtsdb1 device type = DISK


Channel ORA_DISK_1: copied control file copy
Output file name = + SYSTEM/gtsdb/controlfile/current.260.870609283
Output file name = + ARCHIVE/gtsdb/controlfile/current.259.871040903
Output file name = + DATA/gtsdb/controlfile/current.258.871040903
Finished restore at 2015/02/07 11:48:26
RMAN>

RMAN>

RMAN> SQL 'alter database mount ';

SQL statement: alter database mount
Released channel: ORA_DISK_1

RMAN> SQL 'alter database open ';

SQL statement: alter database open

RMAN> exit

Recovery Manager complete.
[Oracle @ gtsdb1 ~] $ Sqlplus/as sysdba

SQL * Plus: Release 11.2.0.3.0 Production ction on Sat Feb 7 11:49:10 2015

Copyright (c) 1982,201 1, Oracle. All rights reserved.

Connected:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0-64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options


SQL> select open_mode, name from v $ database;


OPEN_MODE NAME
-----------------------------
READ WRITE GTSDB


SQL> select name from v $ controlfile;


NAME
--------------------------------------------------------------------------------
+ SYSTEM/gtsdb/controlfile/current.260.870609283
+ ARCHIVE/gtsdb/controlfile/current.259.871040903
+ DATA/gtsdb/controlfile/current.258.871040903

6: Start Node 2!