Comments on: Adding new ASM disk to RAC database fails

By: yogi

yogi — Mon, 09 May 2011 15:50:57 +0000

Perfect, this article really helped me. I used dd if=/dev/zero. it worked.

Thanks a lot.
-Yogi

By: Saurabh Sood

Saurabh Sood — Fri, 21 Jan 2011 12:26:07 +0000

Hi Rafiq,

I am not aware what was the version of my 10gr2 database, but the force usage behavior is not changed in these version. YOu can probably ask for any ORACLE BUG reference to this from Oracle Support.

As per ASM dcumentation the force should work in all 10gr2 version, but in my case it did not work at all.

let us know also if you get any reply from oracle support on any BUG related to this.

BTW did using “force” worked in your case?

Regards,
Saurabh Sood

By: Rafiq

Rafiq — Tue, 18 Jan 2011 18:56:21 +0000

What was the version of Oracle 10gr2. As per Oracle support force option should work with 10.2.0.4. We have similar issue with one of our disk in 10.2.0.4 and opened a SR. I also gave reference of your link but they support person says that force option should work with 10.2.0.4.

By: Jon

Jon — Thu, 11 Nov 2010 21:08:45 +0000

Just a note — I ran into this installing Grid on a standalone server, and it turns out there is a bug when using non-default discovery paths for ASM on standalone. Metalink note 1086140.1 goes into details and a workaround…

By: csk

csk — Sun, 19 Sep 2010 12:08:05 +0000

I raised P1 SR and Oracle support checked the Disks belonging to the Diskgroup and asked me to unmount & mount the Diskgroups to make sure that the partially added disk has not done any serious damage. As I was able to unmount and mount the Diskgroups , they asked me to create a new Diskgroup with FORCE option and it worked. Problem got resolved. Didnt require to use dd command.
Thanks.

By: csk

csk — Tue, 07 Sep 2010 14:15:18 +0000

In my case the adding Disk to an existing Disk Group failed as the disk was not visible from other RAC node.Now the Disk is showing Header_Status as MEMBER and Mount_Status as CLOSED. dd command can be used to erase the Header Status of the Disk. But the Disk Group’s working Disk has details about the Disk that failed to get added. This is causing me worry…

By: Saurabh Sood

Saurabh Sood — Mon, 06 Sep 2010 16:54:08 +0000

Hi CSK,

In this case, the information is already written into disk header, and to reuse the disk the only option i s to erase the header contents and I think dd is a safe way only as we can verify before actually using dd.

I am not aware of any oracle command which will erase the disk header.
Please let us know what reply you get from Oracle Support on this!!

Regards,
Saurabh Sood

By: csk

csk — Mon, 06 Sep 2010 08:50:22 +0000

Yeah. I have opened SR with Oracle. Once I get solution , I will provide it here.

By: Amit

Amit — Mon, 06 Sep 2010 03:39:58 +0000

Csk,

I am not sure about SAN admin module but unless you erase the disk header (using dd), you will not be able to add it back. You can work with oracle support and let them verify your issue.

Cheers
Amit

By: csk

csk — Sun, 05 Sep 2010 12:13:56 +0000

I am facing similar issue in a Production System. To avoid using dd command, can we un-present and present the Disk using SAN admin module. Is it equivalant to using dd command?

By: csk

csk — Sun, 05 Sep 2010 12:02:31 +0000

I am facing similar issue in Production System. But hesitating to use dd command. Is there any other safe way to do this?

By: Ron Gordon

Ron Gordon — Fri, 03 Sep 2010 18:12:27 +0000

I had a simillar ORA-15020: discovered duplicate ASM disk issue, our sysadmin determined that there was a BAD superblock on the disk, he newfs’ed them. Then I used the dd commands with if=/dev/zero, then I re-formatted the device (solaris 10 format command), then I was able to “ALTER DISKGROUP DATA ADD DISK ‘/dev/rdsk/emcpower49a’;”

By: Richard

Richard — Wed, 07 Jul 2010 19:39:57 +0000

Hello,
Great this tip that you sent, you helped me so much.
but take care when to use dd command.

Regards,

By: My little IT blog

My little IT blog — Tue, 14 Jul 2009 13:24:32 +0000

ASM…really sucks…

I’ve always thought that ASM is a sucking unneeded part of oracle. Is really slow, is another abstraction layer between database a disk block, is not mature for production environment and simply sucks. Yesterday I made an error. Altering a di…