Archive logs are used to Recover a database,Update a standby database,
gain info about the history of a database using the LogMiner utility.
The logs are kept on my e drive and there is enough space on the drive. I delete them when they are no longer useful. Sometime ago they get filled up more frequently and i have to delete them to create space.
From V$archive_dest, i noticed that 4 out of the 5 dest_ids are inactive.
if you are deleting them, better take a backup right now!
Will do that immediately. What option do one have when there is no more space in the archive destination drive.
Backup your database to tape
or
move your archive logs to another disk
or
backup your archive logs to tape before deleting them. I normally keep a couple of days worth of archive logs on disk, but that would vary for every case.
For recovery purposes, you only need your archive logs as far back as your most recent backup. I keep them (on tape) for two weeks, just cos I have been bitten by a deleted archive log in the past.
Like I said, every case is different, depending on your business needs.
pls can you compare or advise on the use of LOG_ARCHIVE_DEST and LOG_ARCHIVE_DEST_n with the reopen option. i know you can only use one of them.
also, genereally in normal operation is an archive log generated every 3 minutes? This will grind your system to a halt as the database grows as you will also be log switching every 3 minutes.
As a rule I try and keep my log switches to every 20/30 minutes, you control this by increasing the size of your redo logs.
log_archive_dest and log_archive_dest_n are used when you would like to archive to more than one destination.
I use it as I archive to my local server and a standby server remotely. The reopen command states that if the archive cannot be sent to dest_2 - try again in 60 seconds (if set to reopen 60)
You could always take your database out of archive log mode. Sounds like you're not bothered about recovery?