Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

RMAN-20002: target database already registered in recovery catalog

rysalkaFeb 18 2010 — edited Feb 18 2010
Hi, we are on Oracle 10.2.0.4 + RMAN + RMAN catalog. I think I know what the reason for this error is, I am not sure how to fix it. We have several databases registered in the recovery catalog. We have PROD and TEST (which is a copy of PROD). I have been backing up TEST via RMAN regulary while connecting to RMAN catalog. When I try to backup PROD, I get the following error:
RMAN-03002: failure of resync command at 02/18/2010 11:58:31
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20004: target database name does not match name in recovery catalog
I urregister PROD from the recovery catalog and when I try to register it again I get the same error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 02/18/2010 12:11:20
RMAN-20002: target database already registered in recovery catalog
When I connect to PROD and catalog I see the folloiwng DBID:
RMAN> @connect.rman

RMAN> connect target *
connected to target database: PROD (DBID=4145236187)

RMAN> connect catalog *
connected to recovery catalog database
When I query the recovery database I see TEST database with the same dbid:
SQL> select * from rc_database;

    DB_KEY  DBINC_KEY       DBID NAME     
---------- ---------- ---------- -------- ----------------- ---------
    451123     451124 2701541377 WWW2TST          
      1591     948410  361284079 DPAPRD           
    984705     984706  115452459 PAYDEV                   
    985910     985911 2816177861 PAYPROD                  
         1      68172 3999986570 DPA                
   1001250    1005532 4145236187 TEST        

6 rows selected.
So I guess when we refresh TEST with PROD backups, it inherits PROD's dbid? Because of it, I cannot register PROD in the catalog now. Does anyone know a way out of this? We will be refreshing TEST every month - how do we refresh it with different dbid? Thank you!
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 18 2010
Added on Feb 18 2010
1 comment
5,400 views