Oracle Error From Recovery Catalog Database Ora-01422
(32-bit)) Show: Today's Messages :: Show Polls :: Message Navigator E-mail to friend ORA-01422: exact fetch returns more than requested number of [message #520759] Wed, 24 August 2011 10:16 kytemanaic Messages: 55Registered: February 2009 Member Hi, I have perform a failover and encounters the following problem. ORA-01422: exact fetch returns more than requested number of rows initially primary db: chicago physical standby db: boston after failover primary db:boston physical standby: NA after recreating physical standby primary db:boston physical standby: chicago over at chicago (new standby) log_archive_dest_3=E:\chicago_arc\ over at boston (new primary) log_archive_dest_3=E:\boston_arc\ over at boston when I connect to both boston as target db and recovery catalog RMAN> list archivelog like 'E:\CHICAGO_ARC\%'; List of Archived Log Copies Key Thrd Seq S Low Time Name ------- ---- ------- - --------- ---- 252690 1 10 A 22-AUG-11 E:\CHICAGO_ARC\10_759842424_1.ARC over at chicago when I connect to both chicago as target db and recovery catalog RMAN> list archivelog like 'E:\CHICAGO_ARC\%'; List of Archived Log Copies Key Thrd Seq S Low Time Name ------- ---- ------- - --------- ---- 252690 1 10 A 22-AUG-11 E:\CHICAGO_ARC\10_759842424_1.ARC however at E:\chicago_arc\ when I do a os check C:\Documents and Settings\Administrator>dir /w E:\chicago_arc\ Volume in drive E is New Volume Volume Serial Number is C874-DD6D Directory of E:\chicago_arc [.] [..] 100_759410562_1.ARC 101_759410562_1.ARC 102_759410562_1.ARC 103_759410562_1.ARC 10_759842424_1.ARC 11_759842424_1.ARC 12_759842424_1.ARC 13_759842424_1.ARC 14_759842424_1.ARC 15_759842424_1.ARC 16_759842424_1.ARC 17_759842424_1.ARC 18_759842424_1.ARC 19_759842424_1.ARC 20_759842424_1.ARC 21_759842424_1.ARC 22_759842424_1.ARC 23_759842424_1.ARC 24_759842424_1.ARC 94_759410562_1.ARC 95_759410562_1.ARC 96_759410562_1.ARC 97_759410562_1.ARC 98_759410562_1.ARC 99_759410562_1.ARC listener.ora 26 File(s) 9,077,989 bytes 2 Dir(s) 2,650,337,280 bytes free there's more files than indicated by rman also at both chicago and boston I ha
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet RMAN restoration fails with RMAN-06004 Article:000023269 Publish: Article URL:http://www.veritas.com/docs/000023269 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. http://www.orafaq.com/forum/t/174197/ Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Oracle restore is fails with error RMAN-06004: ORACLE error from recovery catalog database: ORA-01422: exact fetch returns more than requested number of rows Error Message RMAN-06004: ORACLE error from recovery catalog database: ORA-01422: exact fetch returns more than requested number of rows Cause The Oracle recovery catalog database https://www.veritas.com/support/en_US/article.000023269 used by RMAN is having some consistency issues. The inconsistencies in the recovery catalog are preventing RMAN from determining which backup set pieces to request from NetBackup to start the restore. Solution Initiate the restore without having RMAN connect to the recovery catalog database. Instead use the 'nocatalog' option and use the control file for the restore. If necessary, restore a copy of a known good control file first. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpful? Email Address (Optional) Your fstartightforward to restore the controlfile.When you issue the restore controlfile command, RMAN will retieve from teh recovery https://mohamedazar.com/2010/06/09/rman-06004-oracle-error-from-recovery-catalog-database/ catalog the location and name of the file that contains the control file backup and restores the control file approproately. Because the recovery catalog knows the http://www.dbaglobe.com/2009/12/rman-20005-how-to-unregister-database.html location of the RMAN backups piece, It doesn't matter whether the backup piece is in a flash recovery area or in a configured channel location. When oracle error you're connected to the recovery catalog, you can view backup information about your control files even while your target database is in nomount mode. To list backups of your controlfiles ,use the lsit command as shown here. RMAN>connect target / RMAN>connect catalog backup/backup@recover RMAN>startup nomount RMAN>list backup of ocntrolfile; If you have oracle error from registered two database in the recovery datalog with the same name, then you might receive an error such as this when you attempt to list backups or restore the control file RMAN-06004: ORACLE error from recovery catalog database RMAN-20005: target database name is ambiguous In this situation, you will need to first set your database identifier(dbid) before you can restore your control file. How to determine your DBID You can verify that you have multiple databases with the same name in your recovery catalog by querying the recovery catalog RC_DATABASE view sql>connect backup/backup@recover; sql> select db_key,dbid,name from rc_database; DB_KEY DBID NAME ----- --- ----- 1 1124743449 TEST 4241 1140772490 TEST Share this:FacebookTwitterEmailPrintLike this:Like Loading... Related From: Backup & Recovery ← Active/passive vs active /activeCluster Crash Recovery Overview → One Comment Post a comment Marvin # Very good explanation Thank You March 3, 2011 Reply Leave a Reply Cancel reply Enter your co
same database name, but different DBID, registered to the same calalog, during the restoration, must set DBID, otherwise, "RMAN-20005: target database name is ambiguous" error will raise.$ rman target / catalog rman/xxxxx@rmandbRecovery Manager: Release 10.2.0.4.0 - Production on Thu Dec 3 11:56:56 2009Copyright (c) 1982, 2007, Oracle. All rights reserved.connected to target database: hktst (not mounted)connected to recovery catalog databaseRMAN> run {2> allocate channel ch0 device type 'sbt';3> restore controlfile;4> }allocated channel: ch0channel ch0: sid=147 instance=hkdrt1 devtype=SBT_TAPEchannel ch0: Veritas NetBackup for Oracle - Release 6.5 (2009050106)Starting restore at 2009-DEC-03 11:57:20released channel: ch0RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of restore command at 12/03/2009 11:57:20RMAN-06004: ORACLE error from recovery catalog database: RMAN-20005: target database name is ambiguousRMAN> exitselect * from rc_database where name='HKTST' order by resetlogs_time; DB_KEY DBINC_KEY DBID NAME RESETLOGS_CHANGE# RESETLOGS---------- ---------- ---------- -------- ----------------- --------- 29211 29212 1902399835 HKTST 602821 15-OCT-09 30110 52364 1902498142 HKTST 841865 21-OCT-09 36494 221103 1902647353 HKTST 5191383 03-DEC-09How to unresgister a databaseman catalog rman/xxxxx@rmandbRecovery Manager: Release 10.2.0.4.0 - Production on Fri Dec 4 11:11:14 2009Copyright (c) 1982, 2007, Oracle. All rights reserved.connected to recovery catalog databaseRMAN> set dbid 1902399835;executing command: SET DBIDdatabase name is "HKTST" and DBID is 1902399835RMAN> unregister database;database name is "HKTST" and DBID is 1902399835Do you really want to unregister the database (enter YES or NO)? yesdatabase unregistere