instance-specific spfile entry is only updated for RAC for instance executing create diskgroup statement
(Doc ID 741791.1)
Last updated on SEPTEMBER 16, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.6 [Release 10.1 to 11.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Goal
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?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |