- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 72 Insurance
- 537.2K On-Premises Infrastructure
- 138.6K Analytics Software
- 38.6K Application Development Software
- 6K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.2K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
ASM-XXXX: FAILGROUP DOES NOT EXISTS
Who else wants this error?
It’s actually very easy to make a huge mess in you disk group by just writing the FAILGROUP name wrong. It should have some ways to block you to make this kind of mistake.
There is no problem to have some overhead with controls, because it’s not a very common task. I believe it could have a step to create fail groups like:
[CREATE|ALTER] DISKGROUP [ADD] FAILGROUP controller1,controller2[,…];
Then when adding disk in fail group CONTROLER1 (with only 1 L, for example), it raises the error:
ASM-XXXX: FAILGROUP ‘controler1' DOES NOT EXISTS
Actually you gonna create a new fail group called controler1, and now have 3 failgroups unbalanced. And it’s a problem to fix this situation...