Versions 10.2, 11.1, 11.2, 12.1
Error: RMAN-05520 database name mismatch, auxiliary instance has %s, command specified
%s
---------------------------------------------------------------------------
Cause:-
The database name specified in the initialization parameter was not the same as the database name provided in the DUPLICATE command.
Solution:-
Correct the database name in the command or adjust the database name of the auxiliary instance.
OR
Rman leaves modified auxiliary spfile parameters if DUPLICATE fails (Doc ID 1283344.1) To BottomTo Bottom
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.1 [Release 11.2]
Information in this document applies to any platform.
SYMPTOMS:-
RMAN duplicate leaves behind an spfile for the auxiliary database if the duplicate fails with db_name set to the target db_name.
This causes subsequent rerun of the duplicate after fixing the failure to fail with:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/26/2010 13:22:29
RMAN-05520: database name mismatch, auxiliary instance has <target db_name>, command specified <auxilliary db_name>
CAUSE:-
Bug 9302045: RMAN DUPLICATE W/O CONNECTION TO TARGET CREATES SPFILE WITH DB_NAME OF TARGET.
This is a duplicate of unpublished bug 9393650: IF AUXILIARY STARTED WITH SPFILE AND DUPLICATE FAILS SPFILE HAS BAD PARAMETERS
SOLUTION:-
Manually amend the auxiliary spfile prior to rerunning duplicate or request a backport of unpublished bug 9393650 to 11.2.0.1 for your platform.
Unpublished bug 9393650 is fixed in 11.2.0.2 Patch Set Release.
REFERENCES
BUG:9302045 - RMAN DUPLICATE W/O CONNECTION TO TARGET CREATES SPFILE WITH DB_NAME OF TARGET
Error: RMAN-05520 database name mismatch, auxiliary instance has %s, command specified
%s
---------------------------------------------------------------------------
Cause:-
The database name specified in the initialization parameter was not the same as the database name provided in the DUPLICATE command.
Solution:-
Correct the database name in the command or adjust the database name of the auxiliary instance.
OR
Rman leaves modified auxiliary spfile parameters if DUPLICATE fails (Doc ID 1283344.1) To BottomTo Bottom
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.1 [Release 11.2]
Information in this document applies to any platform.
SYMPTOMS:-
RMAN duplicate leaves behind an spfile for the auxiliary database if the duplicate fails with db_name set to the target db_name.
This causes subsequent rerun of the duplicate after fixing the failure to fail with:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/26/2010 13:22:29
RMAN-05520: database name mismatch, auxiliary instance has <target db_name>, command specified <auxilliary db_name>
CAUSE:-
Bug 9302045: RMAN DUPLICATE W/O CONNECTION TO TARGET CREATES SPFILE WITH DB_NAME OF TARGET.
This is a duplicate of unpublished bug 9393650: IF AUXILIARY STARTED WITH SPFILE AND DUPLICATE FAILS SPFILE HAS BAD PARAMETERS
SOLUTION:-
Manually amend the auxiliary spfile prior to rerunning duplicate or request a backport of unpublished bug 9393650 to 11.2.0.1 for your platform.
Unpublished bug 9393650 is fixed in 11.2.0.2 Patch Set Release.
REFERENCES
BUG:9302045 - RMAN DUPLICATE W/O CONNECTION TO TARGET CREATES SPFILE WITH DB_NAME OF TARGET
No comments:
Post a Comment