This content has been marked as final. Show 4 replies
This can occur if the volume is open from a previously unclean dismount or shutdown.
The volume needs to be closed before it can be deleted in the driver.
Could you please check each of your nodes and first see if the volume devices exists?
If so, you can verify that the volume is open by running:
lsof /dev/asm/v_dir_sig2-133Close all open volume references and retry the volume delete command.
Hi, thanks for the reply.
I checked on every node and got this:
[grid@CLU ~]$ ls /dev/asm/v_dir_sig2-133
ls: impossible d'accéder à /dev/asm/v_dir_sig2-133: Aucun fichier ou dossier de ce type
[grid@CLU ~]$ lsof /dev/asm/v_dir_sig2-133
lsof: status error on /dev/asm/v_dir_sig2-133: No such file or directory
It seems that the volume doesn't exist.
FYI: When I tried to create the volume, another volume was not really clean (its diskgroup had been dropped). ASMCMD didn't want to remove this other volume. I had to recreate a diskgroup with the same name and I was abble to remove the volume.
But i'm not sure this has something to do with my issue.
Edited by: Eska on 25 avr. 2013 23:58
What version of ASM are you using?
There should be more information in the alert.log file on the node where you attempted to add/drop the volume. Specifically, it should indicate the node number where the volume
failed to be created/dropped. On the node indicated in the alert.log file, there should be more information in the CKPT trace file about exact error seen.
Thanks for the answer.
First I've to say that the problem is solved. This morning I tried to execute the same command again and this time it succeed. I really don't know how and why.
When the problem what still there I check the alertlog and nothing was in there.
My version is:
Oracle Database 11g Enterprise Edition Release 126.96.36.199.0 - 64bit Production
PL/SQL Release 188.8.131.52.0 - Production
CORE 184.108.40.206.0 Production
TNS for Linux: Version 220.127.116.11.0 - Production
NLSRTL Version 18.104.22.168.0 - Production
Thanks anyway :) Sorry I can't tell you what solved the issue :(