This content has been marked as final. Show 6 replies
Try deleting the empty disks using "crsctl delete css". I am not sure whether that will work, since the paths are empty.
Other option is to reinitialize the OCR by running root.sh, after a complete clean-up.
But make sure that the voting disk locations are set correctly by the OUI in "$ORA_CRS_HOME/install/rootconfig" script.
Thnx for your reaction.
The first option does not work for the command requires a path to a disc.
Secondly I am running on W2003. (forgot to mention)
I ran into the samething today and figured out how to get rid of them at least on a Win 2003 SP2R2 cluster. Mine were showing 0s for the path as well so after a lot of trial and error I finally just tried:
crsctl delete css votedisk 0
And it worked... What happens is, when you have to do a -force to create extra votedisks the cluster has to be stopped on all nodes or this will happen. We were doing a totally fresh install so we played with it a little to determine this is what happened. When we stopped everything before adding votedisks using -force and cleaning up the bad ones, everything went fine.
I kind of misworded that last sentence... we:
1. Cleaned up the bad votedisks
2. Stopped the cluster on both nodes involved
3. Created the new, added votedisks using -force
And I was also able to issue the "crsctl delete css votedisk 0" twice in a row to remove both extras... Sorry for any confusion.
Yes, the CRS needs to be shutdown on all the nodes of the cluster before you add or delete the voting devices and also use the -force option with it. This has been well documented in one of the metalink notes.
I had the same problem on a nfs voting disk whos path disapeared in the crsctl query css votedisk.
We are on a 11gr1 extended RAC.
I deleted it by using the empty string "" as path.
==> crsctl delete css votedisk ""
Edited by: user2457908 on 26 sept. 2012 03:14