Last updated on NOVEMBER 24, 2011
Applies to:Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 220.127.116.11 - Release: 10.1 to 11.1
Information in this document applies to any platform.
When using an spfile for clustered ASM instances, the asm_diskgroup in the spfile will be updated only for the ASM instance where the CREATE DISKGROUP command was executed from.
This causes no problem at the beginning. However when the ASM instances are stoppped and restarted or after we issue ALTER DISKGROUP ALL [DISMOUNT|MOUNT], the newly created diskgroup will be automatically mounted only in the ASM instance where it was created from
Is this expected? Why? Where is it documented?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms