ORA-000257 is the "archiver stuck" error. If enough space is available, this will not happen... in a perfect world..... Based on the activity of the database and the amount of free space I have been able to allocate to archived redo logs, I have scheduled the logs to be written to our offline backup mechanism and then removed from the file system(s) at different time intervals. This can be done whether you have a single location or multiple locations designated for archived redo logs. In a UNIX environment, it is straight forward to write a shell script which can perform the backup and then use cron to schedule the script to execute. In a Windows environment, a bat file can be written to perform the same types of actions and then scheduled via the Windows scheduling system. I have the luxury of using TSM backups which has a "deletefile" option when the file has been successfully written to backup. This provides a sense of reduced risk that the file is restorable in case a recovery would be needed.
In your environment it may be necessary to work with your backup and restore team and maybe your System Administrator to accomplish a similar activity. If no offline backups are available, then available disk storage will be needed to avoid the error.
I didn't realize that someone else had submitted another answer while I was typing this one. But, they had a couple of points that I missed. 1) be sure that automatic archiving is turned on in case you are getting stuck by lack of archiving. and also 2) after each database backup be sure to remove at least part of your archived redo logs as part of your general cleanup process. You may choose to keep a certain portion of your redo logs online to facilitate quick recovery if needed.
Last Wiki Answer Submitted: October 28, 2008 9:36 pm by Jcmdba555 pts.
All Answer Wiki Contributors: Jcmdba555 pts. ,