RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target

Similar Questions

• RMAN-06004: ORACLE recovery catalog database error: ORA-03113: end - of -

  Hello
  
  I experience backup scripts. because once done, she will move to pod pre box.
  
  Database runs in mode archvelog
  I have lgged in the dbserver himself.
  
  the shell scripts is:
  #! / usr/bin/sh
  source. / game - env # this file will have ID password for catalogue and the target sources
  echo executing command: database Backup
  ECHO
  RMAN TARGET $dbuser / $dbpwd$ rmandb CATALOG $rmanuser/$rmanpwd@$rmandb < < eof
  Run {}
  stop immediately;
  start-up;
  }
  expressions of folklore
  output
  
  
  When I run, I get the following error
  
  connected to target database: HERMESQA (DBID = 3819666523)
  connected to the recovery catalog database
  
  RMAN > 2 > 3 > 4 > 5 >
  database closed
  dismounted database
  Instance Oracle to close
  
  connected to the database target (not started)
  Oracle instance started
  mounted database
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the boot command at 11/06/2009 11:27:54
  RMAN-06004: the recovery catalog database ORACLE error: ORA-03113: end of file on communication channel
  
  could you suggest where I have error.
  
  Thank you
  Benjamin Gopal

  Do not back up the database using the same catalog of recovery recovery catalog of accommodation. You could just try it back up without a recovery catalog and to ensure that this database has an automatic backup of controlfile, for example.

• RMAN-20001: target not found in the recovery catalog database

  I'm practicing the loss of all control files. I have backups of catalog rman configured for controlfile autobackup. So far, I did this.
  
  
  RMAN > startup nomount;
  Oracle instance started
  
  Total System Global Area 209715200 bytes
  
  Bytes of size 1272864 fixed
  155190240 variable size bytes
  Buffers 50331648 database bytes
  Redo buffers 2920448 bytes
  
  
  RMAN > restore controlfile autobackup.
  
  From restoration to SEPT. 08.-10
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 156 devtype = DISK
  
  field of recovery destination: / u02/flash_recovery
  name of database (or unique name of database) used for research: TEST
  channel ORA_DISK_1: autobackup found in the recovery area
  channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
  channel ORA_DISK_1: restore full automatic backup of control file
  output filename=/u02/control_files/TEST/control02.ctl
  output filename=/u03/oradata/TEST/control03.ctl
  Restoration finished in 08-SEVEN.-10
  
  RMAN > change the editing of the database;
  
  mounted database
  output channel: ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure to modify the order db at 08/09/2010 14:54:50
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target not found in the recovery catalog database
  
  
  I guess it has something to do with the DBID but... I don't have and I do not know how to find.

  Hello
  Try this
  RMAN > Connect target /.
  RMAN > Connect catalog rman/rman@test
  RMAN > startup nomount;
  RMAN > list backup of controlfile;

• RMAN-06004: error recovery catalog database ORACLE

  Hi all
  
  I'm new to the RMAN module, please help me solve the error below.
  

  Recovery Manager: Release 9.2.0.6.0 - Production
  
  Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.
  
  connected to target database: DB96 (DBID=2450380394)
  connected to recovery catalog database
  
  RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '\\10.101.22.80\Backup\Rman\Prologs\DB96/DB96_FULL_%T_%U.rman' MAXPIECESIZE 4 G; 
  2> CONFIGURE CONTROLFILE AUTOBACKUP ON; 
  3> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '\\10.101.22.80\Backup\Rman\Prologs\DB96/DB96_ctlfile_%F'; 
  4> CONFIGURE RETENTION POLICY TO REDUNDANCY 1; 
  5> shutdown immediate; 
  6> startup mount; 
  7> backup database; 
  8> CROSSCHECK BACKUP; 
  9> DELETE NOPROMPT OBSOLETE; 
  10> alter database open; 
  11> list backup summary; 
  12> exit;
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of configure command at 06/20/2011 11:31:55
  RMAN-06004: ORACLE error from recovery catalog database:
   
  RMAN-20001: target database not found in recovery catalog
  Recovery Manager complete.

  Please do the neeful.
  
  Kind regards
  Jame

  Jame,

  connect to retrieve catalog owner user (RMAN) using SQLPLUS on the catalog database and run the following query.

  SQL> select * from rc_database;
  

  Another thing is, check, if your catalog is accidentally created in the target database or you sure sound in a separate database (possibly on a separate server).

  Thank you
  RANA

  Published by: RANA June 20, 2011 17:08

  Published by: RANA June 20, 2011 17:41

