Ora-19571 Archived-log Recid Stamp Not Found In Control File
Tagged: how to solve ora-19588, ORA-19588: archived log recid stamp is no longer valid, resolving ora-19588. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
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.
Command
Error
Thanks for any help.
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:
Aiohow.fun is not responsible for third party website content. Ravishankar guruji bhajans mp3 free download.
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.
Ora-19571 Archived Log Recid Stamp Not Found In Control File
Not the answer you're looking for? Browse other questions tagged oracleoracle-12crmanduplication or ask your own question.
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.
Command
Error
Thanks for any help.
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. 2005 pro bowl highlights.
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.
Not the answer you're looking for? Browse other questions tagged oracleoracle-12crmanduplication or ask your own question.
Comments are closed.