ASM OMF single-file creation form 重命名

OMF下不能自动命名，需要重新命名的话：1

1. spfile 可以 create pfile from spfile 后再create spfile from pfile

2 redo？

3 datafile？

Here are some details of the copy problem:

a) You are not allowed to set the numbers for the target file
ASMCMD> cp +AUX/AUX/DATAFILE/RMANTEST.265.804096431 +DATA/xydb/DATAFILE/RMANTEST.265.804096431
copying +AUX/AUX/DATAFILE/RMANTEST.265.804096431 -> +DATA/xydb/DATAFILE/RMANTEST.265.804096431
ASMCMD-8016: copy source->'+AUX/AUX/DATAFILE/RMANTEST.265.804096431' and target->'+DATA/xydb/DATAFILE/RMANTEST.265.804096431' failed
ORA-15056: additional error message
ORA-15046: ASM file name '+DATA/xydb/DATAFILE/RMANTEST.265.804096431' is not in single-file creation form
ORA-06512: at "SYS.X$DBMS_DISKGROUP", line 413
ORA-06512: at line 3 (DBD ERROR: OCIStmtExecute)
ASMCMD>

b) If you omit the numbers then the structure of the datafile in the target ASM directory is different to the others:
ASMCMD> cp +AUX/AUX/DATAFILE/RMANTEST.265.804096431 +DATA/xydb/DATAFILE/RMANTEST
copying +AUX/AUX/DATAFILE/RMANTEST.265.804096431 -> +DATA/xydb/DATAFILE/RMANTEST
ASMCMD> ls -l
Type      Redund  Striped  Time             Sys  Name
DATAFILE  MIRROR  COARSE   JAN 08 14:00:00  Y    TBS01.264.774103285
                                            N    RMANTEST => +DATA/ASM/DATAFILE/RMANTEST.274.804179419
DATAFILE  MIRROR  COARSE   JAN 08 00:00:00  Y    SYSAUX.261.774103259
DATAFILE  MIRROR  COARSE   JAN 08 00:00:00  Y    SYSTEM.260.774103249
DATAFILE  MIRROR  COARSE   JAN 08 00:00:00  Y    UNDOTBS1.262.774103267
DATAFILE  MIRROR  COARSE   JAN 08 00:00:00  Y    UNDOTBS2.265.774103287
DATAFILE  MIRROR  COARSE   JAN 08 00:00:00  Y    UNDOTBS3.266.774103291
ASMCMD>

SYMPTOMS

ORA-15046 when using asmcmd pwmove command on password file
 

$ asmcmd pwmove --asm +DG/ASM/PASSWORD/pwdasm.256.934825981 +DG1/ASM/PASSWORD/pwdasm.256.934825981 -f
moving +DG/ASM/PASSWORD/pwdasm.256.934825981 -> +DG1/ASM/PASSWORD/pwdasm.256.934825981
ASMCMD-8016: copy source '+DG/ASM/PASSWORD/pwdasm.256.934825981' and target '+DG1/ASM/PASSWORD/pwdasm.256.934825981' failed
ORA-15056: additional error message
ORA-15046: ASM file name '+DG1/ASM/PASSWORD/pwdasm.256.934825981' is not in single-file creation form       <<<-----------------------
ORA-06512: at "SYS.X$DBMS_DISKGROUP", line 603
ORA-06512: at line 3 (DBD ERROR: OCIStmtExecute)

CHANGES

None

CAUSE

Destination file name cannot be in a OMF format
 
target '+DG/ASM/PASSWORD/pwdasm.256.934825981' failed <<<----------"pwdasm.256.934825981" is an OMF compliant name

Using Oracle Managed Files
 

SOLUTION

Use a non-OMF destination file name

Example:
$ asmcmd pwmove --asm +DG/ASM/PASSWORD/pwdasm.256.934825981 +DG1/ASM/PASSWORD/asmpwdfile -f

Note: you may or may not need to use the force "-f" option in the command.

RMAN duplicate has failed with ORA-15046 while restoring the spfile
 

RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-19870: error while restoring backup piece <backup piece name>
ORA-32015: unable to restore SPFILE
ORA-17502: ksfdcre:4 Failed to create file <ASM DG Name>/<DB_UNIQUE_NAME>/PARAMETERFILE/spfile.<nnnn>.<nnnnnnn>
ORA-15046: ASM file name '<ASM DG Name>/<DB_UNIQUE_NAME>/PARAMETERFILE/spfile.<nnnn>.<nnnnnnn>' is not in single-file creation form

CHANGES

CAUSE

Bug 35801772
 
Symptoms match with the Bug which is in status 11 { Dev working }
 

SOLUTION

Action Plan which helped to resolve the issue given in the above Bug was :

If the spfile is specified within CRS on the auxiliary instance, this will cause the error for the spfile. Clearing it removes the issue.

Run the below command at the Auxiliary DB to confirm if spfile has been configured in CRS

$ srvctl config database -db '<db_unique_name/db_name>';

The above command showed that spfile setting was configured in CRS.

Clear the spfile setting in CRS using the below command : 

At the Auxiliary DB

========

$ srvctl modify database -db <db_unique_name/db_name> -spfile '' # it is two single quotes

 Then the spfile got Restored and RMAN Duplicate was successful.