Did you guys ever performed RMAN DUPLICATION from a production backup which has block change tracking (BCT) enabled ?
I had to duplicate only one application tablespace to an AUXIL instance on test server from the backups of production.
I used RMAN script as below:
|SERVER1\:/flash/data/auxil/auxil >rman auxiliary /Recovery Manager: Release 184.108.40.206.0 – Production on Thu Oct 30 03:51:11 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to auxiliary database: AUXIL (not mounted)
This RMAN DUPLICATION will do a successful restoration and fails after recovering almost 80% of the archive log files with the error:
Don’t you think, why RMAN is looking out for Block CHANGE tracking file during the recovery of the datafiles?
I have raised this case to Oracle Support and they advised the following:
- Apply the patch 11744544 and issue set newname for block change tracking file to new; – This doesnt work as the error says that it is unable to find BCT, then what benefits us renaming it.
- Asked to disable BCT on production and take the backup to restore – This is not at all possible, will you ever disable a BCT on production where daily incremental backups are scheduled?
- To set autoextend off on datafiles – This seems to be fine, but we have been using BIGFILE tablespaces with autoextend on, so doesnt imply us.
A new Bug 20301188 has been raised by oracle and development is still working. It has been more than 9 months and still development is working on this 🙂