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-36728: (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.

1 Answers  

---

SQL*Loader-00916: Error checking path homogeneity

1 Answers  

---

ORA-16724: the intended state for the database has been set to OFFLINE

1 Answers  

---

NNL-00960: Time until cache flush: string

1 Answers  

---

ORA-09969: scurls: unable to close lock file

1 Answers  

---

LSX-00244: invalid NCName "~S"

1 Answers  

---

ORA-09353: Windows 32-bit Two-Task driver unable to open event semaphore

1 Answers  

---

LFI-01503: Max filename size exceeded generating filename.

1 Answers  

---

ORA-07549: sftopn: $OPEN failure

1 Answers  

---

ORA-01511: error in renaming log/data files

1 Answers  

---

DRG-12211: section or section id string does not exist

1 Answers  

---

PLS-00592: the type of a object table must be an object type

1 Answers  

---