• RMAN-04004: recovery catalog database error: ORA-12170: TNS: connect the ti

  Hello:
  
  Last night ' RMAN backup error: ' RMAN-04004: recovery catalog database error: ORA-12170: TNS: Connect timeout.
  
  I can sqlplus to the target database and the catalog database. The listener is in place. What is the problem? What should I check?
  
  Thanks in advance for your help.

  in the oratest/orapass@rmandb1 CATALOG,.

  rmandb1 is the name of the service. normally the name of the service and the name of db are kept same.

  check rmandb1 tnsping where you try to run ' RMAN TARGET / CATALOG oratest/orapass@rmandb1 "command.

  as optput will get the ip address of the server on which db is resident, no port, Protocol

  as

  ---------

  [Oracle@RAC3 ~] $ tnsping orcl

  AMT Ping utility for Linux: Version 10.2.0.5.0 - Production on December 23, 2011 21:12:20

  Copyright (c) 1997, 2010, Oracle. All rights reserved.

  Use settings files:
  /opt/app/Oracle/product/DB/10.2.1/network/admin/SQLNET.ora

  TNSNAMES adapter used to resolve the alias
  Try to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = rac3.rajesh.com) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl)))
  OK (10 ms)
  -------------------------------

  Here the HOST = rac3.rajesh.com is the present db Server

  Published by: Rajesh.Rathod on December 23, 2011 07:43

• ORA-25408: can not read the appeal during a duplicate backup with rman catalog database safely

  Hello

  I did a database duplicate backup with rman catalog connection and got the ORA-25408: cannot read error call safely.

  The catalog database is running in a Data Guard environment.

  During the double process database failover occurred because of a server restart.

  The restore of the data files was successful:

  RMAN-08023: channel t1: restored the backup part 1

  RMAN-08180: channel t1: restoration complete, duration: 00:01:15

  RMAN-03091: finished the restoration at 27.08.2014 09:27:10

  During execution of script memory:

  RMAN-08161: content of the Script from memory:

  {

  switch from clone datafile;

  }

  RMAN-08162: execution of Script memory

  I got this error:

  RMAN-08162: execution of Script memory

  RMAN-08031: output channel: t1

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of Db in dual at 27/08/2014 09:27:10

  RMAN-05501: abandonment of duplicate target database

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-06004: ORACLE recovery catalog database error: ORA-25408: cannot read safely call

  Dual boot time: 16:00

  Failover time: 18:00

  Error time: 09:00 the next day

  DB version: 11.2.0.4.0, not the RAC environment, single instances

  That's happened? My My db catalog rman session did not survive? Why the error happened at 09:00 (and not 17:00)? Why the session called the catalog rman during switching of the data files?

  Can someone explain it to me?

  Thank you!

  Hello

  The connection of the RMAN catalog remains inactive during the backup/restore process, once rman completes the task and try to activate the connection it gets error.

  What is expected as you said the rebooted server. If this happens because of the expiration time, we went with the parameter net expire_time to maintain the connection.

  Thank you

  Bigot

