ORA-00257 error: Solutions?
Recently came across an Ora-00257 error in production.
From my research this appears to be due to the archiver having problems with the redo logs. My first step was to take the database out of archivelog mode (so at least I could get it up and running.) So, things are stable right now.
However, I am looking for a better fix. Some of the searches that I've found suggest running 'alter system archive log all' or 'delete archivelog all' as a way to clear things up, but this seems to be useful only after the error occurs. Is there a way to be more proactive? (I don't want to implement a temporary fix only to have the problem reappear some time in a month or 2.) Or am I bet to leave the database in noarchivelog?
I'm also wondering if anyone might have an idea what the cause of the problems were. The disk drive pointed to by db_recovery_file_dest seems to have enough space. I had the db_recovery_file_dest_size set pretty high. (The user wanted a rather large setting for the undo retention logs which might have contributed to the problem?