Duplicate for Standby fails with RMAN-05535 even when LOG_FILE_NAME_CONVERT is set (Doc ID 2756315.1

In this Document

APPLIES TO:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later

Information in this document applies to any platform.

SYMPTOMS

RMAN duplicate for standby fails with RMAN-05535 although the LOG_FILE_NAME_CONVERT parameter is defined: 

rman<<_EOF

connect target sys/oracle@orcl36

connect auxiliary sys/oracle@orcl39

 run {

    allocate channel t1 type disk;

    allocate channel t2 type disk;

    allocate auxiliary channel a1 type disk;

    allocate auxiliary channel a2 type disk;

    duplicate target database for standby from active database nofilenamecheck

       dorecover

       spfile

       PARAMETER_VALUE_CONVERT 'ORCL36','ORCL39','orcl36','orcl39'

       set db_unique_name='orcl39'

       set log_archive_dest_1='LOCATION=/u01/app/oracle/archive/ORCL/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl39'

       set log_archive_dest_2=''

       set log_archive_dest_3=''

       set db_file_name_convert='/oradata/ORCL/','/oradata/ORCL/'

       set standby_file_management='MANUAL'

       ;

     }

_EOF

......

RMAN-05535: warning: All redo log files were not defined properly.

RMAN-05535: warning: All redo log files were not defined properly.

RMAN-05535: warning: All redo log files were not defined properly.

RMAN-05535: warning: All redo log files were not defined properly.

RMAN-05535: warning: All redo log files were not defined properly.

RMAN-05535: warning: All redo log files were not defined properly.

RMAN-05535: warning: All redo log files were not defined properly.

......

Recovery Manager is complete.

The alert.log of the standby auxiliary instance shows the following:

alter database rename file '/oradata/ORCL/redo01.log' to 'broken0'

Completed: alter database rename file '/oradata/ORCL/redo01.log' to 'broken0'

alter database rename file '/oradata/ORCL/redo02.log' to 'broken1'

Completed: alter database rename file '/oradata/ORCL/redo02.log' to 'broken1'

alter database rename file '/oradata/ORCL/redo03.log' to 'broken2'

Completed: alter database rename file '/oradata/ORCL/redo03.log' to 'broken2'

alter database rename file '/oradata/ORCL/standby_redo11.log' to 'broken3'

Completed: alter database rename file '/oradata/ORCL/standby_redo11.log' to 'broken3'

alter database rename file '/oradata/ORCL/standby_redo12.log' to 'broken4'

Completed: alter database rename file '/oradata/ORCL/standby_redo12.log' to 'broken4'

alter database rename file '/oradata/ORCL/standby_redo13.log' to 'broken5'

Completed: alter database rename file '/oradata/ORCL/standby_redo13.log' to 'broken5'

alter database rename file '/oradata/ORCL/standby_redo14.log' to 'broken6'

Completed: alter database rename file '/oradata/ORCL/standby_redo14.log' to 'broken6'

CAUSE

This issue is similar to Bug 30776075: RMAN DUPLICATE WITH SRLS ERROR RMAN-05535: WARNING: ALL REDO LOG FILES WERE NOT DEFINED PROPERLY.

This bug is awaiting the fix of the base Bug 23127716: SRL IS NOT CONVERTED BY LOG_FILE_NAME_CONVERT ON CASCADED STANDBY which at this time is currently open and under investigation.

SOLUTION

The workaround for this issue is to rename the redo log files manually.  

1. Issue the 'alter database' command to rename the redo log files reported in the alert.log of the standby/auxiliary:

For example, if the alert log shows the following: 

alter database rename file '<PATH1>/<ORACLE_SID>/redo1/redo01.log' to 'broken0'

execute the rename like the following:

alter database rename file '<ORACLE_HOME>/dbs/broken0' to '<PATH1>/<ORACLE_SID>/redo1/redo01.log';

2. Confirm the redo log filename have changed using the following query: 

select v1.thread#, v1.group#, v2.member from v𝑙𝑜𝑔𝑣1,𝑣

logfile v2 where v1.group#=v2.group#

order by v1.group#;

Repeat step #1 above for any redo logfile listed in the above query which has not been renamed.  

3. The above steps does not create the redo log file, it just updates the controlfile with a valid location and name.  Once all the redo

log files have been renamed, you must execute the following to physically create them: 

alter database clear logfile group <REDO LOG group  number>;

The REDO LOG group value is the same as that returned by group# column in v$logfile view.  

4.  Once complete, the standby database can begin redo apply.

REFERENCES

BUG:23127716 - SRL IS NOT CONVERTED BY LOG_FILE_NAME_CONVERT ON CASCADED STANDBY

————————————————

版权声明：本文为CSDN博主「lixora」的原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接及本声明。

原文链接：https://blog.csdn.net/lixora/article/details/137598189