• RMAN - 06004:ORACLE error in the recovery catalog. ORA-00904: invalid...

  Hello all,.
  
  One of our backups RMAN fails with the following error message. Any suggestions would be greatly appreciated.
  
  ==================================================================================================
  
  From backup 2008-12-30 22:03:47
  using channel ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to 2008-12-30 22:03:47
  RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier
  
  RMAN >
  RMAN > #BACKUP # ARCHIVELOG delete all '% d_bkp_al_ % t_Set % s_Piece %p' entry FORMAT;
  2 >
  3 > # DELETE ARCHIVELOG until ' SYSDATE-7 ";
  4 >
  5 > # check if the database can be restored
  6 > RESTORE DATABASE # VALIDATE;
  7 >
  8 > # check if controlfile can be restored
  9 > #RESTORE # CONTROLFILE to ' / backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
  10 >
  11 > # check if archivelogs for these past two weeks can be restored
  12 > # RESTORE ARCHIVELOG FROM TIME ' SYSDATE-7' VALIDATE ';
  13 >
  14 > #-check all backups on backup media are intact
  15 > # CROSSCHECK BACKUP OF DATABASE;
  16 >
  17 > #-display based on a list of files that need to be stored on the retention
  18 > policy #. For this case study, the files that do not have at least 1 backups
  19 > # will be reported.
  20 > REPORT NEED backup.
  RMAN retention policy apply to the order
  RMAN retention policy is set to 7 days recovery window
  Report of the files whose recovery needs more 7 days of archived newspapers
  Days of files name
  ---- ----- -----------------------------------------------------
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of command report at 2008-12-30 22:03:48
  RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier
  
  RMAN >
  RMAN > #-remove unnecessary backups. This command deletes the backups based on the
  2 > retention policy of #.
  3 > # commented DELETE OBSOLETE - TSM not configured to remove on 68
  4 > #DELETE # OBSOLETE;
  5 >
  6 > #-complete list of the existing backups
  7 > LIST BACKUP;
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the list command at 2008-12-30 22:03:49
  RMAN-06004: the recovery catalog database ORACLE error: ORA-00904: invalid identifier
  
  RMAN >
  RMAN > # end of file.
  2 > * end-of-file *.
  
  RMAN >
  
  Published by: ORA_UMAIR on December 31, 2008 07:51

  No help is possible.
  You publish a file of newspaper only, and can not see the command that failed.
  Also you include, contrary to the recommendation in the post on Forums label, the complete version number of 4-digit.
  This is important because they either has an error in your script that does not find RMAN or you hit a bug.

  -----
  Sybrand Bakker
  Senior Oracle DBA

• Error during the registration of RMAN from the primary to the catalog database

  Hi all
  
  Here we have an environment with db1 (db_unique_name) 10g dataguard as primary and db2 (db_unique_name) Physics of the standby database. Also, we have configured a schema on a third computer as a database of catalog using following steps.
  
  The measures taken in the catalog database (appsdb):
  
  SQL > create tablespace rmancatlog_tbs datafile ' / u01/app/oracle/oradata/NEW/rman_catalog.dbf' size 500M autoextend extent management local segment space management auto;
  
  SQL > create user rman identified by oracle
  2 default tablespace rmancatlog_tbs
  3 unlimited quota on rmancatlog_tbs
  4;
  
  SQL > GRANT connect, resource, recovery_catalog_owner to rman;
  
  RMAN > create catalog.
  Recovery catalog created
  
  AMT added entries of catalog in primary and standby database. Then the primary database, we have tried to register for the catalog database. It shows that it registers. But all queries later rman throws the error. Here are the steps and the error:
  
  [oracle@db1 ~] $ rman target sys/oracle catalog rman/oracle@appsdb
  Recovery Manager: release 10.2.0.3.0 - Production on Mon Aug 13 21:39:32 2012
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  connected to target database: NIOS (DBID = 1589015669)
  connected to the recovery catalog database
  
  RMAN > register database;
  registered in the recovery catalog database
  
  RMAN > outline report;
  Report of the database schema
  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  ----
  -------------------- ------------------------
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of command report to the 08/10/2012 06:16:06
  [RMAN-00600: internal error, arguments [8201] [] [] []]
  
  Can anyone help on this error?
  Thanks in advance.

  Hello;

  Then, you have to re-create the controlfile to the target database. (Not funny)

  I like to use the method of trace file myself.

  How to recreate a Controlfile [ID 735106.1]

  Best regards

  mseberg

