RMAN-20005: target database name is ambiguous
RMAN Operation Fails With RMAN-20005: target data base name is ambiguous (Doc ID 224352.1)
RMAN-03002: failure of resync from db_unique_name command
RMAN catalog. In case you are not connected to the RMAN catalog you end up with the following error:
1
2
3
4
5
6
7
8
| RMAN> SHOW ARCHIVELOG DELETION POLICY FOR DB_UNIQUE_NAME 'DBIT121_SITE2';using target database control file instead of recovery catalogRMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of show command at 02/21/2017 13:58:53RMAN-05037: FOR DB_UNIQUE_NAME option cannot be used in nocatalog mode |
After connecting to the catalog, you can use this feature, e.g. to show the archive deletion policy.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| $ rman target sys/welcome1 catalog /@rcatRecovery Manager: Release 12.1.0.2.0 - Production on Tue Feb 21 14:25:10 2017Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.connected to target database: DBIT121 (DBID=644484523)connected to recovery catalog databaseRMAN> SHOW ARCHIVELOG DELETION POLICY FOR DB_UNIQUE_NAME 'DBIT121_SITE1';RMAN configuration parameters for database with db_unique_name DBIT121_SITE1 are:CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY BACKED UP 1 TIMES TO DISK;RMAN> SHOW ARCHIVELOG DELETION POLICY FOR DB_UNIQUE_NAME 'DBIT121_SITE2';RMAN configuration parameters for database with db_unique_name DBIT121_SITE2 are:CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY; |
There are quite a lot options which can be combined with the DB_UNIQUE_NAME feature like the following.
1
2
3
| LIST ARCHIVELOG ALL FOR DB_UNIQUE_NAME 'DBIT121_SITE2';REPORT SCHEMA FOR DB_UNIQUE_NAME 'DBIT121_SITE2';SHOW ALL FOR DB_UNIQUE_NAME 'DBIT121_SITE2'; |
But getting back to my issue. I was running a resync catalog from my Standby database and ended up with the following error:
1
2
3
4
5
6
7
8
| RMAN> RESYNC CATALOG FROM DB_UNIQUE_NAME 'DBIT121_SITE1';resyncing from database with DB_UNIQUE_NAME DBIT121_SITE1RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03009: failure of resync from db_unique_name command on default channel at 02/21/2017 13:08:42RMAN-20005: target database name is ambiguous |
RMAN says that the target database name is ambiguous. But what does this mean. Let’s take a look a the RMAN error with the oerr utility. The oerr utility can not only be used with “ORA” error codes like “oerr ora 01555”, but also with “RMAN” error codes.
1
2
3
4
5
| $ oerr rman 2000520005, 1, "target database name is ambiguous"// *Cause: two or more databases in the recovery catalog match this name// *Action:// |
Ok. This error is much more precise. Looks like that RMAN found more the one database called DBIT121 in the catalog, and so RMAN does not know, on which DBID to perform the requested command. Ok. So let’s connect to the RMAN catalog and check if this is really the case.
1
2
3
4
5
6
7
8
9
| SQL> SELECT DB.DB_KEY,DB.DB_ID, DB.CURR_DBINC_KEY, DBINC.DB_NAME FROM DB, DBINC WHERE DB.CURR_DBINC_KEY = DBINC.DBINC_KEY AND DBINC.DB_NAME = 'DBIT121' ; 2 3 4 DB_KEY DB_ID CURR_DBINC_KEY DB_NAME---------- ---------- -------------- -------- 1 642589239 2 DBIT121 546780 644484523 546781 DBIT121 |
Indeed. I do have two different DBID’s pointing to the same DB_NAME. Kinda confusing for RMAN. But which one is the one that have been backed up. We could query the RC_BACKUP_SET and RC_BACKUP_PIECE views to find that out.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
| SQL> SELECT RBS.DB_KEY , RD.NAME , RBS.DB_ID 2 3 4 , RBS.BS_KEY , RBS.RECID , RBS.STAMP , RBS.BACKUP_TYPE , RBS.START_TIME, STATUS 5 6 7 8 9 FROM RC_BACKUP_SET RBS, RC_DATABASE RD WHERE RBS.DB_KEY=RD.DB_KEY AND RBS.DB_ID=RD.DBID AND RD.NAME='DBIT121' ; 10 11 12...... DB_KEY NAME DB_ID BS_KEY RECID STAMP B START_TIM S---------- -------- ---------- ---------- ---------- ---------- - --------- - 546780 DBIT121 644484523 555608 3070 936496831 I 21-FEB-17 A 546780 DBIT121 644484523 555609 3071 936496832 I 21-FEB-17 A 546780 DBIT121 644484523 555610 3072 936496836 D 21-FEB-17 A 546780 DBIT121 644484523 555611 3073 936496860 D 21-FEB-17 A 546780 DBIT121 644484523 555612 3074 936496875 D 21-FEB-17 A 546780 DBIT121 644484523 555613 3075 936496884 D 21-FEB-17 A 546780 DBIT121 644484523 555614 3076 936496890 D 21-FEB-17 A 546780 DBIT121 644484523 555615 3077 936496895 L 21-FEB-17 A 546780 DBIT121 644484523 555616 3078 936496897 L 21-FEB-17 A 546780 DBIT121 644484523 555617 3079 936496897 L 21-FEB-17 A 546780 DBIT121 644484523 555618 3080 936496898 D 21-FEB-17 A DB_KEY NAME DB_ID BS_KEY RECID STAMP B START_TIM S---------- -------- ---------- ---------- ---------- ---------- - --------- - 546780 DBIT121 644484523 555619 3081 936496900 D 21-FEB-17 A 546780 DBIT121 644484523 555620 3082 936498788 D 21-FEB-17 A 546780 DBIT121 644484523 555621 3083 936502389 D 21-FEB-17 A 546780 DBIT121 644484523 555622 3084 936505991 D 21-FEB-17 A 546780 DBIT121 644484523 555623 3085 936509589 D 21-FEB-17 A 546780 DBIT121 644484523 555624 3086 936513189 D 21-FEB-17 A 546780 DBIT121 644484523 555625 3087 936516788 D 21-FEB-17 A 546780 DBIT121 644484523 555626 3088 936520387 D 21-FEB-17 A 546780 DBIT121 644484523 555627 3089 936523988 D 21-FEB-17 A 546780 DBIT121 644484523 555628 3090 936527608 D 21-FEB-17 A 546780 DBIT121 644484523 555629 3091 936531188 D 21-FEB-17 A...... |
After checking the output, I see that DBID 644484523 is the correct one, and DBID 642589239 is the one I want to get rid of.
To do so, we can shutdown the Standby database and start it up with nomount. The reason for that, is that you can’t issue the SET DBID command against a database which is mounted or open.
1
2
3
4
5
6
7
8
| RMAN> SET DBID=642589239;executing command: SET DBIDRMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of set command at 02/21/2017 13:15:26RMAN-06188: cannot use command when connected to a mounted target database |
Ok. Let’s go the nomount and execute the “unregister database;” command after the correct DBID is set.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
| $ rman target sys/welcome1 catalog /@rcatRecovery Manager: Release 12.1.0.2.0 - Production on Tue Feb 21 14:25:10 2017Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.connected to target database: DBIT121 (not mounted)connected to recovery catalog databaseRMAN> SET DBID=642589239;executing command: SET DBIDdatabase name is "DBIT121" and DBID is 642589239RMAN> unregister database;database name is "DBIT121" and DBID is 642589239Do you really want to unregister the database (enter YES or NO)? YESdatabase unregistered from the recovery catalogRMAN> |
Let’s check the RMAN catalog again.
1
2
3
4
5
6
7
8
| SQL> SELECT DB.DB_KEY, DB.DB_ID, DB.CURR_DBINC_KEY, DBINC.DB_NAME FROM DB, DBINC WHERE DB.CURR_DBINC_KEY = DBINC.DBINC_KEY AND DBINC.DB_NAME = 'DBIT121' ; 2 3 4 DB_KEY DB_ID CURR_DBINC_KEY DB_NAME---------- ---------- -------------- -------- 556718 644484523 556719 DBIT121 |
Cool. Looks much better. Now my resync catalog from SITE1 issued from SITE2 works again.
1
2
3
4
5
6
7
8
9
10
11
12
13
| RMAN> LIST DB_UNIQUE_NAME OF DATABASE;List of DatabasesDB Key DB Name DB ID Database Role Db_unique_name------- ------- ----------------- --------------- ------------------556718 DBIT121 644484523 PRIMARY DBIT121_SITE1556718 DBIT121 644484523 STANDBY DBIT121_SITE2RMAN> RESYNC CATALOG FROM DB_UNIQUE_NAME 'DBIT121_SITE1';resyncing from database with DB_UNIQUE_NAME DBIT121_SITE1starting full resync of recovery catalogfull resync complete |
No comments:
Post a Comment