Rman backup on standby - not in catalog

I am trying to backup a standby database using a recover catalog. I connect with target as the standby database, the backup completes and finishes with:
warning - controlfile is not current, controlfile autobackup skipped
Recovery Manager complete.
Which is the way it is supposed to be (I think). The prblem is that this backup does not exist in the catalog so I can't use it. Can anyone tell me how to get these backups in the catalog, or why they are not in the catalog so that the backup might actually be usefull? Thanks

id di another backup and resync'd the catalog as part of the script and it worked.

Similar Messages

  • Rman backup with  standby database

    Hi All,
    I am looking for some suggestions for rman backup with standby  database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at  sql 'alter system archive log current' in rman  with standby as target. which gives following errors  with or without noswitch clause
    RMAN> sql 'alter system archive log current noswitch';
    sql statement: alter system archive log current noswitch
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
    ORA-01109: database not open
    Recovery Manager: Release 11.2.0.1.0
    Oracle databaes  Release 11.2.0.1.0 64 bit
    OS:RHEL 6 x86-64 bit
    Secondly, do I need to cancel manged recovery while taking rman backups on standby.
    I scanned thru MOS but could find solutions for rman with active DG.
    Thanks in advance

    726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
    Hi All,
    I am looking for some suggestions for rman backup with standby  database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at  sql 'alter system archive log current' in rman  with standby as target. which gives following errors  with or without noswitch clause
    RMAN> sql 'alter system archive log current noswitch';
    sql statement: alter system archive log current noswitch
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
    ORA-01109: database not open
    Recovery Manager: Release 11.2.0.1.0
    Oracle databaes  Release 11.2.0.1.0 64 bit
    OS:RHEL 6 x86-64 bit
    Secondly, do I need to cancel manged recovery while taking rman backups on standby.
    I scanned thru MOS but could find solutions for rman with active DG.
    Thanks in advance
    "I scanned thru MOS but could find solutions for rman with active DG."
    Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1)

  • RMAN backup of STANDBY database

    I have just created a STANDBY database using Oracle 8.1.7 which I am trying to backup using RMAN. This would then not impact on the PRODUCTION database, yet still give a valid backup. The problem I am having is that contrary to what I have been told and read about the `duplicate for standby` command, it does not reset the DB_ID. This has the effect that you canot register your new STANDBY database in the RMAN catalog as it sees it as the PRODUCTION instance that was used to create it. I have found several `solutions` on Metalink, which all require the use of a `resetlogs` command, so invalidating the STANDBY database. Does anyone know of a way that I can bypass this problem and carry out valid backups of the STANDBY database ?
    TIA
    Mark Tindall
    Email: [email protected]

    Mark,
    The STANDBY database must have the same DBID as the production or you could not use the backups taken at a standby
    database to recover the production database.
    To backup the standby database with RMAN, you must use a recovery catalog. Take at look at http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96566/rcmbackp.htm#445993
    for information on how to backup the standby with RMAN.
    Tammy

  • RMAN Backup of Standby by Grid Control

    Hello Friends,
    i am trying to take backup of standby..by rman..but when i am trying to create customize backup in grid control, it is saying that you should connect to the recovery catalog. Now i set the recovery catalog in primary database, but still it is giving same message. What should i do..?
    Vivek

    I am using seperate instance for catalog on separate machine...These are the steps ---
    1) Register primary database to the recovery catalog (REP its on other node)
    2) Now i assume that the standby will also register to the catalog, because my SID and DBID is same for primary and standby.
    3) But when i go to the grid control, and try to schedule the backup..then customize backup...i got error message--- Error - Backing up a physical standby database requires a recovery catalog.
    Please suggest solution..?

  • RMAN backup job status not showing in OEM

    Hi, I have created an RMAN backup job and scheduled it through OEM to run daily. The first run of this backup job completed today - however I do not see any entry for the job in OEM through SERVER - ORACLE SCHEDULER - JOBS
    A lot of scheduler jobs are listed but not my backup job.
    Has anyone else experienced this ?

    Duplicate post. Please do not add to this thread.

  • 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 backup jobs does not start automatically

    I have the next question:
    When I run such script in RMan:
    RUN
    ALLOCATE CHANNEL c1 DEVICE TYPE sbt;
    SEND 'OB_MEDIA_FAMILY mf_rman';
    BACKUP archivelog all;
    It creates job on OSB server:
    ob> lsj
    Job ID Sched time Contents State
    oracle10/6 none database cbs3 (dbid=2397799862) processed; Oracle job(s) scheduled
    oracle10/6.1 none archivelog backup retryable at 2010/10/01.23:05 ("lsjob --log oracle10/6.1" for details)
    But it doesn't statrt immediatelly at the same time, so I has to run the job manually:
    ob> runj -n oracle10/6.1 -d Drive2
    ob> lsj
    Job ID Sched time Contents State
    oracle10/6 none database cbs3 (dbid=2397799862) processed; Oracle job(s) scheduled
    oracle10/6.1 none archivelog backup running since 2010/10/01.17:10
    How to make Rman start backup job at once?
    Edited by: OraSun on 01.10.2010 4:44

    If you have created a database storage selector, you don't need to include media manager parameters in the RMAN script. You would include media manager parameters in script, if you want to override the database storage selector settings. For example, in the database storage selector you have indicated that the media family is mf_rman...OSB will automatically use that media family based on database storage selector settings. Per the RMAN script, you want this backup operation to use mf_rman...since database storage selector already defines this, you don't need to include it in the RMAN script. If your database storage selector defines use of mf_rman media family but you want a particular backup to use "foo" media family, then you would include that parameter in your script so it would override the database storage selector.

  • Backup Physical Standby (Dataguard) using RMAN : Issues

    Hello All,
    I am running a RMAN backup on standby server using the command below. The RMAN backup is actually connecting to the primary database on another server, I found this very confusing and to reassure, i shutdown the primary database and ran the backup again. It fails with not able to conenct to target database. Can you please explain?
    run {
    allocate channel t1 type disk format '/backup/oracle/PRODCDW/RMAN/DBFILES_%d_t%t_s%s_p%p';
    allocate channel t2 type disk format '/backup/oracle/PRODCDW/RMAN/DBFILES_%d_t%t_s%s_p%p';
    recover copy of database with tag 'STDBY_PRODCDW';
    backup as compressed backupset format '/backup/oracle/PRODCDW/RMAN/DBFILES_%d_t%t_s%s_p%p' tag 'STDBY_PRODCDW' incremental level 1 for recover of copy with tag 'STDBY_PRODCDW' database plus archivelog delete input;
    }

    I am not doing the image copy anymore, I am taking the RMAN incremental backups for the database. I am not getting any errors now but, Here is what I want to achieve:
    I am running the RMAN backups on the standby database. I want to :
    1) Delete archivelogs on my PRIMARY server only when these logs are successfully TRANSFERED/APPLIED to all my standby databases?
    2) Delete archivelogs on my STANDBY server only when these logs are sucessfully APPLIED to the database?
    Regards

  • Creating a standbay database from an rman backup

    hi,
    I have a situation that a standby database has a large gap in archive log files, the primary server does not now have those files. I understand that you can create a standby from an rman backup of the primary but all reading I have done shows thatn you have to have a recovery catalog to carry this out. The system I am on does not have such a catalog so is there any other way to do this?
    regards
    Alan

    Requirement 'You must have a recovery catalog in a standby requirement' is a little bit misleading. In fact you can do what you want : creating a standby from RMAN backups without having a recovery catalog. 'Duplicate target database for standby' does not require a connection to a recovery catalog.
    You need mandatorily a recovery catalog, when you plan to take backups from the standby later on in order to free the primary from this task. The reason for that is it's not possible to transfer backup records from the standby controlfiles to the primary ones directly. After a backup on the standby you resync the catalog with the standby controlfile. Then you connect to the catalog and the primary,resync again and have actual backup informations in the primary controlfiles. When there's a media recovery problem, you easily can restore/recover the primary.
    Werner

  • RMAN backup files are still exist since long time, how to delete?

    Dear sir;
    I'm using the below script to do daily backup, however there are many rman backup files are still exist and consumes HD size, how could I delete these files in daily bases? some files dated in FEB, MAR, APR,
    ============Daily RMAN script=========
    rman target /<<!
    backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
    backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
    backup current controlfile format '/u15/rman/control_%U.rman';
    delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
    delete noprompt obsolete;
    ================================END
    Thanks and best regards
    Ali

    Hi;
    Our backup policy should have 7 days; however we have here some files from JAN, FEB,MAR, APR /2012 WHICH ARE BEYOND THE RETENTION DATE and these files should be deleted by executing " delete noprompt obsolete; ".
    All files are exist in /u15/rman/
    -rw-r----- 1 oracle oinstall 1151763968 Jan 21 01:36 arc_backup_7kn19h4a_1_1.rman
    -rw-r----- 1 oracle oinstall 1136882176 Jan 21 01:36 arc_backup_7ln19h4q_1_1.rman
    -rw-r----- 1 oracle oinstall 1135984640 Jan 21 01:36 arc_backup_7mn19h5a_1_1.rman
    -rw-r----- 1 oracle oinstall 1126627328 Jan 21 01:37 arc_backup_7nn19h5q_1_1.rman
    -rw-r----- 1 oracle oinstall 880606720 Mar 12 02:53 arc_backup_7nn5ldhp_1_1.rman
    -rw-r----- 1 oracle oinstall 1093043712 Jan 21 01:37 arc_backup_7on19h6a_1_1.rman
    -rw-r----- 1 oracle oinstall 9797632 Dec 15 01:04 control_04mu7tcp_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 3 02:55 control_4cn4tm9k_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 4 02:53 control_4on50ahm_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 5 02:55 control_56n52v1j_1_1.rman
    -rw-r----- 1 oracle oinstall 16252928 Jan 23 01:40 control_8tn1eq3t_1_1.rman
    -rw-r----- 1 oracle oinstall 16252928 Jan 24 01:40 control_9cn1heg0_1_1.rman
    -rw-r----- 1 oracle oinstall 202940416 Dec 15 01:04 full_backup_01mu7t50_1_1.rman
    -rw-r----- 1 oracle oinstall 1097728 Dec 15 01:04 full_backup_02mu7tcc_1_1.rman
    -rw-r----- 1 oracle oinstall 201285632 Dec 14 01:04 full_backup_0nmu58ou_1_1.rman
    -rw-r----- 1 oracle oinstall 5957304320 Feb 29 02:46 full_backup_2ln4g9l1_1_1.rman
    -rw-r----- 1 oracle oinstall 4128768 Feb 29 02:47 full_backup_2mn4gft8_1_1.rman
    -rw-r----- 1 oracle oinstall 6027075584 Mar 1 02:49 full_backup_32n4o6ov_1_1.rman
    -rw-r----- 1 oracle oinstall 4128768 Mar 1 02:49 full_backup_33n4od66_1_1.rman
    -rw-r----- 1 oracle oinstall 6187171840 Mar 2 02:51 full_backup_3gn4qr50_1_1.rman
    -rw-r----- 1 oracle oinstall 4145152 Mar 2 02:51 full_backup_3hn4r1kn_1_1.rman
    -rw-r----- 1 oracle oinstall 6115786752 Mar 3 02:51 full_backup_40n4tfgu_1_1.rman
    above is a short list of contents.
    to do our daily backup we perform the following script (in daily)
    ==================
    backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
    backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
    backup current controlfile format '/u15/rman/control_%U.rman';
    delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
    delete noprompt obsolete;
    ==================
    Thanks and best regards
    Ali

  • RMAN backup for TDPO without catalog not working

    Hi all,
    We have configured IBM tivoli storage for Oracle backup(using RMAN).We did not configure Recovery catalog. Will tivoli support to keep the backups in tape without a catalog?
    OS : IBM AIX 5.3
    Database Version : 10.2.0.4
    Tivoli client version : 5.5.0.0
    Tivoli server version : 5.5.4.0
    oracle API : 5.4.1.0
    Regards.

    Hi Rajesh,
    Thanks for the reply.The script contains the controlfile autobackup option.I have deleted the SBT tape's old backups using RMAN. But the volume space not reduced. This is the script we are using for backup.
    run
    configure controlfile autobackup on;
    crosscheck archivelog all;
    allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/cli
    ent/oracle/bin64/tdpo.opt)';
    #allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/cl
    ient/oracle/bin64/tdpo.opt)';
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    backup incremental level 1
    filesperset 25
    format 'full_%d.%t.bkp'
    database;
    backup
    format 'arch_%d.%t.bkp'
    archivelog all;
    release channel t1;
    regards.

  • Standby database from RMAN backup

    I have been assigned to create a standby database from our RMAN backups in a different machine, as this is my first attempt at recovering, I am struggling a bit. I would appreciate if someone can throw any light on what dumb mistakeI am doing here. I ahve absolutely no control over the back up script which is done by my vendor, but can do anything in the reocvery portion. I did try going through the documentaiton and other help available for the last 2 days.
    Database : Oracle 10G R2
    OS : Windows Server 2003
    My backup script is
    configure channel device type disk format 'J:\RMAN\RMAN_df_%U' maxpiecesize 2048M;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup database;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup current controlfile for standby FORMAT='J:\RMAN\RMAN_sc_%U';
    For recovery of a standby database,
    I have copied the the back up pieces and the archive logs to the standby server where I have just created an instance with the same name as production db.
    set ORACLE_SID=NGINPROD
    set dbid 820336652
    STARTUP NOMOUNT
    RESTORE STANDBY CONTROLFILE FROM 'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    CATALOG BACKUPPIECE 'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_5_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_6_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_7_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2TMIUJLN_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    RESTORE DATABASE;
    Till this step I do not encounter any issues, but when i try to recover the database I am hit with the below error.
    RMAN> recover database;
    Starting recover at 16-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=253340
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/16/2011 09:31:57
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 253340 lowscn 4696173517
    ------------------------------------------------------------------------------------------------------------------------------------------------

    Here's the standard dcoumentation on the procedure :
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377
    Appendix "F Creating a Standby Database with Recovery Manager" of the "Oracle® Data Guard Concepts and Administration" guide.
    I don't see ArchiveLog backups being done by the vendor's script. How do you backup the ArchiveLogs ?
    In your post you state that you have copied the ArchiveLogs. Are they copied to the same log_archive_dest location ? RMAN needs to be "aware" of them. You can use the "CATALOG" command in RMAN to register them into the controlfile.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
    A Standby Database uses a Standby Controlfile which is created from the Primary (with the "ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'locaion';" command) and then copied over to the Standby server.
    Hemant K Chitale

  • RMAN backup on the physical standby database.

    Hello,
    11.2.0.3 EE database. Is it a requirement to open the database in read only mode in order to take a hot backup?
    SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    SQL> ALTER DATABASE OPEN READ ONLY;
    I've initiated a rman backup without opening the db in read only and the following output is so far:
    RMAN> backup format '/dbstor2/LTS/LTS_rman/%d_set%s_piece%p_%T_%U' check logical database plus archivelog;
    Starting backup at 15-OCT-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=603 device type=DISK
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    I plan on taking this backup and using it to refresh our Dev and QA dbs. Do you see any issues with taking a backup without opening the db in ready only mode?
    -SteveV

    No we are not using Active Dataguard. An issue I am investigating is why can't I perform an archivelog backup from the standby?
    RMAN> backup archivelog all format '/dbstor2/LTS/LTS_rman/arc.rman.bak';
    Starting backup at 15-OCT-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=603 device type=DISK
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 15-OCT-12

  • Rman backup on physical standby database without cancelling MRP

    Hi all,
    Could anyone share, is this possible to take RMAN backup on physical standby database without cancelling MRP process.
    regarrds,

    Hi,
    On Standby Side:
    SQL> alter database mount;
    Database altered.
    SQL> alter database recover managed standby database using current logfile disconnect from session;
    Database altered.
    SQL> select max(Sequence#)  from v$archived_log;
    MAX(SEQUENCE#)
            405
    SQL> select max(Sequence#)  from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            404
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:31:43 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=32 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=390 RECID=391 STAMP=815416638
    input archived log thread=1 sequence=391 RECID=392 STAMP=815421952
    input archived log thread=1 sequence=392 RECID=393 STAMP=815422343
    input archived log thread=1 sequence=393 RECID=394 STAMP=815422434
    input archived log thread=1 sequence=394 RECID=395 STAMP=815422570
    input archived log thread=1 sequence=395 RECID=396 STAMP=815476598
    input archived log thread=1 sequence=396 RECID=397 STAMP=815476615
    input archived log thread=1 sequence=397 RECID=398 STAMP=815476645
    input archived log thread=1 sequence=398 RECID=399 STAMP=815477471
    input archived log thread=1 sequence=399 RECID=400 STAMP=815477475
    input archived log thread=1 sequence=400 RECID=401 STAMP=815477628
    input archived log thread=1 sequence=401 RECID=403 STAMP=815584146
    input archived log thread=1 sequence=402 RECID=402 STAMP=815584137
    input archived log thread=1 sequence=403 RECID=405 STAMP=816017446
    *input archived log thread=1 sequence=404 RECID=404 STAMP=816017444*
    *input archived log thread=1 sequence=405 RECID=406 STAMP=816017455*
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T153202_8spm937d_.bkp tag=TAG20130521T153202 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_390_8s48hfrp_.arc RECID=391 STAMP=815416638
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_391_8s4fohwb_.arc RECID=392 STAMP=815421952
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_392_8s4g1q0v_.arc RECID=393 STAMP=815422343
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_393_8s4g4l8z_.arc RECID=394 STAMP=815422434
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_394_8s4g8t9h_.arc RECID=395 STAMP=815422570
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_395_8s631622_.arc RECID=396 STAMP=815476598
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_396_8s631qjj_.arc RECID=397 STAMP=815476615
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_397_8s632od8_.arc RECID=398 STAMP=815476645
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_398_8s63whqc_.arc RECID=399 STAMP=815477471
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_399_8s63wly4_.arc RECID=400 STAMP=815477475
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_400_8s641d8j_.arc RECID=401 STAMP=815477628
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_401_8s9d21jk_.arc RECID=403 STAMP=815584146
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_402_8s9d1skv_.arc RECID=402 STAMP=815584137
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_403_8spm6p4h_.arc RECID=405 STAMP=816017446
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_404_8spm6mqj_.arc RECID=404 STAMP=816017444
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc thread=1 sequence=405
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    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=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T153213_8spm9fnc_.bkp tag=TAG20130521T153213 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T153213_8spmfqxf_.bkp tag=TAG20130521T153213 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> exit
    Recovery Manager complete.
    [oracle@oel62-x64 Desktop]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.3.0 Production on Tue May 21 15:34:42 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, OLAP, Data Mining and Real Application Testing options
    SQL> select max(Sequence#) from  v$archived_log;
    MAX(SEQUENCE#)
            405
    SQL> select max(Sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            404
    SQL> There have no problem, backup database when MRP is running. But if you want delete, then you are getting RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
    And will not delete this archived log, because it is needed for standby or upstream capture process.
    Updated
    When MRP stoped
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:46:07 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=24 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=405 RECID=406 STAMP=816017455
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154617_8spn3s9w_.bkp tag=TAG20130521T154617 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=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc RECID=406 STAMP=816017455
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    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=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154618_8spn3v4f_.bkp tag=TAG20130521T154618 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154618_8spn6779_.bkp tag=TAG20130521T154618 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> Apply process is stopped and new redo received from primary.
    SQL> select max(Sequence#)  from v$archived_log;
    MAX(SEQUENCE#)
            407
    SQL> select max(Sequence#)  from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            405
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:49:28 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=32 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=406 RECID=407 STAMP=816018527
    input archived log thread=1 sequence=407 RECID=408 STAMP=816018530
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154937_8spnb1y3_.bkp tag=TAG20130521T154937 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_406_8spn8hkn_.arc thread=1 sequence=406
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_407_8spn8l69_.arc thread=1 sequence=407
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    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=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154939_8spnb3f5_.bkp tag=TAG20130521T154939 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154939_8spndhly_.bkp tag=TAG20130521T154939 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> I think, codes is understandable.
    Regard
    Mahir M. Quluzade
    Edited by: Mahir M. Quluzade on May 21, 2013 3:36 PM

  • Catalog addiional rman backup files

    Im trying to catalog addiional rman backup files, and getting this error:
    RMAN-07518: Reason: Foreign database file DBID: 2319619701 Database Name: SASP
    Previous activities: Database dictionary was recreated due to charset problems while exporting the database...
    Enterprise Manager was reconfigure with create repos due to same problems....
    Thanks in advance...
    Message was edited by:
    elvyscruz

    Previous activities: Database dictionary was
    recreated due to charset problems while exporting the
    database...
    Enterprise Manager was reconfigure with create repos
    due to same problems....I have not seen the full error messages that follows this one (post it if possible). However, if you recreated the database, then your database will now have a new DBID after it was recreated. You can see the current DBID of the database to see if it matches the one above.
    If it is a standby database and it is logical standby, then it will also have a different DBID.
    select dbid, name, database_role from v$database;

Maybe you are looking for

  • 9iAS installation problem on Solaris 5.8

    I am attempting to install Oracle Application Server 9i release 2 on a Solaris 5.8 server. During the installation, I keep getting the following error at the beginning of the install process: "Error in Writing to File" the file is jlib/oemit-9_0_2.ja

  • Error occured while trying to restore this iphone (-50)

    I was trying to update my iphone 3G software to 4.2.1 (I was running 3. something before then) and I got a message that said "an error occured while trying to restore this iphone (-50)," and my phone has been wiped clean. This happened after updating

  • Perl module not working/installed properly

    I have a perl script that worked fine on Ubuntu.  I've now replaced Ubuntu with Arch and installed the perl modules I need to run this script and one of them doesn't seem to be working properly, I think I had a hiccup during installation of this part

  • Slideshow not sizing portrait images correctly

    Hi I've seen a lot postings about portrait images not showing correctly but none of them helped me with my problem. I'm using DVD Photo Slideshow Professional for Mac to make my MP4  slideshow and I was quite pleased with the results until I loaded i

  • Lots of problems with os X mountain Lion...

    programs don't react ( safari, mail, itunes, iphoto...) problems shutting down my iMac , have to restart several times a day