• Information on RMAN catalog database using and any catalog (controlfile)

  Hi all.

  I´d like some clarification on the subjects of RMAN RMAN usage with or without a recovery catalog (database / schema):

  (1) will be the database controfile target always store ALL changes made on RMAN? For example, configure changes persistent RMAN as a retention strategy, controfile autobackup, backup optimization and so forth, these will always record on the target database controlfile, even if we're connecting to RMAN with a recovery catalog?

  (2) what happens if we stop using the recovery catalog? I mean, if you don't use stored scripts and shot through the OS jobs or same EM control database, may continue to use then and do not connect more on the recovery catalog? It will be a problem? My target database stops?

  I will be the legacy a few databases to administer and they connects to a catalog of recovery of database / schema, it's good, but I want to set up my own backup and restore policies / procedures in a two-step process: (1) have each configuration of RMAN database on controlfile, Later (2) in view of the use of the recovery catalog to centralized databases and keep more disk backup and restore.

  Thanks in advance!

  (1) Yes, everything about the structure of data is stored in the controlfile. The location of the backup controlfile is also stored in the controlfile.

  The backup controlfile location is also stored in the catalog if you synchronize to it.

  (2) you can stop immediately using the catalog if you choose, and as long as you have a backup RMAN script file, you can always backup using this file.

  The catalog is used to store the location of the backupsets, and copy image. If you have any scripts to store, it can store these too. Really, it's all done catalog.

  You can back up and restore/recover without a catalog, as long as you know where all backups are retained.

• Record number of databases in a recovery catalog

  Hello

  How can register for multiple databases targets unrelated in a unique recovery catalog.

  Suppose I have DEV and TEST databases with different dbid and you wish to register in a single commune RC.

  Kindly advice.

  Thank you

  REDA

  We do this on a regular basis in our shop.

  We will have the DEV and TEST on SERVERA, databases while the catalog RMAN (RMANCAT) is located on server b.

  The entries in tnsnames.ora on ServerB:

  RMANCAT =

  (DESCRIPTION =

  (ADDRESS = (PROTOCOL = TCP) (HOST = SERVERB)(PORT = 1541))

  (CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = rmancat)

  )

  )

  LISTENER_RMANCAT =

  (ADDRESS = (PROTOCOL = TCP) (HOST = SERVERB)(PORT = 1541))

  ----------------------------------------------------------------------------------

  The entries in tnsnames.ora on SERVERA:

  LISTENER_DEV =

  (ADDRESS = (PROTOCOL = TCP) (HOST = SERVERA)(PORT = 1551))

  DEV =

  (DESCRIPTION =

  (ADDRESS = (PROTOCOL = TCP) (HOST = SERVERA)(PORT = 1551))

  (CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = dev.servera.something.com)

  )

  )

  LISTENER_TEST =

  (ADDRESS = (PROTOCOL = TCP) (HOST = SERVERA)(PORT = 1551))

  TEST =

  (DESCRIPTION =

  (ADDRESS = (PROTOCOL = TCP) (HOST = SERVERA)(PORT = 1551))

  (CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = test.servera.something.com)

  )

  )

  RMANCAT_SERVERB =

  (DESCRIPTION =

  (ADDRESS_LIST =

  (ADDRESS = (PROTOCOL = TCP) (HOST = SERVERB)(PORT = 1541))

  )

  (CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = RMANCAT. SERVERB. SOMETHING.COM)

  )

  )

  -------------------------------------------------------------------

  Establish a connection between DEV & RMANCAT - RMAN catalog RMAN is controlled by a user called rmanusr, and each database also has a user called rmanusr.

  RMAN target rmanusr /> @dev catalogue rmanusr /> @RMANCAT_SERVERB

  After have connected you, you should be able to see the information of DBID, to check that you have the right of database:

  Recovery Manager: release 11.2.0.3.0 - Production on Thu Nov 6 11:44:01, 2014

  Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

  connected to target database: DEV (DBID = 123456789)

  connected to the recovery catalog database

  You should then be able to issue the SAVE command the DATABASE

  ---------------------------------------------------------------------------------------------------------------------------

  Then, establish a separate connection between TEST & RMANCAT:

  RMAN target rmanusr /> rmanusr catalogue @test /> @RMANCAT_SERVERB

  Recovery Manager: release 11.2.0.3.0 - Production on Thu Nov 6 11:44:01, 2014

  Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

  connected to target database: TEST (DBID = 987654321)

  connected to the recovery catalog database

  You can now enter a second order SAVE the DATABASE

  ---------------------------------------------

  When you are connected to one of the connections of RMAN you implemented and after you have recorded the two databases, run:

  RMAN > list incarnation;

  from full resynchronization of the recovery catalog

  full complete Resync

  List of Incarnations of the database

  DB key Inc key STATE ID DB name DB reset reset time SNA

  ------- ------- -------- ---------------- --- ---------- ----------

  123456 2345678 DEV CURRENT 123456789 1 2014-11-06

  654321 8765432 TEST CURRENT 987654321 1 2014 - 11 - 06

