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-14287: cannot REBUILD a partition of a Composite Range partitioned index

1 Answers  

---

ORA-14084: you may specify TABLESPACE DEFAULT only for a LOCAL index

1 Answers  

---

NNF-02004: NIS map string does not exist

1 Answers  

---

ORA-10634: Segment is already being shrunk

2 Answers  

---

ORA-00162: external dbid length string is greater than maximum (string)

1 Answers  

---

ORA-26530: unable to build materialized view refresh control list

1 Answers  

---

ORA-23361: materialized view "string" does not exist at master site

1 Answers  

---

ORA-24071: cannot perform operation string, queue table string is being migrated

1 Answers  

---

ORA-19854: error obtaining connect string from target

1 Answers  

---

ORA-01125: cannot disable media recovery - file string has online backup set

1 Answers  

---

NNO-00604: disabling all request processing

1 Answers  

---

TNS-01155: Incorrectly specified SID_LIST_string parameter in LISTENER.ORA

1 Answers  

---