Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I inherited a production system with the following setup:

  • Disk A, Failgroup AB
  • Disk B, Failgroup AB
  • Disk C, Failgroup CD
  • Disk D, Failgroup CD

Diskgroups AB and CD are configured with normal redundancy.

All disks are the same size. A and B share a common failure point, that is, it'd be unsafe for physical config reasons to make B a redundant version of A. Same for disks C and D.

If A and B's common failure point occurs and I lose disks A and B, what will happen to my database instance?

I've heard conflicting things:

  1. ASM will halt the database because it can't maintain it's redundancy configuration.
  2. ASM will attempt to use C and D and somehow rebalance the data from A and B.
  3. ASM will issue an alert and continue to allow things to run.

So what will happen? Is the result configurable?

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.