• How to find databases registered in the recovery catalog.

  I want to know how many registered in the recovery catalog databases
  
  How can I find it?
  
  Thank you!

  Dan wrote:
  I want to know how many registered in the recovery catalog databases

  How can I find it?

  Thank you!

  Use the 'RC_DATABASE' in the catalog database

• target, auxiliary and catalog database

  Hi gurus,

  I need to have a few lights on the target, auxiliary and catalog databases.

  especially difference between the auxiliary and the database catalog.

  Kind regards

  Manish

  Hello

  Your target is the database that you are backing up, and in the case of a duplicate database, it would be the source database.  Example below is when I connect to the target database, which is what I want to save (note that below I sign in using the catalog in which case we'll use the controlfile and no catalog).

  oracle:/home/oracle:testdb #> rman target /
  
  Recovery Manager: Release 11.2.0.3.0 - Production on Mon Feb 17 15:24:02 2014
  
  Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
  
  connected to target database: testdb (DBID=2759143361)
  
  RMAN>
  

  The auxiliary database is the database which, in the case of a duplicate database, the database that you duplicate would be.  So, for example, that if you configure a database ensure using the duplicate database (and maybe double active database database) the main database would be the target and the database pending would be the auxiliary.

  The catalog database is when you use a RMAN catalog instead of using the control file... Note below to specify the catalog when you connect and it says 'connected to the datalog retrieval database' once you have connected that he did not in the example above when you signed in using the control file. In this case, the rman information is stored in the control as well as the datalog database file.  (Control NB file is always the primary source").

  oracle:/home/oracle:testdb #> rman target / catalog rman/password@rcat1
  
  Recovery Manager: Release 11.2.0.3.0 - Production on Mon Feb 17 15:24:16 2014
  
  Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
  
  connected to target database: testdb (DBID=2759143361)
  connected to recovery catalog database
  
  RMAN>
  

  There are several reasons why a catalogue database is used... for example:

  (1) it can store scripts.

  (2) you have a central repository for all of your databases.

  (3) you are not limited as to how long you can store your backup information.  Thie is determined by the controlfile_record_keep_time parameter when you use the controlfile and you type can be set quite high but then your controlfile can grow quite large as well.

  Stor for more information on the recovery catalog, you can see below:

  http://docs.Oracle.com/CD/E25054_01/backup.1111/e10642/rcmcatdb.htm

• What is the recommendation on the backup of a recovery catalog?

  While I understand "benefits of using recovery catalog as the RMAN Repository ' as described in
  
  http://download-UK.Oracle.com/docs/CD/B10501_01/server.920/a96566/rcmquick.htm#442214
  
  as well as things to note if you are using the unique control as the rman repository file,
  
  as described in "Monitoring the overwhelming control file Records" in http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrepos.htm#446924
  
  I do not understand why in Backup and Recovery Advanced User Guide
  http://download.Oracle.com/docs/CD/B14117_01/server.101/B10734/rcmrepos.htm
  
  "Save often Recovery Catalog"
  
  Even if you need to restore the recovery catalog database by using a backup control file, you can use full backups folder in your catalog database restored recovery to restore the database target without using a backup of the target database control file.
  
  = > implies without doubt that we can use a different catalog of recovery we'll call it backupbackup to restore the recovery catalog
  
  "Choose the appropriate method for physical backups.
  
  Follow these steps when developing a strategy for RMAN backup to the recovery catalog database:
  
  * Run in ARCHIVELOG mode recovery catalog database so that you can do point-in-time recovery if necessary.
  * Set the retention policy to REDUNDANCY greater than 1.
  * Save the database on two separate media (for example, disks and tapes).
  * Run the base BACKUP of DATA PLUS ARCHIVELOG at regular intervals, to a Media Manager if available, or simply to drive.
  * Do not use a different catalog recovery as a repository for backups. = > This is in contradiction with the previous declaration
  * Set up automatic backup of control file on IT.
  
  so can I know what is the recommendation on the backup of a recovery catalog? should I use another recovery catalog to keep deposits from rman of the main primary catalog or simply use a feature of automatic backup of control file?
  
  Thank you

  To Catalog backup recovery, it is recommended to enable autobackup controlfile ON and save in nocatalog mode (IE without another recovery catalog).

  The doc States that: "even if you have to restore the database catalog of recovery using a backup control file, you can then use the full record of backups in your database to catalog recovery restored to restore the target database without using a backup of the target database control file.".

  What this means, is-
  The target database backup files are stored in the recovery catalog schema tables, not in the controlfile recovery catalog. When you are using a control file backup and restores them recover from the recovery catalog database, you won't lose target database backup files.

• A 2 DB instance recovery catalog

  Hello
  
  I have a up and race catalog rman (catdb) recovery with a recorded case (orcl) in it. How to add another instance (devdb) in my recovery catalog (catdb)?
  
  Thank you

  You can register a number n of database in the recovery catalog database.

  connect to the database of the registry database and recovery catalog;

  for example:

  Catalog RMAN rman/rman@catalog_database_name target = sys/password@target_db_name =

  RMAN > register database;

  To connect to the catalogue of recovery and the query database;

  SQL > select * from db;
  for example:
  Connect on the demo1 recovery catalog database and as a catalog of recovery user sai;

  SQL> conn sai/sai;
  Connected.
  
  SQL> select * from db;
  
      DB_KEY      DB_ID CURR_DBINC_KEY
  
  ---------- ---------- --------------
  
           1 3710360247              2
  
         141 2484479252            14
  

  check out the link:
  http://oracleinstance.blogspot.com/2009/12/how-to-create-register-add-unregister.html

  Published by: rajeysh on August 16, 2010 10:16

• specification does not match any newspaper archive in the recovery catalog

  RMAN > delete archivelog until time = ' sysdate-15';
  
  output channel: ORA_DISK_1
  output channel: ORA_DISK_2
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 151 devtype = DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: sid = 143 devtype = DISK
  specification does not match any newspaper archive in the recovery catalog
  
  
  Database 10.2.0.3.0 on win2008 (VMWARE)
  Thank you

  Honey says:
  RMAN > delete archivelog until time = ' sysdate-15';

  output channel: ORA_DISK_1
  output channel: ORA_DISK_2
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 151 devtype = DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: sid = 143 devtype = DISK
  specification does not match any newspaper archive in the recovery catalog

  Database 10.2.0.3.0 on win2008 (VMWARE)
  Thank you

  There is no archived redo log file corressponding your query. There is no archived for 15 days ago redo log file