Pls can someone explain to me why my oracle 8i database generates 20 .arc archive files in less than 3 minutes. Its has never happenned before and at a point users will not be able to logon to the database any more and they get ora-00257: archiver error. Connect internal only, until freed. When this error occurs i delete some of the .arc files.
How can i stop this error and also how can i detect the process causing this problem to possibly stop it.
because someone is generating a lot of redo. USe logmnr to look at the logs to find out who.
Or tace some sessions to see who is doing what
Plus deleting the files stops you being able to recover as well
Pls how do i setup logmnr and use i. It doesn't exist on our db.
Ever heard of "RTFM" ?
No i've not or rather i've come across it but can remember now.
it means read the fine manual, log miner setup is fully documented there
You're wayyyyy to kind.Quote:
Originally posted by davey23uk
it means read the fine manual, log miner setup is fully documented there
What happen you wake up or something?
im on a roll of fixing real life problems today, might as well carry on here till someone angers me .....
I have located it in the manual as advised. Thanks for that.
This forum has been my first port of call if i encounter problems and i always appreciate all the help i have gotten from this forum.
I have another problem on the archive logs. From Spotlight on Oracle i notice that the archiver is no longer archiving and on mouse over to the archive log bucket it displays "No more room for archiving logs". Pls can someone give me an idea what has gone wrong. There is space on the system to take more archive logs.
Doesn't that answer your question for you? Where are your archive logs being kept and is there enough space on the drive where you're keeping them? Are you deleting them when they're no longer useful or just stockpiling them?Quote:
Originally posted by cca
"No more room for archiving logs". Pls can someone give me an idea what has gone wrong. There is space on the system to take more archive logs.
Tell me, what are archive logs used for?
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?