RE: ASM - removing disk from diskgroup question

HEADER_STATUS VARCHAR2(12) Per-instance status of the disk as seen by discovery:

• UNKNOWN - Automatic Storage Management disk header has not been read
• CANDIDATE - Disk is not part of a disk group and may be added to a disk group with the ALTER DISKGROUP statement
• INCOMPATIBLE - Version number in the disk header is not compatible with the Automatic Storage Management software version.
• PROVISIONED - Disk is not part of a disk group and may be added to a disk group with the ALTER DISKGROUP statement. The PROVISIONED header status is different from the CANDIDATE header status in that PROVISIONED implies that an additional platform-specific action has been taken by an administrator to make the disk available for Automatic Storage Management.
• MEMBER - Disk is a member of an existing disk group. No attempt should be made to add the disk to a different disk group. The ALTER DISKGROUP statement will reject such an addition unless overridden with the FORCE option
• FORMER - Disk was once part of a disk group but has been dropped cleanly from the group. It may be added to a new disk group with the ALTER DISKGROUP statement.
• CONFLICT - Automatic Storage Management disk was not mounted due to a conflict
• FOREIGN - Disk contains data created by an Oracle product other than ASM. This includes datafiles, logfiles, and OCR disks.

Chris

From: Taylor Christopher - Nashville
Sent: Wednesday, October 10, 2012 1:12 PM To: oracle-l_at_freelists.org
Subject: ASM - removing disk from diskgroup question

This is probably a dumb question but I'll ask anyway.

When you drop a disk from a DISKGROUP in ASM, the HEADER status will show as FORMER instead of CANDIDATE, correct? I assume you can add these disks to other DISKGROUPS just like disks that read CANDIDATE?

Chris

--
http://www.freelists.org/webpage/oracle-l