Delete Archive Logs In Dataguard Environment

Hi YFA,
I'm facing a FI, in my DG environrmnt :
OS : Solaris 5.10
Oracle : 10.2.0.4
I've this env :
Prod >>> Prod_DG
In my rman shell svcript that delete archivelogs I make a "Delete Input" after Backup,
but
I fear that the archivelog are deleted without being applied in the dataguard Database.
Does anyone has find a workarround? or does it exist a parameter in RMAN to bypass this ?
PS
To Att of Mr. : "someonelse"
Pls do not Reply to this request,
and Please replace your login from "someonelse" to "nobodyelse"
Thxs

Thxs for your Reply but I need one more Info,
In the Standby Site how do I manage my archivelogs?
When I connect with RMAn and I try a new configuration
i Get an ORA 600
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 02/19/2009 15:40:04
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel at 02/19/2009 15:40:04
ORA-00600: internal error code, arguments: [13011], [51167], [20981165], [7], [20981165], [17], [], []

Similar Messages

  • How to delete archive log on standby site

    hi
    i configured dataguard on 10g. could anyone suggest how to delete archived log on standby site..

    Hi,
    There is no automatic feature out-of-the-box but you have the following views:
    1) Shows archive logs transfered:
    select sequence#, first_time, next_time from v$archived_log order by sequence#;
    2) Shows archive logs applied:
    select sequence#, archived, applied from v$archived_log order by sequence#;
    If you see your archivelogs applied you can safely remove archive log files from your disk. It is your decision if you keep or delete them completely.

  • How to delete archive log files from ASM through Grid Control

    Hi
    Anybody suggest me how to delete archive log files from ASM through Grid Control.
    Thanks

    It is important to specify both, the oracle version and os version when posting, so confusions can be avoided.
    In this particular case, since you are referring to asm and grid control you could be talking about either 10gR1, 10gR2 or 11gR1; but I strongly suggest you to avoid us to be guessing. In either case, you sould go to the maintenance tab of the target database and program a scheduled 'delete noprompt obsolete;' procedure. This will purge the information stored at the Flash recovery area, which I assume you have declared inside the ASM.
    ~ Madrid
    http://hrivera99.blogspot.com/

  • How to delete archive logs on the standby database....in 9i

    Hello,
    We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
    The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
    Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
    thanks,
    C.

    We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
    The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
    Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.From 10g there is option to purge on deletion policy when archives were applied. Check this note.
    *Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]*
    Still it is on 9i, So you need to schedule RMAN job or Shell script file to delete archives.
    Before deleting archives
    1) you need to check is all the archives are applied or not
    2) then you can remove all the archives completed before 'sysdate-2';
    RMAN> delete archvielog all completed before 'sysdate-2';
    As per your requirement.

  • Manual delete archived log files

    Because we don't have RMAN in our development server, I need to use manual operation to delete all archived logs. Is my procedure correct and safe?
    SHUTDOWN IMMEDIATE
    STARTUP MOUNT
    ALTER DATABASE NOARCHIVELOG;
    EXITRun OS command to manually delete archived log files:
    rm /oradata/arch/*
    Login to sqlplus
    SHUTDOWN IMMEDIATE
    STARTUP MOUNT
    ALTER DATABASE ARCHIVELOG;
    STARTUP OPENThanks!

    linuxos wrote:
    Oh I suppose RMAN need to be configured somthing before use. I tried it, and find no pre-requisite is required. Thanks!
    If the archives are deleted manually in open mode, how can Oracle match the archived logs' retention policy? Does Oracle store the archived logs in data dictionary?While you can delete archivelogs manually any time you want, you should let rman manage them with appropriate rman commands, preferably in a script that you schedule for regular execution.
    Some of your questions lead me to question if you understand that archivelogs are not actively open by the database, and they technically are not part of the database. They are simply a series of "offline" copies of the online redo logs. They are written to once, when an online redo is being archived, then they just sit there until needed for a recovery.

  • Is RMAN only way to take backup and delete Archive Logs?

    On primary db:
    ===============
    OS: Windows 2003 server 32-bit
    Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
    On Physical standby db:
    ===============
    OS: Windows 2003 server 32-bit
    Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
    Data Guard just configured. Archive Logs are properly being shipped to standby db. Is RMAN only way to take backup and delete Archive Logs from both primary and standby db? What other command can be used?
    Thanks

    No, but anything else is way more work. Without using RMAN you would have to find another way to keep track of applied logs.
    RMAN make this very simple :
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;Using another method would be like using the handle of your screwdriver as a hammer.
    See "RMAN Recipes for Oracle Database 11g" ISBN 978-1-5959-851-1
    Best Regards
    mseberg

  • How can we delete archive log files from OEM

    Hi,
    I took backup of the archive log file and deleted it at OS level but in it is not reflecting in the EM can any one tell me how to delete archive log files from OEM.
    any help will be appreciated.
    Regards,
    Ashraf

    This link?
    http://download-west.oracle.com/docs/cd/B10501_01/em.920/a96670/ch_backp.htm#26936

  • Unable to delete archive log.

    Hi,
    Our database server's archive log destination is full,but after running
    backup archivelog all delete input;
    it's taking archive log backup,but not deleting archivelogs.
    Could you suggest me what is the reason.

    RMAN> backup archivelog all delete input;
    Starting backup at 17-DEC-10
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=155 recid=422 stamp=737092752
    input archive log thread=1 sequence=156 recid=425 stamp=737156432
    input archive log thread=1 sequence=157 recid=428 stamp=737257293
    input archive log thread=1 sequence=158 recid=431 stamp=737322402
    input archive log thread=1 sequence=159 recid=434 stamp=737389991
    input archive log thread=1 sequence=160 recid=437 stamp=737408597
    input archive log thread=1 sequence=161 recid=440 stamp=737476660
    input archive log thread=1 sequence=162 recid=443 stamp=737542384
    input archive log thread=1 sequence=163 recid=446 stamp=737634615
    input archive log thread=1 sequence=164 recid=449 stamp=737658567
    input archive log thread=1 sequence=165 recid=452 stamp=737726432
    input archive log thread=1 sequence=166 recid=455 stamp=737827094
    input archive log thread=1 sequence=167 recid=456 stamp=737860748
    input archive log thread=1 sequence=168 recid=464 stamp=737980097
    input archive log thread=1 sequence=169 recid=461 stamp=737980094
    input archive log thread=1 sequence=170 recid=467 stamp=737980099
    input archive log thread=1 sequence=171 recid=470 stamp=737980425
    input archive log thread=1 sequence=172 recid=472 stamp=737981508
    input archive log thread=1 sequence=173 recid=474 stamp=737985385
    channel ORA_DISK_1: starting piece 1 at 17-DEC-10
    channel ORA_DISK_1: finished piece 1 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_1_1 comment=NONE
    channel ORA_DISK_1: starting piece 2 at 17-DEC-10
    channel ORA_DISK_1: finished piece 2 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_2_1 comment=NONE
    channel ORA_DISK_1: starting piece 3 at 17-DEC-10
    channel ORA_DISK_1: finished piece 3 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_3_1 comment=NONE
    channel ORA_DISK_1: starting piece 4 at 17-DEC-10
    channel ORA_DISK_1: finished piece 4 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_4_1 comment=NONE
    channel ORA_DISK_1: starting piece 5 at 17-DEC-10
    channel ORA_DISK_1: finished piece 5 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_5_1 comment=NONE
    channel ORA_DISK_1: starting piece 6 at 17-DEC-10
    channel ORA_DISK_1: finished piece 6 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_6_1 comment=NONE
    channel ORA_DISK_1: starting piece 7 at 17-DEC-10
    channel ORA_DISK_1: finished piece 7 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_7_1 comment=NONE
    channel ORA_DISK_1: starting piece 8 at 17-DEC-10
    channel ORA_DISK_1: finished piece 8 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_8_1 comment=NONE
    channel ORA_DISK_1: starting piece 9 at 17-DEC-10
    channel ORA_DISK_1: finished piece 9 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_9_1 comment=NONE
    channel ORA_DISK_1: starting piece 10 at 17-DEC-10
    channel ORA_DISK_1: finished piece 10 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_10_1 comment=NONE
    channel ORA_DISK_1: starting piece 11 at 17-DEC-10
    channel ORA_DISK_1: finished piece 11 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_11_1 comment=NONE
    channel ORA_DISK_1: starting piece 12 at 17-DEC-10
    channel ORA_DISK_1: finished piece 12 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_12_1 comment=NONE
    channel ORA_DISK_1: starting piece 13 at 17-DEC-10
    channel ORA_DISK_1: finished piece 13 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_13_1 comment=NONE
    channel ORA_DISK_1: starting piece 14 at 17-DEC-10
    channel ORA_DISK_1: finished piece 14 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_14_1 comment=NONE
    channel ORA_DISK_1: starting piece 15 at 17-DEC-10
    channel ORA_DISK_1: finished piece 15 at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\0MLVPGRB_15_1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:03:41
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00155.001 recid=422 stamp=737
    092752
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00156.001 recid=425 stamp=737
    156432
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00157.001 recid=428 stamp=737
    257293
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00158.001 recid=431 stamp=737
    322402
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00159.001 recid=434 stamp=737
    389991
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00160.001 recid=437 stamp=737
    408597
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00161.001 recid=440 stamp=737
    476660
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00162.001 recid=443 stamp=737
    542384
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00163.001 recid=446 stamp=737
    634615
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00164.001 recid=449 stamp=737
    658567
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00165.001 recid=452 stamp=737
    726432
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00166.001 recid=455 stamp=737
    827094
    archive log filename=D:\ORANT\ARCLOG1\REDO01.LOGARC00167.001 recid=456 stamp=737
    860748
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00168.001 recid=464 stamp=737
    980097
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00169.001 recid=461 stamp=737
    980094
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00170.001 recid=467 stamp=737
    980099
    archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00171.001 recid=470 stamp=737
    980425
    archive log filename=D:\ORANT\ARCLOG2\REDO02.LOGARC00172.001 recid=472 stamp=737
    981508
    archive log filename=D:\ORANT\ARCLOG1\REDO01.LOGARC00173.001 recid=474 stamp=737
    985385
    Finished backup at 17-DEC-10
    Starting Control File and SPFILE Autobackup at 17-DEC-10
    piece handle=D:\RMAN\BACKUP\C-1738882432-20101217-02 comment=NONE
    Finished Control File and SPFILE Autobackup at 17-DEC-10

  • When to delete Archive Log files ? and is safe to delete ?

    Hi all,
    I have a question, my DB is running in Archive Log mode and is growing day by day, so should I delete archive log files and where i find that my which files are old and how to delete theses files, for info I also take full RMAN and export backup regularly .
    abbas

    Well, if you're not comfortable with Backup and Recovery principles, i'd advise you to first read TFM: Backup and Recovery Concept(click) for you data safety's sake.
    Anyway, just to give you a glance at what could happen, immagine suche a situation where your database is made of 5 different datafiles (whatever they are - SYSTEM, SYSAUX, UNDO, ...), controlfiles and online redo logs. If, for example your backup is done in a timeline such as:T0 : Backup datafile F1 and F2
    T1 : Backup datafile F2 and controlfile
    T2 : Backup datafile F3, F4
    T3 : Backup datafile F5
    T0' : Backup datafile F1 and F2
    T1' : Backup datafile F2 and controlfile
    T2' : Backup datafile F3, F4
    T3' : Backup datafile F5
    ...If your server crashes (for example is thrown though the 5th floor window..) in order to make a full recovery, you could proceed multiple ways.
    . Restore files from Tx' backups. Then you'd need every archived redo logs created from T0' to now in order to be able to do a full recovery.
    . Restore files from backups; T3, T0', T2' and rectreate controlfile. Then you'd need every archived redo log created from T3 (inclusive).
    . Restore Tx backup, ...
    . Restore ...
    and so on.
    What's important is that you're at least able to resynch a full-set backup. What I mean is: if you restored "T3, T0', T2' and rectreate controlfile", in order to open the database you'll absolutely need every archived redo log created between T3 and T2' inclusive. If one is missions, you won't be able to open it.
    That is the principle. Read the concept book I linked to get more infos.
    Regards,
    Yoann.

  • How to delete archive log by RMAN.

    Hi All,
    How to delete archive log by RMAN and what is the difference between
    delete all input & all delete input in RMAN backup.

    plus archivelog all delete inputYou get an error on the syntax.
    "PLUS ARCHIVELOG" does not allow the "ALL" keyword.
    (See "backupSpecOperand" in the RMAN Documentation of the BACKUP command syntax).
    However, "DELETE INPUT" allows the optional "ALL" keyword as in "DELETE ALL INPUT" to delete from all archivelog destinations.
    I guess that you have confused the "ALL" keyword in "BACKUP ARCHIVELOG" as being possible in "BACKUP .. PLUS ARCHIVELOG".
    "ALL" is allowed in "BACKUP ARCHIVELOG" but not in "BACKUP .. PLUS ARCHIVELOG".
    Hemant K Chitale

  • Delete archive log file

    hello,
    I am using oracle 10g on linux i want to delete archive log file automaticaly there is any way to do this.or anyone can tell me scripts for do this.ur help regarding this is highly appreciated
    Regard,s
    Umair Iqbal

    Hi,
    Can you please let us know why you want to delete the archive log file?
    BTW, you can use RMAN to achieve this by taking the backup of archive log and delete the original file using the following command:
    Backup archivelog all delete input;Regards

  • How to delete archive log file

    hii,
    presently i am working on oracle 10gR2 on windows server 2003.
    hard disk drive is almost full.
    when i execute this command
    "DELETE EXPIRED ARCHIVE LOG ALL";
    it give message
    "specifies does not match any archive log in the recovery catalog"
    how can i delete archive log files ??
    Regards
    Vaibhav Dixit

    these are the list
    RMAN> list archivelog all;
    List of Archived Log Copies
    Key Thrd Seq S Low Time Name
    696 1 341 A 25-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_341_758982530.ARC
    698 1 342 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_342_758982530.ARC
    700 1 343 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_343_758982530.ARC
    702 1 344 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_344_758982530.ARC
    704 1 345 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_345_758982530.ARC
    705 1 346 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_346_758982530.ARC
    708 1 347 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_347_758982530.ARC
    710 1 348 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_348_758982530.ARC
    712 1 349 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_349_758982530.ARC
    714 1 350 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_350_758982530.ARC
    716 1 351 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_351_758982530.ARC
    719 1 352 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_352_758982530.ARC
    720 1 353 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_353_758982530.ARC
    721 1 354 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_354_758982530.ARC
    722 1 355 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_355_758982530.ARC
    727 1 356 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_356_758982530.ARC
    728 1 357 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_357_758982530.ARC
    730 1 358 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_358_758982530.ARC
    732 1 359 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_359_758982530.ARC
    734 1 360 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_360_758982530.ARC
    736 1 361 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_361_758982530.ARC
    738 1 362 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_362_758982530.ARC
    740 1 363 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_363_758982530.ARC
    741 1 364 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_364_758982530.ARC
    742 1 365 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_365_758982530.ARC
    743 1 366 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_366_758982530.ARC
    744 1 367 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_367_758982530.ARC
    745 1 368 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_368_758982530.ARC
    746 1 369 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_369_758982530.ARC
    753 1 370 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_370_758982530.ARC
    756 1 371 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_371_758982530.ARC
    758 1 372 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_372_758982530.ARC
    759 1 373 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_373_758982530.ARC
    763 1 374 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_374_758982530.ARC
    764 1 375 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_375_758982530.ARC
    767 1 376 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_376_758982530.ARC
    768 1 377 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_377_758982530.ARC
    770 1 378 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_378_758982530.ARC
    772 1 379 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_379_758982530.ARC
    774 1 380 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_380_758982530.ARC
    776 1 381 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_381_758982530.ARC
    778 1 382 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_382_758982530.ARC
    780 1 383 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_383_758982530.ARC
    782 1 384 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_384_758982530.ARC
    784 1 385 A 04-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_385_758982530.ARC
    785 1 386 A 04-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_386_758982530.ARC
    788 1 387 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_387_758982530.ARC
    790 1 388 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_388_758982530.ARC
    791 1 389 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_389_758982530.ARC
    792 1 390 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_390_758982530.ARC
    793 1 391 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_391_758982530.ARC
    794 1 392 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_392_758982530.ARC
    795 1 393 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_393_758982530.ARC
    796 1 394 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_394_758982530.ARC
    797 1 395 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_395_758982530.ARC
    798 1 396 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_396_758982530.ARC
    799 1 397 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_397_758982530.ARC
    800 1 398 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_398_758982530.ARC
    801 1 399 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_399_758982530.ARC
    802 1 400 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_400_758982530.ARC
    803 1 401 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_401_758982530.ARC
    804 1 402 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_402_758982530.ARC
    805 1 403 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_403_758982530.ARC
    806 1 404 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_404_758982530.ARC
    808 1 405 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_405_758982530.ARC
    814 1 406 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_406_758982530.ARC
    816 1 407 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_407_758982530.ARC
    817 1 408 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_408_758982530.ARC
    822 1 409 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_409_758982530.ARC
    823 1 410 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_410_758982530.ARC
    824 1 411 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_411_758982530.ARC
    826 1 412 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_412_758982530.ARC
    829 1 413 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_413_758982530.ARC
    831 1 414 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_414_758982530.ARC
    839 1 415 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_415_758982530.ARC
    841 1 416 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_416_758982530.ARC
    843 1 417 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_417_758982530.ARC
    844 1 418 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_418_758982530.ARC
    848 1 419 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_419_758982530.ARC
    849 1 420 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_420_758982530.ARC
    850 1 421 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_421_758982530.ARC
    851 1 422 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_422_758982530.ARC
    852 1 423 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_423_758982530.ARC
    853 1 424 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_424_758982530.ARC
    854 1 425 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_425_758982530.ARC
    856 1 426 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_426_758982530.ARC
    862 1 427 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_427_758982530.ARC
    870 1 428 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_428_758982530.ARC
    872 1 429 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_429_758982530.ARC
    874 1 430 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_430_758982530.ARC
    875 1 431 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_431_758982530.ARC
    878 1 432 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_432_758982530.ARC
    880 1 433 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_433_758982530.ARC
    882 1 434 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_434_758982530.ARC
    884 1 435 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_435_758982530.ARC
    886 1 436 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_436_758982530.ARC
    888 1 437 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_437_758982530.ARC
    890 1 438 A 11-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_438_758982530.ARC
    891 1 439 A 11-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_439_758982530.ARC
    893 1 440 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_440_758982530.ARC
    896 1 441 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_441_758982530.ARC
    898 1 442 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_442_758982530.ARC
    900 1 443 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_443_758982530.ARC
    901 1 444 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_444_758982530.ARC
    902 1 445 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_445_758982530.ARC
    903 1 446 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_446_758982530.ARC
    904 1 447 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_447_758982530.ARC
    910 1 448 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_448_758982530.ARC
    912 1 449 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_449_758982530.ARC
    914 1 450 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_450_758982530.ARC
    916 1 451 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_451_758982530.ARC
    918 1 452 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_452_758982530.ARC
    920 1 453 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_453_758982530.ARC
    922 1 454 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_454_758982530.ARC
    924 1 455 A 14-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_455_758982530.ARC
    926 1 456 A 14-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
    PL\1_456_758982530.ARC
    RMAN> delete noprompt expired archivelog all;
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=77 devtype=DISK
    specification does not match any archive log in the recovery catalog

  • Will RMAN delete archive log files on a Standby server?

    Environment:
    Oracle 11.2.0.3 EE on Solaris 10.5
    I am currently NOT using an RMAN repository (coming soon).
    I have a Primary database sending log files to a Standby.
    My Retention Policy is set to 'RECOVERY WINDOW OF 8 DAYS'.
    Question: Will RMAN delete the archive log files on the Standby server after they become obsolete based on the Retention Policy or do I need to remove them manually via O/S command?
    Does the fact that I'm NOT using an RMAN Repository at the moment make a difference?
    Couldn't find the answer in the docs.
    Thanks very much!!
    -gary

    Hello again Gary;
    Sorry for the delay.
    Why is what you suggested better?
    No, its not better, but I prefer to manage the archive. This method works, period.
    Does that fact (running a backup every 4 hours) make my archivelog deletion policy irrelevant?
    No. The policy is important.
    Having the Primary set to :
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBYBut set to "NONE" on the Standby.
    Means the worst thing that can happen is RMAN will bark when you try to delete something. ( this is a good thing )
    How do I prevent the archive backup process from backing up an archive log file before it gets shipped to the standby?
    Should be a non-issue, the archive does not move, the REDO is transported and applied. There's SQL to monitor both ( Transport and Apply )
    For Data Guard I would consider getting a copy of
    "Oracle Data Guard 11g Handbook" - Larry Carpenter (AKA Dr. Paranoid ) ISBN 978-0-07-162111-2
    Best Oracle book I've read in 10 years. Covers a ton of ground clearly.
    Also Data Guard forum here :
    Data Guard
    Best Regards
    mseberg
    Edited by: mseberg on Apr 10, 2012 4:39 PM

  • Best way of deleting archive logs on standby when backup taken on primary

    Hello,
    I have a 11gr2 dataguard configuration without the broker.
    main problem in my particular situation arises from my FRA size on primary much more than on standby (90Gb vs 30Gb) and in some situations I'm constrained with FRA space on standby.... I'm going to align the FRAs but in the mean time....
    can anyone confirm that if I have configuration as in subject with maximum performance mode and I'm not using the broker I should consider a sort of "external" way for archive log deletion on the physical standby?
    In fact I'm setting on primary
    - retention policy = redundancy 1
    - archivelog deletion = applied on standby (without using any "backed up...." option)
    Considering the standby it seems from docs that:
    - retention policy always wins over deletion policy (so no archive eligible for deletion is deleted if retention is not satisfied)
    - I can set on standby archivelog deletion = applied on standby (without using any "backed up...." option)
    But it is not clear to me the effect of this config in case this is a standby itself and without any other cascade standby databases
    The manual says this has to be met:
    1) The archived redo log files have been applied to the required standby databases.
    ---> what does this mean in case the db is a standby.. met or not met as I have no other cascade standby dependant on this one?
    2) The logs are not needed by the BACKED UP ... TIMES TO DEVICE TYPE deletion policy. If the BACKED UP policy is not set, then this condition is always met.
    ---> I should be ok
    So the last question for standby is
    - what to set retention policy to?
    I have not understood if I set it to "NONE", this means no retention at all or retention for ever....
    sometimes I read that there is no policy; in other examples that files will be retained forever (because no file considered as obsolete).... or at least so I understood...
    I would like to have a sort of policy on standby where the archive logs can be deleted as soon as they are applied during the continuous media recovery phase...
    It seems I can't find a self contained set of configurations across the dataguard....
    Thanks in advance.
    Gianluca

    I agree with you.... It is a temporary contingency....
    I already stressed the fact that sizes between sites must be quite identical...
    we are going towards a production dataguard, migrating from a windows config (without it) to a Linux based config....
    but this contingency made me think about these considerations regarding policies and automatic dataguard operations
    I also stressed on equal size grow capability for both sites file systems, also for data tablespaces, so that for example in case of high fragmentation we have to avoid a limit situation where
    1) a file system full for DR datafiles causes abend of automatic media recovery
    2) this generates FRA growth in DR because archive logs are shipped but not applied any more
    3) FRA goes 100% in DR and primary cannot ship any more
    4) archive logs cannot be automatically deleted on primary because not already shipped
    5) FRA full on primary and DB hangs....
    Thanks anyway for input

  • HELP....How to delete archive log from v$archived_log table...

    Hi All
    Our prod database was running in Archive log mode and now it is in NO Archive log mode. I deleted all archive logs from the disk but I can still see them in v$archived_log table. How do I delete them from this table.
    Environment is Oracle8i(8.1.7) running on Windows 2000 Advanced Server.
    Thank you
    Amit

    Hi,
    Recreating the controlfile is the only way to force a cleanup of all entries in v$archived_log.
    You can see information on Metalink Note:1012929.6
    Paolo

Maybe you are looking for

  • How can I see ONLY dead files in my library (newest Itunes update)

    I want to find all of my dead files in one place so I can either delete or find them. I keep seeing ways to use smart playlist to find dead files, but when I try to do that, the Smart Playlist options won't let me. I can only assume it's because ther

  • Adobe Document Services (not installed)

    Hi Guys, I have installed SAP CE 7.2 SP1 as a standard installation and opted for all components at installation time. I have installed also Adobe LiveCycle Designer, created my interactive form and deployed it. When I wanted to run the corresponding

  • Error installing SAP NetWeaver 7.2 ABAP Trial Version

    Hi, At the beginning of the installation of SAP NetWeaver 7.2 ABAP Trial Version the following error occurred: Program is starting... Please wait! ERROR      2010-12-28 18:58:18.804 syxxcniwrapper.cpp:105 NI::CNIInit::CNIInit() lib=syslib module=sysl

  • Stick to the old or buy new?

    Hi. I have an old macbook but currently it is not working as the charger was spoilt (I threw it away) and i have yet to get a new one. just a few months ago, my family bought a mac desktop. however, since i have not yet backed up or retrieve the file

  • Wont go in sleep mode

    I had my hard drive replaced by apple beacause of the seagate hard drive recall and now my system wont go into sleep mode and I get the keyboard idenifier if I restart