Go up

Next thread:	Convert Rows into Columns
Prev thread:	ONE STANDBY DB FOR MULTIPLE PRIARY DB

Message	Score	Author	Date
When trying to list the backup summary by connecti......		shastry mys	Feb 09, 2010
Hi Shastry, Was the datbase recently restored? ......		Noufal Paramboor	Feb 09, 2010
Hi Noufel, Yes we have successfully restored so......		shastry mys	Feb 09, 2010
Hi Shastry, as per metalink notes, This prob......		Noufal Paramboor	Feb 09, 2010

Follow up by mail

Click here

---

Subject:	Rman Restore issue
Author:	shastry mys, India
Date:	Feb 09, 2010, 211 days ago
Os info:	Solaris
Oracle info:	9207
Message:	When trying to list the backup summary by connecting to catalog from target system, i'm getting the following error RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of list command at 02/08/2010 21:08:36 RMAN-03014: implicit resync of recovery catalog failed RMAN-00600: internal error, arguments [9018] [resync_flag] [] [] [] Please help me on this regard Thanks in Advance Thanks, Smys
Goto:	Reply - Top of page

If you think this item violates copyrights, please click here

---

Subject:	Re: Rman Restore issue
Author:	Noufal Paramboor, India
Date:	Feb 09, 2010, 211 days ago
Message:	Hi Shastry, Was the datbase recently restored? Regards, Noufal
Your rating?:	This reply is Good Excellent
Goto:	Reply - Top of page

If you think this item violates copyrights, please click here

---

Subject:	Re: Rman Restore issue
Author:	shastry mys, India
Date:	Feb 09, 2010, 211 days ago
Message:	Hi Noufel, Yes we have successfully restored source database as other DEV database in other server. This is the first time we are restoring in current server; we have RMAN netbackup enabled. Thanks, Achutha Shivashankar
Your rating?:	This reply is Good Excellent
Goto:	Reply - Top of page

If you think this item violates copyrights, please click here

---

Subject:	Re: Rman Restore issue
Author:	Noufal Paramboor, India
Date:	Feb 09, 2010, 211 days ago
Message:	Hi Shastry, as per metalink notes, This problem is provoked by the following facts: 1. The database has been duplicated from outside RMAN and the DBID had not been modified, consequently the DBID is the same for the cloned and the production database... 2. A new database has been registered in the RMAN catalog. You may check this using below steps a. The RMAN recovery catalog views will show the following: RMAN> list incarnation of database; b. SQL> select RESETLOGS_CHANGE# from v$database; SQL>select name,DBID,RESETLOGS_TIME from rc_database order by 1; c. SQL>select db_key,DBID,name,current_incarnation from rc_database_incarnation order by 1; and the recommended solution in metalink is to unregister and reregister the database. Note: Before unregister take an export backup of the catalog schema to be at a safer side.
Your rating?:	This reply is Good Excellent
Goto:	Reply - Top of page

If you think this item violates copyrights, please click here