Answer / guest

Cause: An ALTER DISKGROUP ADD DISK command specified a disk
that could not be discovered by one or more nodes in a RAC
cluster configuration.

Action: Determine which disks are causing the problem from
the GV$OSM_DISK fixed view. Check operating system
permissions for the device and the storage sub-system
configuration on each node in a RAC cluster that cannot
identify the disk.

Please add more information about this Error

Answer / nakka nageswara rao

HI All,

you need to run the bellow command on all other nodes also.
so that the disk come to visible on other nodes also

(root)

#oracleasm listdisks
#oracleasm scandisks
#oracleasm listdisks

Then try to add that newdisk to diskgroup by alter
diskgroup command.

still if you are facing any issues check that asm alert log
and oracleasm logs

cat /var/log/oracleasm

ORA-06315: IPA: Invalid connect string

1 Answers  

---

ORA-33920: (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.

1 Answers  

---

DRG-10314: logging has not been started

1 Answers  

---

QSM-02071: internal error: undefined PCT failure code

1 Answers  

---

ORA-01630: max # extents (string) reached in temp segment in tablespace string

1 Answers  

---

CLSS-02207: error string getting status from vendor node monitor

1 Answers  

---

ORA-16128: User initiated shut down successfully completed

1 Answers  

---

ORA-24431: Statement does not exist in the cache

1 Answers  

---

ORA-19608: %s is not a backup piece

1 Answers  

---

NID-00406: Reversion of database name failed.

1 Answers  

---

ORA-08341: On nCUBE, this command can only be executed from instance 1.

1 Answers  

---

RMAN-06181: multiple channels require Enterprise Edition

1 Answers  

---