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

Similar Messages

  • 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

  • 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

  • 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

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

  • 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

  • RMAN catalog resync in Dataguard environment

    Hello,
    I have a quick question regarding the resync of the recovery Catalog in a 10g Dataguard environment...
    I plan to perform the backups from the physical standby side. (Backups of DB and archives).
    If I want to restore/recover a datafile on the primary side, do I automatically see the backup information once i am connected to the catalog DB, or do I have to perform a "resync catalog;" statement to resync the control file of the primary side with the actual backup information from the catalog?
    Thanks in advance,
    Boris...

    But what is the effect, if I perform this statement on the primary side? Do I loose backup information if I perform a resync of the catalog because the backups were made from standby side? If I perform all backups from standby side the control file on the primary side does not know about the backups.
    I am asking because I want to know if I have to adjust the backupscripts. They perform a resync of catalog per default.
    Thx, Boris..

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

  • Registering primary database to catalog database.

    Hi all,
    Here we have a 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?

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

  • From no recovery catalog to recovery catalog

    sorry for the message to be posted 2nd time due to error in internet connection.
    Message was edited by:
    Nitesh Jain

    Hi Nitesh Jain!
    First thing to do ist to register all your database in the RC (RC = Recovery Catalog)
    test@localhost> rman target system/oracle@PRODDB1 catalog catowner/password@CATDB
    REGISTER DATABASE;
    exit;
    In this example PRODDB1 is your first production Database and CATDB ist your Catalog database. The REGISTER DATABASE Command registers your DB in the RC. Do this step for all your productiv DBs.
    Next thing to do is to resync your controlfile with your RC for all your productiv DBs.
    i]test@localhost> rman target system/oracle@PRODDB1 catalog catowner/password@CATDB
    RESYNC CATALOG;
    exit;
    RESYNC CATALOG takes all Information from your controlfiles and puts it into your RC.
    This should be all. You can use LIST BACKUP to check whether your Backups are registered in your RC or not. If you have to register Backups manually try the CATALOG START WITH '/path_to_your_backups/' Command. You can read about it in the Onlinedocumentation in the RMAN Reference.
    Hope this helps!

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

  • Oracle Standby and RAMN CATALOG

    Dear experts,
    I have physical data guard implemented and I also scheduled the backup of database with cron on Linux to IBM tape. Everything was fine for about 6 months.
    few days ago I realized that backup is not performed from standby database. After same investigation I found out that this is because RMAN from standby DB wants to resync catalog but can't connect to catalog database  which is separate database.
    this is from my log from cron
    ORA-20079: full resync from primary database is not done
    doing automatic resync from primary
    resyncing from database with DB_UNIQUE_NAME XYZS1DG1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of configure command at 10/02/2013 04:00:18
    RMAN-03014: implicit resync of recovery catalog failed
    RMAN-03009: failure of partial resync command on default channel at 10/02/2013 04:00:18
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified
    ORA-17629: Cannot connect to the remote database server
    I tried to connect via RMAN to catalog and it works.
    #:~> rman target / catalog XXX/XXX@XXX 
    Recovery Manager: Release 11.2.0.3.0 - Production on Wed Oct 2 12:24:05 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: XYZS1 (DBID=3537003386)
    connected to recovery catalog database
    but when I started resync
    RMAN> resync catalog;
    starting partial resync of recovery catalog
    ORA-20079: full resync from primary database is not done
    doing automatic resync from primary
    resyncing from database with DB_UNIQUE_NAME XYZS1DG1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of resync command on default channel at 10/02/2013 12:25:51
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified
    ORA-17629: Cannot connect to the remote database server
    How can be this possible ? I not connected to catalog database already ? or I am missing something......
    What I did.
    I resync catalog from Primary database so Standby not need to resync it again and my backup works well in night but this is only for 1 night. Next day again some problem.
    Please help, advise.
    Thanks in advance.

    Yes I can connect to catalog db from here.
    # sqlplus XXX/XXX@XXX
    SQL*Plus: Release 11.2.0.3.0 Production on Wed Oct 2 22:00:46 2013
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning option
    SQL> select * from v$instance;
    INSTANCE_NUMBER INSTANCE_NAME
    HOST_NAME
    VERSION           STARTUP_T STATUS       PAR    THREAD# ARCHIVE LOG_SWITCH_WAIT
    LOGINS     SHU DATABASE_STATUS   INSTANCE_ROLE      ACTIVE_ST BLO
                  1 XXXXX
    XXXX-XXXX
    11.2.0.3.0        24-SEP-13 OPEN         NO           1 STARTED
    ALLOWED    NO  ACTIVE            PRIMARY_INSTANCE   NORMAL    NO
    SQL>

  • 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

  • RMAN retention policy - backup spfile and then redundancy = 5 removes it.

    I have a database that is Oracle Standard Edition and it is version 9.2.0.6.
    The spfile has not changed since November, 2005. A list backup does not show an spfile backup with a tag of "hot_database_spfile_backup_full". I took a close look at the RMAN script log and was shocked to discover that the spfile backup from the current day is being deleted. Is that because of the redundancy = 5? I'm trying to figure out why a backup piece from the current day is being deleted?
    Examples follow.
    The script deletes obsolete with redundancy = 5, however, I believe the intent was to keep 25 days because one of the configure clauses is set to a recovery window of 25 days. I realize that the redundancy overrides the configure retention policy command. I can fix the script and remove the redundancy = 5.
    In the RMAN run statement, I first resync the catalog, backup the spfile, a full backup of the database including current controlfile plus archive log (delete input), resync catalog, switch logfile, and backup any additional archive logs. The backup looks fine.
    Then, I allocate a channel for maintenance type sbt. The script then has a "delete noprompt expired backup;" a "delete noprompt obsolete redundancy = 5;" and finally, a crosscheck;
    example of backup piece that is later deleted:
    Starting backup at 07/18/2006 20:00:14
    channel t1: starting full datafile backupset
    channel t1: specifying datafile(s) in backupset
    including current SPFILE in backupset
    channel t1: starting piece 1 at 07/18/2006 20:00:14
    channel t1: finished piece 1 at 07/18/2006 20:00:15
    piece handle=P*****_2338_1_596145614_FULL comment=API Version 2.0,MMS Version 5.2.0.0
    channel t1: backup set complete, elapsed time: 00:00:01
    Finished backup at 07/18/2006 20:00:15
    deletion:
    Deleting the following obsolete backups and copies:
    Type Key Completion Time Filename/Handle
    <other lines deleted>
    Backup Set 27453 07/18/2006 20:00:14
    Backup Piece 27454 07/18/2006 20:00:14
    P*****_2338_1_596145614_FULL
    deleted backup piece
    backup piece handle=P*****_2338_1_596145614_FULL recid=2039 stamp=596145614
    Deleted 12 objects
    Why is a backup piece created on 7/18 being deleted in the maintenance step?
    Thanks in advance!

    In the next step in the script, the controlfile and spfile are backed up:
    backup
    full
    skip inaccessible
    tag hot_database_backup_full
    format '%d_%s_%p_%t_FULL'
    (Database
    include current controlfile)
    Plus Archivelog delete input;
    Even though my backup script is redundant by backing up the spfile twice, when I list the backup of the spfile, I would have expected to find 5 backups with a tag of hot_database_spfile_backup_full and 5 with a tag of hot_database_backup_full. That is not the case. I only find spfiles with a tag of hot_database_backup_full. i am still perplexed by RMAN.
    I will modify my script - remove the backup of the spfile, and crosscheck before the delete commands. I will also remove the redundancy = 5. The intent is to keep 25 days of backups.
    Thanks for your comments

  • Backup file getting generated on FRA insted of format path

    Hi,
    I have below script to generate RMAN full backup on given path in FORMAT directory, still RMAN genarate one .bkp file on FRA.
    We require to generate all backup files on given format path only.
    below file was generated on FRA
    o1_mf_nnndf_TAG20100804T043926_65l9t06h_.bkpBelow is the code for generating full backup.
    backup database plus archivelog FORMAT '/export/home/nfs_bak/lims/backup/ndb/backup_%d_DB_%D%M%Y_%U_%s'  delete all input;
    resync catalog;
    report schema;
    list backup;
    CROSSCHECK BACKUP;
    CROSSCHECK BACKUPSET;
    DELETE NOPROMPT EXPIRED BACKUP;
    DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
    CROSSCHECK  ARCHIVELOG ALL;
    DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;Oracle : 11gR2
    OS:Solaris

    Output for old command:
    RMAN> backup database plus archivelog FORMAT '/export/home/nfs_bak/lims/backup/ndb/backup_%d_DB_%D%M%Y_%U_%s'  delete all input;
    Starting backup at 05-AUG-10
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=194 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=225 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=26 RECID=24 STAMP=726199910
    channel ORA_DISK_1: starting piece 1 at 05-AUG-10
    channel ORA_DISK_1: finished piece 1 at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_16lkhrj8_1_1_38 tag=TAG20100805T021152 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_26_65nok6fb_.arc RECID=24 STAMP=726199910
    Finished backup at 05-AUG-10
    Starting backup at 05-AUG-10
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=+DATA/lims/ndb/system01.dbf
    input datafile file number=00002 name=+DATA/lims/ndb/sysaux01.dbf
    input datafile file number=00006 name=+DATA/lims/ndb/datafile/ndb_cellmap_idx_tbs_01.dbf
    input datafile file number=00008 name=+DATA/lims/ndb/datafile/ndb_fingerprint_tbs_idx_01.dbf
    input datafile file number=00010 name=+DATA/lims/ndb/datafile/ndb_sys_idx_tbs_01.dbf
    channel ORA_DISK_1: starting piece 1 at 05-AUG-10
    channel ORA_DISK_2: starting full datafile backup set
    channel ORA_DISK_2: specifying datafile(s) in backup set
    input datafile file number=00005 name=+DATA/lims/ndb/datafile/ndb_cellmap_tbs_01.dbf
    input datafile file number=00007 name=+DATA/lims/ndb/datafile/ndb_fingerprint_tbs_01.dbf
    input datafile file number=00009 name=+DATA/lims/ndb/datafile/ndb_sys_tbs_01.dbf
    input datafile file number=00003 name=+DATA/lims/ndb/undotbs01.dbf
    input datafile file number=00004 name=+DATA/lims/ndb/users01.dbf
    channel ORA_DISK_2: starting piece 1 at 05-AUG-10
    channel ORA_DISK_1: finished piece 1 at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_17lkhrj9_1_1_39 tag=TAG20100805T021153 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:06:46
    channel ORA_DISK_2: finished piece 1 at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/NDB/backupset/2010_08_05/o1_mf_nnndf_TAG20100805T021153_65nokdyo_.bkp tag=TAG20100805T021153 comment=NONE
    channel ORA_DISK_2: backup set complete, elapsed time: 00:06:56
    Finished backup at 05-AUG-10
    Starting backup at 05-AUG-10
    current log archived
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=27 RECID=25 STAMP=726200330
    channel ORA_DISK_1: starting piece 1 at 05-AUG-10
    channel ORA_DISK_1: finished piece 1 at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_19lkhs0b_1_1_41 tag=TAG20100805T021851 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_27_65noyb7m_.arc RECID=25 STAMP=726200330
    Finished backup at 05-AUG-10
    Starting Control File and SPFILE Autobackup at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/db11g_c-1074407344-20100805-01 comment=NONE
    Finished Control File and SPFILE Autobackup at 05-AUG-10output for updated command:
    RMAN> RUN
    2> {
    3>  allocate channel channel1 device type disk format '/export/home/nfs_bak/lims/backup/ndb/backup_%d_DB_%D%M%Y_%U_%s';
    4>  backup database plus archivelog delete all input;
    5> release channel channel1;
    6> }
    7> resync catalog;
    8> report schema;
    9> list backup;
    10> crosscheck backup;
    11> crosscheck backupset;
    12> delete noprompt expired backup;
    13> delete noprompt obsolete;
    14> crosscheck archivelog all;
    15> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
    16>
    starting full resync of recovery catalog
    full resync complete
    allocated channel: channel1
    channel channel1: SID=98 device type=DISK
    Starting backup at 05-AUG-10
    current log archived
    channel channel1: starting archived log backup set
    channel channel1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=20 RECID=18 STAMP=726148869
    input archived log thread=1 sequence=21 RECID=19 STAMP=726175480
    input archived log thread=1 sequence=22 RECID=20 STAMP=726185922
    input archived log thread=1 sequence=23 RECID=21 STAMP=726195156
    input archived log thread=1 sequence=24 RECID=22 STAMP=726197409
    channel channel1: starting piece 1 at 05-AUG-10
    channel channel1: finished piece 1 at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_12lkhp52_1_1_34 tag=TAG20100805T013010 comment=NONE
    channel channel1: backup set complete, elapsed time: 00:00:07
    channel channel1: deleting archived log(s)
    archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_04/o1_mf_1_20_65m3p0rz_.arc RECID=18 STAMP=726148869
    archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_04/o1_mf_1_21_65mxonbz_.arc RECID=19 STAMP=726175480
    archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_04/o1_mf_1_22_65n7vtog_.arc RECID=20 STAMP=726185922
    archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_23_65njwhld_.arc RECID=21 STAMP=726195156
    archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_24_65nm31ko_.arc RECID=22 STAMP=726197409
    Finished backup at 05-AUG-10
    Starting backup at 05-AUG-10
    channel channel1: starting full datafile backup set
    channel channel1: specifying datafile(s) in backup set
    input datafile file number=00005 name=+DATA/lims/ndb/datafile/ndb_cellmap_tbs_01.dbf
    input datafile file number=00001 name=+DATA/lims/ndb/system01.dbf
    input datafile file number=00002 name=+DATA/lims/ndb/sysaux01.dbf
    input datafile file number=00007 name=+DATA/lims/ndb/datafile/ndb_fingerprint_tbs_01.dbf
    input datafile file number=00006 name=+DATA/lims/ndb/datafile/ndb_cellmap_idx_tbs_01.dbf
    input datafile file number=00008 name=+DATA/lims/ndb/datafile/ndb_fingerprint_tbs_idx_01.dbf
    input datafile file number=00009 name=+DATA/lims/ndb/datafile/ndb_sys_tbs_01.dbf
    input datafile file number=00003 name=+DATA/lims/ndb/undotbs01.dbf
    input datafile file number=00010 name=+DATA/lims/ndb/datafile/ndb_sys_idx_tbs_01.dbf
    input datafile file number=00004 name=+DATA/lims/ndb/users01.dbf
    channel channel1: starting piece 1 at 05-AUG-10
    channel channel1: finished piece 1 at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_13lkhp5a_1_1_35 tag=TAG20100805T013018 comment=NONE
    channel channel1: backup set complete, elapsed time: 00:06:55
    Finished backup at 05-AUG-10
    Starting backup at 05-AUG-10
    current log archived
    channel channel1: starting archived log backup set
    channel channel1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=25 RECID=23 STAMP=726197834
    channel channel1: starting piece 1 at 05-AUG-10
    channel channel1: finished piece 1 at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_14lkhpia_1_1_36 tag=TAG20100805T013714 comment=NONE
    channel channel1: backup set complete, elapsed time: 00:00:01
    channel channel1: deleting archived log(s)
    archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_25_65nmj9y9_.arc RECID=23 STAMP=726197834
    Finished backup at 05-AUG-10
    Starting Control File and SPFILE Autobackup at 05-AUG-10
    piece handle=/export/home/nfs_bak/lims/backup/ndb/db11g_c-1074407344-20100805-00 comment=NONE
    Finished Control File and SPFILE Autobackup at 05-AUG-10
    released channel: channel1

