Backing up an RMAN Catalog/OEM Repository

This may be a supid question but I will ask it nonethelss.
I have an RMAN catalog/OEM Repository which has never been backed up.
Can I use register this (RMAN catalog/OEM Repository) DB within the catalog on the same instance and then back it up as well?
Tks & Regards

Hi 860user6196,
And how are you going to recover your database in case of a disaster?
Clearly the catalog won't be available...
Regards,
Tycho

Similar Messages

  • Backing up the RMAN catalog database

    Version: 10.2.0.1.0
    We have created a database to host our RMAN catalog. This catalog holds backup info plus RMAN stored scripts for 5 production databases . Now, we need to backup this RMAN catalog database.
    I am going to use the control file as the catalog (ie. NOCATALOG) for our RMAN catalog database. This should be fine. Right? Any best practices i should follow regarding this?

    Sometime back I had the same question.
    What I decided was cold backuo and RMAN using the control file. (A Belt-and-suspenders approach)
    I also do an export daily after all the other backups are done.
    In addition I keep an information on it, location and size of all files, a current PFILE (it does not change much), what patches etc.
    Given its tiny footprint it would be easy to rebuild given all this.

  • Best strategy for backing up the rman catalog database

    I have seen people do
    1. full export
    2. backup with control files
    3. put a repository in another database and cross backup
    What do you use?
    I am in 10.1, but this is a general question.

    Hi,
    1. full export
    This is a logical backup - don' treat it as permanent - it's not physical backup for recovery scenarios.
    2. backup with control files
    In the case of loss of control files, its can be used for that.
    3. put a repository in another database and cross backup
    It's to persits the data Base backup histories in another database, gives the facility to clone/ re- build the DB to different node - in terms of crashes.
    For stratergy you need to checl with your SLA's and primarly refer to ORACLE Doc's you can able know the pro's and con's. Based on that you jutify what better suits your Application.
    - Pavan Kumar N

  • Repository views for RMAN Catalog check

    Hi All,
    Is there any view which tells if the database is using catalog for backup, we have scheduled the rman using OEM, now i need to create a UDM which sends an alert if not using catalog, i would like to do this using the sql command with OEM Views.
    any view which can be my help ???
    I have gone through http://docs.oracle.com/cd/B1930601/em.102/b16246/views.htm#BACDGFJC_ ,
    but couldnt find any appropriate view,
    Have checked this : "MGMT$HA_BACKUP", will this view give the required information ???
    please suggest.
    Thanks and Regards,
    Harish

    Hi EricvdS,
    Thanks a lot, i have used the following command to get my result :
    select dbid,name,t.ct qct from rc_database q,(select DB_ID,max(COMPLETION_TIME) ct from rc_backup_set where db_id in (select dbid from rc_database where name like 'IN%') group by DB_ID having to_date(max(COMPLETION_TIME),'dd-mon-yy')!=trim(sysdate) ) t where q.dbid = t. db_id and q.dbid not in ('586755576','580830361','894607119','881224701') order by 3;but after seeing your comment i again went through all the available tables and found the following to get my result :
    select DB_NAME from rc_backup_set_summary where to_date(NEWEST_BACKUP_TIME,'dd-mon-yy')!=to_date(sysdate,'dd-mon-yy') and db_name like 'IN%';Both of them work properly.
    thanks a lot.
    Thanks and Regards,
    LittleFoot
    Edited by: Little Foot on May 9, 2013 12:27 AM

  • What's the recommended guideline on backing up a recovery catalog?

    while I understand "Benefits of Using the Recovery Catalog as the RMAN Repository" as stated in
    http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmquick.htm#442214
    as well as things to take note if using control file as the sole rman repository,
    as stated in "Monitoring the Overwriting of 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's Guide
    http://download.oracle.com/docs/cd/B14117_01/server.101/b10734/rcmrepos.htm
    "Back Up the Recovery Catalog Often"
    Even if you have to restore the recovery catalog database using a control file autobackup, you can then use the full record of backups in your restored recovery catalog database to restore the target database without using a control file autobackup for the target database.
    =>probably implies that we can use another recovery catalog let's call it backupbackup to restore the recovery catalog
    "Choosing the Appropriate Method for Physical Backups"
    Follow these guidelines when developing an RMAN backup strategy for the recovery catalog database:
    * Run the recovery catalog database in ARCHIVELOG mode so that you can do point-in-time recovery if needed.
    * Set the retention policy to a REDUNDANCY value greater than 1.
    * Back up the database onto two separate media (for example, disk and tape).
    * Run BACKUP DATABASE PLUS ARCHIVELOG at regular intervals, to a media manager if available, or just to disk.
    * Do not use another recovery catalog as the repository for the backups.=> this contradicts the previous statement
    * Configure the control file autobackup feature to ON.
    so may I know what's the recommended guideline on backing up a recovery catalog? should we use another recovery catalog to keep the rman repositories of the the main primary catalog or just use a control file autobackup feature?
    thanks

    I understand the question and the confusion.
    Please note, however, that this forum is for discussing problems and errors with the documentation in general. Your question is related to a specific product and is, as far as I can tell, not a note about a documentation error or a correction.
    The appropriate place to discuss this is the Database (General) forum or - perhaps surprisingly - the RMAN forum. These can both be found by
    1) Clicking on the 'Forum Home' link at the top of this page;
    2) Scrolling down to the category 'Database' (a category is identified by a special row format that does not list the number of topics)
    3) Expanding the category by clicking on the 'More ...' link.
    4) Scrolling down to the "Database - General" or "Recovery Manager" forum and clicking on it's link.
    Note that forums have a search function that may be used to find answers if someone has already asked a similar question.

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

  • Resync or any other maintenace work on RMAN catalog....

    I have inherited RMAN catalog created in Oracle 10g R2 to take the backup of 10g databases.
    1.I want to check what are all the databases backed up. What query I should run? Like view names.
    2.Is there any command I should run to make sure RMAN catalog is up to date. Like synchronizing. Wants to make sure my backup is recoverable.
    Thank you,
    Smith

    1. Use RC_DATABASES view to get registered databases in recovery catalog and RC_BACKUP_SET view to get registered backup sets.
    See http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmreprt.htm#CHDIJDEF
    2. see RESYNC CATALOG in http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta052.htm#RCMRF150
    which says:
    >
    RMAN automatically executes a full or partial resynchronization of the recovery catalog as needed when you execute RMAN commands, so long as the control file is mounted and the recovery catalog database is available at command execution.
    >
    Note however that database control file is always the source repository even if you use a recovery catalog.
    Even if you loose recovery catalog you should be be able to retrieve RMAN backups. See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov.htm#BRADV156.
    Edited by: P. Forstmann on 25 févr. 2010 20:15

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

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

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

  • 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

  • Need a create db script to manually create a 10g rman catalog db on unix

    Hi, Gurus:
    I would like to manually create a rman catalog database (Oracle 10g) on a HP-UX environment. Could anyone share a sql script to do that?
    It is going to be used to backup about 15 databases directly to tape and the retention policy is going to be 35 days. How big the database should be?
    Thanks in advance.

    I can't find any documentation supporting Oracle support's theory.And who writes the Oracle documentation? People in this forum?
    You got the "Best Practice" advise.
    If you have rman catalog on the same server or on the same database, it is like storing your backup on the same server you took it from.
    So, the idea od RMAN catalog is to have your catalog available for any recovery. If you cannot recover your recovery catalog, then you are better off using the controlfile as the repository.

  • Creating RMAN catalog. Are these steps correct?

    Are these steps to set up the RMAN catalog correct?
    I.
    The following two databases are the target databases which needs to be backed up.
    1. a 11.1.0.7.0 database
    2. a 10.2.0.1.0 databaseII.
    Catalog schema in a 10.2.0.4.0 database called catdb.
    III.
    I am going to use the RMAN client(10.2.0.1.0) in my laptop (Windows Server 2003).
    CATALOG schema creation
    =======================
    To create the Catalog Database (10.2.0.4.0), this what i am going to do in catdb
         a. create tablespace CAT_TBS
         b.     CREATE USER rman_cat_schema
              IDENTIFIED BY rman_cat_schema
              DEFAULT TABLESPACE cat_tbs
              TEMPORARY TABLESPACE temp
              QUOTA UNLIMITED ON cat_tbs;
         c.      GRANT create session TO rman_cat_schema;
         d.      GRANT recovery_catalog_owner TO rman_cat_schema;
         e.      GRANT execute ON dbms_stats TO rman_cat_schema;
       f. Invoke the <font color="red"><b>RMAN binary from my laptop</b></font> :
                  C:\>set ORACLE_SID=catdb
               C:\>rman catalog rman_cat_schema/rman_cat_schema@catdb log=catalog.log
                               Hopefully Catalog will get the created at catdb .
    Registering the database
    =========================
    To register the database,this is what i am going to do.
         a. Add the Tns Entry about the catdb in tnsnames.ora file of the target database
         b. Log in to target database's machine and invoke the<font color="red"><b> RMAN executable in the target database. </b></font>
            $  export ORACLE_SID=oraprod314
            $  rman TARGET / CATALOG rman_cat_schema/rman_cat_schema@catdb
                 c. Then i can give the REGISTER DATABASE command. like
                 $rman > register database;
            Edited by: Citizen_2 on 14-Sep-2009 11:46

    Yes, You can connect to RMAN catalog using a lower version client. see this.
    SQL> conn rman/rman@mycatdb
    Connected.
    SQL> select * from rcver;
    VERSION
    11.01.00.06
    SQL>
    rman
    Recovery Manager: Release 9.2.0.7.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    RMAN> connect target /
    connected to target database: STSTDB (DBID=2045697105)
    RMAN> connect catalog rman/rman@abcd.
    connected to recovery catalog database
    RMAN>
    You can take the backups and do recoveries. But, if you want to achieve certain features of the recovery catalog of higher versions to backup / recover your database, you better use the right RMAN client which allows the features to use.
    It is always advisable to use the RMAN Client same as the database version you want to backup to avoid any confusions.
    Hope it is helpul.
    Regards
    Edited by: vasu77 on Sep 15, 2009 10:01 AM
    Edited by: vasu77 on Sep 15, 2009 2:11 PM

  • RMAN Catalog Upgrade Understanding.

    Hi,
    We just upgraded our target database from oracle version 9.2.0.7 to 9.2.0.8 and our catalog database is still in 9.2.0.7 . Do we need to upgrade the recovery catalog schema in the catalog database If so then how to do that.
    I tried running upgrade catalog command on the recovery schema of the catalog database and it is upgrading to the 9.2.00 version packages.
    reldb3d:instra /opt/app/oracle/product/9.2.0.8/rdbms/admin> rman catalog instra/[email protected]
    Recovery Manager: Release 9.2.0.8.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to recovery catalog database
    RMAN> upgrade catalog;
    recovery catalog owner is INSTRA
    enter UPGRADE CATALOG command again to confirm catalog upgrade
    RMAN> upgrade catalog;
    recovery catalog upgraded to version 09.02.00
    DBMS_RCVMAN package upgraded to version 09.02.00
    DBMS_RCVCAT package upgraded to version 09.02.00
    Right now I am skeptical is it the correct way of upgrading the catalog schema in the catalog database.
    Any suggestions/advice will be highly appreciated.
    Thanks,
    Raheem

    The schema version (or the objects therein) is different from the version of the database in which the rc schema resides. As long as oracle wouldn't force you to upgrade the database, upgrading the schema is enough. The same applies to the the repository database for grid control. The version of the grid repository schema can be different from the version of the database software.
    Whatever you did is correct.

  • Backup rman catalog

    Hi
    my RMAN catalog db is is non archive log mode
    and we never back it up
    for better protection , i will convert it to archive mode and hotbackup it and use controlfile as catalog
    am i in the right way to backup my rman catalog db?
    Thanks

    user9145417 wrote:
    Hi
    my RMAN catalog db is is non archive log mode
    and we never back it up
    for better protection , i will convert it to archive mode and hotbackup it and use controlfile as catalog
    am i in the right way to backup my rman catalog db?
    Yes , you should take a hot backup of catalog DB and also configure controlfile auto backup.
    Regards
    Rajesh

Maybe you are looking for