The RMAN catalog database backup

Version: 10.2.0.1.0

We have created a database to host our RMAN catalog. This catalog contains info backup more RMAN stored scripts for 5 production databases. Now, we have to save this the RMAN catalog database.

I'm going to use the control as the catalog file (IE. NOCATALOG) for our the RMAN catalog database. This should be good. Right? Best practices should I follow this topic?

The catalog database can be saved as a BACKUP when COLD, if not in use for other purposes. Simple and easy backup and restore.

Otherwise, you can make backups RMAN, but the this backup catalog database Controlfile.

(You can even take copies to export the schema from the RMAN catalog!)

Hemant K Collette

Published by: Hemant K grapple on July 8, 2010 14:45

Tags: Database

Similar Questions

  • Stop planned of the rman catalog database

    Hello
    We have several databases are backed up using RMAN and we use the catalog database.
    AIX, database catalog rman hosts servers will go for weekly maintenance and therefore this catalogue
    database is not available for 8-10 hours.

    We have jobs as
    (1) the hot backup jobs
    (2) cold backup jobs
    (3) archive files backups

    Can I know what would become of the work when the catalog database is down?
    Y at - there any preventive measure, we have to take or to do something once the
    Catalog database is running.

    Thank you
    Guz

    In this case, I think I need to move all these files on tapes
    just before the planned closure to avoid the ORA-257 archive error space then...

    I don't understand this. When you remove the connection to the catalog of your scripts, backups will continue to function - with only controlfile. This means that your archivelog backups will continue to run and to clear the archivelog destinations (I assume that you have a policy of suppression for archives).

    Werner

  • 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

  • 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

  • Version of the RMAN catalog

    Hi, we are modernizing our databases 9i to 11g R2 R2 target, use us RMAN to make backups and our version of RMAN catlog is 10.2.0.2, I need to know if we continue with the current version of our data catalog RMAN or it must be upgraded to version equilent to our target databases You also have to configure Data protector with RMAN will be compatible with the lower version of the RMAN catalog database.

    Kind regards

    In our case when we improve our database to 10.2.0.2 to 10.2.0.4 didn't us connect with the catalogue. After the upgrade of the database catalog in 10.2.0.4 we took over with the RMAN backup.

    You can take the RMAN backup without a catalog database.

    Concerning
    Asif Kabir

  • 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

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

  • Control to the RMAN catalog file

    Dear friends,

    Now my RMAN backup is running using the control file. How can I change the catalog?

    Please guide me.

    Thanks in advance.

    If there is no drawback application RMAN catalog, then I guess I do it with her.

    Like when I want to recover the database in a new server with the backup and so on... >

    The downside is the maintenance you need to do for the catalog. He had some performance issues with the catalog in previous versions, but I think he's fine now.

    Do I need to back up the RMAN catalog or back up separately in addition to the backup of the database?

    Could I lose the catalog if I lose my database

    Just save as regularly as you can afford. RMAN or export. Losing the catalog is a hassle but not the end of the world.

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

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

  • Get information directly from the database of the RMAN catalog

    All,

    Assuming that one is unable to connect to the target database, but can directly connect to the catalog database:

    HostName: rman.prod.hobank.net
    User name of the operating system: oracle
    Oracle SID: RMAN
    User RMAN: rman

    When you are connected to the RMAN database as user rman (as shown below),

    [oracle@rman] sqlplus rman/rman

    What views I need to ask for the following information:

    -Backups performed
    -Backup type (for each backup)
    -Calendar

    Thanks in advance.

    Baffy

    You can get all the information backup recovery catalog views. For example, V$ RC_BACKUP_SET, V$ RC_BACKUP_PIECE, V$ RC_BACKUP_FILES, etc. and the view contains the type of backup as
    V$ RC_BACKUP_FILES. BACKUP. But I don't understand your 'calendar' means.

  • ORA-39080: cannot create queues during the backup from the rman catalog

    Hello
    I am trying to upgrade my database 10 g and 11 g and I'm trying to back up my rman catalog. However, I get an error. Can someone help me please-

    That's what I give-
    nohup expdp DIRECTORY = EXPORT_DIR userid=rman/adc1243@rmandb full = y job_name = full_rmandb_upg_exp DUMPFILE=EXPORT_DIR:rmandb_upg_exp%U_20100618.dmp LOGFILE = PARALLEL EXPORT_DIR:rmandb_upg_exp_20100618 = 3 &

    and I get this-

    Oracle @ < progd1 >: / home/oracle $tail f nohup.out
    ORA-31626: there is no job
    ORA-31637: could not create user RMAN FULL_RMANDB_UPG_EXP work
    ORA-06512: at "SYS." DBMS_SYS_ERROR', line 95
    ORA-06512: at "SYS." "KUPV$ FT_INT", line 600
    ORA-39080: cannot create queues ' KUPC$ C_1_20100618202950 ' and ' KUPC$ S_1_20100618202950 ' to Data Pump task
    ORA-06512: at "SYS." DBMS_SYS_ERROR', line 95
    ORA-06512: at "SYS." ' KUPC$ QUE_INT ', line 1606
    ORA-04031: unable to allocate 56 bytes of shared memory ('pool feed', 'unknown object', 'pool feed', 'set the allocation callback')

    ORA-04031: unable to allocate 56 bytes of shared memory ('pool feed', 'unknown object', 'pool feed', 'set the allocation callback')

    04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")"
    // *Cause:  More shared memory is needed than was allocated in the shared
    //          pool.
    // *Action: If the shared pool is out of memory, either use the
    //          DBMS_SHARED_POOL package to pin large packages,
    //          reduce your use of shared memory, or increase the amount of
    //          available shared memory by increasing the value of the
    //          initialization parameters SHARED_POOL_RESERVED_SIZE and
    //          SHARED_POOL_SIZE.
    //          If the large pool is out of memory, increase the initialization
    //          parameter LARGE_POOL_SIZE.  
    

    Stream uses system global area (SGA) memory to store the information required to capture and apply. To allocate memory from the SGA for use by water courses, establish a flow pool in the SGA by specifying the STREAMS_POOL_SIZE parameter. The default value for this setting is 0, which means that the stream instead uses the shared pool memory. If you leave the STREAMS_POOL_SIZE to its default value (0), water courses will be considering using up to 10 percent of the SHARED_POOL_SIZE, then Oracle recommends at least 200 MB for the STREAMS_POOL_SIZE parameter. The source and destination databases must take account of this memory in the SGA.

    Published by: sb92075 on June 18, 2010 19:17

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

  • Cleaning of the RMAN catalog

    I left a cron job run Friday, so all the hours, he did a complete backup of my VTL. Here are the steps I did:

    run
    {allocate channel ch00 type sbt
    format = '% d_data_set % s_piece % p_ T_ %U '.
    PARMS "ENV=(TDPO_OPTFILE=/a0221/oracle/tivoli/ufms609_jd1su221_tdpo.opt);
    delete the backup of database;
    output channel ch00;
    }



    After rman had removed all backupsets that looks like the catalog is keeping the information of these backups:


    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    7165 full 9.25 M SBT_TAPE 00:00:08 22 March 10
    BP key: 7169 situation: AVAILABLE Tablet: NO Tag: TAG20100322T055403
    Handle: UFMS609_data_set204_piece1_20100322_6cl96gqu_1_1 Media:
    SPFILE included: Modification Date: March 17, 10
    SPFILE db_unique_name: UFMS609
    Control file included: cash SNA: 5993074 cash time: 22 March 10

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    7237 full 9.25 M SBT_TAPE 00:00:08 22 March 10
    BP key: 7241 situation: AVAILABLE Tablet: NO Tag: TAG20100322T065403
    Handle: UFMS609_data_set206_piece1_20100322_6el96ker_1_1 Media:
    SPFILE included: Modification Date: March 17, 10
    SPFILE db_unique_name: UFMS609
    Control file included: cash SNA: 5995378 cash time: 22 March 10


    How can I remove these entries from my catalog? I tried to delete backupset 7165,7237; but who didn't clean up the catalog.

    Thank you!!!

    RMAN-06091: any string allocated for maintenance (of a suitable type)

    Delete... is an operation of maintenance, so use «assign channel for maintenance...» ».

    Werner

Maybe you are looking for