RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

Hi Oracle Community,

I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.

During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?

Concerning

J

Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:

RMAN> backup database plus archivelog;
RMAN> delete noprompt archivelog all completed before 'sysdate-1';

Tags: Database

Similar Questions

  • RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    I get RMAN-08120: WARNING: journal archived not deleted, not yet applied watch on primaries
    but when I run under query, I get the same result of primary and backup

    SQL > select max(sequence#) from v$ archived_log;

    MAX(SEQUENCE#)
    --------------
    44051

    SQL >


    Eve is a log switch behind only!

    Hello;

    If RMAN tries to remove an archive which is not yet applied in standby log, you see the RMAN-08120

    It's a good thing. As long as you don't have any archives for days on standby, you probably don't have a problem.

    What are your RMAN settings for the database of the day before?

    MetaLink Note: 361182.1 can help too. Or Note 1079953.1

    Your main, make sure that:

    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

    Please consider closing some of your old issues to clean up the forum.

    Best regards

    mseberg

  • RMAN asking newspapers to archive old (deleted) after a backup full database

    Hello guys,.

    Am a little lost here. Is there something I'm missing. Would be great if you guys can report to help me learn.

    We are 11 GR 2. I tried to restore a database to a new machine. I have a RMAN backup with the archive logs.

    The current sequence number is 272.html but when I 'Recover databse' RMAN is asking me for sequence 3. 3 of the sequence, I guess has been deleted manually and we do not have a backup of it. I ran cross-check to clear in the RMAN Repository. He said that validation succeeded for all available logs.

    The sequence 3-119 number are missing (accidentally deleted). We have backups only from sequence number 134 - 272.When I throw summary restoring a complete database of backup it complains about missing archives. Did not really understand what is happening. Would be great if someone can help out me.

    Thank you

    It seems that one or several or all the data in the backup files are older than the SEQUENCE # 3.  Make a BACKUP of the LIST and view details of control point for each of the data files.

    Another alternative is that one or several areas of storage is / was in BACKUP STARTED at the RMAN backup mode.

    Hemant K Collette

  • RMAN backup with log archiving

    Hello

    I'm using oracle 11G (11.2.0.1). My open database and I'm using the RMAN command to perform a backup hot below. My doubt is the reason we have the backup of the database to archivelog more? What is the use of the archivelog backup because the archivelogs will keep generation while the database is open.

    RMAN > backup the database archivelog;

    Kind regards

    007

    I agree with Oviwan. You must archivelogs in the recovery database to the last second. If you have the base of mission critical data, then you must also add redo log members on different disks.

    And I also suggest to run command before backup below.

    RMAN > sql 'ALTER SYSTEM SWITCH LOGFILE;

    You can remove the logs to archive that are saved.

    RMAN > delete any backup archivelog entry;

    Also, I suggest to backup database and Archives journal separately.

  • Logs archiving not required for recovery

    Hello

    I have a basic test of 200 GB with backup running every night. He made a full backup with a cleaning of the archiving log

    The backup has not happened for the past 2 weeks and the archivelog filled the disk free space available.

    Now, if I take a backup completes, or a backup of level 0 in the database right now, can I go ahead and remove the logs of archiving that were created before backups?

    Unfortunately, archive logs are too big to make a backup of it to the backup location

    According to my understanding of the current backup should have all changes recorded in the archivelogs created before she and I should be able to remove the archive logs

    Thank you

    Hello;

    I remove all but the last two days and then do an overlap archivelog all;

    And then do the backup.

    And then ask the boss to drive more!

    Best regards

    mseberg

  • Data Guard archive political deletion log

    Hi all

    I configured the data guard with 2 bases Eve in oracle 11g.

    I want to use rman to delete archives on all servers.

    I have configured no FRA, no recovery catalog.

    My question is:

    If I delete waiting til sequence # 1627 and on primary sequence til = # = 1620 or vice versa this would cause problems for Data Guard.

    I say delete until the different sequences # on primary and standby cause problems for synchronization?

    Thank you

    So if I understand delete archivelog to sysdate - or delete archivelog all completed before sysdate n is not the archivelog deletion policy you put on RMAN?

    She depends on it. The note was made at the base of the MOS document how ensure that RMAN is NOT delete archived logs that have not yet shipped to standby mode (Doc ID 394261.1)

    Delete archivelog to sysdate - depends on all of the deletion policy. If the deletion policy is set on "applied pending all", then it does not delete the archives, if they are not applied on the day before. If the deletion policy is set to none, then it does not check if the archive is applied on the eve and deletes them directly.

    Last Archive generated on primary:

    SYS@oraprim > select max(sequence#) from v$ archived_log;

    MAX(SEQUENCE#)

    --------------

    114

    Last check-in applied in mode ensures:

    SYS@orastb > select max(sequence#) from v$ archived_log in case of application = 'YES ';

    MAX(SEQUENCE#)

    --------------

    109

    Delete policy set to NONE on primary:

    RMAN > show archivelog deletion policy;

    using the control file of the target instead of recovery catalog database

    RMAN settings for database with db_unique_name ORAPRIM are:

    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;

    RMAN > delete archivelog until 'sysdate;

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 60 type of device = DISK

    List copies of newspapers archived to database with db_unique_name ORAPRIM

    =====================================================================

    Thrd Seq S key low time

    ------- ---- ------- - ---------

    110-1-214 A JANUARY 13, 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727

    216-1-111 A JANUARY 13, 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731

    217-1-112 A JANUARY 13, 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731

    113. OF 1 219 A 13 JANUARY 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733

    222 1 114 A JANUARY 13, 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737

    You sure you want to delete the items above (enter YES or NO)? NO.

    It is the removal of primary archives that have not yet been applied on the eve.

    Delete policy 'APPLIES ON STANDBY ALL' value on the primary:

    RMAN > show archivelog deletion policy;

    RMAN settings for database with db_unique_name ORAPRIM are:

    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

    RMAN > delete archivelog until 'sysdate;

    output channel: ORA_DISK_1

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 60 type of device = DISK

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727 thread = 1 sequence = 110

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731 thread = 1 sequence = 111

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731 thread = 1 sequence = 112

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733 thread = 1 sequence = 113

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737 thread = 1 sequence = 114

    It checks if the archive has been applied on the day before. As the 110 to 114 sequence is not applied in the waiting, the archives are not deleted on the primary.

    Hope that gives you a clear picture of how it works.

    -Jonathan Rolland

  • The front last backup RMAN delete file even if redundancy on 3 days

    Dear Oracle gurus

    My environment
    Node 2 11g R2 Cluster with ASM
    Database 11.2.0.3.0

    I got to know that file below is delete by RMAN even if redundancy on 3 days
    * 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 * is removed

    can you please provide a reason or recommendations to correct the backup configuration

    =========Before Backup========================================
    917M rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
    Rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 669M
    Rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 101M
    64M rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
    116M rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
    Rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 85M
    1003M rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
    689M rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
    87M rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
    Rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013 73M
    110M rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
    Rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013 103M
    115M rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
    88M rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
    1011M rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
    701M rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
    226M rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
    215M rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
    * 230M rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
    * 568M rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
    * 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
    ===========================================================================

    ===================After Backup========================================================
    -rw - r - 1 oracle oinstall 1049755648 12 May 20:05 rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
    -rw - r - 1 oracle oinstall 720715776 12 May 20:05 rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
    -rw - r - 1 oracle oinstall 91013120 13 May 20:05 rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
    -rw - r - 1 oracle oinstall 75726848 13 May 20:05 rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
    -rw - r - 1 oracle oinstall 114327552 14 May 20:05 rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
    -rw - r - 1 oracle oinstall 107782144 14 May 20:05 rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
    -rw - r - 1 oracle oinstall 120307712 15 May 20:05 rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
    -rw - r - 1 oracle oinstall 91226112 15 May 20:05 rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
    -rw - r - 1 oracle oinstall 1058840576 16 May 20:05 rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
    -rw - r - 1 oracle oinstall 733757440 16 May 20:05 rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
    -rw - r - 1 oracle oinstall 236716032 17 May 20:05 rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
    -rw - r - 1 oracle oinstall 224174080 17 May 20:05 rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
    -rw - r - 1 oracle oinstall 594411520 18 May 20:06 rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
    -rw - r - 1 oracle oinstall 240123904 18 May 20:06 rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
    -rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    -rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    -rw - r - 1 oracle oinstall 254590976 19 May 20:06 rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    -rw - r - 1 oracle oinstall 709885952 19 May 20:07 rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    -rw - r - 1 oracle oinstall 19234816 19 May 20:07 rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    ==================================================================================


    Configuration of RMAN
    bash-$3.2 rman target /.

    Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 14:34:26 2013

    Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

    connected to target database: ORCL (DBID = 3171721304)

    RMAN > show all.

    using the control file of the target instead of recovery catalog database
    RMAN settings for database with db_unique_name ORCLDR are:
    CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcldr2.f'; # by default

    RMAN > exit
    =========================================================================================
    RMAN Full Backup Script
    RMAN level 0
    #! / bin/bash
    . /Home/Oracle/.bash_profile
    logloc = 'date' + rman_backup_lvl0_orcldr_ %m %y hour %M %S %d ".log
    Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF
    run
    {
    allocate channels ch1 type disk maxpiecesize = 1024 M;
    allocate channel ch2 type disk maxpiecesize = 1024M;
    database backup incremental level 0 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL0_%D_%M_%Y'
    include current controlfile more archivelog delete all entries
    tag 'datafile_full ';
    }
    delete noprompt obsolete;
    EXIT;
    EXPRESSIONS OF FOLKLORE
    =========================================================================================

    Backup logs
    -bash-3, $ 2 cat rman_backup_lvl0_ORCLdr_190513200501.log

    Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 20:05:01 2013

    Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

    connected to target database: ORCL (DBID = 3171721304)

    RMAN >
    RMAN > 2 > 3 > 4 > 5 > 6 > 7 > 8 >
    using the control file of the target instead of recovery catalog database
    allocated channel: ch1
    channel ch1: SID = instance 1753 = ORCLdr2 = DISK device type

    allocated channel: ch2
    channel ch2: SID = 5 = device type ORCLdr2 = DISK instance


    From backup may 19, 13
    Current archived log
    archived journal of wire 1 to jump with sequence 84; already saved
    skip the journal archived thread 2 with sequence 79; already saved
    channel ch1: Startup archived log backup set
    channel ch1: specifying the newspapers archived in the backup set
    archived journal entry thread = 2 sequence = 81 RECID = 388 STAMP = 815810424
    archived journal entry thread = 1 sequence = 85 RECID = 385 STAMP = 815793508
    archived journal entry thread = 1 sequence = 86 RECID = 389 STAMP = 815810426
    archived journal entry thread = 1 sequence = 87 RECID = 391 STAMP = 815828071
    channel ch1: from room 1 to May 19, 13
    channel ch2: Startup archived log backup set
    channel ch2: specifying the newspapers archived in the backup set
    archived journal thread = sequence 2 = 82 entry RECID = 396 STAMP = 815861105
    archived journal entry thread = 1 sequence = 88 RECID = 393 = 815846442 STAMP
    archived journal entry thread = 1 sequence = 89 RECID = 397 STAMP = 815861108
    channel ch2: from room 1 to May 19, 13
    channel ch1: finished piece 1 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
    channel ch1: from part 2 to May 19, 13
    channel ch2: finished piece 1 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
    channel ch2: from part 2 to May 19, 13
    channel ch1: finished part 2 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
    channel ch1: from 3 to 19 May 13 piece
    channel ch2: finished part 2 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
    channel ch2: complete set of backups, time: 00:01:10
    channel ch2: archived deletion or newspapers
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_82_814540431.arc RECID archived log file = 396 STAMP = 815861105
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_88_814540431.arc RECID archived log file = 393 = 815846442 STAMP
    RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
    Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_89_814540431.arc thread = 1 sequence = 89
    channel ch2: archived deletion or newspapers
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_84_814540431.arc RECID archived log file = 383 STAMP = 815774802
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_79_814540431.arc RECID archived log file = 378 STAMP = 815774705
    channel ch1: finished part 3 to 19 May 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_3_1 tag = DATAFILE_FULL comment = NONE
    channel ch1: complete set of backups, time: 00:01:25
    channel ch1: archived deletion or newspapers
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_81_814540431.arc RECID archived log file = 388 STAMP = 815810424
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_85_814540431.arc RECID archived log file = 385 STAMP = 815793508
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_86_814540431.arc RECID archived log file = 389 STAMP = 815810426
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_87_814540431.arc RECID archived log file = 391 STAMP = 815828071
    Backup finished on 19 May 13

    From backup may 19, 13
    channel ch1: start the incremental level 0 datafile backup set
    channel ch1: specification-datafile in the backup set (s)
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_5.dbf 00009
    Enter a number of file datafile = 00001 name=+ORASYS/ORCLdr/datafile/system.257.814500985
    Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/undotbs1.259.814500991 00003
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app2.dbf 00006
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app.dbf 00008
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users01.dbf 00011
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users03.dbf 00013
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users05.dbf 00015
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users07.dbf 00017
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_5.dbf 00019
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_7.dbf 00021
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_9.dbf 00023
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_11.dbf 00025
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdrmaxdat.dbf 00027
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradcdr.dbf 00029
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_8.dbf 00031
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_10.dbf 00033
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_5.dbf 00037
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_7.dbf 00039
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_9.dbf 00041
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_11.dbf 00043
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdrmaxdat.dbf 00045
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradinterimcdr.dbf 00047
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/reports.dbf 00048
    channel ch1: from room 1 to May 19, 13
    channel ch2: start the incremental level 0 datafile backup set
    channel ch2: specification-datafile in the backup set (s)
    Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/sysaux.256.814500977 00002
    Enter a number of file datafile = 00005 name=+ORASYS/ORCLdr/datafile/undotbs2.258.814500987
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/namestatistics.dbf 00035
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/gidstatistics.dbf 00036
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/stat01.dbf 00007
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_6.dbf 00010
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users02.dbf 00012
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users04.dbf 00014
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users06.dbf 00016
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users08.dbf 00018
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_6.dbf 00020
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_8.dbf 00022
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_10.dbf 00024
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_12.dbf 00026
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/unameradcdr.dbf 00028
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_7.dbf 00030
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_9.dbf 00032
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statisticsmaxdate.dbf 00034
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radintdr2013_6.dbf 00038
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radiusintcdr2013_8.dbf 00040
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radinterimcdr2013_10.dbf 00042
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/tb2013_12.dbf 00044
    Enter a file datafile 00046 name=+ORADATA1/ORCLdr/datafile/tberimcdr.dbf = number
    Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/users.260.814500995 00004
    channel ch2: from room 1 to May 19, 13
    channel ch1: finished piece 1 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch1: from part 2 to May 19, 13
    channel ch2: finished piece 1 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch2: from part 2 to May 19, 13
    channel ch1: finished part 2 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch1: complete set of backups, time: 00:00:22
    channel ch1: start the incremental level 0 datafile backup set
    channel ch1: specification-datafile in the backup set (s)
    channel ch2: finished part 2 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch2: complete set of backups, time: 00:00:22
    including the current control in the backup set file
    channel ch1: from room 1 to May 19, 13
    channel ch1: finished piece 1 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch1: complete set of backups, time: 00:00:01
    Backup finished on 19 May 13

    From backup may 19, 13
    Current archived log
    channel ch1: Startup archived log backup set
    channel ch1: specifying the newspapers archived in the backup set
    archived journal entry thread = 2 sequence = 83 RECID = 399 STAMP = 815861227
    channel ch1: from room 1 to May 19, 13
    channel ch2: Startup archived log backup set
    channel ch2: specifying the newspapers archived in the backup set
    archived journal entry thread = 1 sequence = 90 RECID = 401 STAMP = 815861227
    channel ch2: from room 1 to May 19, 13
    channel ch1: finished piece 1 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/47oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
    channel ch1: complete set of backups, time: 00:00:01
    channel ch1: archived deletion or newspapers
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_83_814540431.arc RECID archived log file = 399 STAMP = 815861227
    channel ch2: finished piece 1 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/48oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
    channel ch2: complete set of backups, time: 00:00:01
    channel ch2: archived deletion or newspapers
    RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
    Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_90_814540431.arc thread = 1 sequence = 90
    Backup finished on 19 May 13

    From control file and SPFILE Autobackup 19 May 13
    room handle=/u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130519-00 comment = NONE
    File control finished and Autobackup SPFILE to 19 May 13
    output channel: ch1
    output channel: ch2

    RMAN >
    RMAN >
    RMAN retention policy apply to the order
    RMAN retention policy is set to 3 redundancy
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = instance 1753 = ORCLdr2 = DISK device type
    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    8 4 may control file copy 13 /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f
    Game save 40 9 May 13
    Save the piece 40 9 May 13/backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
    Save game 39 may 9, 13
    Save the song 39 9 May 13/backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
    Backs up the entire 42 9 May 13
    Backup total 42 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1mo97nkl_1_1
    Backs up the entire 43 9 May 13
    Backup total 43 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1no97nkl_1_1
    Save game 46 may 10, 13
    Backup total 46 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1po9abvp_1_1
    Game backup 45 may 10, 13
    Backup total 45 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1qo9abvp_1_1
    Save game 47 10 May 13
    Save room 47 10 May 13/backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
    Backs up the entire 48 may 10, 13
    Save the piece 48 10 May 13/backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
    Backs up the entire 50 10 May 13
    Backup total 50 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1uo9ac0l_1_1
    Backs up the entire 51 may 10, 13
    Backup total 51 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1vo9ac0l_1_1
    Backs up the entire 54 may 11, 13
    Backup total 54 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/21o9d0bi_1_1
    Save game 53 may 11, 13
    Backup total 53 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/22o9d0bi_1_1
    Save game 55 may 11, 13
    Save the piece 55 may 11, 13/backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
    Backs up the entire 56 may 11, 13
    Save the song 56 11 May 13/backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
    Backs up the entire 58 may 11, 13
    Backup total 58 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/26o9d0cj_1_1
    Save game 59 may 11, 13
    Backup total 59 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/27o9d0cj_1_1
    Backs up the entire 62 12 May 13
    Backup total 62 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/29o9fknp_1_1
    Save game 61 12 May 13
    Backup total 61 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/2ao9fknp_1_1
    Save game 77 14 May 13
    Backup total 77 14 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00
    Game backup 101 16 May 13
    Backup total 101 16 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130516-00
    Backs up the entire 114 18 May 13
    Save the song 117 may 18, 13/backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = 40 STAMP = 814997122
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = STAMP 39 = 814997122
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1mo97nkl_1_1 element of backup RECID = STAMP 42 = 814997141
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1no97nkl_1_1 element of backup RECID = STAMP 43 = 814997141
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1po9abvp_1_1 element of backup RECID = STAMP 46 = 815083513
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1qo9abvp_1_1 element of backup RECID = STAMP 45 = 815083514
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = STAMP 47 = 815083522
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = 48 STAMP = 815083522
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1uo9ac0l_1_1 element of backup RECID = STAMP 50 = 815083541
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1vo9ac0l_1_1 element of backup RECID = STAMP 51 = 815083541
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/21o9d0bi_1_1 backup RECID piece = 54 STAMP = 815169906
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/22o9d0bi_1_1 element of backup RECID = STAMP 53 = 815169906
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 55 = 815169915
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 56 = 815169917
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/26o9d0cj_1_1 element of backup RECID = STAMP 58 = 815169939
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/27o9d0cj_1_1 element of backup RECID = 59 STAMP = 815169939
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/29o9fknp_1_1 element of backup RECID = 62 STAMP = 815256313
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/2ao9fknp_1_1 backup RECID piece = 61 = 815256313 STAMP
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/c-3171721304-20130516-00 element of backup RECID = 101 STAMP = 815601943
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 RECID = 117 STAMP = 815774800
    20 objects deleted

    RMAN-06207: WARNING: 2 items could not be removed for DISC due channels
    RMAN-06208: status do not match. Use the OVERLAP command to set status
    RMAN-06210: list of relevant objects
    RMAN-06211: =.
    RMAN-06212: filename/Type object Handle
    RMAN-06213: --------------- ---------------------------------------------------
    RMAN-06214: copy of the data /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f file
    RMAN-06214: /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00 piece of backup


    RMAN >
    RMAN >

    Complete recovery manager.
    -bash - $3.2

    Concerning
    Hitgon

    Published by: hitgon on May 20, 2013 02:09

    Published by: hitgon on May 20, 2013 02:15

    It contained a real data file? Or was it a backup controlfile? A backup controlfile may be outdated if another backup controlfile does not capture the same information it contains.

    Hemant K Collette

  • Why Firefox does not delete cookies by leaving to open tabs?

    Firefox does not delete cookies for the tabs that are left open when you quit the browser even with empty cookie options set. Cookies are only eligible for the tabs that are closed before leaving the browser. I do not understand how this could possibly be a design decision because it completely defeats the purpose of the privacy settings.

    Under Options > Privacy I enabled/selected, the following options.

    • Accept cookies (no "Exceptions... »)
    • Continue until the "closing of Firefox".
    • Clear history of Firefox closing
    • * Download history
    • * Cookies
    • * Active Logins
    • * Cache
    • * Data from the Web site offline

    These cookies are stored in session data.

    You can set the browser.sessionstore.privacy_level pref 2 (never) or 1 (no HTTPS, default in the Firefox 3 versions) on the topic: config page to disable the registration of cookies via session restore.

  • How do you not delete entries updated?

    To using Windows (any version) is there a way to delete entries failed in the windows update list?

    Hi Milito_g,

     

    Welcome to Microsoft Answers Forums.

    Well we can not delete entries for updates failed, but we can remove all entries available in the Windows Update history.

    If you want to delete all entries in Windows update, you can check out the link below and run the fix it tool

    How to reset the Windows Update components?

    http://support.Microsoft.com/kb/971058

    Halima S - Microsoft technical support.

    Visit our Microsoft answers feedback Forum and let us know what you think.

  • RMAN-06820: WARNING: unable to archive the current log on the primary database

    I got the following exception when I try to backup the data files and the archivelogs on the physical by uisng RMAN standby database.

    RMAN-06820: WARNING: unable to archive the current log on the primary database

    Target ORACLE database error:

    ORA-17629: unable to connect to the remote database server

    ORA-17627: ORA-00942: table or view does not exist

    It's the backup script

    "

    connection target sys/oracle

    Configure controlfile autobackup on;

    Run {}

    nocfau together;

    allocate channel ch01 device type disc format ' / test/%U';

    allocate channel ch02 device type disc format ' / test/%U';

    backup database copy archivelog;

    backup copy current controlfile;

    }

    "

    And there is no error ora in the primary alert log.

    I was able to tnsping two server (primary/secondary) properly and could also primary of the remote login on standby db server and switch logfile. I read there is a very similar thread, but it has failed so I post again and hope I could get a few clues. Thank you.

    Hello again;

    Try to change this:

    connection target sys/oracle

    to something like this:

    RMAN target sys/password@PRIMARY auxiliary.

    Complete example:

    http://www.Visi.com/~mseberg/data_guard/duprman2.html

    Best regards

    mseberg

  • Purge logs archiving on things primary and Standby and for Data Guard RMAN


    Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

    Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

    Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

    Q1. The above only removes logs archiving to the primary or primary and Standby?

    Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

    I also saw

    CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

    Q3. That what precedes, and once again it is something that you re primary side?

    I saw the following advice in the manual of Concepts of data protection & Admin

    Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

    Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

    Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

    Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

    Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

    Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

    Any idea greatly appreciated,

    Jim

    The above only removes logs archiving to the primary or primary and Standby?

    When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

    including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

    You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

    If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

    Its a configuration, it will not erase by itself.

    If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

    1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

    2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

    If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

    Great example:

    http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

    All Oracle is worth a peek here:

    http://emrebaransel.blogspot.com/

    That what precedes, and once again it is something that you re primary side?

    I would never use it. I always had it put it this way:

    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

    I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

    Why would I want my primary ro connect to the RMAN Repository?

    Because if you break down, you want to be able to backup there, too.

    Also if it remains idle for awhile you want.

    Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

    Always use a database of catalog RMAN with Data Guard.

    If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

    Same answer as 5, use a catalog database.

    Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

    Same answer as 5, use a catalog database.

    What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

    I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

    Best regards

    mseberg

    Summary

    Always use a database with RMAN catalog.

    Always use CRF with RMAN.

    Always set the deletion «To APPLY ON ALL STANDBY» policy

    DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

    Post edited by: mseberg

  • Removal of the log archiving using RMAN Target in Oracle 10 g

    Hi all
    Recently, I noticed that archive logs have been 102 GBs out of the car and I need to free up space. When I tried to connect using the RMAN catalog
    connect catalog user@db
    I got error message like
    RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used
    But I could get through the use
    connect target user@db
    My query is that I can use
    RMAN> delete noprompt expired archivelog all;
    as shown in [how to remove the log file archive | https://forums.oracle.com/forums/thread.jspa?threadID=2321257 & start = 0 & tstart = 0]
    Or I'll take another approach to remove obsolete archive logs?

    Kind regards
    * 009 *.

    Hello;

    Recently, I noticed that archive logs have been 102 GBs out of the car and I need to free up space. When I tried to connect using the RMAN catalog

    connect catalog user@db

    I got error message like

    RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used

    But I could get through the use

    connect target user@db

    Are you trying to connect through Grid control? If you connect via a script, then please post its content.
    Make sure that you are not connected to the database target using "nocatalog.

    rman target sys/@ catalog /@

    My query is that I can use

    RMAN> delete noprompt expired archivelog all;

    as shown in [how to remove the log file archive | https://forums.Oracle.com/forums/thread.jspa?threadID=2321257&Start=0&tstart=0]
    Or I'll take another approach to remove obsolete archive logs?

    Kind regards
    * 009 *.

    These archives are saved? The command above does not update the RMAN Repository if in case, the archives have been manually delete at the OS level.
    I recommend you save these records and then remove them.

    RMAN>backup archivelog all not backedup 1 times delete input;

    If these archives are already saved and were not deleted from the disk, then you can use the below command

    RMAN>delete force noprompt archivelog all completed before 'SYSDATE-n';

    where "n" is the number of days of delay on the current date. Be sure to check if these archives have been saved before deleting.

    Kind regards
    Shivananda

  • RMAN delete policy has not worked and not delete outdated backup

    Hi all

    I am facing a problem this obsolete backup is not delete unwanted backup.

    I used to take level 0 once weekly and cumulative incremental in 3 times a day.

    I have 2 TB hard drive, every week, I used the backup from command remove obsolete based file can delete based on my redundancy strategy 1.

    The previous week it works fine and deleted obsolete backup based on the deletion policy. but this week when I try to use the delete obsolete command, it is not removed and the hard drive is always full and I couldn't take later backup.

    It's live server, I need to take the free space on the hard drive. Please help me.

    You will find details of error that I met in the log file.

    output channel: C1

    output channel: C2

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of backup so archivelog command at 05/05/2015 10:57:14

    ORA-19502: write error on file 'G:\RMAN\AWSPROCESS\BACKUP\AWSPROCESS\BACKUPSET\2015_05_05\O1_MF_NNND1_TAG20150505T090032_BNJGC9RR_. BKP", the number of block 7227648 (block size = 8192)

    ORA-27070: async read/write failed

    OSD-04016: error queuing an asynchronous i/o request.

    S/O-error: (OS 112) there is not enough space on the disk.

    Your backup on May 02 is not a valid backup, then you can try something like:

    RMAN > delete database backup completed after 'sysdate-6 ";

  • RMAN-06025: no log backup archived for thread 1 with sequence - on double

    I tried to make a duplicate of a database, something I have done before, but this time I have run in to a problem.

    So, make a

    RMAN > list archivelog all;

    Shows that I have log sequence numbers 2600-2862 available.

    I have removed the expired archive logs and made an overlap and have issued the order on «alter system current archivelog» DB

    I did the pfile file and open the destination DB in nomount.

    The backup of the DB and the archivelogs seems to work fine without error.

    RMAN > backup as backupset = compressed database format ' / u04/tmpback/%u' tag "CLONE_TO_PPRD" include current controlfile;

    RMAN > backup as backupset archivelog Tablet all format = ' / u04/tmpback/al_%u' tag "CLONE_TO_PPRD_AL".

    Thus, with the environment on the destination DB (PPRD), opening a new rman to make the duplicate... "' rman target auxiliary sys@source_db /" "

    Then run the command

    target database duplicate to the PPRD until the SNA 2538794790;

    It seems to work fine, until this...

    Instance Oracle to close

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of the command duplicate Db at 30/10/2014 14:46:22

    RMAN-05501: abandonment of duplicate target database

    RMAN-03015: an error has occurred in the script stored memory Script

    RMAN-06053: unable to perform the recovery of the media because of the missing journal

    RMAN-06025: no backup log archived for thread 1 with sequence 2599 and YVERT departure from 2500202517 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2598 and YVERT departure from 2500201335 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2597 and YVERT departure from 2500102904 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2596 and YVERT departure from 2499995595 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2595 and YVERT departure from 2499836289 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2594 and YVERT departure from 2499642775 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2593 and YVERT departure from 2499478641 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2592 and YVERT departure from 2499413468 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2591 and YVERT departure from 2499410632 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2590 and YVERT departure from 2499408867 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2589 and YVERT departure from 2499381186 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2588 and YVERT departure from 2499068021 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2587 and YVERT departure from 2498925555 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2586 and YVERT departure from 2498802786 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2585 and YVERT departure from 2498614939 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2584 and YVERT departure from 2498564861 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2583 and YVERT departure from 2498562153 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2582 and YVERT departure from 2498561088 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2581 and YVERT departure from 2498484636 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2580 and YVERT departure from 2498271487 found to restore

    RMAN-06025: no backup log archived for 1 with sequence 2579 threads and YVERT departure from 2498214991 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2578 and YVERT departure from 2498212309 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2577 and YVERT departure from 2498211201 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2576 and YVERT departure from 2498136750 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2575 and YVERT departure from 2498007880 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2574 and YVERT departure from 2497940390 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2573 and YVERT departure from 2497937659 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2572 and YVERT departure from 2497935694 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2571 and YVERT departure from 2497906173 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2570 and YVERT departure from 2497856983 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2569 and YVERT departure from 2497596547 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2568 and YVERT departure from 2497456509 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2567 and YVERT departure from 2497319931 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2566 and YVERT departure from 2497256972 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2565 and YVERT departure from 2497254201 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2564 and YVERT departure from 2497252909 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2563 and YVERT departure from 2497193527 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2562 and YVERT departure from 2496934735 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2561 and YVERT departure from 2496745593 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2560 and YVERT departure from 2496657121 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2559 and YVERT departure from 2496603411 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2558 and YVERT departure from 2496600720 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2557 and YVERT departure from 2496599649 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2556 and YVERT departure from 2496488543 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2555 and YVERT departure from 2495585865 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2554 and YVERT departure from 2495399778 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2553 and YVERT departure from 2495269888 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2552 and YVERT departure from 2495267113 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2551 and YVERT departure from 2495264943 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2550 and YVERT departure from 2495263264 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2549 and YVERT departure from 2495032426 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2548 and YVERT departure from 2494891192 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2547 and YVERT departure from 2494748475 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2546 and YVERT departure from 2494688135 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2545 and YVERT departure from 2494685342 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2544 and YVERT departure from 2494684167 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2543 and YVERT departure from 2494617350 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2542 and YVERT departure from 2494441823 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2541 and YVERT departure from 2494219188 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2540 and YVERT departure from 2494146694 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2539 and YVERT departure from 2494143651 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2538 and YVERT departure from 2494141374 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2537 and YVERT departure from 2494140316 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2536 and YVERT departure from 2494039070 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2535 and YVERT departure from 2493969002 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2534 and YVERT departure from 2493966234 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2533 and YVERT departure from 2493964141 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2532 and YVERT departure from 2493962603 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2531 and YVERT departure from 2493730362 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2530 and YVERT departure from 2493626024 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2529 and YVERT departure from 2493623327 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2528 and YVERT departure from 2493620995 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2527 and YVERT departure from 2493619424 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2526 and YVERT departure from 2493412146 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2525 and YVERT departure from 2493235154 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2524 and YVERT departure from 2493121677 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2523 and YVERT departure from 2493059844 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2522 and YVERT departure from 2493057083 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2521 and YVERT departure from 2493055871 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2520 and YVERT departure from 2492957915 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2519 and YVERT departure from 2492880955 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2518 and YVERT departure from 2492544076 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2517 and YVERT departure from 2492423758 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2516 and YVERT departure from 2492417400 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2515 and YVERT departure from 2492414719 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2514 and YVERT departure from 2492413908 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2513 and YVERT departure from 2492327128 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2512 and YVERT departure from 2492230125 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2511 and YVERT departure from 2491947217 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2510 and YVERT departure from 2491884830 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2509 and YVERT departure from 2491821845 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2508 and YVERT departure from 2491819116 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2507 and YVERT departure from 2491817468 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2506 and YVERT departure from 2491784652 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2505 and YVERT departure from 2491719981 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2504 and YVERT departure from 2487354643 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2503 and YVERT departure from 2487272304 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2502 and YVERT departure from 2487218716 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2501 and YVERT departure from 2487215968 found to restore

    RMAN-06025: no backup log archived for thread 1 with 2500 sequence and YVERT departure from 2487214915 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2499 and YVERT departure from 2487178867 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2498 and YVERT departure from 2475666929 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2497 and YVERT departure from 2475424798 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2496 and YVERT departure from 2475356185 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2495 and YVERT departure from 2475353406 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2494 and YVERT departure from 2475352071 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2493 and YVERT departure from 2475297238 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2492 and YVERT departure from 2475237220 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2491 and YVERT departure from 2475177867 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2490 and YVERT departure from 2475175065 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2489 and YVERT departure from 2475173911 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2488 and YVERT departure from 2475116250 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2487 and YVERT departure from 2475011369 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2486 and YVERT departure from 2474948383 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2485 and YVERT departure from 2474945180 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2484 and YVERT departure from 2474943701 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2483 and YVERT departure from 2474893025 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2482 and YVERT departure from 2474114073 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2481 and YVERT departure from 2473907191 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2480 and YVERT departure from 2473776113 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2479 and YVERT departure from 2473773241 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2478 and YVERT departure from 2473770145 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2477 and YVERT departure from 2473769454 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2476 and YVERT departure from 2473666106 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2475 and YVERT departure from 2473483998 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2474 and YVERT departure from 2473381579 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2473 and YVERT departure from 2473134334 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2472 and YVERT departure from 2473066760 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2471 and YVERT departure from 2473064023 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2470 and YVERT departure from 2473062119 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2469 and YVERT departure from 2473038503 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2468 and YVERT departure from 2472797901 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2467 and YVERT departure from 2472710532 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2466 and YVERT departure from 2472456854 found to restore

    RMAN-00567: Recovery Manager could not print error messages

    Why is it always get all these old newspapers archive? What should I do to get that continues. I'm sure miss me something small, but it is just eluding me.

    Thank you

    Rob

    Follow these steps:

    RMAN > crosscheck backup;

    RMAN > overlapping copy;

  • Current archive log has been deleted, how to recover using the previous archive log?

    Hello

    My current log sequence #819 and it has been deleted and no other choice to get it back and I have previous newspapers archived with sequences #814 à 818.

    When I start my database is to show that the use ' MUST USE RESETLOGS or NORESETLOGS option of database open, then I used the command

    SQL > ALTER DATABASE OPEN RESETLOGS;
    ALTER DATABASE OPEN RESETLOGS
    *
    ERROR on line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: ' E:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01. DBF'

    SQL > alter database recover;
    ALTER database recover
    *
    ERROR on line 1:
    ORA-00283: cool cancelled due to errors
    ORA-01610: recovery using BACKUP CONTROLFILE option must be
    SQL > alter database recovery using backup controlfile;
    change the database recovery using backup controlfile
    *
    ERROR on line 1:
    ORA-00279: change 8433746 September at 15/01/2013 19:51:59 needed to screw 1
    ORA-00289: suggestion:
    E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_01_16\O1_MF_1_819_

    % U_. ARC
    ORA-00280: change 8433746 thread 1 is in sequence #819

    now, I don't have the log archiving with 819 sequence, I recover from 818. Please tell me how to do?

    Hello

    1. select * from v$log and see which log file is current. Query v$logfile to check physical file location belonging to current log group.
2. Take bacup of your curent control file using copy/paste of your OS
3. Issue following command in mount state
recover database until cancel using backup controlfile
4. When it finishes applying available archived logs, still it will ask for the location of archived logs which have not been applied, here provide path of current redo log file you got in first step. Here your recovery will finish after applying current redo log
5.alter database open resetlogs.

    Salman

Maybe you are looking for

  • Install the link Dropbox with Terminal mpkg file

    Hello I'm looking at the best way to install a mpkg on multiple Macs in our society.  With our MDM solution limited, it will be via a script/Terminal command.  I wonder if someone would be able to help the best way to do it.  I placed the file in a l

  • Save two using table 1 d

    I'm adding picture and the labview vi I'm trying to make a viable program. I am trying to record two table 1 text file, but it is coming in the line current line voltage single column 2. 1 st. How can I get them on separate column. Second thing I tri

  • Disk partition question

    Hi, I have a laptop CQ60-422DX. I went to disk management via the search box on the start menu. When I looked at my scores, I saw that I have the standard C drive and the recovery partition. However, I have seen an additional partition listed. There

  • LaserJet 2840: LaserJet 2840 Stopped printing in color

    My 2840 has just stopped printing in color only in black and white.  It comes from working well for over a year.  Help!

  • Bad BIOS for m7667c Desktop Update

    Background:I have an HP Pavilion m7667c a Media Center Pc, Prod/system #: RC643AAI was trying to update the BIOS by HP before orientationtry an upgrade to VISTA from Windows XP Media Center Edition 2005.The update of the BIOS was not good and now the