Maybe you are looking for

  • Mavericks / Canon Canoscan 8800F:  Hardware Buttons not working.

    I've just upgraded to Mavericks.  I've also updated the driver (to 13.9.2a) and installed the latest MP Navigator 1.0 (1.0.7).  Is there something else I need to do? I'm having two problems since the upgrade: - The hardware buttons on the scanner cov

  • IPhone 4s bluetooth wont work with car

    My Blackberry bold and iPhone 4 were absolutely fine with 3 different cars. I have just upgraded to the iPhone 4s and now the phone connects to the bluetooth but doesnt work properly. It rings and the screen shows that there is a call there, it even

  • Camera issue with 520

    My camera swap icon is not working. When i tap on the camera icon on the screen to change from video mode to picture mode, it starts recording and when i click again it stops instead of changing the mode. I own a 520. Camera works fine using the lens

  • W701 esata port suffering from poor design/qua​lity from manufactur​e?

    After having my W701 for 5 weeks, with 2 replacment of MB due to different problems, last time bios and port problems, I got i back from Lenovo today. I had reported it with a no functional/very poor functional esata port. What happens is that: With

  • How can i get sample CSV files for Demo BI Content

    Hello Experts. Documentation say that there is sample CSV files for modules that come with delivered BI content. I am planning to work with the demo content which i have already installed. I then need to populate the objects with the relevant demo da