Automatically removing archive logs

I'm currentyl running level 0 and level 1 backups and then removing archive logs using the following command:
backup incremental level 0 database diskratio=0 plus archivelog delete input;
I want to retain a weeks worth of archive logs on disk, I'd like to still use RMAN to manage the archive logs. Any suggestion how I would do so?
TIA

Don't use the DELETE INPUT and have another delete command that deletes the archivelogs once you know the backup was successful.
RMAN> delete noprompt archivelog all completed before 'sysdate - 7';

Similar Messages

  • Cleanup job to remove archive logs automatically through OEM Grid control

    Hi All,
    I am working on 11gR2 3node RAC database. we have enabled archivelog mode for the databases and don't have any backup processes (like rman) and not using ASM.
    Please let me know how to cleanup the old archivelogs automatically through oem Grid control.
    I have some idea how to do it in standalone database, but not sure how it works in RAC environment through OEM. Please let me know.
    Thanks in advance.

    Hari wrote:
    Thanks for your reply and The requirement is, put the DB in archive log mode and cleanup the old archive logs which is more than 5days. We are doing this because of space issue and don't have backup for these files and the DB must be in archive log mode.
    I have few question here.
    1. Is it must to take the backup of the archive log files and before delete them?No, but if you aren't backing up, why create the archivelogs in the first place?
    2. If i delete them without backup, what is the negative impact?If you aren't backing up the database in the first place (as you stated in an earlier post) then it really doesn't matter what you do with the archivelogs as they are worthless anyway.
    3. What is the recommended process to do it?My recommendation is you first start using rman to backup the database
    4. I need to setup this process through OEM grid control.
    Please let me know.
    Thanks,
    HariIt all begs the question which has already been asked and you avoided answering . . . if you are not taking backups, why bother archiving? The archive logs have ZERO VALUE outside of a consistent backup strategy. So how is it you have a 'requirement' to run in archivelog mode but no requirement for backups?
    Edited by: EdStevens on Dec 2, 2011 9:30 PM

  • How to remove archive log files from ASM managed 11g R2 database?

    Hi,
    I am planning to automate deletion of older archive log files from my 11g R2 Production instance which is ASM managed.
    Also want to remove the archive log files files from standby database.
    Please provide your inputs on how can I remove the older archive log files.
    Regards,
    Avinash

    Greetings
    Did you check RMAN,
    RMAN>show all;
    CONFIGURE RETENTION POLICY . . . .
    CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
    DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
    DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-10';
    This will be part of your RMAN Backup scripts/process
    Check the urls below:
    11gRel2:
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmmaint.htm#BRADV90079
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmmaint.htm#BRADV89634
    10g:
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14193/toc.htm#sthref45
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1008093
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/maint003.htm#sthref712
    Regards & Thanks
    BN

  • How to remove archive log files using Enterprise Manger

    Hi,
    I took backup of the archive log files and i deleted those files at OS level but it is not reflecting in the Enterprise Manager it is showing the same. Can any one help in how to delete the archive log files by using Enterprise Manger.
    version 10.2.0.1.0
    any help is appreciated.
    Regards,
    Ashraf

    I have the same problem. I have 10gr1 and 10gr2 on different servers. On 10gr1, under administration/manage current backup/image, I can see archivelog files, and can mange them. But on 10gr2, the image doesn't show archivelog files. I can only remove them using rman. I wonder if it's because the different design on 10gr2 or I missed something when setup the backup?

  • Removing archived log files

    Hello all,
    Using Oracle 10g R2 ( 10.2.4.0) under UNIX Sun Solaris 10 , I have two rman backup types
    1-L0 backup
    2-L1 Backup ( Incremental cummulative)
    Facts:
    -Due to space pressure on archived log destination I'm trying to get less archived files possible under the archived log fs thus at any given time the archived log files destination contains archived log files aged no more than 22hours.
    * The backup runs each day at 4PM and there is custom script that remove and compressed archived log files ( out of backup jobs windows) from midnight until 3:45PM
    * From the above removal schedule task L0 or L1 backup will always have 24 hours worth of archived log files available during the backup.
    -The Backup files Windows retention period is 22 hours meaning that each backup type L0 or L1 removes previous backup files aged more than 22hours.
    -Tracking file is enabled
    Target:
    Knowing that our backup retention windows is 22hours.
    Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup.
    Would this affect L1 backup? and how?
    Thank in advance for your response
    Alex

    user8979607 wrote:
    Hello all,
    Using Oracle 10g R2 ( 10.2.4.0) under UNIX Sun Solaris 10 , I have two rman backup types
    1-L0 backup
    2-L1 Backup ( Incremental cummulative)
    Facts:
    -Due to space pressure on archived log destination I'm trying to get less archived files possible under the archived log fs thus at any given time the archived log files destination contains archived log files aged no more than 22hours.
    * The backup runs each day at 4PM and there is custom script that remove and compressed archived log files ( out of backup jobs windows) from midnight until 3:45PM
    * From the above removal schedule task L0 or L1 backup will always have 24 hours worth of archived log files available during the backup.
    -The Backup files Windows retention period is 22 hours meaning that each backup type L0 or L1 removes previous backup files aged more than 22hours.
    -Tracking file is enabled
    Target:
    Knowing that our backup retention windows is 22hours.
    Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup.
    Would this affect L1 backup? and how?
    Thank in advance for your response
    AlexI'm not sure what you are talking about with Backup files Windows retention period ... 22 hours".
    I don't know what you mean by "Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup."
    If you are not taking your database backups with rman you are on shaky ground. The principles are simple. To recover your database from a failure, you will need to start with an L0 backup. The rman RESTORE command will then restore individual blocks from any applicable and available L1 backups. You would follow that with a RECOVER command, that would attempt to apply all necessary redo from available archivelogs. If the necessary archivelogs have been deleted, rman will attempt to restore them from a backup. You can use rman to backup AND DELETE archivelog files to keep the archivelog destination cleaned out.
    I take an L0 backup once a week, an L1 the other 6 days, and archivelogs twice a day. The only time I've had a problem with the archivelog dest filling up is when some buggy code that has a loop goes into production and starts flooding redo.
    Exactly how are you taking your database backups? If you are not using rman, then you are already on shaky ground.

  • Remove archived logs

    dear all,
    scenario:
    day1: i put the database in archive log. Then i had a cold_backup.
    day2: i saw that this archive logs copy in flash_recovery_area. Everything ok.
    day3: i put the db in NOARCHIVEMODE. Then the creation of the archive files stopped. And i had another cold_backup.
    This is a test database. but i have a little problem...
    How i could delete archived files in order to remove physically from OS and its not view from EM ??
    I deleted the first directory created when i configured archivelog mode from OS but when i saw through EM, it appears.
    version: 10gr2
    OS. RHES VERSION3
    thanks a lot.

    You see still these archivelogs in EM,because they are still recorded in the controlfiles. Oracle does not recognize, when archivelogs are removed on OS level. After 'CONTROL_FILE_RECORD_KEEP_TIME' number of days Oracle will start to reuse records in the controlfiles, so sometime these orphan entries will disappear.
    To avoid such inconsistencies move to RMAN as backup/recovery tool.
    Werner

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

  • Purge archive logs standby database

    How can I purge automaticly the archives logs in the standby database?
    I have oracle versión 11.2.0.2 with +ASM in solaris.
    Thanks.

    My bad.
    Will update my notes.
    This is still there :
    Applied Archivelogs Are Not Deleted On Physical Standby Site from Flash Recovery Area [ID 404338.1]
    Since you have your DELETION POLICY set correctly you can also run something like this on the Standby :
    run {
    allocate channel for maintenance device type disk;
    delete archivelog until time 'sysdate -5';
    }Best Regards
    mseberg
    Edited by: mseberg on Aug 16, 2012 4:36 AM

  • Changing archive log mode without shutting down database

    Hi all,
    Is there any way to set the database to archive log mode before shutting down the database and when the database shuts and starts, the database should be automatically in archive log mode?
    because we can not shutdown the database in weekdays and we have system reboot on weekend and we are not here on that day. So is there a way to set the database in archive log at the memory level so that when the database reboots, it should automatically start in archive log mode.
    my environment is windows server 2008 R2 with oracle 11.2.0.3
    Thanks in advance.
    Edited by: 931643 on Dec 5, 2012 10:37 AM

    931643 wrote:
    thank you for the reply Max Seleznev,
    First I thought of writing script in order to include in that process. But we can not run any commands in the sqlplus using the windows jobs. for eg:
    you can write a batch file as below:
    cd \
    sqlplus / as sysdba
    select name,open_mode from v$database;
    when you run this, it will open until sqlplus prompt but then will not execute the query.
    What did you expect? Well, actually, I know what you expected. But think about it for a second. You have a batch file with the mentioned three lines. How does that batch file get processed .. what is happening when it is being processed?
    It is not being processed by sqlplus, it is being processed by the windows command processor. Just like the cmd.exe. Each line is read by the command processor and executed accordingly. So ....
    cd \the command processor calls 'cd' , and passes the value '\' to do with as it sees fit. 'cd' then changes the current directory of the session to whatever is indicated by the passed parameter. in this case, that value is '\' , so the resulting current directory is the base (root, in *nix terms) of the current drive.  When 'cd' has finished, it returns control to the command processor, who then reads the next line ....
    sqlplus / as sysdbathe command processor calls sqlplus.exe and passes it the command line parms '/ as sysdba' to do with as it (sqlplus) sees fit. sqlplus does whatever it does with what it has been given In this case it tries to connect to whatever local database is indicated by the value of ORACLE_SID, then waits for more input. Whenever sqlplus exits (how does it know to exit?) it returns control to the command processor, who then reads the next line ....
    select name,open_mode from v$database;The command processor will read this line and attempt to find an executable file named 'select' and pass it the rest of the command line 'name,open_mode from v$database;'
    Hmm, what do you suppose will happen with that operation?
    that is the reason I am figuring out whether there is an alternate way.yes but you have to use the proper technique. And since you are building this into a production stop/start without testing the actual stop/start commands ... what do you suppose will be the outcome if something goes wrong?
    After hours and weekend work is one reason DBA's make more money than developers.
    >
    Thanks

  • To clear db2 archive log after db2 database backup

    After db2 backup archive log remains as it is.is there setting to remove archive logs after database backup.DAS is not installed.
    DB2 9.1 FP 6
    os HP unix

    Hello Anand,
    If the archvied logs are not required, ie they are not required for restore    
    you can remove them. 
    You can check this is by running                                                                               
    db2 list history all for db <sid>                                                                               
    The above command will give you a detailed overview of the backup           
    history and what logs were archived and what logs were included or needed for restore of backups.
    If they are no longer needed for a restore, then it is safe to remove them.
    Kind regards,
    Paul

  • Data Guard archive log remove

    Hi,
    I am using 9i Data Guard now. I try to set up automatic procedure to remove the archive log on the standby site once it got applied. But except the manual remove/delete, there is no option to set the automatic procedure in Oracle Data Guard setting.
    Do anyone has solution for it?
    Thanks

    user3076922 wrote:
    Hi
    Standby database configured with broker and applying the redo in really time; however, I want to change this to archive log apply mode without losing the broker configuration. Is it possible? If it is not possible to use broker to do archive log apply, can I remove the broker and use data guard to set up the standby to use archive log apply?
    RegardsHi
    I think mseberg is answered correct, you can use enable/disable apply log with change of state on standby database with DGMGRL, as writen mseberg.
    or you can disable recover standby database with following script from SQL*Plus.
    SQL> alter database recover managed standby database cancel;Regards
    Mahir M. Quluzade
    www.mahir-quluzade.com

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

  • Archive log automatically getting deleted

    Hi,
    My Archive logs are getting automatically deleted from ASM. I keep my Archive logs in FRA. My alert log shows deletions like this:
    Deleted Oracle managed file +DATA1/orcl/archivelog/...Retention policy to recovery window is set to 24 days. The +DATA1 ASM disk has lots of free space. Archivelog deletion policy is set to None and I don't run archive deletion from rman too...
    Is there any other option I need to check?

    Thank you werner,
    Below queries show that I already have space in FRA...
    SQL> select (SPACE_LIMIT/1024/1024/1024), (SPACE_USED/1024/1024/1024), (SPACE_RECLAIMABLE/1024/1024/1024) from v$recovery_file_dest;
    (SPACE_LIMIT/1024/1024/1024) (SPACE_USED/1024/1024/1024) (SPACE_RECLAIMABLE/1024/1024/1024)
                             500                  36.6706381                          3.2632184
    SQL>
    SQL> select * from v$flash_recovery_area_usage;
    FILE_TYPE                            PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
    CONTROLFILE                                         .02                         0               1
    ONLINELOG                                           .12                         0              12
    ARCHIVELOG                                         1.03                       .65              29
    BACKUPPIECE                                           0                         0               0
    IMAGECOPY                                             0                         0               0
    FLASHBACKLOG                                       6.36                      6.15             125
    6 rows selected.
    SQL>See my alert log after some "alter system switch logfile;"
    Tue Apr 27 11:17:46 2010
    Thread 1 advanced to log sequence 83570
      Current log# 109 seq# 83570 mem# 0: +DATA1/orcl/onlinelog/group_109.19715.679998731
      Current log# 109 seq# 83570 mem# 1: +DATA1/orcl/onlinelog/group_109.20362.679998737
    Tue Apr 27 11:17:47 2010
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_3_seq_90114.17125.717358729
    Deleted Oracle managed file +DATA1/orcl/flashback/log_74.12659.717340839
    Deleted Oracle managed file +DATA1/orcl/flashback/log_85.18441.717351679
    Deleted Oracle managed file +DATA1/orcl/flashback/log_8.11194.717355103
    Deleted Oracle managed file +DATA1/orcl/flashback/log_9.12991.717355123
    Deleted Oracle managed file +DATA1/orcl/flashback/log_10.17043.717355141
    Deleted Oracle managed file +DATA1/orcl/flashback/log_1.15281.717355097
    Deleted Oracle managed file +DATA1/orcl/flashback/log_79.13174.717355163
    Deleted Oracle managed file +DATA1/orcl/flashback/log_138.15374.717355185
    Deleted Oracle managed file +DATA1/orcl/flashback/log_139.19996.717357319
    Tue Apr 27 11:17:48 2010
    Thread 1 advanced to log sequence 83571
      Current log# 105 seq# 83571 mem# 0: +DATA1/orcl/onlinelog/group_105.12632.679998535
      Current log# 105 seq# 83571 mem# 1: +DATA1/orcl/onlinelog/group_105.15649.679998539
    Tue Apr 27 11:17:49 2010
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_2_seq_87077.21363.717362485
    Tue Apr 27 11:17:49 2010
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_4_seq_87136.11714.717365975
    Deleted Oracle managed file +DATA1/orcl/flashback/log_129.20212.717344739
    Deleted Oracle managed file +DATA1/orcl/flashback/log_140.11185.717358727
    Deleted Oracle managed file +DATA1/orcl/flashback/log_5.21454.717358739
    Deleted Oracle managed file +DATA1/orcl/flashback/log_11.15673.717358753
    Deleted Oracle managed file +DATA1/orcl/flashback/log_87.12289.717358783
    Deleted Oracle managed file +DATA1/orcl/flashback/log_12.21878.717358779
    Deleted Oracle managed file +DATA1/orcl/flashback/log_141.17658.717358807
    Deleted Oracle managed file +DATA1/orcl/flashback/log_143.20355.717358847
    Deleted Oracle managed file +DATA1/orcl/flashback/log_142.15020.717358817
    Deleted Oracle managed file +DATA1/orcl/flashback/log_145.11651.717358889
    Deleted Oracle managed file +DATA1/orcl/flashback/log_137.13239.717351771
    Deleted Oracle managed file +DATA1/orcl/flashback/log_86.20900.717355183
    Deleted Oracle managed file +DATA1/orcl/flashback/log_147.11174.717362357
    Deleted Oracle managed file +DATA1/orcl/flashback/log_146.10495.717358957
    Deleted Oracle managed file +DATA1/orcl/flashback/log_149.14900.717362391
    Deleted Oracle managed file +DATA1/orcl/flashback/log_150.19760.717362403
    Deleted Oracle managed file +DATA1/orcl/flashback/log_14.20074.717362515
    Deleted Oracle managed file +DATA1/orcl/flashback/log_148.12779.717362383
    Deleted Oracle managed file +DATA1/orcl/flashback/log_13.15276.717362485
    Deleted Oracle managed file +DATA1/orcl/flashback/log_151.13222.717365933
    Deleted Oracle managed file +DATA1/orcl/flashback/log_152.21251.717365947
    Tue Apr 27 11:17:53 2010
    Thread 1 advanced to log sequence 83572
      Current log# 104 seq# 83572 mem# 0: +DATA1/orcl/onlinelog/group_104.18737.679998357
      Current log# 104 seq# 83572 mem# 1: +DATA1/orcl/onlinelog/group_104.17641.679998363
    Tue Apr 27 11:17:53 2010
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_1_seq_83563.18107.717366141
    Tue Apr 27 11:17:54 2010
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_4_seq_87137.10526.717366139
    Deleted Oracle managed file +DATA1/orcl/flashback/log_153.20718.717365963
    Deleted Oracle managed file +DATA1/orcl/flashback/log_17.21619.717365977
    Deleted Oracle managed file +DATA1/orcl/flashback/log_18.20172.717365989
    Deleted Oracle managed file +DATA1/orcl/flashback/log_19.12078.717366005
    Deleted Oracle managed file +DATA1/orcl/flashback/log_48.19221.717366017
    Deleted Oracle managed file +DATA1/orcl/flashback/log_154.14279.717366053
    Deleted Oracle managed file +DATA1/orcl/flashback/log_155.14745.717366079
    Deleted Oracle managed file +DATA1/orcl/flashback/log_156.17031.717366101
    Tue Apr 27 11:18:07 2010
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_2_seq_87079.20751.717379897
    Deleted Oracle managed file +DATA1/orcl/flashback/log_157.10653.717366127
    Deleted Oracle managed file +DATA1/orcl/flashback/log_144.17927.717358881
    Deleted Oracle managed file +DATA1/orcl/flashback/log_2.18495.717366169
    Deleted Oracle managed file +DATA1/orcl/flashback/log_20.16857.717369567
    Deleted Oracle managed file +DATA1/orcl/flashback/log_16.12724.717363263
    Deleted Oracle managed file +DATA1/orcl/flashback/log_23.13471.717369587
    Deleted Oracle managed file +DATA1/orcl/flashback/log_89.16244.717369613
    Deleted Oracle managed file +DATA1/orcl/flashback/log_88.11076.717369605
    Deleted Oracle managed file +DATA1/orcl/flashback/log_158.11103.717369643
    Deleted Oracle managed file +DATA1/orcl/flashback/log_159.21379.717369685
    Deleted Oracle managed file +DATA1/orcl/flashback/log_15.22226.717362555
    Deleted Oracle managed file +DATA1/orcl/flashback/log_160.13946.717369711
    Deleted Oracle managed file +DATA1/orcl/flashback/log_6.14447.717369491
    Deleted Oracle managed file +DATA1/orcl/flashback/log_24.11233.717373129
    Deleted Oracle managed file +DATA1/orcl/flashback/log_76.10929.717373141
    Deleted Oracle managed file +DATA1/orcl/flashback/log_90.12864.717373157
    Deleted Oracle managed file +DATA1/orcl/flashback/log_163.13475.717373171
    Deleted Oracle managed file +DATA1/orcl/flashback/log_164.20384.717373187
    Deleted Oracle managed file +DATA1/orcl/flashback/log_165.15963.717373215
    Deleted Oracle managed file +DATA1/orcl/flashback/log_166.20629.717373249
    Deleted Oracle managed file +DATA1/orcl/flashback/log_167.21197.717373279
    Deleted Oracle managed file +DATA1/orcl/flashback/log_161.13500.717369751
    Deleted Oracle managed file +DATA1/orcl/flashback/log_25.13335.717373553
    Deleted Oracle managed file +DATA1/orcl/flashback/log_162.17288.717372027
    Deleted Oracle managed file +DATA1/orcl/flashback/log_22.20002.717372205
    Deleted Oracle managed file +DATA1/orcl/flashback/log_91.16639.717376749
    Deleted Oracle managed file +DATA1/orcl/flashback/log_92.15382.717376759
    Deleted Oracle managed file +DATA1/orcl/flashback/log_169.19652.717376787
    Deleted Oracle managed file +DATA1/orcl/flashback/log_170.14527.717376801
    Deleted Oracle managed file +DATA1/orcl/flashback/log_168.10371.717376781
    Tue Apr 27 11:21:28 2010
    Thread 1 advanced to log sequence 83573
      Current log# 103 seq# 83573 mem# 0: +DATA1/orcl/onlinelog/group_103.11697.679998293
      Current log# 103 seq# 83573 mem# 1: +DATA1/orcl/onlinelog/group_103.21923.679998297
    Tue Apr 27 11:21:28 2010
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_1_seq_83564.19690.717379897
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_2_seq_87080.11232.717383337
    Tue Apr 27 11:22:10 2010
    Deleted Oracle managed file +DATA1/orcl/flashback/log_26.12608.717374927
    Deleted Oracle managed file +DATA1/orcl/flashback/log_27.12714.717380335
    Deleted Oracle managed file +DATA1/orcl/flashback/log_33.17297.717380353
    Deleted Oracle managed file +DATA1/orcl/flashback/log_34.14547.717380371
    Deleted Oracle managed file +DATA1/orcl/flashback/log_36.17079.717380389
    Deleted Oracle managed file +DATA1/orcl/flashback/log_93.18491.717380407
    Deleted Oracle managed file +DATA1/orcl/flashback/log_174.10790.717380465
    Tue Apr 27 11:22:11 2010
    Thread 1 advanced to log sequence 83574
      Current log# 108 seq# 83574 mem# 0: +DATA1/orcl/onlinelog/group_108.15776.679998703
      Current log# 108 seq# 83574 mem# 1: +DATA1/orcl/onlinelog/group_108.13383.679998709
    Tue Apr 27 11:22:11 2010
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_1_seq_83566.16358.717383421
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_4_seq_87141.11563.717383423
    Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_3_seq_90119.12158.717383423
    Tue Apr 27 11:22:25 2010Edited by: OSSGeek on Apr 27, 2010 12:49 AM

  • Script for automatic delete of archive logs/redologs

    Hi Experts,
    Do you have any idea on how to create a shell script. Actually the function of it, is to automatically deletes the archive logs/redologs if reaches the limit. Or is there any parameter to change to set the automatic deletion of archive logs/redologs.
    Regards

    Hi,
    at first, archivelogs should always be saved to tape before you delete them. If you don't want to backup them, may be for a test system, you can suppress them in ORACLE instead to delete them later.
    You can run the database in "NOARCHIVE LOG MODE". If you do so, the online redologs are not archived, they are still reused and overwritten. You can not run an online Backup, when the database is in noarchive log mode. If you want to backup the database, you have to run an offline backup.
    Do not use the NOARCHIVE LOG MODE for production or developemet systems.
    To change the archive log mode:
    shutdown the database
    startup mount;
    alter database noarchivelog;
    alter database open;
    archive log list       will show the actual status
    regards Ulrich

  • How to removed the 300GB old archive logs???

    Dear Gurus
    Site-A
    Our Environment:
    Live Production 2-Node RAC Oracle10g r2 10.2.0.4
    Data and Archive is stored in Oracle ASM
    Operating System: Sun Solaris10 64bit
    We have two databases.
    ==>db-1(Site-A db-1 is Oracle streaming with Site-B db-1,so archive logs should not be deleted which is required for oracle streaming)
    ==>db-2
    Existing Backup and Recovery Strategy:
    Daily logical backup of application schema using DATA PUMP.
    We have not taken any RMAN Backup still.
    Please find the status of Shared Storage.
    -bash-3.00$ asmcmd
    ASMCMD> lsdg
    State Type Rebal Unbal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name
    MOUNTED EXTERN N N 512 4096 1048576 614256 577801 0 577801 0 DATA/
    MOUNTED EXTERN N N 512 4096 1048576 298948 38635 0 38635 0 FLASH/
    We want to removed the old archive logs?
    Please suggest the best way of removed the old archive logs for db-2 and db-1?
    Can you Please suggest that how many time and how many space it's required for completed the backup?
    Regards
    Hitesh Gondalia
    Edited by: hitgon on Oct 1, 2011 9:50 PM
    Edited by: hitgon on Oct 1, 2011 10:09 PM
    Edited by: hitgon on Oct 1, 2011 10:13 PM

    You should consider using RMAN for backup/recovery. Logical exports (Data Pump) are useful for some purposes, but are not the preferred way to go for your backup and recovery needs. RMAN will give you better performance and so much more options.
    Long-term, a great way to delete archivelog backups is via RMAN “backup archivelog …. delete input” and/or “delete archivelog … “commands.
    Please delete archivelogs only after they are already backed up. RMAN will also take into consideration if the backups are needed for Streams and/or Standby.
    About the backup space – a full RMAN backup is typically smaller than the size of your DB. You need to run a test to see the exact size. The frequency and type of backup should be based on your SLE for this DB.
    Iordan Iotzov
    http://iiotzov.wordpress.com/

Maybe you are looking for

  • Heaviest performance issue impacting business Free Pct showing 9.41%

    Dears, We are facing heaviest performance issue on our database and and Application, Our Key users Oracle Techno functional consultant complaining that when "Free Pct" was 18% performance was excellent but now the "Free Pct" has reached to 9.41%. Am

  • 1415 fnw printer wireless connection extremely slow or not working with OS X, works with windows

    The wireless connection to the printer is either extremely slow or not working at all on OS X Yosemite.  It shows up in the list of printers in Bonjour in Safari, and I can connect to parts of the web interface if I wait a very long time.  However, I

  • Work flow & SRM configuration step by step guide

    Hello All.... Please send me the Work flow DOcumnetation related to SRM/EBP Thanks in Advance and points rewarded. Arshad

  • Facebook erroe 2405

    I have had a Blackberry Curve for several months now and I am quite happy with it. I have used facebook intensively from it. However, three days ago it just disconnected from facebook without me doing anything for this to happen. I try to log in, and

  • T530, mSata not safe for use as OS drive?

    According to the User manual, an mSata drive should not be used as an OS drive. "If your computer is equipped with both a hard disk drive and an mSATA solid state drive, you are not recommended to use the mSATA solid state drive as a bootable device.