Question about Archive Log Deletion policy

I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
Messages of the database are in German, but I guess you'll understand them.
SQL> startup
ORACLE-Instance hochgefahren.
Total System Global Area 5344731136 bytes
Fixed Size                  2129240 bytes
Variable Size            2684355240 bytes
Database Buffers         2617245696 bytes
Redo Buffers               41000960 bytes
Datenbank mounted.
Datenbank geöffnet.
SQL> archive log list
Datenbank-Log-Modus              Archive-Modus
Automatische Archivierung             Aktiviert
Archivierungsziel            E:\oracle\thetis_iv\arch
Älteste Online-Log-Sequenz     17917
Nächste zu archivierende Log-Sequenz   17919
Aktuelle Log-Sequenz           17919
SQL> alter system switch logfile;
System wurde geändert.I created a brand new archive log.
SQL> exit
Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011  15:04    <DIR>          .
06.04.2011  15:04    <DIR>          ..
06.04.2011  15:04        17.137.152 ARC17919_0721667907.001
               1 Datei(en),     17.137.152 Bytes
               2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
Kennwort für Recovery-Katalog-Datenbank:
Verbindung mit Datenbank des Recovery-Katalogs
RMAN> show all;
RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
Now I backup all archive logs, that havn't been backed up for at least two times.
RMAN> run { backup archivelog all not backed up 2 times
2>       format '%d_AR_%Y%M%D_%s_%t'
3>       tag 'ARCHIVE LOGS'
4>       DELETE ALL INPUT;
5>     }
Starten backup um 06.04.2011 15:08:01
Aktuelles Log archiviert
Zugewiesener Kanal: ORA_SBT_TAPE_1
Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
Beendet backup um 06.04.2011 15:08:10
RMAN> exit
Recovery Manager abgeschlossen.
D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011  15:08    <DIR>          .
06.04.2011  15:08    <DIR>          ..
               0 Datei(en),              0 Bytes
               2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
Thats not what I expected. Where is my mistake?

Hi,
I do new tests it's very strange.
BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
You can open a SR on MOS. (to check bugs)
I reproduce the same test and the result was the same, it seems that this is a bug.
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
RMAN> backup archivelog all not backed up 2 times delete all input;
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=15 RECID=16 STAMP=747753711
input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
Finished backup at 06-APR-11
RMAN> list archivelog all;
specification does not match any archived log in the repositoryOracle Docs Says:
The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
This command eliminates the separate step of manually deleting archived redo logs.
With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
As explained in "Configuring an Archived Redo Log Deletion Policy",
the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
But in ours case it's not honors this policy.
Only with the FORCE command should this happen. But it is not our case.
Oracle Docs:
If FORCE is not specified on the deletion commands,
then these deletion commands obey the archived log deletion policy.
If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
Alternatively you can do the following:
Set the commands separately.
Check this:
RMAN>  run {
2> backup archivelog all not backed up 2 times ;
3> delete archivelog all backed up 2 times to disk;
4> }
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=2 sequence=22 RECID=21 STAMP=747755128
input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 06-APR-11
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM

