RMAN - resync catalog

Hi,
I have a database "orcl" on which I do tests of backup and recovery. I have a database where is the catalog of the database orcl.
I did backups with rman on orcl, I changed structure of orcl.
At a moment I want to do a cold restore of the database from a cold backup. I did this.
When I enter now in rman and after I do connect catalog ... and connect target
I give the command "resync catalog" and the result is:
"failure of resync command on default channel at 08/08/2007 15:34 checkpoint change# too low"
What to do? There is another solution different than "drop catalog"?
Thank you,
Mihaela

Mihaela,
The previous posting is correct I think if all you want to do is get the catalog and database back together again, but some if it depends on what you plan on doing in the future as well.
Let me see if I understand what you did:
1. Backed up database.
2. Made changes to database
3. Restored database from a cold backup (I am assuming through RMAN)
4. ?????? I don't know what you did here???????
5. Now trying to resync database.
Here are a couple of questions that might lend help in understanding your situation.
What did you do at point #4 above? Did you do a point in time recovery? Did you open resetlogs? Did you take another backup of the database after the recovery?
Now another question is why are you trying to resync the database and catalog? Is there something going on that you need to resync? What do you think resyncing will accomplish? What are you trying to accomplish?
There are solutions different than "drop catalog" but I need to know where you are going with this, because it can get quit complicated.
Regards
Tim

Similar Messages

  • RESYNC CATALOG

    I'm looking at the following reference and a bit confused about the Full Resynchronization process
    http://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta038.htm
    From one hand it says :
    "you run RESYNC CATALOG When You made changes to the physical structure of the target database such as adding or dropping a tablespace. As with log archiving, *the recovery catalog is not updated automatically when the physical schema changes*"
    On the other hand, a few line later iit says :
    RMAN performs a full resynchronization after structural changes to database (adding or dropping database files, creating new incarnation, and so on)
    Thank you.

    Hello,
    "you run RESYNC CATALOG When You made changes to the physical structure of the target database such as adding or dropping a tablespace. As with log archiving, *the recovery catalog is not updated automatically when the physical schema changes*" it means that it's good practise to run RESYNC CATALOG manually after changes to physical structer of target database and if you know that you are not running any RMAN script after the changes - there isn't any background connection between target database and catalog if you are not running RMAN (connected to target + catalog)
    On the other hand, a few line later iit says :
    RMAN performs a full resynchronization after structural changes to database (adding or dropping database files, creating new incarnation, and so on) if you will be connected to target database and catalog using RMAN, RESYNC CATALOG will be run automatically after structural changes (if you will have new archived logs - 10 and more, resync will run too).
    Lukas

  • RMAN backup fails atlast during resync catalog with ORA-00001

    Hi Everyone,
    Database version:10.2.0.2.0
    single instance database
    My Rman backups were running fine but today i got the error , almost at the end of backup
    Finished Control File and SPFILE Autobackup
    released channel: t1
    released channel: t2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03008: error while performing automatic resync of recovery catalog
    ORA-00001: unique constraint (RMAN.CKP_P) violated
    Recovery Manager complete.
    This problem occured 2 days before.I connected to catalog and ran a resync catalog and the backup worked fine for next day.
    Now again today iam experiencing the same problem.
    Any help would be great

    Thanks for the reply
    SQL> select * from rman.rcver;
    VERSION
    10.02.00.00
    10.02.00.02
    when i do the resync catalog manually it works fine.only during the end of backup it throws me the error;
    was wondering whether can i disable the primary key constraint on CKP table so that i can avoid the error.
    since its a live system im thinking lot before i do anything
    Thanks
    Edited by: centerB on 14-Apr-2011 06:40
    Edited by: centerB on 14-Apr-2011 06:57
    Edited by: centerB on 14-Apr-2011 07:03

  • Backup size is increased after resync catalog

    Hi everyone,
    I have describe my problem, if anyone have a solution please provide me.
    Rman catalog database version : 10.2.0.1.0, OS : red hat linux
    Target database version : 10.2.0.5.0, OS : solaris 10
    rman catalog database space is full, then i move my example tablespace to another location, but i forgot to change the ownership of new file.
    And I have no backup of my rman catalog database. so i offline the datafile first for opening the rman catalog database after opening the database I have offline the whole example tablespace and this tablespace cannot contain any thing related the catalog.
    after that I used the command : crosscheck archivelog all;
    DELETE EXPIRED ARCHIVELOG ALL
    then i run the command : CROSSCHECK BACKUP;
    DELETE EXPIRED BACKUP;
    then i run the command : report obsolete;
    delete obsolete;
    then i run the command : RESYNC CATALOG;
    then i run the command : change archivelog all validate;
    after doing all the thing when I am taking a backup of archive log by using following command :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/ARCH_%d_%s.bak';
    backup archivelog all;
    before performing all the above thing my archive backup of whole day is around 5gb but after the above thing my archive backup of one day is around : 126gb
    and my level0 backup is alright after and before the above thing and the size is around : 139gb
    the script for the full backup is :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/FULL_%d_%s_%c.bak';
    backup incremental level 0 database skip offline;
    after that I have perform the incremental level 1 backup by using the following script :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/INC1_%d_%s_%c.bak';
    backup incremental level 1 database;
    before the above activity the size of incremental backup is around : 4.5gb but after performing the above activity the incremental backup size is around : 120gb
    it is very critical for me, if any one have the solution please provide me as early as possible.
    Thanks & Regards
    Rakesh Kumar

    Hi Hemant K Chitale,
    you said that I am using the COMPRESSED BACKUPSETs till 22-Jan, so I am posting
    the rman configuration here that is used before all this happening and same
    configuration is used right now.
    but before resync catalog the archivelog is generated only one location then I used to archive log
    dest for archive log generation then after 5 month I will resync my catalog. may be it is the
    reason.
    because there are no compressed backupset is defined in the rman configuration.
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/appl2/prodback_rman/prod_fullbackup/ctrl_%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/appl2/prodback_rman/prod_fullbackup/prod_%d_%s_%c.bak', '/appl2/prodback_rman/usb/prod_%d_%s_%c.bak';
    CONFIGURE MAXSETSIZE TO 20 G;
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/appl2/prodback_rman/prod_fullbackup/snapcf_PROD.f';
    Archive log generation log on the daily basis.
    SQL> select trunc(COMPLETION_TIME,'DD') Day, thread#,
    round(sum(BLOCKS*BLOCK_SIZE)/1048576) MB,
    count(*) Archives_Generated from v$archived_log
    group by trunc(COMPLETION_TIME,'DD'),thread# order by 1;
    DAY THREAD# MB ARCHIVES_GENERATED
    04-FEB-13 1 2776 37
    05-FEB-13 1 16767 220
    06-FEB-13 1 16545 216
    07-FEB-13 1 15772 208
    08-FEB-13 1 15056 198
    09-FEB-13 1 18486 244
    10-FEB-13 1 17591 232
    11-FEB-13 1 18163 238
    12-FEB-13 1 15062 198
    13-FEB-13 1 26383 342
    14-FEB-13 1 36279 462
    DAY THREAD# MB ARCHIVES_GENERATED
    15-FEB-13 1 34010 432
    16-FEB-13 1 32230 413
    17-FEB-13 1 31904 408
    18-FEB-13 1 33448 426
    19-FEB-13 1 34639 444
    20-FEB-13 1 36684 468
    21-FEB-13 1 27547 352
    right know the archive log backup size by rman is around 19gb per day.
    so tell me how we reduce the size of my archive log backup according to
    my rman configuration and how can i reduce the archive log generation on
    my production server on daily basis.
    Thanks & Regards
    Rakesh Kumar

  • Oracle RMAN recovery catalog database in a Primary and Standby mode

    Hello All,
    The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups. There are are 200+ databases running on OEL, RHEL and Windows. So we planned to host the recovery catalog database on Oracle Active DataGuard 11.2.0.1 Enterprise Edition on RedHat EL 5.8 version on two physical servers. The Primary Instance will be in one server in the Primary DC and the Standby Instance will be on another server in another DC. Also all the database datafiles are hosted in ASM Diskgroups on SAN (DATA, FRA, REDO, ARCH diskgroups).
    Are there any specific RPM/patch/OS user custom/specific settings or configurations needed..?
    Thanks in advance..
    Regards,
    Abhijit

    "The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups"
    Hi,
    i think you can achieve HA for the catalog DB. (Rac and Asm should work fine)
    There's no way (afaik) to use TAF with the rman backup. If you have a failure during a backup it simply fails.
    There is no TAF in this situation.
    Hope this helps.
    Regs,
    Drew

  • RMAN - upgrade catalog taking too long

    Hello ,
    I am trying to upgrade the rman catalog and it is taking too long to upgrade , infact after 4 hours wait time it is still excuting the upgrade command .
    Target database is : 11.2.0.3 PSU1
    catalog database : 11.2.0.2
    upgrading the rman catalog to 11.2.0.3 .
    I tried executing the command at a very quiet time of the day when catalog is not been used by any database . Please advice if you have encountered the similar issue and fixed it .
    Thanks
    Venkat

    After some time into execution of "upgrade catalog" i got the output as below , and after that i let all the jobs of rman execute completely from diff databases that are connected to catalog and re-executed the "upgrade catalog" command , which finally completed the upgrade process with out the issues .
    Error :
    RMAN> upgrade catalog;
    error creating upgcat_strt_0
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00060: deadlock detected while waiting for resource
    Re-executed when no sessions are connected to catalog and the upgrade process is successful .
    RMAN> connect catalog rman/rman@database
    connected to recovery catalog database
    PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.02 in RCVCAT database is not cu
    PL/SQL package RMAN.DBMS_RCVMAN version 11.02.00.02 in RCVCAT database is not cu
    RMAN> upgrade catalog;
    recovery catalog owner is RMAN
    enter UPGRADE CATALOG command again to confirm catalog upgrade
    RMAN> upgrade catalog;
    recovery catalog upgraded to version 11.02.00.03
    DBMS_RCVMAN package upgraded to version 11.02.00.03
    DBMS_RCVCAT package upgraded to version 11.02.00.03
    Thanks
    Venkat

  • RMAN resync

    Hi,
    i have created second catalog database and registered in target database. And i checked with "show all" command.
    Here it showing same configurations whatever i have given in first catalog database. Do i need to run any new configurations for second catalog or no need?
    Both catalogs use same configurations?
    i am working on "Increasing Availability of the Recovery Catalog" , below is the doc.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcatdb.htm
    Thanks,
    Raja

    One you register the databaes in both catalogs then resync catalog operation should be all you need to do, however this will all be manual so therefore ensure that you have processes/procedures to ensure that happens regularly.

  • Different between normal rman and rman with catalog

    Hi all ,
    my question is what is the advantage of using rman with catalog server , and how i can making rman backup to protect my database till last transaction
    thanks

    my question is what is the advantage of using rman with catalog server , and how i can making rman backup to protect my database till last transaction Catalog database/server can register number of target database backup information.
    Lets suppose you have 10 databases in your environment, If you want to check each database backup details you have to check in each and every database, where in case of catalog, you just need to connect catalog and you can see all the information from RC_ views.
    Its a centralized repository database.
    Of course the backup information will hold both the catalog database & target database, When your Retention is high the backup information will stores in controlfile, then there is chance to huge growth in controlfile size which is not good. Also you lost whole Target database then with the help of catalog you can easily find out which is latest backup and easy to restore with that information.
    Hope this clears.

  • RMAN ( PROBLEM while resync catalog)

    We are facing this problem. when we are firing any command using RMAN/
    Following are two samples.
    Recovery Manager: Release 8.0.4.0.0 - Production
    RMAN-06005: connected to target database: ORC1
    RMAN-06008: connected to recovery catalog database
    1)
    RMAN> LIST BACKUPSET OF TABLESPACE SYSTEM2> ;
    RMAN-03022: compiling command: list
    RMAN-03026: error recovery releasing channel resources
    RMAN-00569: ================error message stack follows================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: list
    RMAN-03014: implicit resync of recovery catalog failed
    RMAN-06038: recovery catalog package detected an error
    RMAN-20035: invalid high recid
    2)
    RMAN> RUN {2> ALLOCATE CHANNEL C1 TYPE DISK;3> BACKUP DATABASE FORMAT 'E:\ORANTV8\TESTD
    ATA\BACKUP\DB_s%s_p%p' ;4> RELEASE CHANNEL C1;5> }
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: c1
    RMAN-08500: channel c1: sid=16 devtype=DISK
    RMAN-03022: compiling command: backup
    RMAN-03026: error recovery releasing channel resources
    RMAN-08031: released channel: c1
    RMAN-00569: ================error message stack follows================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: backup
    RMAN-03014: implicit resync of recovery catalog failed
    RMAN-06038: recovery catalog package detected an error
    RMAN-20035: invalid high recid
    RMAN> exit
    Recovery Manager complete.
    null

    take a look at the RMAN troubleshooting section in the documentation on OTN @ http://technet.oracle.com/docs/products/oracle8i/doc_library/817_doc/server.817/a76990/troubler.htm#447659.
    This will step you through 2 different solutions to fix the problem.

  • Upgrading rman 9i catalog to 10g catalog.

    Hi,
    I need to know the typical steps to upgrade the rman catalog from 9i to oracle oracle 10g. We have already 9i db's registered with 9i catalog and 10g db's are there which we will register with the upgraded 10g catalog.
    Kindly provide links and also summarise here the typical steps involved.
    Thanks in advance for all the help !!

    Depends. If you want to do an in-place upgrade, then upgrade the database to at least the highest 10g database that will be connecting. For example, if the highest 10g version you have is 10.2.0.1, then go to at least 10.2.0.1. I have been running 10.2.0.3 without any issues.
    After upgrading the database, login to the rman catalog using the same ORACLE_HOME as the database, and run:
    upgrade catalog;
    That's it. No bells, no whistles. The docs are very clear on this and it's not a huge ordeal.
    Or, you can export/import to a new database, and run 'upgrade catalog' on it.

  • Rman no catalog or no repository

    I need some clarification about rman configuration without repository
    and catalog.I like to configure for a smal database (solaris9, oracle
    9.2 ,100gb).
    My conclusion about rman configuration without repository and nocatalog
    The metadata will be in controlfile and it wil be reused depends upon
    the value of parameter control_file_keep_record
    If i proper backup of full database (including cotnrolfile) i can
    recover the data if the database or system crashes.
    1) Can u specify whats is the advantages and disadvantages if i am
    using rman in same database without catalog and without repository.

    You may want to read the following.
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrepos.htm#431413

  • RMAN create catalog

    I will backup my oracle10g database( target DB) using rman in oracle9i database (Rman catalog Dabase)
    How could I create a 10g recovery catalog in the 9i catalog database.

    Do you have a 9i catalog already or not?
    You just create a catalog in 10g the way you do in any other version - connect using the 10g rman exe to the user in the catalog database (which is of course just an empty DB at this point) and create catalog.
    If you already have a 9i catalog, you can either upgrade this catalog to 10g or create a seperate 10g catalog schema owner in the same DB, connect to that and create the 10g catalog.
    A mate of mine who is a RMAN nut prefers to keep the different catalog versions in seperate schemas inside the same catalog database (so you need to backup each DB connecting to the appropriate catalog), whereas I prefer to upgrade the catalog and backup all DBs to it.
    HTH
    Chris

  • RMAN GRID CATALOG

    Hi,
    1) I am palnning to find the list of databases the are being backed up every day. I also need the list of all databases for which backup is there. I found out that there are few catalog Views like RC_BACKUP_DATAFILE_DETAILS, RC_DATABASE etc. In these views i can only see the list of databases the are registered. I dont know if they are being backed up. I need to know the last backup time if possible. I know how to do it for single database. I need one query which gives information of all the databases that are being backup under this catalog.
    2) I also need to know the diffrence between GRID jobs BACKUP and regular RMAN backup. Like are they different. Do we have any special views for backup in GRID control. I have seen MGMT$HA_BACKUP view. I wonder if there is any better view where it gives the information of when it is being backup every day.

    1. Try selecting from rc_rman_status e.g following is one we use to detect failed backups.
    select db_name, start_time, status, object_type
    from rcowner.rc_rman_status
    where start_time > (sysdate-1) and (status like '%FAILED%' or status like '%ERRORS%');
    2. If it is a scheduled OEM job try selecting form MGMT_JOB_EXEC_SUMMARY, mgmt_job
    select count(*) from
    sysman.MGMT_JOB_EXEC_SUMMARY e, sysman.mgmt_job d
    where e.job_id=d.job_id and job_owner not like 'SYS%' and start_time > (sysdate-1);
    OEM will just run an rman job. You can check the job parameters to find out what it is doing.

  • Error while registering RMAN from primary to catalog database

    Hi all,
    Here we have a 10g dataguard environment with db1(db_unique_name) as primary and db2(db_unique_name) as physical standby database. Also we configured one schema on a third machine as catalog database using following steps.
    The steps executed in catalog database(appsdb):
    SQL> create tablespace rmancatlog_tbs datafile '/u01/app/oracle/oradata/NEW/rman_catalog.dbf' size 500M autoextend off extent management local segment space management auto;
    SQL> create user rman identified by oracle
    2 default tablespace rmancatlog_tbs
    3 quota unlimited on rmancatlog_tbs
    4 ;
    SQL> GRANT connect, resource, recovery_catalog_owner TO rman;
    RMAN> create catalog;
    recovery catalog created
    Added tns entries of catalog database in primary and standby. Then from primary database we tried to register to catalog database. It is showing that it is registering. But every query afterwards in rman is throwing the error. Below are the steps and error:
    [oracle@db1 ~]$ rman target sys/oracle catalog rman/oracle@appsdb
    Recovery Manager: Release 10.2.0.3.0 - Production on Mon Aug 13 21:39:32 2012
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: NIOS (DBID=1589015669)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    RMAN> report schema;
    Report of database schema
    List of Permanent Datafiles
    ===========================
    File Size(MB) Tablespace RB segs Datafile Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 10/08/2012 06:16:06
    RMAN-00600: internal error, arguments [8201] [] [] [] []
    Can anyone help regarding this error?
    Thanks in advance.

    on resync catalog it is throwing no output or error.
    but it shows same error afterwards.
    RMAN> resync catalog;
    RMAN> report schema;
    Report of database schema
    List of Permanent Datafiles
    ===========================
    File Size(MB) Tablespace RB segs Datafile Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 10/09/2012 03:55:53
    RMAN-00600: internal error, arguments [8201] [] [] [] []

  • Error while taking RMAN back up - RMAN-03009: failure of backup command ..

    Hi Experts,
    I am trying to take RMAN back up but at the end I get this error message.. I found a solution at http://www.oracle-base.com/articles/9i/RecoveryManager9i.php
    But this is of oracle 9i. Can I use it on 10g too ?
    So is this Step correct ?
    1) First create a user to hold the recovery catalog:
    a) CONNECT sys/password@w2k1 AS SYSDBA
    b) GRANT connect, resource, recovery_catalog_owner TO rman;
    2) Then create the recovery catalog:
    a) C:>rman catalog=rman/rman@w2k1
    b) RMAN> create catalog tablespace "RMAN";
    c) RMAN> exit
    3) Register Database
    a) C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
    b) RMAN> register database;
    c) Existing user-created backups can be added to the catalog using: (*So far no Back up taken so I guess this step can be ignored*)
    i) RMAN> catalog datafilecopy 'C:\Oracle\Oradata\TSH1.dbf';
    ii) RMAN> catalog archivelog 'log1', 'log2', 'log3', ... 'logN';
    4) Full Backup Configuration
    RMAN> configure retention policy to recovery window of 7 days;
    RMAN> configure default device type to disk;
    RMAN> configure controlfile autobackup on;
    RMAN> configure channel device type disk format 'C:\Oracle\Admin\W2K2\Backup%d_DB_%u_%s_%p';
    5) Full back up
    RMAN> run {
    backup database plus archivelog;
    delete noprompt obsolete;
    6) RMAN> resync catalog;
    Starting backup at 15-MAY-10
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00006 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\DM_MENTOR200
    60430230208_DB.DBF
    input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\UNDOTBS01.DB
    F
    input datafile fno=00007 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\DM_MENTOR200
    60430230208_IND.DBF
    input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSTEM01.DBF
    input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSAUX01.DBF
    input datafile fno=00005 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\EXAMPLE01.DB
    F
    input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 15-MAY-10
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/15/2010 05:11:
    03
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
    continuing other job steps, job failed will not be re-run
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current controlfile in backupset
    channel ORA_DISK_1: starting piece 1 at 15-MAY-10
    channel ORA_DISK_1: finished piece 1 at 15-MAY-10
    piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\BACKUPSET\2010_05
    _15\O1_MF_NCNNF_TAG20100515T045136_5YX3TTFT_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:17
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup plus archivelog command at 05/15/2010 05:11:21
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/15/2010 05:11:
    03
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
    RMAN>
    Thanks & Regards,
    Ranjith John

    Provided you consult the 10g RMAN documentation and the online error documentation: yes.
    But apparently you didn't check documentation, not even the error messages!!!!! Why?
    You are backing up to the Flash Recovery Area, and the error messages mean too much space is occupied.
    How to configure the Flash Recovery Areea is fully documented in the Backup and Recovery manual for 10g at http://tahiti.oracle.com
    READ IT.
    Please do not ask a volunteer to abstract it.
    Sybrand Bakker
    Senior Oracle DBA

Maybe you are looking for