In this Document
  Symptoms
  Changes
  Cause
  Solution

---

Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.4 - Release: 10.1 to 10.2
Information in this document applies to any platform.

Symptoms

While checking from the RDBMS instance the status of ASM diskgroup is shown as DISMOUNTED.

From ASM instance the status is shown as MOUNTED.

Following messages are present in the alert log of RDBMS instance.

Changes

No changes

Cause

The problem is due to RDBMS instance not able to communicate to ASM instance. Whenever it is trying to communicate it is running out of OS resources. It is not able to fork new process at OS level.

From the RDBMS instance, if we check the STATE of diskgroup:

SQL > select name,state from v$asm_diskgroup;

NAME                                  STATE
------------------------------    -----------
ASMDISK01                       CONNECTED
ASMDISK02                       DISMOUNTED

The state CONNECTED means that rdbms instance is currently using this particular diskgroup and the state DISMOUNTED means that rdbms instance is seeing the diskgroup not available for use.

Solution

In this case new processes from ASM instance cannot be started as it has reached its maximum limit, thus RDBMS instance is not able to communicate to ASM instance.

The default number of ASM processes is 40. To solve this we need to set the processes parameter to a large value (100 etc.)

 

---

相关的 产品 Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition 关键字 ASM; DISKGROUP; UNABLE TO CONNECT; V$ASM_DISKGROUP 错误 ORA-15055; ORA-17503; ORA-12549; ORA-20; ORA-312; ORA-313

返回页首