Similar Messages

  • RMAN-08591: WARNING: invalid archived log deletion policy

    Hi,
    My database is 11.2.0.1 running on OEL 5.
    We have stndby database running on other server, i have configured rman like this
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    But while running db backup, getting the error
    RMAN-08591: WARNING: invalid archived log deletion policy.
    RMAN retention policy is set to redundancy 1.
    The archive files are deleting even though they are not applied on standby.
    Thanks,

    kkrm333 wrote:
    Hi,
    My database is 11.2.0.1 running on OEL 5.
    We have stndby database running on other server, i have configured rman like this
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    But while running db backup, getting the error
    RMAN-08591: WARNING: invalid archived log deletion policy.
    RMAN retention policy is set to redundancy 1.
    The archive files are deleting even though they are not applied on standby.
    Thanks,
    bcm@bcm-laptop:~$ oerr rman 8591
    8591, 3, "WARNING: invalid archived log deletion policy"
    // *Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived
    //         log deletion policy was APPLIED but there was no mandatory
    //         archived log destinations.
    // *Action: One of the following:
    //          1) Change archived log deletion policy using CONFIGURE command
    //          2) Make one or more of standby destination as MANDATORY.

  • Question about archived logs

    Hi!
    I wonder if there is possibility to configure archiving policy in a way:
    set one destination (/arch1/oracle) as primary, and another (/arch2/oracle) as optionally.
    redo Logs will be copied to /arch2/oracle only if /arch1/oracle fails, but after it will be available again, files will be moved (or copied) from /arch2/oracle to /arch1/oracle. Anybody tried to store backup files in that way? is it possible? I tried various combinations of log_archive_dest_n and log_archive_dest_state_n parameters, but it won't work in a way I expected.
    Message was edited by:
    wojaczek

    it's about limitation of disk place on server where DB operates. Archived logs are stored on NFS filesystem, but time to time there are some problems with remote filesystem. In such cases DB will hang and manual change of arch log destination to local FS is needed. But this destination could not be set permanently because of disk space limitations.
    When i set destination 1 as mandatory and 2 as optionally db hangs when arc can't use mandatory destination.
    Setting both destinations as optionally gives finally inconsistency and storing files on local fs, what is not desirable

  • Question about imap log format.

    I hava a question about imap log file.
    Here are sample imap log lines
    [26/Dec/2005:13:21:24 +0900] mail imapd[513]: Account Notice: close [203.231.11.113] ywmoon 2005/12/26 13:21:24 0:00:00 1013 2843 2
    [26/Dec/2005:13:21:32 +0900] mail imapd[513]: Account Notice: close [203.231.14.251] hkchoi 2005/12/26 13:20:37 0:00:55 446 1196 0
    Above line...
    First line
    ywmoon : UserID
    2005/12/26 : Date
    13:21:24 : login time (hour:minute:second)
    0:00:00 : ?
    1013 : bytes from client to server
    2843 : bytes from server to client
    2 : ?
    next line
    13:20:37 : same above
    0:00:55 : ?
    446 : same above
    1196 : same above
    0 : ?
    From above, I don't know "?" mark fields.
    0:00:00 or 0:00:55 ==> expenditure time to login ? And is this "hour:minute:second" OR "minute:second:milliSecond" ?
    2 or 0 ==> 1 means INBOX. 0 and 2, what they are mean ?
    Thank you in advance...

    I hava a question about imap log file.
    Here are sample imap log lines
    [26/Dec/2005:13:21:24 +0900] mail imapd[513]: Account
    Notice: close [203.231.11.113] ywmoon 2005/12/26
    13:21:24 0:00:00 1013 2843 2
    [26/Dec/2005:13:21:32 +0900] mail imapd[513]: Account
    Notice: close [203.231.14.251] hkchoi 2005/12/26
    13:20:37 0:00:55 446 1196 0
    Above line...
    First line
    ywmoon : UserID
    2005/12/26 : Date
    13:21:24 : login time (hour:minute:second)
    0:00:00 : ?how long the connection lasted.
    1013 : bytes from client to server
    2843 : bytes from server to client
    2 : ?Number of messages?
    that's a guess. we don't actually document this stuff.
    >
    next line
    13:20:37 : same above
    0:00:55 : ?
    446 : same above
    1196 : same above
    0 : ?
    From above, I don't know "?" mark fields.
    0:00:00 or 0:00:55 ==> expenditure time to login ?
    And is this "hour:minute:second" OR
    "minute:second:milliSecond" ?
    2 or 0 ==> 1 means INBOX. 0 and 2, what they are mean
    Thank you in advance...

  • Subtitling (question about archived material)

    OK, I've looked through the archived questions about how to subtitle...and I just want to make sure I do this right. If I do subtitles in DVDSP, do I write them up in a text file first and then import them, or just type them in manually?
    If I do subtitles in FCP I just use something like Title3D and type them in manually...creating a whole buncha overlay (title) clips, right?
    Forgive the redundency, I know how subtitles are supposed to look, just trying to find the best (and least time consuming) way to produce them.
    FYI...the subtitles will be of a person from Spain speaking English (it's kinda hard to understand him since he talks fast and has a heavy Spanish accent).
    Thanks, all, in advance.
    Jonathan

    subtitling (question about archived material)< </div>
    So you are trying put subtitles on your archived material?
    If you use the subtitle track in DVDSP, the text will be switchable by the user. (This is made more complicated by several factors like your desire to make the subtitles permanent or uncontrollable by the user. These are options you can control by programming the DVDSP project. Not difficult but very confusing.)
    If you use a text tool in FCP, the titles will be permanently burned into the video image.
    If you use some fo the more sophisticated (read: Expensive) subtitling tools for FCP, you can export a caption-compliant file that can be printed to videotape or mastered to DVD. If you own one of these products, you are at the complete mercy of their manual's writer.
    bogiesan

  • RMAN,Data Guard and Archive log deletion

    Our DG environment is running Oracle 11g R2
    we have a 3 node DG environment with
    A being the Primary
    B and C being Active Data Guard Standbys
    Backups are taken off of B and go directly to tape.
    Standby Redo Logs and Fast Recovery Area are being used
    Taking recommendation from "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
    RMAN Setting on Primary ("A")
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
    RMAN Setting on Standby ("B") where Backup is done
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE
    RMAN Setting on other Standby ("C")
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
    How can we know what archive logs are eligible to be deleted from "A" and "C" ?
    When does the delete take place?
    How can we tell when the archive logs are being deleted from "A" and "C" ?

    Dear user10260925,
    The documentation that you have read is reliable but insufficient.
    The Oracle can manage the archivelog directory and knows which one is eligible for the deletion. Those stuff you have posted in here has been taken from the online documentation and is supported and can be used when the Oracle knows and manages the archivelogs. That is simply called the flash recovery area. Please read about the FRA in this very moment.
    Under normal circumstances people in the industry uses some scripts to achive the archivelog deletion on the standby system.
    Here is a useful example to you;
    # Remove old archivelogs
    00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
    vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
    export ORACLE_SID=optstby
    export ORACLE_HOME=/oracle/product/10.2.0/db_1
    cd /db/optima/archive/OPTPROD/archivelog
    /oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
    grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
    chmod 755 delete_applied_redo_logs_1.sh
    sh delete_applied_redo_logs_1.sh
    rm delete_applied_redo_logs_1.sh
    rm delete_applied_redo_logs.lst
    vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
    vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
    set echo off
    set heading off
    spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
    select 'rm -f ' || name from v$archived_log where applied = 'YES';
    spool off
    exit
    vals3:/db/optima/archive/OPTPROD/archivelog#Hope That Helps.
    Ogan

  • Archive log deletion

    Hello,
    -rw-r----- 1 oracle dba 193739264 Jun 22 13:23 1_5_754473298.dbf
    -rw-r----- 1 oracle dba 193052160 Jun 22 15:00 1_6_754473298.dbf
    -rw-r----- 1 oracle dba 492818944 Jun 22 16:14 2_161956_733073720.dbf
    -rw-r----- 1 oracle dba 491902976 Jun 22 16:14 2_161955_733073720.dbf
    -rw-r----- 1 oracle dba 193459200 Jun 22 16:14 2_161957_733073720.dbf
    -rw-r----- 1 oracle dba 193587200 Jun 22 16:14 2_161958_733073720.dbf
    -rw-r----- 1 oracle dba 193142272 Jun 22 16:14 2_161959_733073720.dbf
    rw-r----- 1 oracle dba 1024 Jun 23 23:17 1_56660_733073720.dbf
    -rw-r----- 1 oracle dba 196693504 Jun 23 23:17 2_163084_733073720.dbf
    -rw-r----- 1 oracle dba 493167104 Jun 23 23:18 2_163085_733073720.dbf
    -rw-r----- 1 oracle dba 492434944 Jun 23 23:19 2_163086_733073720.dbf
    -rw-r----- 1 oracle dba 226295808 Jun 24 04:07 c-1981727300-20110624-00
    -rw-r----- 1 oracle dba 226263040 Jun 24 10:09 52mfm6c2_1_1
    -rw-r----- 1 oracle dba 491752448 Jun 26 23:29 2_164881_733073720.dbf
    -rw-r----- 1 oracle dba 192917504 Jun 26 23:31 2_164882_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 26 23:31 1_57258_733073720.dbf
    -rw-r----- 1 oracle dba 193144320 Jun 26 23:32 2_164883_733073720.dbf
    -rw-r----- 1 oracle dba 193007616 Jun 26 23:34 2_164884_733073720.dbf
    -rw-r----- 1 oracle dba 194516480 Jun 27 23:48 2_165577_733073720.dbf
    -rw-r----- 1 oracle dba 195362816 Jun 27 23:48 2_165578_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 27 23:48 1_57490_733073720.dbf
    -rw-r----- 1 oracle dba 194276864 Jun 27 23:49 2_165579_733073720.dbf
    -rw-r----- 1 oracle dba 494327296 Jun 27 23:51 2_165580_733073720.dbf
    -rw-r----- 1 oracle dba 493318656 Jun 27 23:53 2_165581_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 27 23:56 1_57491_733073720.dbf
    -rw-r----- 1 oracle dba 193768448 Jun 27 23:56 2_165582_733073720.dbf
    -rw-r----- 1 oracle dba 193017344 Jun 28 00:10 2_165583_733073720.dbf
    -rw-r----- 1 oracle dba 197171712 Jun 28 00:12 2_165584_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 28 00:13 1_57492_733073720.dbf
    -rw-r----- 1 oracle dba 491688448 Jun 28 00:14 2_165585_733073720.dbf
    -rw-r----- 1 oracle dba 494400512 Jun 28 00:15 2_165586_733073720.dbf
    -rw-r----- 1 oracle dba 195551232 Jun 28 00:15 2_165587_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 28 00:15 1_57493_733073720.dbf
    -rw-r----- 1 oracle dba 195021824 Jun 28 00:15 2_165588_733073720.dbf
    22,23,24,26,27 of june archive log exist in archive folder when i run
    delete archivelog all completed before 'SYSDATE -1'
    this command 26 june of some archive deleted but i want to delete above 22,23,24,27 of june archive.how can i delete above dates archivelog.
    Thanks,
    Umair

    Hi;
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF X DAYS; << it says how many days you will keep your db and archive backups If you set it 2 its mean 2 days bakcup will be keep your db backups
    For your issue you can set this parameter or you can delete them manualy and then can run crosscheck from rman(Both method mention by Mdtaylor already)
    For me i am also using this:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    delete noprompt backup of archivelog until time 'sysdate-4'; << My system is keep my backups 7 days but wiht this command i can delete sysdate-4 hours archivelog from system(Dont forget it will delete wiht hour base,i mean if your time is now 10.00 am than it will delete sysdate-4 until 10.00 am, you can see 10.20 asrchivelog on your system)
    Regard
    Helios

  • Logical standby | archive log deleted | how to remove gap ???

    hi gurus...
    i have problem on logical standby
    by mistake standby log coming to logical standby has been deleted , now how to fill up the gap ???
    ON STANDBY
    SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# APPLIED
    228 674847 674872 YES
    229 674872 674973 CURRENT
    230 674973 674997 NO
    231 674997 675023 NO
    232 675023 675048 NO
    233 675048 675109 NO
    234 675109 675135 NO
    235 675135 675160 NO
    236 675160 675183 NO
    237 675183 675208 NO
    238 675208 675232 NO
    239 675232 675257 NO
    240 675257 675282 NO
    241 675282 675382 NO
    242 675382 675383 NO
    243 675383 675650 NO
    244 675650 675652 NO
    245 675652 675670 NO
    246 675670 675688 NO
    247 675688 675791 NO
    248 675791 678524 NO
    archive log are shipping to standby location also and getting registered
    ALERT LOG OF STANDBY
    Fri May 7 12:25:36 2010
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[21]: Successfully opened standby log 5: '/u01/app/oracle/oradata/BEST/redo05.log'
    Fri May 7 12:25:37 2010
    RFS LogMiner: Registered logfile [u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_248_1_715617824.dbf] to LogMiner session id [1]
    but i dont have standby log after 229 sequence ...
    ON PRIMARY
    SYS@TEST AS SYSDBA> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /u01/app/oracle/flash_recovery_area/TEST/standlogOldest online log sequence 247
    Next log sequence to archive 249
    Current log sequence 249
    what to do next to apply sequences and bring both in sync.
    please help me ,,,,
    Edited by: user12281508 on May 7, 2010 9:45 AM

    thanks for response.
    no its pure logical standby
    i have tried to ftp the archive logs of primary to standby and applied manually
    SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf';
    alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf'
    ERROR at line 1:
    ORA-01289: cannot add duplicate logfile
    SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf';
    alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf'
    ERROR at line 1:
    ORA-01289: cannot add duplicate logfile
    any other way ????

  • Question about archive destination.

    Hi All,
    When we set the archived destination to this parameter log_archive_dest like:
    SQL>alter system set LOG_ARCHIVE_DEST_.. = 'location=/archivelogpath reopen';
    Could you help me to know about 'reopen' keyword here. Please help me know, what does it mean and whats the use of it. I have failed to get this in oracle documentation.
    Best Regards,
    Michel.

    From the documentation:
    Rearchiving to a Failed Destination
    Use the REOPEN attribute of the LOG_ARCHIVE_DEST_n parameter to specify whether and when ARCn should attempt to rearchive to a failed destination following an error. REOPEN applies to all errors, not just OPEN errors.
    REOPEN=n sets the minimum number of seconds before ARCn should try to reopen a failed destination. The default value for n is 300 seconds. A value of 0 is the same as turning off the REOPEN attribute; ARCn will not attempt to archive after a failure. If you do not specify the REOPEN keyword, ARCn will never reopen a destination following an error.
    You cannot use REOPEN to specify the number of attempts ARCn should make to reconnect and transfer archived logs. The REOPEN attempt either succeeds or fails.
    When you specify REOPEN for an OPTIONAL destination, the database can overwrite online logs if there is an error. If you specify REOPEN for a MANDATORY destination, the database stalls the production database when it cannot successfully archive. In this situation, consider the following options:
    Archive manually to the failed destination.
    Change the destination by deferring the destination, specifying the destination as optional, or changing the service.
    Drop the destination.
    When using the REOPEN keyword, note the following:
    ARCn reopens a destination only when starting an archive operation from the beginning of the log file, never during a current operation. ARCn always retries the log copy from the beginning.
    If you specified REOPEN, either with a specified time the default, ARCn checks to see whether the time of the recorded error plus the REOPEN interval is less than the current time. If it is, ARCn retries the log copy.
    The REOPEN clause successfully affects the ACTIVE=TRUE destination state. The VALID and ENABLED states are not changed.

  • Archive logs deletion using VI or VIM editor

    Dear professional,
    Recently I moved from one organization to another. In my team all are deleting archive log files using VI editor, They are copying archivelog file names in new vi file and deleting simply.. Can anyone suggest me how to do that (with Deletion command)?
    Thanks
    Sagar

    Thank you for your response..
    This is the way we are deleting archivelog files after backups done to make free space in disk.
    [root@apps /]# mkdir test
    [root@apps /]# cd test
    [root@apps test]# vim test1.log
    [root@apps test]# vim test2.log
    [root@apps test]# vim test3.log
    [root@apps test]# vim test4.log
    [root@apps test]# vim test5.log
    [root@apps test]#
    [root@apps test]# ls -lrt
    total 20
    -rw-r--r-- 1 root root 23 Sep  4 20:36 test1.log
    -rw-r--r-- 1 root root 17 Sep  4 20:36 test2.log
    -rw-r--r-- 1 root root  7 Sep  4 20:36 test3.log
    -rw-r--r-- 1 root root 14 Sep  4 20:37 test4.log
    -rw-r--r-- 1 root root 14 Sep  4 20:37 test5.log
    [root@apps test]# vim list
    test1.log
    test2.log
    test3.log
    test4.log
    test5.log
    :wq
    [root@apps test]# cat list
    test1.log
    test2.log
    test3.log
    test4.log
    test5.log
    [root@apps test]# rm -R `cat list`
    [root@apps test]# ls
    list
    [root@apps test]# rm list
    [root@apps test]# ls
    [root@apps test]#
    Thanks

  • Auto archive log deletion from single location out of multiple locations.

    Hi,
    I am running database on 11r1 version.
    I have set two archive log locations. now i want archive logs to be deleted through RMAN from only one location the other location shouldn't be affected. what are the specific parameters to be set. Is there any specific command for this please advise.
    Thanks in advance.

    If you see Hemant's reply in the below link, he had shown how to delete archives from 1 location.
    RMAN backup with 2 archive log locations

  • Archived logs deletion

    Hi
    I Have deleted 3 of my archivedlogs manually,but they have not marked deleted in V$ARCHIVED_LOG .
    so when i'm trying to backup my remained archived logs in RMAN.It doesn't back them up.because RMAN has not been notified with thw deletion.So..
    How can I notify RMAN & mark them deleted in V$ARCHIVED_LOG.
    Thanks

    hi
    use crosscheck
    SQL> select name from v$archived_log;
    NAME
    D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\O1_MF_1_
    25_2PC98N8M_.ARC
    D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\O1_MF_1_
    26_2PC9CZF4_.ARC
    C:\>del D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\
    *.ARC
    C:\>sqlplus "sys as sysdba"
    SQL*Plus: Release 10.1.0.2.0 - Production on Thu Nov 23 18:54:39 2006
    Copyright (c) 1982, 2004, Oracle.  All rights reserved.
    Enter password:
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> select name from v$archived_log;
    NAME
    D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\O1_MF_1_
    25_2PC98N8M_.ARC
    D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2006_11_23\O1_MF_1_
    26_2PC9CZF4_.ARC
    SQL> host rman target=sys
    Recovery Manager: Release 10.1.0.2.0 - Production
    Copyright (c) 1995, 2004, Oracle.  All rights reserved.
    target database Password:
    connected to target database: ORCL (DBID=1134976990)
    RMAN> crosscheck archivelog all;
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=215 devtype=DISK
    validation failed for archived log
    archive log filename=D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
    G\2006_11_23\O1_MF_1_25_2PC98N8M_.ARC recid=1 stamp=607282901
    validation failed for archived log
    archive log filename=D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
    G\2006_11_23\O1_MF_1_26_2PC9CZF4_.ARC recid=2 stamp=607283007
    Crosschecked 2 objects
    RMAN> delete expired archivelog all;
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=215 devtype=DISK
    List of Archived Log Copies
    Key     Thrd Seq     S Low Time  Name
    1       1    25      X 23-NOV-06 D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\OR
    CL\ARCHIVELOG\2006_11_23\O1_MF_1_25_2PC98N8M_.ARC
    2       1    26      X 23-NOV-06 D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\OR
    CL\ARCHIVELOG\2006_11_23\O1_MF_1_26_2PC9CZF4_.ARC
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted archive log
    archive log filename=D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
    G\2006_11_23\O1_MF_1_25_2PC98N8M_.ARC recid=1 stamp=607282901
    deleted archive log
    archive log filename=D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
    G\2006_11_23\O1_MF_1_26_2PC9CZF4_.ARC recid=2 stamp=607283007
    Deleted 2 EXPIRED objects
    SQL> select name,deleted from v$archived_log;
    NAME
    DEL
    YES
    YESHope this helps
    Taj

  • Recovery question using archive log

    HPUX 11X
    Oracle 10.2.0.2
    I have a standby database that the customers want to test the ability to fail over. They also want to test the data integrity of the standby once it's brought on line as the primary.
    I've already told the customer that any writes that they do on the standby during the test time WILL be lost. I plan on doing a incomplete recovery back to a specific sequence number / archive log when the tests are complete.
    My plan is to take note of the current sequence number just before I bring the standby live. When all is said and done, I was going to do a recover back to the sequence number one PRIOR to that one. Then when I place the db back in standby mode, it will sync back up to the primary.
    What I need to know is if this is a good or a bad idea. Should I plan on doing it differently and for what reason.
    Thanks! :)

    Use flashback database to recover the former primary database to a new standby.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
    Therefore the changes made on standby won't be lost (unless you want to lose them).
    If your databases do not have Flashback Database feature enabled, you can use incomplete recovery instead.
    I think Flashback Database should be your first option.

  • About archive log issue

    DB version: 11.1.0.7
    when I issue cmd " alter system archive log current", the alertlog raise error "Thread 1 cannot allocate new log, sequence 149, Private strand flush not complete".
    I think it's normal, because in the log file , here some dirty data have NOT been written to the data_files, so it can raise the error Private strand flush not complete.
    BUT in my point, when I issue the cmd "alter system checkpoint" and then, subsequently, I issue the " alter system archive log current", there shoud not raise any error" becasue the dirty data already been written via the cmd "alter system checkpoint". but in the alertlog the error still here (Private strand flush not complete).
    that's why, How can I understand that. thanks!

    To understand it, please check Doc 372557.1 Alert Log Messages: Private Strand Flush Not Complete
    and
    cannot allocate new log&Private strand flush not complete
    Edited by: Fran on 25-jun-2012 1:07

  • Question about frequent log switches

    I support an Oracle 10g database (10.2.0.4) and database activity has increase to the point that, during the heaviest parts of the day, log switches are occurring too frequently (15 - 20 times per hour!). We also utilize Data Guard to replicate the database to our DR site. We currently have 2 log groups with 2 membes in each group.
    I understand that I can tackle this issue 2 ways: either to increase the size of my redo log files (they are currently at 50 Meg each), or I can add additional redo log groups to the database.
    I would like to get some opinions on whether on solution is better than the other, or the pros and cons of each course of action.
    Thank you in advance for your advice with my question!

    CowTown_dba wrote:
    Thanks for helping me to understand my true problem. The issue is that because of the frequent log switches, database performance is degrading.Maybe that's the cause, maybe it isn't.
    Users are complaining about slow response. So if I add more groups it will buy the archiver extra time but it will not help with the slow response issue.Depends on the root cause of the slow response issue. That has yet to be determined. While it may be true that your car has a short in the electrical system and your car doesn't start, it doesn't necessarily follow that the car doesn't start because of the short in the electrical system.
    >
    I really appreciate everyone contributing to my understanding of the issue, and helping clarify the root problem so that I can fix it the first time around.
    You guys rock!

Maybe you are looking for