RMAN 05535 during duplicate on 19c - denis-kol4ev/OraDBA GitHub Wiki

NOTE: Best approach don't use identical locations for redo logs, in this way we avoid RMAN-05535 error and additional manual actions.

On 19C when NOFILENAMECHECK option used in conjunction with log_file_name_convert pointing to the same path (for example, log_file_name_convert='+REDO/gkprd/','+REDO/gkprd/') and standby_file_management=auto, follow errors occurred at the end of duplicate.

Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.

RMAN-05535: warning: All redo log files were not defined properly.
Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.

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

Standby redo is missing, try to recreate it

ALTER DATABASE DROP STANDBY LOGFILE GROUP 4;
ALTER DATABASE DROP STANDBY LOGFILE GROUP 5;
ALTER DATABASE DROP STANDBY LOGFILE GROUP 6;
ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;

ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 4 ('+REDO/gkprd/redo04.stb') SIZE 200M;
ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 5 ('+REDO/gkprd/redo05.stb') SIZE 200M;
ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 6 ('+REDO/gkprd/redo06.stb') SIZE 200M;
ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 7 ('+REDO/gkprd/redo07.stb') SIZE 200M;

All the same case, but standby_file_management=manual, at the end of duplicate we get

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

and in alert log

alter database rename file '+REDO/gkprd/redo01.log' to 'broken0'
Completed: alter database rename file '+REDO/gkprd/redo01.log' to 'broken0'
alter database rename file '+REDO/gkprd/redo02.log' to 'broken1'
Completed: alter database rename file '+REDO/gkprd/redo02.log' to 'broken1'
alter database rename file '+REDO/gkprd/redo03.log' to 'broken2'
Completed: alter database rename file '+REDO/gkprd/redo03.log' to 'broken2'

all redo renamed to 'broken'

SQL> select member from v$logfile;

MEMBER
--------------------------------------------------------------------------------
/opt/oracle/rdbms/19c/19.3.0.0.0/dbs/broken2
/opt/oracle/rdbms/19c/19.3.0.0.0/dbs/broken1
/opt/oracle/rdbms/19c/19.3.0.0.0/dbs/broken0
/opt/oracle/rdbms/19c/19.3.0.0.0/dbs/broken3
/opt/oracle/rdbms/19c/19.3.0.0.0/dbs/broken4
/opt/oracle/rdbms/19c/19.3.0.0.0/dbs/broken5
/opt/oracle/rdbms/19c/19.3.0.0.0/dbs/broken6

solution is rename log files manualy

alter database rename file 'broken0' to '+REDO/gkprd/redo01.log';
alter database rename file 'broken1' to '+REDO/gkprd/redo02.log';
alter database rename file 'broken2' to '+REDO/gkprd/redo03.log';
alter database rename file 'broken3' to '+REDO/gkprd/redo04.stb';
alter database rename file 'broken4' to '+REDO/gkprd/redo05.stb';
alter database rename file 'broken5' to '+REDO/gkprd/redo06.stb';
alter database rename file 'broken6' to '+REDO/gkprd/redo07.stb';