The instance cannot be started after the second node of rac _ restarts: dismount of the disk group, racdismount

Source: Internet
Author: User

The instance cannot be started after the second node of rac _ restarts: dismount of the disk group, racdismount

Original Works are from the blog of "Deep Blue blog". You are welcome to reprint them. Please note the following source when reprinting them. Otherwise, you will be held legally liable for copyright.

Deep Blue blog: http://blog.csdn.net/huangyanlong/article/details/41480075

 

The instance cannot be started after the second node of rac is restarted: dismount of the disk group

Lab case:

Lab environment: CentOS 6.4, Oracle 11.2.0.1

Recurrence:
1. Restart the server at the second point.
2. Start the instance at the second node manually and report an error.
[Root @ node2 ~] # Su-oracle
[Oracle @ node2 ~] $ Sqlplus '/as sysdba'

SQL * Plus: Release 11.2.0.1.0 Production on Sun Nov 23 15:11:04 2014

Copyright (c) 1982,200 9, Oracle. All rights reserved.

Connected to an idle instance.

Database startup error:
SQL> startup
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+ DG1/xcky/spfilexky. 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 is not mounted.
ORA-06512: at line 4
According to the above error, locking to the ORA-15001 error, which means there is a disk group without mount, so follow this idea to view.

3. view the status of the disk group under the grid user
[Root @ node2 ~] # Su-grid
[Grid @ node2 ~] $ Sqlplus '/as sysdba'

SQL * Plus: Release 11.2.0.1.0 Production on Sun Nov 23 15:27:04 2014

Copyright (c) 1982,200 9, Oracle. All rights reserved.


Connected:
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 and RCY1 disk groups are in the dismounted state, so they are manually started to the mount state. The following operations are performed:

4. Start the disk group to the mount status.
Note that you must use sysasm to operate on a disk group. The user has the following permissions to operate on the disk group:
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
So far, all the disk groups have been started to the mount state.

5. Start the instance of Node 2 again
[Root @ node2 ~] # Su-oracle
[Oracle @ node2 ~] $ Sqlplus '/as sysdba'

SQL * Plus: Release 11.2.0.1.0 Production on Sun Nov 23 15:31:11 2014

Copyright (c) 1982,200 9, 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. We can see that both nodes have been started.
STATUS INSTANCE_NAME
----------------------------
OPEN xcky2
OPEN xcky1


So far, the single-node instance cannot be started because the disk group is in the dismount state.

 

Original Works are from the blog of "Deep Blue blog". You are welcome to reprint them. Please note the following source when reprinting them. Otherwise, you will be held legally liable for copyright.

Deep Blue blog: http://blog.csdn.net/huangyanlong/article/details/41480075

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.