RMAN DUPLICATE SKIP READ ONLY DOES NOT SKIP READ ONLY TABLESPACES
(Doc ID 1582612.1)
Last updated on MARCH 17, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 11.2]
Information in this document applies to any platform.
Rman 'duplicate skip read only' does not skip read only tablespace and overwrites the datafile from the target Database when target and Auxiliary instance are running on the same host.
Duplicating the Database using for example:
set until scn 32771956;
allocate auxiliary channel c1 device type sbt;
duplicate target database to aux skip readonly;
release channel c1;
The duplicate will succeed but when stopping/starting the Target database, it will fail with for example:
ORA-01113: file 6 needs media recovery
ORA-01110: data file 6: '+<ASM diskgroup>/<db unique name>/datafile/<file name>'
Rman restores the datafile of the read only tablespace into the original location while ignoring the skip read only option.
This happens when the read only tablespace has been put 'read write' and back to 'read only' between the time of the backup and the duplicate.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!