Starting with ASM version 11.2, the ASM spfile can be stored in an ASM disk group. Indeed, during a new ASM installation, the Oracle Universal Installer (OUI) will place the ASM spfile in the disk group that gets created during the installation.
spbackup – Backs up an ASM spfile to a backup file. The backup file is not a special file type and is not identified as an spfile.
spcopy – Copies an ASM spfile from the source location to an spfile in the destination location.
spmove – moves an ASM spfile from source to destination and automatically updates the GPnP profile.
- spget – Retrieves the location of the Oracle ASM SPFILE.
ASMCMD> spget +DATA/asm/asmparameterfile/registry.253.820278587
Taking backup of current spfile
ASMCMD> spbackup +DATA/asm/asmparameterfile/registry.253.820278587 /tmp/ASMspfile.backup
spmove will copy the current spfile to the new location and update the gpnp profile for next startup.This command throw errors as not all alterations performed as current spfile is being used, in the next startup the new spfile will be effective and we can manually remove the old spfile
lets move the spfile to the $ORACLE_HOME/dbs directory.
ASMCMD> spmove +DATA/asm/asmparameterfile/registry.253.820278587 /u01/app/oracle/product/11.2.0/grid/dbs/spfile+ASM.ora ORA-15032: not all alterations performed ORA-15028: ASM file '+DATA/asm/asmparameterfile/registry.253.820278587' not dropped; currently being used(DBD ERROR: OCIStmtExecute)
Restart the HA stack to verify that ASM starts up fine with moved spfile
[oracle@node1 ~]$ srvctl stop asm [oracle@node1 ~]$ srvctl start asm
Lets check current location of SPFILE
[oracle@node1 ~]$ srvctl config asm ASM home: /u01/app/oracle/product/11.2.0/grid ASM listener: LISTENER Spfile: /u01/app/oracle/product/11.2.0/grid/dbs/spfile+ASM.ora