Maybe mknod will be better for ur configuration.
Does the node rebooted between 16:53 and 17:15? If so, udev must be configured. ORACLE-BASE - UDEV SCSI Rules Configuration for ASM in Oracle Linux 5 and 6
The OK button for "Change discovery path" wouldn't change ownerships from oracle to root. The change would have happened earlier. How was the ownership set to "oracle" ? Was there a reboot before running asmca ?
Hemant K Chitale
What I meant by "OK" button was the button you press after inputting the "disk discovery path". I was watching the disk ownership in a separate putty session using following script:
ls -l /dev/sd*
It may not be the OK button code but maybe some Oracle background process (ocssd or something like that) who changed the ownership.
The ownership was set using chown and is made effective at boot time using "/etc/rc.local". We did reboot the server to check if the ownership stays after reboot - it did remain what it was set to (oracle:oinstall).
I am puzzled why oracle is changing the ownership of disks from correct (oracle:oinstall) to incorrect (root:root) and then start complaining about it?
Is this a BUG?
I opened an SR with support. They asked me to follow MOS Doc ID 1313687.1 (disk aliases - "mknod" as Ali said in his response above). I did follow this document but "asmca" was not able to see/detect the disk devices.
I was about to miss the deadline but I was asked to go ahead to use filesystem instead of ASM.
Now my server has GI installed but the databases are on filesystem. I did not have time to try and uninstall the GI. It is a bit of mess I guess.
Message was edited by: user130038