Using ASRU On Cloned Diskgroup may wipe out wrong disks (Doc ID 1519007.1)

Last updated on OCTOBER 31, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Information in this document applies to any platform.

Symptoms

When executing ASRU on cloned diskgroups (using EMC storage tools), experiencing a mismatch of the ASM disks contained in the ASM diskgroups.
ASRU build a list of disks to execute the dd commands against, but the list of disks is not correct (beloning to another diskgroup).

ASRU correctly rebalances the diskgroup and then performs a  lookup to determine which ASMLib disks to perform the OS level dd - commands against to perform the zero-out.
The disks returned as being part of the cloned diskgroup (DGREONDV0001_C01) are NOT correct.
Here the disks of another diskgroup (DGREONDV0001_S02) are listed. (the listed disks ending on _S02 are not part of the  DGREONDV0001_C01 diskgroup !)
This effectively wipes out part of the wrong disks.

SELECT PATH,LIBRARY FROM V$ASM_DISK WHERE NAME='DATA1056'
This returns multiple rows (because oracleasm renamedisks only changes the label, not the name):


PATH ----------------------------- LIBRARY -----------------------------
ORCL:DATA1056_S01       ASM Library - Generic Linux, version 2.0.4 (KABI_V2)
ORCL:DATA1056_C01       ASM Library - Generic Linux, version 2.0.4 (KABI_V2) 
ORCL:DATA1056_C02       ASM Library - Generic Linux, version 2.0.4 (KABI_V2) 
ORCL:DATA1056_S02       ASM Library - Generic Linux, version 2.0.4 (KABI_V2)

Changes

ASRU version used was 1.2 (OTN zip file : asru-1409713.zip)

Cloning diskgroups using storage tools (eg EMC) and running  ASRU on the cloned disks.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms