Original works, from the "Blue Blog" blog, Welcome to reprint, please be sure to indicate the following sources, otherwise, the legal responsibility to pursue copyright.
The blog:http://blog.csdn.net/huangyanlong/article/details/41480075 of Blue
Unable to start an instance after the second node of RAC restarts: Disk group dismount problem
Experimental cases:
Lab environment: CentOS 6.4, Oracle 11.2.0.1
The phenomenon repeats itself:
1. Restart the second node server
2. Manually start the second node instance, error
[Email protected] ~]# su-oracle
[Email protected] ~]$ sqlplus '/as sysdba '
Sql*plus:release 11.2.0.1.0 Production on Sun Nov 23 15:11:04 2014
Copyright (c) 1982, Oracle. All rights reserved.
Connected to an idle instance.
Start database error as follows:
Sql> Startup
Ora-01078:failure in processing system parameters
Ora-01565:error in identifying file ' +dg1/xcky/spfilexcky.ora '
Ora-17503:ksfdopn:2 Failed to open file +dg1/xcky/spfilexcky.ora
Ora-15056:additional error message
Ora-17503:ksfdopn:dgopenfile05 Failed to open file +dg1/xcky/spfilexcky.ora
Ora-17503:ksfdopn:2 Failed to open file +dg1/xcky/spfilexcky.ora
Ora-15001:diskgroup "DG1" does not exist or was not mounted
Ora-06512:at Line 4
According to the above error, locked to the ORA-15001 error, which is represented by a disk group without mount, then follow this idea to view.
3. Under grid user, view disk group status
[Email protected] ~]# Su-grid
[Email protected] ~]$ sqlplus '/as sysdba '
Sql*plus:release 11.2.0.1.0 Production on Sun Nov 23 15:27:04 2014
Copyright (c) 1982, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-64bit Production
With the Real application Clusters and Automatic Storage Management options
Sql> select Name,state from V$asm_diskgroup;
NAME State
------------------------------ -----------
CRS Mounted
DG1 dismounted
RCY1 dismounted
It can be found that the DG1, RCY1 Disk Group in the dismounted state, and then manually boot to the Mount state, the following actions:
4. Start disk Group to mount state
It is important to note that when working with disk groups, you need to use the Sysasm user, who has permissions to disk group operations, as follows:
Sql> Conn/as Sysasm
Connected.
Sql> select Name,state from V$asm_diskgroup;
NAME State
------------------------------ -----------
CRS Mounted
DG1 dismounted
RCY1 dismounted
Sql> alter DiskGroup DG1 Mount;
DiskGroup altered.
Sql> alter DiskGroup RCY1 Mount;
DiskGroup altered.
Sql> select Name,state from V$asm_diskgroup;
NAME State
------------------------------ -----------
CRS Mounted
DG1 Mounted
RCY1 Mounted
This completes the boot of all disk groups into the Mount state.
5. Start the instance of node 2 again
[Email protected] ~]# su-oracle
[Email protected] ~]$ sqlplus '/as sysdba '
Sql*plus:release 11.2.0.1.0 Production on Sun Nov 23 15:31:11 2014
Copyright (c) 1982, Oracle. All rights reserved.
Connected to an idle instance.
Sql> Startup
ORACLE instance started.
Total System Global area 730714112 bytes
Fixed Size 2216944 bytes
Variable Size 557845520 bytes
Database buffers 167772160 bytes
Redo buffers 2879488 bytes
Database mounted.
Database opened.
Sql> select Status,instance_name from Gv$instance;
--Query the entire cluster environment, you can see that two nodes have been started
STATUS instance_name
------------ ----------------
OPEN Xcky2
OPEN Xcky1
At this point, the single-node instance that is caused by the disk group in the dismount State cannot start the problem, resolved.
Original works, from the "Blue Blog" blog, Welcome to reprint, please be sure to indicate the following sources, otherwise, the legal responsibility to pursue copyright.
The blog:http://blog.csdn.net/huangyanlong/article/details/41480075 of Blue
-
Top
RAC 11g_ cannot start after the second node restarts: Disk group dismount issue