Record number of databases in a recovery catalog

Similar Questions

• Can us refresh database using the recovery catalog?

  Hi all, I need update the dev of database using the prod database backup, we have TSM server and database of separate catalog for storing backups. No, my doubt is, we can update database dev using catalog, which has the backup of all info the prod

  In my previous organization, we used to copy the backup of the prod dev we restore and recover it in dev db. But in this organization, we have a TSM server that stores all backups of prod and dev.

  Please tell me we can update dev db using info catalogue simply and without copying backups of prod? If possible how?

  Thank you

  Harish

  user8596912 wrote:

  Yes I know that the content of the rman script.

  But we have not, so how can we be expected to comment on?

  My question is that the connection to the rman is good or bad?

  It would depend on the content of the script you do not think that we need to see.

  In the end, you can determine whether this is good or bad by testing.

  Because the rman is not connected directly to the target db prod.

  Have you read the link I gave you?

  I would limit for you: a database mirroring

  The docs in detail how to duplicate a database

  1 - active database

  2 - from a backup WITH a connection target (the database prod)

  3. from a backup WITHOUT a connection target (the database prod) but WITH a recovery catalog connection

  4 - from a backup WITHOUT connection AND connection catalog recovery target (the database prod)

  BTW, why you score your own messages as 'useful' to your own problem?

• 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

• RMAN cloning using the recovery catalog

  Hi all
  
  I do RMAN cloning using the recovery catalog.
  
  I use oracle 10R2 on solaris, I have a PRIMARY primary database name. I create another database for the catalog name of recovery REC_DB. and the master database with REC_DB record and took the full backup. now I have a full backup of the PRIMARY database in the recovery catalog.
  
  Now I want to clone the MAIN database using this backup (backup of the catalog).
  
  I've done this before, without using the catalogue,
  
  I know that the orders and the cloning procedure, I want to ask how to connect from the auxiliary.
  
  RMAN target sys/password@source_DB_string auxiliary sys / password@clone_DB_string *.
  
  here target means what? primary or catalog database. kindly help me on this.
  
  Kind regards
  Kumar

  >

  >

  I know that the orders and the cloning procedure, I want to ask how to connect from the auxiliary.

  RMAN target sys/password@source_DB_string auxiliary sys / password@clone_DB_string *.

  here target means what? primary or catalog database. kindly help me on this.

  Looks like it is exactly what you were asking.

  You need to connect to the TARGET, CATALOG & AUXILIARY of the rman prompt instance.
  You then run your script/command clone, which you claim you already know how to do.

• How do I know if the recovery catalog is configured

  Hi friends,
  
  Today I faced a typical question that I've never heard and looking for a response that
  
  If I got a database, how to check if that database has a recovery catalog configured or not?
  
  I know, by catalogue, we can check databases saved using view v$ RC_DATABASE. but it's new to me...
  
  Please shed some light... Thanks in advance

  mseberg wrote:
  You can try to select the RC_SITE view in your catalog database.

  He wants to know the information of target database_ no recovery catalog database.
  View RC_DATABASE is used to search the database of registered in the recovery catalog.
  View RC_SITE lists information about all databases in a Data Guard environment that are known to the recovery catalog.

• RMAN recovery catalog number

  Hi all;

  Lem I have a probwhen you configure the recovery catalog.

  SERVER 01: 192.168.1.105 DB - NAME (db1)

  SERVER 02: 192.168.1.106 DB - NAME (db2)

  DB1 the TNS alias name is : DBONE -> 192.168.1.105 

  db2  the TNS alias name is : DBTWO -> 192.168.1.106

  I tried to cash catalog of recovery in db2 to db1. but I encountered some problems.

  Already, I have configured listener, tns entered into two servers.

  The OS level - in db2 database) (192.168.1.106 server) here's the problem ...

  rman catalog username $ / password@tns_aliasname.

  I want to know, TNS ALIAS name should be what server what show above the command?

  Thanks in advance...

  Run rman in your data base (d1) target server (105).  The tns for the catalog alias is dbtwo.

  Connect to 192.168.1.105 'oracle' (or the owner of oracle)

  value your ORACLE_SID db1

  RMAN target / catalog rmn_rc/rmn_rc@dbtwo

  Hemant K Collette

• 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

• 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

• 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-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: 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-06004: error ORACLE recovery catalog database: RMAN-20001: target

  Hello
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to 2009-03-31 21:59:24
  RMAN-03014: implicit recovery catalog Resync failed
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target not found in the recovery catalog database
  
  
  I get the above error while taking backup RMAN Level0. I am able to connect to the database of the catalogue without any problem.
  
  I already have this registry database command in RMAN prompt. Now I am able to see backup list but I don't know how that DB asking to sign up for today. Until yesterday, the backups were running fine btu today his application to enter the catalog DB.
  
  Here we manually to connect the catalogue in this way
  rman target $ /.
  RMAN > catalog connection rmanuser/password @ < globalcatalogDB >
  connected.
  
  After that if I give this command means...
  
  RMAN > backup from the list of database;
  I get the error I pasted at the earliest.
  
  Thanks in advance.

  If you do not have a catalog, you need not to save the database. Rely you only on the target database controlfile. If you use a catalog, you must save the target database, but only once. If you sometimes use a catalog - and sometimes not--the appropriate command is RESYNC (although in many cases RMAN automatically done).

  Werner

• 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.

• 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.

• 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