ORA-15018 ORA-15003 Unable To Create/Mount Diskgroup [ID 437081.1]

ORA-15018 ORA-15003 Unable To Create/Mount Diskgroup [ID 437081.1]
		修改时间 24-DEC-2009 类型 PROBLEM 状态 PUBLISHED

In this Document
Symptoms
Cause
Solution

---

Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.3
Information in this document applies to any platform.
***Checked for relevance on 24-Dec-2009***

Symptoms

In Non- RAC system, while trying to create the diskgroup, following errors are observed

SQL> CREATE DISKGROUP SANPROD1_B EXTERNAL REDUNDANCY DISK 'ORCL:SAN1';
CREATE DISKGROUP SANPROD1_A EXTERNAL REDUNDANCY DISK 'ORCL:SAN1'
*
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15003: diskgroup "SANPROD1_B" already mounted in another lock name space

Same error can be used while mounting diskgroup

ALTER DISKGROUP SANPROD1_B MOUNT;

These errors are observed only when adding a disk present in shared storage (SAN,etc) or mounting the diskgroup.

Note :- In case of RAC, while upgrading CRS in rolling fashion from 10.1. to 10.2 could also cause ORA-15003 while trying to mount the diskgroup. According to Bug 5905597 (which was closed as not a bug) , Rolling Upgrades of Patch /Sets/ in a RAC Cluster are ONLY supported for the CRS upgrade, not for ASM nor for database homes.

Cause

NOTE: cache dismounting group 3/0x0EAB3430 (SANPROD1_B)
SUCCESS: diskgroup SANPROD1_B was created
NOTE: cache registered group SANPROD1_B number=3 incarn=0x19eb3432
Wed Jun 20 01:45:58 2007
NOTE: Hbeat: instance first (grp 3)
Wed Jun 20 01:46:02 2007
ERROR: PST found another heartbeat (grp 3) <<<< -- Here it detects
Wed Jun 20 01:46:02 2007
Errors in file /home/oracle/admin/+ASM/udump/+asm_ora_18387.trc:
ORA-15003: diskgroup "SANPROD1_B" already mounted in another lock name space
Wed Jun 20 01:46:03 2007
NOTE: cache dismounting group 3/0x19EB3432 (SANPROD1_B)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup SANPROD1_B was not mounted

In ASM alert log we see that as part of creation of diskgroup it is first dismounted and then it is to be mounted again by ASM instance. But before this operation PST has found another ASM instance accessing the diskgroup.

This situation can happen when multiple ASM instances are running on same/separate machines and accessing the common raw device.

Solution

In order to be able to use the same ASM diskgroup on two different nodes pointing to the same storage, they(the nodes) would have to be a part of the same RAC environment. As long as they are part of different RAC environments they won't be able to share the same ASM diskgroup.
This can be quite dangerous as you can overwrite the other instance data in case you use Force option to create the diskgroup.

Please contact your System Admin and make sure that you are not accessing the same devices for two separate ASM instances[@more@]

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/161195/viewspace-1051559/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/161195/viewspace-1051559/