Hi,

We are using Oracle/RAC 10GR2 with ASM for disk management of diskspace

used by the database. ASM requires that the disks are NOT included in a

volume group and also uses the first block of the disk to store
essential information. RAC 10GR2 does not need HACMP anymore.
This setup imposes a serious problem for AIX systemmanagement:
1) It is difficult to distinguish disks on the AIX servers since they
are not part of a volume group.
2) The usage of the first block by Oracle implies that chdev may not be

used to create a PVID, since chdev overwrites the first block. If chdev

is being used on a ASM disk, Oracle can not read that disk, and the
database is lost.
3) Since ASM disks are writable by all servers in the cluster,
reserve_policy is switched off, the probability that a disk is by
accident used for a volume group is not unthinkable, with fatal
consequences for the database.
4) Changes in SAN configuration may imply that existing devices have to

be rearranged with rmdev. Rmdev removes disk devices and other devices
nodes in /dev having equal major/minor number. Using sybolic names for
hdisk devices in the Oracle database by creating devices nodes in /dev
is not a viable option.

Question:
Does anybody recognise these issues, and is there a workaround so that
ASM gets better integrated into standard AIX system management ?.


Thanks in advance.


Erik

I've been saying for years that there is a risk of overwriting raw
devices, but people just dismiss it with "that's not an issue with
modern volume managers." Therefore, it needs to be handled with local
digit removal procedures for violations.

So the answer is, no, nobody recognizes these issues.

Hopefully, someone will come up with a better answer than that.

jg
--
@home.com is bogus.
http://www.ncbi.nlm.nih.gov/entrez/q...&dopt=Abstract