RMAN - catalog of recovery

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 - Catalog and ControlFile Recovery

  I recorded rock database (same host) and Fatima databases (in another machine) in the RECOVERY CATALOG.
  
  I m sticking with Faure database backup using the recovery catalog
  
  
  
  RMAN >
  
  Complete recovery manager.
  ^ C
  H:\ > rman target sys/farooq@farooq catalog rman2/cat@rock
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Mon Sep 8 14:41:17 2008
  
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  
  connected to target database: FAURE (DBID = 1820635189)
  connected to the recovery catalog database
  
  RMAN > register database;
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the register command to the default channel on 2008-09-08 14:41:37
  RMAN-20002: target database is already registered in the recovery catalog
  
  RMAN > outline report;
  
  Report of the database schema
  
  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  ---- -------- -------------------- ------- ------------------------
  1 YES D:\ORADATA\FAROOQ\SYSTEM01 480 SYSTEM. DBF
  2 35 UNDOTBS1 D:\ORADATA\FAROOQ\UNDOTBS01 YES. DBF
  SYSAUX 3 250 NO D:\ORADATA\FAROOQ\SYSAUX01. DBF
  4 5 USERS WITHOUT D:\ORADATA\FAROOQ\USERS01. DBF
  5 100 EXAMPLE NO D:\ORADATA\FAROOQ\EXAMPLE01. DBF
  
  RMAN > list backup;
  
  
  RMAN > backup as incremental compressed backupset of level 0 database more archivelog;
  
  
  From backup 08-SEP-08
  Current archived log
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of command thus backup archivelog at 2008-09-08 14:43:03
  RMAN-03014: implicit recovery catalog Resync failed
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20020: incarnation of the database not defined
  
  RMAN > list incarnation of database;
  
  
  List of Incarnations of the database
  DB key Inc key STATE ID DB name DB reset reset time SNA
  ------- ------- -------- ---------------- --- ---------- ----------
  3641 3649 FAURE 1820635189 PARENT 534907 29 JULY 08
  FAURE 3641 3642 1820635189 CURRENT 695424 08-SEP-08
  
  RMAN > RESET DATABASE to incarnation 3642
  2 >.
  
  database restore the incarnation 3642
  
  RMAN > backup as incremental compressed backupset of level 0 database more archivelog;
  
  
  From backup 08-SEP-08
  Current archived log
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 142 devtype = DISK
  channel ORA_DISK_1: starting from backupset journal archive compressed
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 1 sequence 1 recid = 4 = 664886867 stamp =
  archive log entry thread = 1 sequence 2 recid = 5 = 664888152 stamp =
  archive log entry thread = 1 sequence = recid 3 = 6 = 664888938 stamp
  archive log entry thread = 1 sequence 4 recid = 7 = 664889572 stamp =
  archive log entry thread = 1 sequence 5 recid = 8 = 664889658 stamp =
  archive log entry thread = 1 sequence 6 recid = 9 = 664891871 stamp =
  archive log entry thread = 1 sequence 7 recid = 10 = 664892590 stamp =
  archive log entry thread = 1 sequence 8 recid = 11 = 664900983 stamp =
  archive log entry thread = 1 sequence 9 recid = 12 = 664902190 stamp =
  channel ORA_DISK_1: from room 1 to 08 - SEP-08
  channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
  piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150314_4D9Y35PK_. Tag BKP = comment TAG20080908T150314 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:26
  channel ORA_DISK_1: starting from backupset journal archive compressed
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 1 sequence 8 recid = 1 stamp = 664886398 =
  archive log entry thread = 1 sequence 9 recid = 2 = 664886399 stamp =
  archive log entry thread = 1 sequence 10 recid = 3 = 664886403 stamp =
  channel ORA_DISK_1: from room 1 to 08 - SEP-08
  channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
  piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150314_4D9Y407K_. Tag BKP = comment TAG20080908T150314 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:09
  Backup finished 08-SEP-08
  
  From backup 08-SEP-08
  using channel ORA_DISK_1
  channel ORA_DISK_1: additional start-up compressed 0 datafile backupset
  channel ORA_DISK_1: specifying datafile (s) in backupset
  input datafile fno = 00001 name = D:\ORADATA\FAROOQ\SYSTEM01. DBF
  input datafile fno = 00003 name = D:\ORADATA\FAROOQ\SYSAUX01. DBF
  input datafile fno = 00005 name = D:\ORADATA\FAROOQ\EXAMPLE01. DBF
  input datafile fno = name 00002 = D:\ORADATA\FAROOQ\UNDOTBS01. DBF
  input datafile fno = 00004 name = D:\ORADATA\FAROOQ\USERS01. DBF
  channel ORA_DISK_1: from room 1 to 08 - SEP-08
  channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
  piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_NNND0_TAG20080908T150351_4D9Y49WW_. Tag BKP = comment TAG20080908T150351 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:01:15
  Backup finished 08-SEP-08
  
  From backup 08-SEP-08
  Current archived log
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting from backupset journal archive compressed
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 1 sequence 10 recid = 13 = 664902308 stamp =
  channel ORA_DISK_1: from room 1 to 08 - SEP-08
  channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
  piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150512_4D9Y6T1D_. Tag BKP = comment TAG20080908T150512 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:02
  Backup finished 08-SEP-08
  
  From control file and SPFILE Autobackup 08-SEP-08
  piece handle = D:\ORACLE\RMAN_BACKUP\CTL_SP_BAK_C-1820635189-20080908-09 comment = NONE
  Control finished and Autobackup SPFILE file 08-SEP-08
  
  RMAN > list backup;
  
  
  Backup list
  ===============
  S LV TY Device Type delay #Pieces compressed #Copies Tag key
  ------- -- -- - ----------- --------------- ------- ------- ---------- ---
  4615 DISC 08-SEP-08 1 1 YES TAG20080908T150314
  4617 B 0 A DRIVE 08-SEP-08 1 1 YES TAG20080908T150351
  4650 DISC 08-SEP-08 1 1 YES TAG20080908T150512
  4670 HAS NO DISK 1 1 08 - SEP - 08 NO TAG20080908T150517
  
  RMAN >
  
  
  
  Now, I m conneting to Faure - target database and obtaining the same information from the control file backup.
  
  H:\ > rman target sys/farooq@farooq
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Mon 8 Sep 15:05:38 2008
  
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  
  connected to target database: FAURE (DBID = 1820635189)
  
  RMAN > LIST BACKUP SUMMARY;
  
  using the control file of the target instead of recovery catalog database
  
  Backup list
  ===============
  S LV TY Device Type delay #Pieces compressed #Copies Tag key
  ------- -- -- - ----------- --------------- ------- ------- ---------- ---
  21. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150314
  22. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150314
  23 B 0 A DRIVE 08-SEP-08 1 1 YES TAG20080908T150351
  24. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150512
  25 A NO DISK 1 1 08 - SEP - 08 NO TAG20080908T150517
  
  My question: why are the information stored in the database control file (Faure) target so that its stored in the recovery catalog?

  Hello

  By default, RMAN stored metadata in the file control, all the RMAN is first written to control the file and then catalog of recovery if leaves. For example, when rman creates a new backupset, you can view the information in the v$ backup_set and you can also view the same information of the recovery RC_BAKCUP_SET catalog views.
  So every change repository is stored in two places... Control file and optionally recovery_catalog

  The catalog of recovery of the RMAN Repository versions are stored in database tables and version control repository os file stored as files in with in the control file.

  -Pavan Kumar N

