Enable DG Failed 'DCS-12514:Failed to duplicate database using RMAN' 'RMAN-05...

刘泽宇

SYMPTOMS
Enable Dataguard (DG) failed with message 'DCS-12514:Failed to duplicate database using RMAN'

From /opt/oracle/dcs/log/dcs-agent.log (pry node & stdby node)

2020-09-25 04:32:08,657 ERROR [dw-52 - GET /backups/getBackupJobStatus?dbId=332525d5-10cd-4305-a3d1-4f7f6d6112fa&isLatestBackupReport=true&backupType=archivelog] [] c.o.d.a.r.BackupsApi: No job report found for DBID: 332525d5-10cd-4305-xxxxxxxxxxxxxxfa
2020-09-25 04:32:18,770 ERROR [rman Active Duplicate : JobId=f785a474-cd5d-4391-97b9-bd60f3a8dcb7] [] c.o.d.a.u.d.RmanHelper: Failed to run the rman script /tmp/rman2020-09-25_04-27-49-8570896523646484791.script and refer :/opt/oracle/dcs/log/<nodename>/rman/bkup/rman_2020-09-25_04-31-28-7669303067258926284.log for more details.
2020-09-25 04:32:18,770 INFO [rman Active Duplicate : JobId=f785a474-cd5d-4391-97b9-bd60f3a8dcb7] [] c.o.d.a.r.s.d.DataguardOperations: Copy orapw file from local to shared space
2020-09-25 04:32:20,248 ERROR [rman Active Duplicate : JobId=f785a474-cd5d-4391-97b9-bd60f3a8dcb7] [] c.o.d.a.r.s.d.DataguardOperations: rmanActiveDuplicate : failed
2020-09-25 04:32:20,248 ERROR [rman Active Duplicate : JobId=f785a474-cd5d-4391-97b9-bd60f3a8dcb7] [] c.o.d.a.r.s.d.DataguardActions: Unable to duplicated primary db using rman active
2020-09-25 04:32:20,252 ERROR [rman Active Duplicate : JobId=f785a474-cd5d-4391-97b9-bd60f3a8dcb7] [] c.o.d.c.j.JsonRequestProcessor: RPC request invocation failed on request: {"classz":"******** "
! com.oracle.dcs.commons.exception.DcsException: DCS-12514:Failed to duplicate database using RMAN.
! at com.oracle.dcs.commons.exception.DcsException$Builder.build(DcsException.java:69)
! at com.oracle.dcs.agent.rpc.service.dataguard.DataguardActions.rmanActiveDuplicate(DataguardActions.java:250)
! at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


From rman_2020-09-25_04-29-53-6612036879168586089.log

Finished restore at 25-SEP-20
contents of Memory Script:
{
sql clone 'alter database mount standby database';
}
executing Memory Script

sql statement: alter database mount standby database
RMAN-05538: warning: implicitly using DB_FILE_NAME_CONVERT
RMAN-05529: warning: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
released channel: DG_ORA_DISK_1
released channel: DG_ORA_DISK_2
released channel: DG_ORA_AUX_DISK_1
released channel: DG_ORA_AUX_DISK_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/25/2020 04:30:44
RMAN-05501: aborting duplication of target database
RMAN-05517: tempfile +RECO/dbname_iad12q/7A2647F69AAF31E8E0530314650A23AF/TEMPFILE/temp.718.1051800647 conflicts with file used by target database

From standby node alert.log

2020-09-25T04:29:09.908259+00:00
Starting Data Guard Broker (DMON)
2020-09-25T04:29:09.993290+00:00
NOTE: ASMB mounting group 1 (DATA)
NOTE: ASM background process initiating disk discovery for grp 1 (reqid:0)
2020-09-25T04:29:10.076918+00:00
*****************************************
WARNING: The converted filename '+DATA/dbname_iad12q/datafile/system.293.1051797959'
is an ASM fully qualified filename.
Changing the filename to '+DATA/MUST_RENAME_THIS_DATAFILE_0.4294967295.4294967295'.
Please rename it accordingly.
*****************************************

2020-09-25T04:29:10.094324+00:00
*****************************************
WARNING: The converted filename '+DATA/oraprd1_iad12q/datafile/sysaux.290.1051797961'
is an ASM fully qualified filename.
Changing the filename to '+DATA/MUST_RENAME_THIS_DATAFILE_0.4294967295.4294967295'.
Please rename it accordingly.

CAUSE
User have set below parameters at pry DB  
DB_FILE_NAME_CONVERT
LOG_FILE_NAME_CONVERT

Enable DG fialed @ rman duplicate


SOLUTION
O unset below parameters at pry side

DB_FILE_NAME_CONVERT
LOG_FILE_NAME_CONVERT
example:
ALTER SYSTEM RESET db_file_name_convert SCOPE=SPFILE;
ALTER SYSTEM RESET log_file_name_convert SCOPE=SPFILE;

O Retry enable DG

OR

Launch new DB system using latest Full / Stand alone backup and then enable DG .