How to move ASM spfile to a different disk group
(Doc ID 1082943.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2 to 12.1]
Information in this document applies to any platform.
Relevance checked on 06-Aug-2014
The goal is to move ASM spfile from one disk group to another.
During initial ASM setup the spfile might have been created in a default disk group (e.g. DATA). The requirement is now to move the ASM spfile to another disk group.
NOTE: The ASM instance has to be restarted for this change to take effect. In a cluster environment, all ASM instances in the cluster have to be restarted and that can be done in a rolling fashion - one ASM instance at the time.
According to Oracle ASM documentation it should be possible to use 'asmcmd spmove' command to move ASM spfile:
Oracle Database Storage Administrator's Guide 11g Release 2 (11.2)
Section ASMCMD Instance Management Commands
Purpose: Moves an Oracle ASM SPFILE from source to destination and automatically updates the GPnP profile.
But an attempt to move the ASM spfile fails as follows:
ORA-15032: not all alterations performed
ORA-15028: ASM file '+DATA/asm/asmparameterfile/REGISTRY.253.715881237' not dropped; currently being accessed (DBD ERROR: OCIStmtExecute)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!