• The Rman catalog must be registered?

  Hello experts,

  Don't you think that would be recorded in the database catalog Rman or not? If so could be in the same Rman catalog or in other different database?

  In the documentation of Rman something about this?

  My 11.2.0.3 Rman catalog database have a controlfile and default 15-day CONTROL_FILE_RECORD_KEEP_TIME.

  My media layer has a 90-day supply. So if I would to restore an older version of 15 days from the catalog in another machine I had to sign up former backups before games.

  Would be, this example above, a real possibility that I had to listen to extracts?

  Thank you and best regards.

  Francesco

  user4339084 wrote:

  Hello

  Thanks for the reply,

  but do you think useful registry the Rman catalog database in the catalog itself? Or is nonsense? a why?

  Thanks and greetings

  Of course, it is absurd to register in the database catalog with himself.  The entire purpose of the catalog is to help the recovery.  So how the catalog database can help in recovery if the catalog database needs recovery.

  https://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmcatdb.htm#BRADV89662

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

• 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

• Change the settings of catalog of recovery for all DBs in EM Cloud control 12 c

  Hello

  A project to migrate our RMAN recovery catalog (11.2.0.3 database) to the CAR, I need to update the Manager of the company with the new catalog of recovery settings. So far I couldn't find how to change it for each database individually, which will be your time to 40 + databases! I found this doc metalink [Doc ID 840051.1] on how to do it in the EM grid control, but don't find anything on how to do this for Cloud control 12 c.

  Does anyone know how to do this? Pointers would be much appreciated.

  Thank you

  Robin

  Hi Robin,

  This should also work for Cloud control 12 c.

  -Go to the homepage of the EM.

  -In the target tab click on databases.

  -In availability tab click 'Catalogues of recovery. "

  -Edit and modify data

  Concerning

  Stefan

