We help IT Professionals succeed at work.

Archieved Logs Full

lium1
lium1 asked
on
First, when archieved logs are full and run out of space, what do you suggest to do first?
Second, what is your suggestion to delete archieved logs, please in details!
Finally, you procedure or steps to take for actions. Database is in Oracle 11gR2 RAC.

Thanks in advance.
Comment
Watch Question

Chief Database Architect
CERTIFIED EXPERT
Commented:
hi

1. increase the DB_RECOVERY_FILE_DEST_SIZE for more space for the archive logs.
2. if you backup using RMAN then issue the : BACKUP ARCHIVELOG ALL DELETE INPUT; command
this will delete all archive logs after backing them up.
3. use the : delete expired archivelog all; to delete all expired archive log files.

Author

Commented:
Do I need to shutdown the data base to make the changes and make changes effected?
CERTIFIED EXPERT
Most Valuable Expert 2012
Distinguished Expert 2019

Commented:
>>Second, what is your suggestion to delete archieved logs, please in details!

We really cannot answer this.  

This is specific for your database and organization.

for example:
What are your disaster recovery requirements?
What are your uptime requirements?
Aaron ShiloChief Database Architect
CERTIFIED EXPERT

Commented:
>> Do I need to shutdown the data base to make the changes and make changes effected?

NO.

slightwv : if using RMAN then i see no problem since it will comply with the retention period they configured.
CERTIFIED EXPERT
Most Valuable Expert 2012
Distinguished Expert 2019

Commented:
>>i see no problem since

The fact that the space filled up likely means there isn't a proper disaster recovery policy in place.

I would make sure I am safe before I deleted anything.
Aaron ShiloChief Database Architect
CERTIFIED EXPERT

Commented:
i agree that is why i said use rman and backup the logs then remove them VIA rman.
so if no backup was taken the no archives will be expired.

but again i agree "liuom1" you should check what is your disaster recovery plan and act acording to it.
CERTIFIED EXPERT
Most Valuable Expert 2012
Distinguished Expert 2019
Commented:
>>rman and backup the logs then remove them VIA rman

What if the default channel was disk.  Then they delete the archive logs and the disk crashes?  They are now unrecoverable.

They need to come up with a sound and tested disaster recovery plan and not just issue a simple backup/delete from a Q&A site like this because we say so.

Author

Commented:
Excuse me for the dumb question, where do I look for rman scripts for backup in OEM? Also, where do I check for disaster recovery plan that I have?
CERTIFIED EXPERT
Most Valuable Expert 2012
Distinguished Expert 2019

Commented:
>>where do I look for rman scripts for backup in OEM?

It might not be set up under OEM.  Many shops have them separated out as part of a server backup process.

If it was set up it should be under the backup tabs somewhere.  I'm not a GUI admin so I'm not sure exactly where it is.

The OEM docs should have information on how to set it up and view backup jobs set up through the GUI.

>>Also, where do I check for disaster recovery plan that I have?

Your DBA's, System Adminstrators, Project Managers, ???

In some larger organizations they have their own disaster recovery groups.

Someone should know how important the data is and makes sure it is able to be recovered.

Author

Commented:
I can view the backup jobs through GUI, but I don't see RMAN scripts for that in GUI. Any idea?
CERTIFIED EXPERT
Most Valuable Expert 2012
Distinguished Expert 2019

Commented:
Then backups have not been scheduled through OEM.

Doesn't mean you are not using RMAN.

Your DBA should know how things are backup up.
Greg CloughSenior Oracle DBA

Commented:
If your archivelog destination is full, such that the disk is 100% full and that's causing your database to stall then:

1) Move (don't Delete... MOVE) a bunch of the oldest archivelogs to a different filesystem/disk that has spare capacity.  This will allow the database to continue and will get the boss off of your back whilst you fix it properly.  (You can find the archivelog destinations by running this in SQL*Plus: "show parameter log_archive_dest")

2) Consult with your DBA, or keep pursuing this thread in EE to get it resolved correctly.  As the previous posters have noted there are many and varied ways to clean this up, and it relies heavily on your specific requirements.

Author

Commented:
The solutions provided were not quite completed.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.