Advantages of RMAN Catalog

Hi,
In RMAN what are the major advantages of using a catalog ?
Also whether catalog is required for a single database instance.
Thanks in advance.

Recovery catalog is never required, it's an optional structure, and it makes sense if you have multiple DBs to backup (as Kuljeet says), and the database with recovery catalog is on a different machine.
The advantages I can see in using recovery catalog instead of controlfile are substantially two :
- the control file has finite space for records of backup activities, while a recovery catalog can store a much longer history
- RMAN stored scripts are stored in the recovery catalog, so commands related to them require the use of a recovery catalog.
Moreover, in versions older than 10g, it was not possible to have multiple incarnations without recovery catalog.

Similar Messages

  • SQL Reports Bad Idea Against RMAN Catalog?

    11.2.0.1 SPARC 64
    We use OEM to manage/execute our backups. The MML is NetBackup. One downside to this is that the "job" within OEM executes the backup for 20+ databases. In a serial fashion the backups occur in NetBackup...but most are queued - they throttle through and over time they complete. To this end, we have no way of seeing the true backup duration. We know the rman start and completion times, but they're not "actual."
    I started looking at creating a sql statement/report/[pl/sql] block that would give us the granular informatin on the true timings of the backup "pieces" as they relate to a "set."
    Research out on the wire shows a number of high level solutions, but nothing to which a report shows the data files, etc. Usually when I see this I start to question..."hey, is this even a good approach?"
    I do realize that through the RMAN utility there are a number of reports which are available...this post, however, is focused on the idea of sql reports against the rman catalog.
    Any advice would be welcome.
    Conceptual report:
    -> INCREMENTAL LEVEL 0
    --> BACKUP SET
    ---> BACKUP PIECE
    ----> HANDLE, TAG, DATAFILE, START, COMPLETION
    I'm NOT looking for the sql...I can work that out, I just want to know if this is a smart approach or best to stay out of the catalog.
    -abe
    Boulder, Colorado
    Edited by: user10863631 on Mar 10, 2011 7:43 AM
    Edited by: user10863631 on Mar 10, 2011 7:56 AM

    I think this is the wrong forum for such a question. The Database - General (General Database Discussions might be better suited. Or maybe the RMAN forum (Recovery Manager (RMAN)

  • How to upgrade RMAN catalog from 10.2.0.4 to 11?

    Hi, we are on Oracle 10.2.0.4, Solaris 5.10. Our RMAN catalog is 10.2.0.4 version and we have several 11g databases that need to connect to the catalog and obviously cannot. So we need to upgrade the catalog to 11. Does anyone have any docs on how to do it. Do I need to upgrade RMAN database to 11 via conventional upgrade and then do UPGRADE CATALOG? Really confusing, any help would be very appreciated.
    Thank you!

    You need to:
    1 - upgrade the recovery catalog database
    2 - upgrade the recovery catalog Schema
    Please check the details on note *452529.1 Recovery catalog for RMAN backup*.
    Normally newer databases (target) can be cataloged on previous version catalog database, but with 11g there is the bug 6756872 (RMAN REGISTER OF 11G TARGET INTO 10G CATALOG FAILS WITH ORA-04028) which force you to upgrade the catalog.
    You can also review RMAN Compatibility Matrix (Note 73431.1) which has all valid version combinations.
    If your scenario is simple enough, another option could be create a new 11g RMAN catalog and register there your databases, without importing data from the 10.2 catalog.
    Regards.

  • Can't register a database in RMAN catalog (PL/SQL package not current)

    Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
    $ rman catalog rman/rman target sys@MPOWER
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
    PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
    connected to target database: MPOWER (DBID=**********)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    RMAN-00571: ===============
    RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
    RMAN-00571: =================
    RMAN-03008: error while performing automatic resync of recovery catalog
    ORA-00904: : invalid identifier
    Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
    I cannot register the target database into the RMAN catalog.
    I highly appretiate if you give me an advice on this.
    Regards

    user13064912 wrote:
    Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
    $ rman catalog rman/rman target sys@MPOWER
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
    PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
    connected to target database: MPOWER (DBID=**********)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    RMAN-00571: ===============
    RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
    RMAN-00571: =================
    RMAN-03008: error while performing automatic resync of recovery catalog
    ORA-00904: : invalid identifier
    Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
    I cannot register the target database into the RMAN catalog.
    I highly appretiate if you give me an advice on this.
    RegardsCould you try to run the rman at the target database server (MPOWER), instead of rman catalog server ant try to register your database?
    Your rman client is higher than your target server. That could be the problem.
    Best Regards,
    Gokhan
    If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

  • Question: Which is better and why....RMAN catalog or Flashback Recovery

    Hey All,
    Newly testing and reading up on 10g. I am on information overload and would appreciate pro's advice on which to choose and why.
    Thanks,
    d.

    Different things, not necessarily alternative. That is, RMAN catalog is normally (at least should be) on another machine, and does not contain physical backups, but only information about them : physical backups are normally stored on external devices, like tapes.
    Flashback Recovery technique is based on Flashback logs in Flash Recovery Area, which is a disk area on local machine, and so cannot be unlimited.
    Therefore, Flashback Recovery is much faster than Media Recovery, since you don't need to restore anything, but you have limits in using that : your disks size.
    On the other hand, RMAN backups are safer, being physically elsewhere.
    See http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#g1023042

  • To Find the instance name in RMAN catalog

    Hi ,
    I have rman catalog which got registered 150 databases. Am able to get the dbname,id for the 150 databases but not able to get the server name (host name) of the correspoding databases in catalog views as well as in db views.
    Kindly revert us if you know any other analyisis or way to find the server names.
    Regards
    Krishnan

    What does RMAN care if RAC is involved or not?
    Oracle provides RMAN for backing up and restoring the database. RMAN enables you to back up, copy, restore, and recover datafiles, control files, SPFILEs, and archived redo logs. RMAN is included with the Oracle server and it is installed by default. You can run RMAN from the command line or you can use it from the Backup Manager in Oracle Enterprise Manager. The procedures for using RMAN in RAC environments do not differ substantially from those for Oracle single-instance environments. Refer to the Oracle Backup and Recovery documentation set for more information about single-instance RMAN backup procedures.

  • Why use RMAN CATALOG ?

    Hi,
    Anybody tell me why use RMAN CATALOG and what benifits if i have create catalog ?

    No we have to configure it. I see. But did this user understand that when you quoted my reply ? We need to understand that a lot of users who post here need help and may not have the level of knowlege you have. So, a response like that adds more problems to the one they already have.
    So even if you are using nocatalog, if it is not configured to auto backup and it is not backed up, you can still loose your RMAN repository.

  • A possible bug in RMAN CATALOG command in 10g on Linux (SLES9 SP3)

    Hi,
    I ran into this issue while using RMAN command "CATALOG DATAFILECOPY <filename> TAG <tagname>". In this instance, RMAN is actually trying to write 8K data at block 1. Since a copy is being cataloged, it doen't make any sense to modify it. Please note that this modification doesn't happen without TAG option. This behavious doesn't seem to be present on Oracle 9 on Solaris 8. For more details, please check the following thread:
    help with RMAN CATALOG command
    Thanks,
    Raghu.

    Hi Steve,
    Unfortunately this is a bug, bug 3612370 in fact. I've published the bug so that it can be tracked via metalink if you have a support contract.
    The bug is as you suspected with JDev's parse of the modules. We don't have a workaround at the moment but I'll post here again if we make any progress.
    Thanks for reporting this,
    Geoff
    JDev Test Team

  • Unregistering of a database from RMAN Catalog

    Hello,
    We had set up RMAN backup though RMAN Catalog for one of our database.
    We later decided not to take the backups of this particular database. One of the DBA did something but what we can see now is that -
    1. Target database is not registered in the catalog so no information can be gathered rman prompt after connecting to catalog through target database
    2. But the recovery catalog "rc_backup_datafile" is showing as if it has old backups
    We know that the tapes don't have the backup of this database.
    Question - How to remove information from recovery catalog for a database in such a situation where although the database is not registered in the catalog but somehow the information related to old backups still persists in the catalog tables.
    Thanks!

    Thanks Tycho, for my purpose DBMS_RCVCAT.UNREGISTERDATABASE worked fine.
    I have another question though -
    We have compressed backup for one of the database/
    If I look at backupset by executing "list backupset xxxxxxx;" command it shows the correct compressed value (in GB) of the backup set.
    BUT when I look at the rc_backup_datafile table of the rman catalog for the size of of the backupset, it shows the uncompresses size of the backupset. I am using following query -
    select BS_KEY,SUM(blocks*block_size)/1024/1024/1024 GB from rc_backup_datafile where DB_NAME='CCSTG04' and BS_KEY=1 group by BS_KEY;
    Question - How to check the compressed size of the backupset from the Catalog tables/views?
    Thanks for your help on this!
    Thanks!
    ,

  • Schedule a crontab in rman catalog

    Hi,
    I am trying to schedule a crontab in rman catalog side but it wasn't work.
    I prepared a scripts and I dont know why it was not worked.
    Please can anyone tell me how can I schedule my crontab in rman.
    The scripts is this,
    00 01 * * 0 ksh /u01/app/oracle/product/10.2.0/bin/ora_rman.sh >/dev/null 2>&1
    vi ora_rman.sh
    ORACLE_SID=p001
    ORACLE_BASE=/orahome/p001
    ORACLE_HOME=$ORACLE_BASE/10.0.2
    PATH=$ORACLE_HOME/bin:$PATH
    $ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 /u01/app/oracle/product/10.2.0/bin/ora_rman.sh <<EOF
    run {
    backup incremental level 0 as compressed backupset database plus archivelog;
    delete noprompt archivelog all completed before 'sysdate-7';
    00 19 * * * ksh /u01/app/oracle/product/10.2.0/bin/ora01_rman.sh >/dev/null 2>&1
    vi ora01_rman.sh
    ORACLE_SID=p001
    ORACLE_BASE=/orahome/p001
    ORACLE_HOME=$ORACLE_BASE/10.0.2
    PATH=$ORACLE_HOME/bin:$PATH
    $ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 u01/app/oracle/product/10.2.0/bin/ora01_rman.sh <<EOF
    run {
    backup incremental level 1 as compressed backupset database plus archivelog;
    delete noprompt archivelog all completed before 'sysdate-7';
    waiting for your replies,
    Thanks & Regards

    Here's my working stuff:
    I use an .env file. Here's the crontab entry, script and env file.
    00 16 * * 0-6 /u01/app/oracle/dba_tool/PRIMARY/db_rman_full.sh > /tmp/PRIMARY_rmanfull.out
    #!/bin/bash
    # Name: db_rman_full.sh
    # Purpose: Database rman backup
    # Usage : db_rman_full <DBNAME>
    . /u01/app/oracle/dba_tool/env/PRIMARY.env
    echo "Starting RMAN..."
    $ORACLE_HOME/bin/rman target / catalog <catalog_user>/@<catalog_db> << EOF
    run { allocate channel d1 type disk;
    backup full as compressed backupset
    database plus archivelog;}
    crosscheck backup;
    delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-5';
    DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
    exit
    EOF
    echo `date`
    echo
    echo 'RMAN Full on PRIMARY Complete'
    env
    ORACLE_BASE=/u01/app/oracle
    ULIMIT=unlimited
    ORACLE_SID=PRIMARY
    ORACLE_HOME=$ORACLE_BASE/product/11.2.0
    ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
    LIBPATH=$LD_LIBRARY_PATH:/usr/lib
    TNS_ADMIN=$ORACLE_HOME/network/admin
    PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
    export TERM=vt100
    export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
    export ORACLE_HOME
    export LIBPATH LD_LIBRARY_PATH ORA_NLS33
    export TNS_ADMIN
    export PATH
    ----If you find this helpful please mark it so----

  • How to get RMAN catalog information from Target database?

    Hi,
    How to get RMAN catalog information from Target database because i don't know about catalog database? is it possible?
    Thanks

    If you run RMAN backups of a target database using a Catalog schema in another database, the target is not aware of the catalog.
    The RMAN backup script would have the connection identifier for the Catalog.
    Hemant K Chitale

  • RMAN catalog fails to show target database information when in nomount mode

    Hello everyone, I am trying to restore a dev. database from its own backup taken a week back. The DB is in noarchivelog mode and recently 2 of the datafiles were removed from the files system and thus the need to restore the DB from its backup. However rest of the files and control files are intact.
    Now, when I put the database in mount mode and connect to the catalog then I can see the DB's incarnation;
    :->rman catalog cde01_rman4/xxxxxxx@prman10g target /
    Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:54:40 2009
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: EGVBFI2 (DBID=4238332493, not open)
    connected to recovery catalog database
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    84789 84883 EGVBFI2 4238332493 PARENT 2478183021921 17-JAN-04
    84789 84790 EGVBFI2 4238332493 CURRENT 2498633332010 10-OCT-07
    RMAN>
    However I am not able to see DB incarnation in the RMAN catalog if I put the DB in nomount mode (which is required to recover DB);
    :->rman catalog cde01_rman4/xxxxxx@prman10g target /
    Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:58:29 2009
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: egvbfi2 (not mounted)
    connected to recovery catalog database
    RMAN> list incarnation;
    RMAN>
    Please advice?
    Thanks,
    Jairaj

    Hi,
    You won't be able to see incarnation information when the DB is in "nomount" since the incarnation is written in the control file. I don't think the catalog has this information.
    Anyway, in order to restore datafiles, the instance must be mounted, so you should be OK.
    Mount the instance and just restore the datafiles.
    Liron Amitzi
    Senior DBA consultant
    link: [www.dbsnaps.com]
    link: [www.obriumsoftware.com]

  • 10G RMAN catalog in 9i

    Hi,
    I can't find this information in any documentation, so this is the best place for it.
    Can we create a 10g RMAN catalog on 9i database? If no why? If yes, then is
    there any known issue/problem with this?
    Thanks....

    Hi,
    You can create !!
    But you might experience the problems, with Backward compatability..
    I suppose.. that..
    Thanks
    Pavan Kumar N

  • New RMAN catalog in existing EMREP database - new user and tablespace?

    Hi all,
    I am FINALLY getting "with the times" and trying to get my databases to back up with RMAN. I already have a dedicated server that is running Oracle Enterprise Manager 10g Grid Control, so it already has the OMS database on it, called EMREP. I was hoping to just use this database as my RMAN catalog, is that considered good practice or not?
    So assuming this practice is considered OK, I know that I need to create a new user (which I'll just call RMAN) in this database. Would it be best to also create a separate tablespace for this user? I have no idea how big I should expect this RMAN schema to get. I'm sure it all depends on the number of databases I'm backing up, but can anyone give me some realistic size expectations that I could start with?
    Any advice/info is greatly appreciated!

    I think that the catalog is only applicable if you will have several databases to manage.
    If you he will have only one, I dont see necessity to use the catalog, therefore with backups of controlfiles only, you can to execute the tasks of backup/restore/recovery.
    But, for catalog creation information, see
    RMAN CATALOG CREATION STEP BY STEP by Joel Pérez
    RMAN ( CATALOG CREATION ) STEP BY STEP by Joel Pérez
    Message was edited by:
    ARF

  • Howto: RMAN catalog backupset in different location

    Hi,
    How can I tell RMAN catalog that the location of backup set has changed.
    For example: after my RMAN backup all my backup pieces went to C:\first_location\
    directory. I am using a catalog while running backup.
    Now I moved the backup pieces to D:\new_location\ directory. Say C:\first_location\ directory is no longer for some reason. How do I tell my catalog that the backup pieces about the new location D:\new_location\
    Catalog, Rman, database all in 10.2 version.
    thank you in advance

    Thank you for your response to my question.
    Can someone help me with syntax and usage of new location of backup pieces in a backup set to be reflected in my catalog. Catalog, target and rman all 10g version.
    thanks in advance

Maybe you are looking for