• Moving the RMAN catalog

  Hello
  My question concerns the RMAN catalog. A few months ago we moved from solaris zones linux servers. A new catalog of recovery was created on linux servers (same name as the catalog of recovery on solaris zones). There are a few databases that couldn't be moved on the linux server and I would like to re - run databases on solaris zones to use the linux RMAN catalog. Should what steps I follow? Thank you.
  
  J

  A new catalog of recovery was created on linux servers (same name as the catalog of recovery on solaris zones).

  Since its new catalogue, then you will need to register your database in this catalogue and use this database schema name while making the connection to this rman catalog.

• How to save a database to use the RMAN catalog using the OEM 11 g grid

  How to save a database to use the RMAN catalog using the OEM 11 g grid?
  
  ---------------------------------------------------------------------
  Enterprise Manager Version: 11.2.0.2

  See the availability tab, and then click 'Recovery catalog settings' under the Backup/Restore Configuration.

  Choose the option 'Use Recovery Catalog'. Click the 'Add Recovery Catalog' button to add the recovery catalog. And fill required fields like username, host, port, sid, etc..

  Talip Hakan Öztürk
  http://taliphakanozturken.WordPress.com/

• RMAN catalog 11 GR 2 Update Catalog RMAN-06429

  Hi all
  
  I have databases oracle 11 GR 1 material and GR 11, 2 in use.
  Last time I would upgrade the catalog with 'Upgrade catalog' database to backup databases the new 11 GR 2.
  
  The upgrade looks good, but after this task, I have 21 invalid objects in the RMAN catalog and it was not possible to compile without error. And all the other which backups using the catalog fails the RMAN-06429.
  -> Package PL/SQL BAKRMAN. DBMS_RCVCAT Version 11.02.00.02 in the RCVCAT too recent database.
  I therefore return to the action.
  
  What is the right way to use the catalog rman with levels of different database?
  How can I use the catalog also for 11 GR 2 databases without any side effect on my other 11 GR 1 material databases?
  The rman catalog reside on a 11.1.0.7.0 database.
  
  BR
  Daniel
  
  http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28273/compat003.htm
  Database TARGET RMAN-06429 is not Compatible with this Version of RMAN [245698.1 ID]

  Hello

  So, how I understand, I should send the command "upgrade catalog" new 11 GR 2 database server.

  Yes, the process of looking at this.

  Opening of session of rman 11 GR 2 binary upgrade CLI:

  $ rman catalog bakrman /@.

  connected to the recovery catalog database
  RMAN PL/SQL package. Version X.X.X.X in database RCVCAT DBMS_RCVCAT is too old

  RMAN > upgrade catalog;

  recovery catalog owner is BAKRMAN
  Enter the command of CATALOG to UPGRADE again to confirm the upgrade of the catalogue

  RMAN > upgrade catalog;

  Upgraded to version X.X.X.X recovery catalog
  DBMS_RCVMAN package updated to version X.X.X.X
  DBMS_RCVCAT package updated to version X.X.X.X

  After that this upgrade, only objects of schema in the recovery catalog database should be improved, right?

  Fix.

  Kind regards
  Tycho

  Edited by: tychos January 25, 2011 14:40

