昨天晚上加班到3点，早上还正在睡觉，朋友打电话来：数据库不能正常登陆，所有业务连接中断，报错代码为ORA-00257，已经通过rman的delete命令删除归档，但是还是不能正常登陆，下面是分析思路
欢迎大家加入ORACLE超级群：17115662 免费解决各种ORACLE问题,以后BLOG将迁移到http://www.htz.pw
1，查看数据库的归档路径
archive log list;
2，查看fra区的使用情况
select * from v$recovery_file_dest;
里面未使用任何空间。
3，v$archived_log中能查看归档记录。
4，查看fra区的大小。
此时发现fra区的大小为0，手动修改fra区大小配置为50G，数据库能正常登陆
How to Resolve ORA-00257: Archiver is Stuck Error in 10g and higher (文档 ID 278308.1)修改时间:2013-3-2类型:PROBLEMIn this Document Symptoms Cause Solution ReferencesThis document is being delivered to you via Oracle Support’s Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.APPLIES TO:Oracle Server – Standard Edition – Version: 10.1.0.2 to 11.2.0.2 – Release: 10.1 to 11.2Information in this document applies to any platform.***Checked for relevance on 17-10-2011***SYMPTOMSConnections to the database receive ORA-00257: archiver is stuck error.CAUSEThe max limit for flash recovery area(db_recovery_file_dest_size) is reached.SOLUTION1. Check whether the database is in archive log mode and automatic archiving is enabled.SQL> archive log list;2. If archive destination is defined by USE_DB_RECOVERY_FILE_DEST, find the archive destination by :SQL> show parameter db_recovery_file_dest;Check what is the value set for db_recovery_file_dest_size3. Find the space used in flash recovery area by :SQL> SELECT * FROM V$RECOVERY_FILE_DEST;4. If SPACE_USED is equal to SPACE_LIMIT, move the archive logs to a different destination.5. Archive all the log filesSQL> alter system archive log all;NOTE: See Note 315098.1 for pointers on backing up files from the flash recovery area to decrease space usage.6. If ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST is received for step 5, then for each destination give the correct archivelog path and issue:SQL>alter system set LOG_ARCHIVE_DEST_.. = ‘location=/archivelogpath reopen’;NOTE: =====If you have configured Flash Recovery Area (default in 10gR2) — meaning that you have set the two initialization parameters: — DB_RECOVERY_FILE_DEST_SIZE — DB_RECOVERY_FILE_DESTyou cannot use the LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters any more. You must always use the LOG_ARCHIVE_DEST_n parameters in case you have configured flash recovery area. LOG_ARCHIVE_DEST_10 is implicitly set to USE_DB_RECOVERY_FILE_DEST if you create a recovery area and do not set any other local archiving destinations.If you try to use LOG_ARCHIVE_DEST with a Flash Recovery Area configured, you will receive errors like:ERROR at line 1: ORA-02097: parameter cannot be modified because specified value is invalid ORA-16018: cannot use LOG_ARCHIVE_DEST with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST 7. Just switch the logs to verify:SQL> alter system switch logfile;NOTE:====If you want to increase the flash recovery area:STEPS:=====1. Note down the path of flash recovery area.SQL> show parameter db_recovery_file_dest;2. Disable the Flash Recovery AreaSQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST=” SCOPE=BOTH SID=’*’;3. Increase the Flash Recovery AreaSQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10g SCOPE=BOTH SID=’*’; 4. Enable the Flash Recovery Area SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = ‘/dir1′ SCOPE=BOTH SID=’*’;If the flash recovery area location is an Automatic Storage Management disk group named disk1, for example, then you can do the following:SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = ‘+disk1′ SCOPE=BOTH SID=’*’;REFERENCESNOTE:305796.1 – RMAN and Flash Recovery AreaNOTE:315098.1 – How is the space pressure managed in the Flash Recovery Area – An Example.NOTE:316074.1 – Correctly configuring the Flash Recovery Area to allow the release of reclaimable spaceNOTE:305648.1 – What is a Flash Recovery Area and how to configure it ?