We came across something in RMAN while working on a duplicate database. The ‘skip tablespace’ command when doing an RMAN duplicate database will work for self-contained tablespaces, but not for a set of self-contained tablespaces. In other words, if each tablespace can be individually dropped, its fine, but where the indexes are placed separately from the tables, this won’t work for the duplicate.
Oracle calls it “not a bug”. read more on Metalink.
Share this
You May Also Like
These Related Stories
How to retrieve growth history for oracle tablespaces
How to retrieve growth history for oracle tablespaces
Feb 28, 2019
3
min read
Using transportable tablespaces with partitioned tables
Using transportable tablespaces with partitioned tables
Apr 6, 2017
4
min read
Be Careful When Revoking UNLIMITED TABLESPACE
Be Careful When Revoking UNLIMITED TABLESPACE
Mar 5, 2013
2
min read
No Comments Yet
Let us know what you think