ASM and EMC PowerPath

  • From: "Radoulov, Dimitre" <cichomitiko@xxxxxxxxx>
  • To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 07 Apr 2011 16:03:07 +0200

Hi all,

RAC on
Linux  2.6.18-92.el5 #1 SMP  x86_64 x86_64 x86_64 GNU/Linux
Oracle Database 10g Enterprise Edition Release - 64bit Production

We need to add disks to the Production environment for the first time.

Given the example below (querydisk on an existing disk):

# /etc/init.d/oracleasm querydisk -d BLOB
Disk "BLOB" is a valid ASM disk on device [66, 97]

 # /etc/init.d/oracleasm querydisk -p BLOB
Disk "BLOB" is a valid ASM disk
/dev/sdam1: LABEL="BLOB" TYPE="oracleasm"
/dev/sdbc1: LABEL="BLOB" TYPE="oracleasm"
/dev/emcpowerz1: LABEL="BLOB" TYPE="oracleasm"

In /proc/partitions we have:

66    97   31457264 sdam1

ORACLEASM_SCANORDER and ORACLEASM_SCANEXCLUDE are both set to "" in /etc/sysconfig/oracleasm.

So the question is: which path should we use with the createdisk command (oracleasm createdisk <diskname> </path>)? Is the multipathing used , given querydisk -d returns the major/minor numbers of the phisical device?

After adding and marking the disks for asm from one node, we'll need to run oracleasm scandisks on the remaining nodes, is it safe to run this command (scandisks) in a live production environment?

Thank you!



Other related posts: