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

Similar Messages

  • 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';

  • 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

  • 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

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

  • 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

  • How to view v$_sql_bind_capture bind values through EM Grid Control?

    Last week I stumbled upon having the options to show the bind variables to a sql statement. I can no longer find how to get back to this. Can someone guide me to the spot?
    Regards,
    Joe

    there are intresting undocumented dbms_xplan.display_cursor options for bind values and I guess these strange data inside v$sql.bind_data is input for these options, like;
    dbms_xplan.display_cursor(sql_id, 0, 'basic +PEEKED_BINDS')
    dbms_xplan.display_cursor(sql_id, 0, 'ADVANCED')
    dbms_sqltune.extract_binds(bind_data) http://optimizermagic.blogspot.com/2008/02/displaying-and-reading-execution-plans.html
    http://arkzoyd.blogspot.com/2007/04/valeurs-des-variables-bind-sans-10046.html
    SELECT t2.*, t1.sql_id, t1.elapsed_time
      FROM (SELECT *
              FROM v$sql b
             WHERE b.bind_data IS NOT NULL
               AND b.parsing_schema_name NOT LIKE 'SYS%') t1,
           TABLE(dbms_xplan.display_cursor(t1.sql_id,
                                           0,
                                           'basic +PEEKED_BINDS')) t2;
    SELECT dbms_sqltune.extract_binds(bind_data) bind, sql_text
      FROM v$sql
    WHERE sql_id = '07w3mujspwj2q';If somehow I can guarantee v$sql.bind_data to be published for each bind value and kept stored in AWR I guess I will be able to handle this problem, still investigating :)
    Thank you for your intrest.

  • Monitoring the Hyperion Essbase Database through OEM.

    Hi DBAs,
    I have setup the Hyperion Planning application (on windows 2003 server 64bit) with Essbase DB and Oracle (10.2.0.3) RDBMS (on Linux 5.3 64bit). I want to monitor the Planning Applicatoin and Essbase DB through OEM Grid Control. I have already installed the agent on Windows and Linux Server. Only able to monitor the Oracle RDBMS.
    Can someone guide me how I can monitor the Essbase DB? Also how can I setup the Hyperion Planning Application with OEM ?
    Thanks
    -Samar-

    See the below link
    http://www.oracle.com/technology/products/bi/epm/pdf/sys9_oem_integration.pdf
    It may help,
    Regards,
    http://www.oracleracexpert.com
    Click here to [Send EMAIL using UTL_MAIL in Oracle 10g |http://www.oracleracexpert.com/2009/11/send-email-using-utlmail-in-oracle-10g.html]
    Click here for [Backup and Restore SPFILE and PFILE|http://www.oracleracexpert.com/2009/11/oracle-spfile-and-pfile.html]

  • Problem about space management of archived log files

    Dear friends,
    I have a problem about space management of archived log files.
    my database is Oracle 10g release 1 running in archivelog mode. I use OEM(web based) to config all the backup and recovery settings.
    I config "Flash Recovery Area" to do backup and recovery automatically. my daily backup schedule is every night at 2:00am. and my backup setting is "disk settings"--"compressed backup set". the following is the RMAN script:
    Daily Script:
    run {
    allocate channel oem_disk_backup device type disk;
    recover copy of database with tag 'ORA$OEM_LEVEL_0';
    backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
    the retention policy is the second choice, that is "Retain backups that are necessary for a recovery to any time within the specified number of days (point-in-time recovery)". the recovery window is 1 day.
    I assign enough space for flash recovery area. my database size is about 2G. I assign 20G as flash recovery area.
    now here is the problem, through oracle online manual, it said oracle can manage the flash recovery area automatically, that is, when the space is full, it can delete the obsolete archived log files. but in fact, it never works! whenever the space is full, the database will hang up! besides, the status of archived log files is very strange, for example, it can change "obsolete" stauts from "yes" to "no", and then from "no" to "yes". I really have no idea about this! even though I know oracle usually keep archived files for some longer days than retention policy, but I really don't know why the obsolete status can change automatically. although I can write a schedule job to delete obsolete archived files every day, but I just want to know the reason. my goal is to backup all the files on disk and let oracle automatically manage them.
    also, there is another problem about archive mode. I have two oracle 10g databases(release one), the size of db1 is more than 20G, the size of db2 is about 2G. both of them have the same backup and recovery policy, except I assign more flash recovery area for db1. both of them are on archive mode. both of nearly nobody access except for the schedule backup job and sometime I will admin through oem. the strange thing is that the number of archived log files of smaller database, db2, are much bigger than ones of bigger database. also the same situation for the size of the flashback logs for point-in-time recovery. (I enable flashback logging for fast database point-in-time recovery, the flashback retention time is 24 hours.) I found the memory utility of smaller database is higher than bigger database. nearly all the time the smaller database's memory utility keeps more than 99%. while the bigger one's memory utility keeps about 97%. (I enable "Automatic Shared Memory Management" on both databases.) but both database's cup and queue are very low. I'm nearly sure no one hack the databases. so I really have no idea why the same backup and recovery policy will result so different result, especially the smaller one produces more redo logs than bigger one. does there anyone happen to know the reason or how should I do to check the reason?
    by the way, I found web based OEM can't reflect the correct database status when the database shutdown abnormally. for example, if the database hang up because of out of flash recovery area, after I assign more flash recovery area space and then restart the database, the OEM usually can't reflect the correct database status. I must restart OEM manually to correctly reflect the current database status. does there anyone know in what situation I should restart OEM to reflect the correct database status?
    sorry for the long message, I just want to describe in details to easy diagnosis.
    any hint will be greatly appreciated!
    Sammy

    thank you very much, in fact, my site's oracle never works about managing archive files automatically although I have tried all my best. at last, I made a job running daily to check the archive files and delete them.
    thanks again.

  • Roblem about space management of archived log files

    Dear friends,
    I have a problem about space management of archived log files.
    my database is Oracle 10g release 1 running in archivelog mode. I use OEM(web based) to config all the backup and recovery settings.
    I config "Flash Recovery Area" to do backup and recovery automatically. my daily backup schedule is every night at 2:00am. and my backup setting is "disk settings"--"compressed backup set". the following is the RMAN script:
    Daily Script:
    run {
    allocate channel oem_disk_backup device type disk;
    recover copy of database with tag 'ORA$OEM_LEVEL_0';
    backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
    the retention policy is the second choice, that is "Retain backups that are necessary for a recovery to any time within the specified number of days (point-in-time recovery)". the recovery window is 1 day.
    I assign enough space for flash recovery area. my database size is about 2G. I assign 20G as flash recovery area.
    now here is the problem, through oracle online manual, it said oracle can manage the flash recovery area automatically, that is, when the space is full, it can delete the obsolete archived log files. but in fact, it never works! whenever the space is full, the database will hang up! besides, the status of archived log files is very strange, for example, it can change "obsolete" stauts from "yes" to "no", and then from "no" to "yes". I really have no idea about this! even though I know oracle usually keep archived files for some longer days than retention policy, but I really don't know why the obsolete status can change automatically. although I can write a schedule job to delete obsolete archived files every day, but I just want to know the reason. my goal is to backup all the files on disk and let oracle automatically manage them.
    also, there is another problem about archive mode. I have two oracle 10g databases(release one), the size of db1 is more than 20G, the size of db2 is about 2G. both of them have the same backup and recovery policy, except I assign more flash recovery area for db1. both of them are on archive mode. both of nearly nobody access except for the schedule backup job and sometime I will admin through oem. the strange thing is that the number of archived log files of smaller database, db2, are much bigger than ones of bigger database. also the same situation for the size of the flashback logs for point-in-time recovery. (I enable flashback logging for fast database point-in-time recovery, the flashback retention time is 24 hours.) I found the memory utility of smaller database is higher than bigger database. nearly all the time the smaller database's memory utility keeps more than 99%. while the bigger one's memory utility keeps about 97%. (I enable "Automatic Shared Memory Management" on both databases.) but both database's cup and queue are very low. I'm nearly sure no one hack the databases. so I really have no idea why the same backup and recovery policy will result so different result, especially the smaller one produces more redo logs than bigger one. does there anyone happen to know the reason or how should I do to check the reason?
    by the way, I found web based OEM can't reflect the correct database status when the database shutdown abnormally. for example, if the database hang up because of out of flash recovery area, after I assign more flash recovery area space and then restart the database, the OEM usually can't reflect the correct database status. I must restart OEM manually to correctly reflect the current database status. does there anyone know in what situation I should restart OEM to reflect the correct database status?
    sorry for the long message, I just want to describe in details to easy diagnosis.
    any hint will be greatly appreciated!
    Sammy

    thank you very much, in fact, my site's oracle never works about managing archive files automatically although I have tried all my best. at last, I made a job running daily to check the archive files and delete them.
    thanks again.

  • RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE

    제품 : RMAN
    작성날짜 : 2002-12-09
    RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE
    ==========================================================
    PURPOSE
    이 자료는 Oracle 9.2 이상의 RMAN에서 사용 가능한 MAXSIZE 기능에 대하여
    설명할 것이다.
    How to restore archive logs with limited disk space
    Old Backup을 사용하여 RMAN으로 database를 recvoery할때, 모든 archived
    redo logfile들을 Restore할 destination의 disk space가 모자란 경우를 종종 만난다.
    이러한 경우 여러 개의 restore and recovery job으로 나누어 수행한다.
    즉, 첫 번째 restore and recovery job이 끝나면 archived redo logfile들을 지우고
    다음 적용될 것들을 restore한다. 그리고 다시 Recovery를 수행한다. 이러한 작업을
    원하는 시점까지 recovery를 하기위해 반복적으로 수행한다.
    Oracle 9iR2(9.2.0.x)부터 RMAN은 MAXSIZE option을 제공하는데 이것은 archive log
    file이 restore될 disk의 space를 control할 수 있게 해 준다.
    만약 disk space가 매우 제한적이라면, 즉 예를 들어 모든 archive log의 size 합보다
    disk free space가 적다면 MAXSIZE option을 사용하는 것은 매우 유용하다.
    이 OPTION이 기술되면 RMAN은 Media Manager에게 disk space 크기에 부합하는 만큼만
    archive log들을 restore하도록 한다. 부가적인 restore operation들은 restore된
    마지막 archive log가 적용될 때마다 발생한다.
    MAXSIZE option은 이러한 작업들을 하나의 rman job으로 처리하게 해 주고
    실수를 하지 않게 해 준다.
    아래는 MAXSIZE를 설명하기 위한 예제이며 총 6 단계로 구성되어 있다.
    STEP 1: Add data to the database to enforce log switches
    STEP 2: Backup the database and archive logs and delete the logs
    STEP 3: Add additional data to enforce new log switches
    STEP 4: Remove the data file and simulate a database crash
    STEP 5: Restore the data file from the backup
    STEP 6: Recover the database using MAXSIZE
    위 예제는 Unix와 Windows 모두에 적용될 수 있다.
    STEP 6 는 다음과 같은 조건으로 두 번 수행될 것이다.
    1) MAXSIZE가 archive log size보다 작은 경우:
    이 경우 RMAN-6558 Error message를 만나게 된다.
    그러므로 MAXSIZE를 archive log보다는 크게 설정해야한다.
    2) MAXSIZE가 archive log size보다 큰 경우:
    예를 들어 여러 개의 archive log를 포함할 수 있을 정도로 크게 설정하면
    restore/recovery는 user에게 transparent하게 수행되어진다.
    즉 archive log들은 restore된 후 applied되고 deleted되어 진다. 다시 새로운
    archive log들이 restore되어지고 applied된 후 deleted 되어 진다. 이러한 작업은
    recovery가 끝날 때까지 반복되어진다. 이러한 작업들이 진행되는 동안 RMAN은
    아무런 Message도 발생시키지 않는다.
    # Step 1: INSERT enough new data to generate log switches
    create table rman_tst (col1 varchar2 (10));
    begin
    for i in 1..30000 loop
    insert into rman_tst values(i,'test');
    commit;
    end loop;
    end;
    # Step 2: BACKUP the database and the archive logs automatically
    # and then delete the input
    run {
    backup database format='/web01/usupport/krosenme/admin/backups/db_%d%s%t'
    plus archivelog format='/web01/usupport/krosenme/admin/backups/arch_%d%s%t'
    delete input;
    # Step 3: INSERT enough new data to generate new log switches
    begin
    for i in 1..30000 loop
    insert into rman_tst values(i,'test');
    commit;
    end loop;
    end;
    # Step 4: REMOVE users01.dbf file and crash the database
    mv users01.dbf users01.org
    shutdown abort
    # Restore is now needed as the data file is deleted. The backup was
    # taken before the new data was added to it, thus archive logs are
    # needed to bring the database up to date
    # Step 5: RESTORE the data file from the full backup
    run {
    restore datafile '/web01/usupport/krosenme/oradata/kro_920/users01.dbf';
    # Step 6: RECOVER
    run {
    recover database delete archivelog maxsize 10 K;
    # This will fail with RMAN-6558 as the archived log has a size of 16 KB,
    # which is bigger than MAXSIZE limit of 10 KB. So the error is expected
    # and MAXSIZE works as designed.
    # Now rerunning STEP 6: but with MAXSIZE 50 K
    run {
    recover database delete archivelog maxsize 50 K;
    RELATED DOCUMENTS
    Recovery Manager Reference, Release 2 (9.2)

    cold backup means offline backup, you shut database normally and copy datafiles to another location.
    i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
    backing up archivelogs whith rman script which is:
    run {
    allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
    change archivelog all validate;
    sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
    release channel c1;
    so here is the details.
    1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
    2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
    So
    first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
    and then restore them and then apply them.
    we need rman commands to register these backups and restore them.
    Regards,
    Kamil

  • Archive log missing on standby: FAL[client]: Failed to request gap sequence

    My current environment is Oracle 10.2.0.4 with ASM 10.2.0.4 on a 2 node RAC in production and a standby that is the same setup. I'm also running on Oracle Linux 5. Almost daily now an archivelog doesnt make it to the standby and oracle doesnt seem to resolve the gap sequence from the primary. If I stop and restart recovery it gets the logfile and continues recovery just fine. I have checked my fal_client and fal_server settings and they look good. The logs after this error do continue to get written to the standby but the standby wont continue recovery until I stop and restart recovery and it fetches this missing log.
    The only thing I know thats happening is that the firewall people are disconnecting any connections that are inactive for 60 minutes and recently did an upgrade that they are claiming didnt change anything:)  I dont know if this is causing this problem or not. Any thoughts on what might be happening?
    Error in standby alert.log:
    Tue Jun 29 23:15:35 2010
    RFS[258]: Possible network disconnect with primary database
    Tue Jun 29 23:15:36 2010
    Fetching gap sequence in thread 2, gap sequence 9206-9206
    Tue Jun 29 23:16:46 2010
    FAL[client]: Failed to request gap sequence
    GAP - thread 2 sequence 9206-9206
    DBID 661398854 branch 714087609
    FAL[client]: All defined FAL servers have been attempted.
    Error on primary alert.log:
    Tue Jun 29 23:00:07 2010
    ARC0: Creating remote archive destination LOG_ARCHIVE_DEST_2: 'WSSPRDB' (thread 1 sequence 9265)
    (WSSPRD1)
    ARC0: Transmitting activation ID 0x29c37469
    Tue Jun 29 23:00:07 2010
    Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc0_14024.trc:
    ORA-03135: connection lost contact
    FAL[server, ARC0]: FAL archive failed, see trace file.
    Tue Jun 29 23:00:07 2010
    Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc0_14024.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Tue Jun 29 23:00:07 2010
    ORACLE Instance WSSPRD1 - Archival Error. Archiver continuing.
    Tue Jun 29 23:00:41 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    Tue Jun 29 23:00:41 2010
    FAL[server, ARC2]: Begin FAL archive (dbid 0 branch 714087609 thread 2 sequence 9206 dest WSSPRDB)
    FAL[server, ARC2]: FAL archive failed, see trace file.
    Tue Jun 29 23:00:43 2010
    Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc2_14028.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Tue Jun 29 23:00:43 2010
    ORACLE Instance WSSPRD1 - Archival Error. Archiver continuing.
    Tue Jun 29 23:01:16 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    Tue Jun 29 23:15:01 2010
    Thread 1 advanced to log sequence 9267 (LGWR switch)
    I have checked the trace files that get spit out but they arent anything meaningful to me as to whats really happening. Snipit of the trace file:
    tkcrrwkx: Starting to process work request
    tkcrfgli: SRL header: 0
    tkcrfgli: SRL tail: 0
    tkcrfgli: ORL to arch: 4
    tkcrfgli: le# seq thr for bck tba flags
    tkcrfgli: 1 359 1 2 0 3 0x0008 ORL active cur
    tkcrfgli: 2 358 1 0 1 1 0x0000 ORL active
    tkcrfgli: 3 361 2 4 0 0 0x0008 ORL active cur
    tkcrfgli: 4 360 2 0 3 2 0x0000 ORL active
    tkcrfgli: 5 -- entry deleted --
    tkcrfgli: 6 -- entry deleted --
    tkcrfgli: 7 -- entry deleted --
    tkcrfgli: 8 -- entry deleted --
    tkcrfgli: 9 -- entry deleted --
    tkcrfgli: 191 -- entry deleted --
    tkcrfgli: 192 -- entry deleted --
    *** 2010-03-27 01:30:32.603 20998 kcrr.c
    tkcrrwkx: Request from LGWR to perform: <startup>
    tkcrrcrlc: Starting CRL ARCH check
    *** 2010-03-27 01:30:32.603 66085 kcrr.c
    Beginning controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20395 (14011)]
    *** 2010-03-27 01:30:32.645 66173 kcrr.c
    Acquired controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20395 (14024)]
    *** 2010-03-27 01:30:32.649 66394 kcrr.c
    Ending controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20397]
    tkcrrasgn: Checking for 'no FAL', 'no SRL', and 'HB' ARCH process
    # HB NoF NoS CRL Name
    29 NO NO NO NO ARC0
    28 NO YES YES NO ARC1
    27 NO NO NO NO ARC2
    26 NO NO NO NO ARC3
    25 YES NO NO NO ARC4
    24 NO NO NO NO ARC5
    23 NO NO NO NO ARC6
    22 NO NO NO NO ARC7
    21 NO NO NO NO ARC8
    20 NO NO NO NO ARC9
    Thanks.
    Kristi

    It's the network that's messing up; unlikely due to firewall timeout as it waits for 60 minutes and you are switching every 15 minutes. There may be some other network glitch that needs rectified.
    In any case - arch file missing/ corrupt / halfway through - FAL setting should have refetched the problematic archive log automatically.
    As many had suggested already, the best way to resolve RFS issues I believe is to use real-time apply by configuring standby redo logs. It's very easy to configure it and you can opt for real-time apply even in max-performance mode that you are using right now.
    Even though you are maintaining (I guess) 1-1 between primary & standby instances, you can provide both primary instances in fal_server (like fal_server=string1,string2). See if that helps.
    lastly, check if you are having simiar issue at other times as well that might be getting rectified automatically as expected.
    col message for a80
    col time for a20
    select message, to_char(timestamp,'dd-mon-rr hh24:mi:ss') time
    from v$dataguard_status
    where severity in ('Error','Fatal')
    order by timestamp;
    Cheers.

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

Maybe you are looking for

  • No Tools in new project window for xcode

    Hi Can anyone please help? I have recently started to learn C language and currently reading a book that advices using xcode, this has been downloaded with no problems from the original disk. In the back of the book it advices opening a new project w

  • WWDOC_DOCUMENT$ record deletion

    Hi all, I have a portlet form that upload a BLOB file on a custom table. Every time I insert a record on my table I find a record on PORTAL30.WWDOC_DOCUMENT$ table. 2 questions: - will the uploaded BLOBs be stored on the filesystem? (but where?) - wh

  • IWeb Link Question

    Is there a way to create a link and I can indicate that if someone clicks on the link that it opens the new page in a new finder window?

  • CS4 Initializing Version Cue on Mac

    anyone done it?  seems really hard, working with servers, Adobe Drive and all.

  • Trying to set-up Cannon iP4500 on Airport Express. Not seeing it on scan.

    Just got a used Airport Express and plugged my Cannon iP4500 into the USB connection and plugged the Airport Express into the power strip. When I opened up the Airport Utility, the initial scan didn't find the Airport Express. I'm using a 3rd party w