• change a catalog of recovery to another

  Hi Experts,
  
  We have temporarily created a recovery database [cattemp] catlog and used this database to make RMAN bakcup during more than a week. Currently, we have created the permanent recovery catalog database [rcat11g].
  
  now, I have to cancel the registration of the existing and register with the database to catalog new recovery. If I unregiter will get the existing base of the catalog the repositary of file recovery deleted what is the correct procedure to migrate from one catlog to another.
  
  Please notify.
  
  Best regards, Salai.

  See [import and move a catalog of recovery. | http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcatdb.htm#CHDGEHCG]

  Hemant K Collette

• The RMAN catalog questions

  Hello
  We plan application catalog RMAN various databases in our society. We had some problems that I write here and hope that people who have already done something like this would be able to guide me also highlight the pitfalls.
  
  Catalogues DB environment:
  Oracle 10.2.0.4 on Sun Solaris 5.10 (Sparc)
  
  Target environment:
  Various DBS, 10 g (10.2.0.4) mostly, a few (9.2.0.8) 9i and some 8i 8.1.7 (8.1.6,) for the most part, Sun Solaris and RHEL4/5
  
  Issues related to the:
  (1) it will work installation where there is a mix of the target db versions. Are there special requirements to do this job or any restriction
  (2) say the catalog db is down, and the accident of my database target. I would still be able to restore my available target without the catalog db database?
  (3) what are the best practices for the maintenance of catalog db so that it does not become a SPOF? (DG, etc..)
  
  Your help is very appreciated.
  
  Thanks in advance.

  1 see http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/compat002.htm#sthref1153
  2 Yes: If you still have at least a current control file: restoration should be transparent. If you've lost all control files, then you must recover the backup file DBID and control location and know how to restore in a DRP as situation
  3. my humble opinion, it is more important to know how to restore without a catalog of recovery available to use the high availability features for the recovery catalog database.
  See also http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcatdb.htm#i1007067
  and http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcatdb.htm#CIHFEIIH.

• RMAN catalog upgrade 11.2.0.4.7 with 11.2.0.4.0 database

  Hello

  One of my new database received from group fixes 11.2.0.4.7.

  When I want to join this real my rman catalog database, I "PL/SQL package RMAN. DBMS_RCVCAT version 11.02.00.03 in the RCVCAT database is not current."

  I can easily do a "catalogue of upgrade", but is there an impact on my other databases running 11.2.0.4.0, which cannot receive the patches group before long.

  Thank you for your kind reply.

  Eric

  Hello

  Having the RMAN catalog with a newer version than the database version and will not create any problem.

  (Doc ID 73431.1) RMAN compatibility matrix

  Thank you

  Sundar

• Firewall rules RMAN target database and RMAN catalog database

  Hi, we are on Oracle 11.2.0.4 and we just build a new environment, in which case the RMAN catalog is located on a seprate from the target database server. I'm trying to figure if the firewall between these two rules should be two-way, so that the target database and RMAN catalog database can ping each other. If bi-directional rules in place, so what's the reason for this? I understand that during RMAN backup entries are made in the RMAN catalog database, but do not know if the RMAN catalog database must always meet target db. Thank you!

  If you run the rman command on the target database server, it acts as a client to the catalog database server by connecting on sqlnet to the catalog database.

  If you run the rman command on the catalog database server, it's a sqlnet connection join the target database server.

  In both cases, rman is simply a client that connects to the two databases.

  Hemant K Collette

• RMAN catalog by default for all databases of the value

  Hello

  I run a catalog RMAN 11 GR 1 material.

  I wonder if it is possible to change a default setting in the RMAN catalog so that he will inherit all new databases.

  For example, I would that all new data entered in the catalog for:

  BACKUP OPTIMIZATION

  REDUNDANCY 7 RETENTION STRATEGY

  Thank you

  Massi

  No, the catalogue cannot "dictate" configurations for databases.  Each database maintains configuration in the controlfile and this can be changed that by rman connection (i.e. rman connection to the database target). The command SETS in rman is used to define a "permanent" for a database configuration parameter but must be issued individually for each database.

  Hemant K Collette