Ora-19571 Archived-log Recid Stamp Not Found In Control File
I am trying to duplicate a DB from live to dev but it is failing. Can anybody advise what is going wrong? Both databases are running Oracle 12c. All database files seem to be copied over but it fails when trying to apply the archive logs.
I am running a full database and archive log backup before executing the DUPLICATE command.
How to fix ORA-19571 during running of RMAN? Alex Lima October 23, 2008 January 23, 2017 General DBA, RMAN. ORA-19571: archived-log recid 173477 stamp 668795179 not found in controlfile. Check control_file_record_keep_time.
Command
- Mar 23, 2018 - ORA-19571: archived-log recid 118360 stamp 705446770. Recid 118360 stamp not found in control file. ORA-19571: archived-log recid.
- ORA-19571: archived-log recid 94689 stamp 653763600 not found in controlfile ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices.
Error
Thanks for any help.
Ora-19571 Archived Log Recid Stamp Not Found In Control File
1 Answer
Could you please tell us how you connected to rman?
For example:
The reason for you problem is that the two databases have trouble communicating with each other.
If you use auxiliary / because your rman session is located on the dev server this is not going to work. The reason is pretty simple as follows.
Lets say your rman session was opened on server dev. You use this connection:
The auxiliary database uses the TNSalias 'prod' to connect to the target database. The prod database uses the TNSalias 'dev' to connect to the auxiliary database. This means you have to configure the tnsnames.ora on both sides to be able to connect to the other database. Since the rman session is on dev in this example you have to configure the TNSalias 'dev' on dev as well.
Back to the example with auxiliary /, it is obvious now why it cannot work.
Then there are additional stuff to keep in mind. The auxiliary database needs to be restarted several times. In some cases you loose the connection to the auxiliary database when it shuts down. This means you have to configure the dev database in the SID_LIST of the listener on the dev server. And take care that the password file is present.
Well, this sounds like a lot configuration overhead. If you have to refresh your dev database frequently this is not a big deal. But I personally prefer to clone from backup location because this is much more simple. You can also skip the SPFILE clause when you create it manually. In my experience you need 2 or 3 attempts to work out the correct parameter conversion. If some parameters change on your prod database you might have to adjust this clause again.
