Search This Blog

Tuesday, January 17, 2017

RMAN-05520: database name mismatch, auxiliary instance has PROD, command specified CLONE

Hello DBA's,

Lemme just help with how to resolve the error :

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/17/2017 11:02:45
RMAN-05501: aborting duplication of target database
RMAN-05520: database name mismatch, auxiliary instance has PROD, command specified CLONE

Cause:

I started the duplicate while instance is in nomount and duplicate returned into error after mounting the database due to no backup or found. This duplicate was triggered after connecting to both target and auxiliary instances. During the clone RMAN will begin the clone instance with the target instance name (its PROD in my case) and  proceed with the duplicate. When the duplication is successful it will clone the database with the auxiliary instance name. Since the duplicate resulted into error it left the instance with target instance name (PROD).

Fix :

- Just shut abort or immediate the auxiliary instance.
- Start the auxiliary instance (CLONE) in nomount using pfile
- Re-run the duplicate

Thanks!
Hope this helps.
at

1 comment:

  1. DBAApril 9, 2020 at 7:38 AM

    Thank you for the post.
    1 correction though, after starting the auxiliary instance in nomount using pfile, you need to create the spfile from pfile.
    Otherwise the RMAN duplicate command uses the existing spfile, which has the old entries.

    ReplyDelete

Subscribe to: Post Comments (Atom)

You cannot complete this task because one of the following events caused a loss of page data: A system failure has occurred "Front end is locked after 12.2 upgrade"

  If you have upgraded to Oracle E-Business Suite 12.2.10 Release Update Pack from Oracle E-Business Suite 12.2.6 Release Update Pack (or ea...