How to move ASM spfile to a different disk group
(Doc ID 1082943.1)
Last updated on JUNE 18, 2024
Applies to:
Oracle Database Exadata Cloud Machine - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Relevance checked on 06-Aug-2014
Goal
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. <OLD_DG_NAME>). 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 <OLD_DG_NAME>base Storage Administrator's Guide 11g Release 2 (11.2)
Section ASMCMD Instance Management Commands
spmove
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:
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 |