Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

log archive destination full tips

Oracle Database Tips by Donald BurlesonFebruary 27, 2016

Question: What do I do when my instance loks up due to the log archive destination getting full?  I see this message, indicating that the diectory is full:

archive log full waiting to be freed

How can I fix the log archive destination full, and more important, how do I prevent this from happening? 

Answer:  Most Oracle shops use a crontab task to monitor the log archive destination to see when it crosses 90% full, and then invokes a solution that deletes the oldestredo logs from the directory.  This Linux/UNIX command will remove all archoved redo logs that are more than two weeks old:

root> cd <redo log directory>
root> find -name '*.log' -mtime +140 -exec rm -rf {} \;

You can also fix this full problem by adding space to your archived redo log directory. 

Here is a UNIX/Linux cron job that is handy for removing "clutter" (obsolete archived redo log files) from external Oracle filesystems:

#!/bin/ksh
 
# Cleanup PROD archive logs more than 3 days old
/usr/bin/find /u01/app/oracle/admin/PROD/arch/arch_prod*.arc -ctime +3 -exec rm {} \;

The following commands can be used to locate the Oracle archive logs:

  •  Issue the archive log list command:

       SQL> archive log list
  • Issue the show parameter command:

       SQL> show parameter db_recovery_file_dest
  • Query the v$archive_dest view:

       SQL> select dest_name, status, destination from v$archive_dest;  

If you are using RMAN you can issue these commands when the archived redo log diectlory becomes full:

run {
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
delete noprompt expired archivelog all;
delete noprompt expired backup;
}

For full scripts to monitor and remove archived redo logs, see the book "Oracle Shell Scripting" by Jon Emmons.

   
Oracle Training from Don Burleson 

The best on site "Oracle training classes" are just a phone call away! You can get personalized Oracle training by Donald Burleson, right at your shop!

Oracle training
 
 


 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster