ORA-16014: 日志 1 的序列号 83 未归档, 没有可用的目的
2011-02-14 16:40 乱世文章 阅读(272) 评论(0) 编辑 收藏 举报D:/oracle/BIN>sqlplus "sys/leuphis@leuphis as sysdba"
SQL> alter database open;
alter database open
*
第 1 行出现错误:
ORA-16014: 日志 1 的序列号 83 未归档, 没有可用的目的地
ORA-00312: 联机日志 1 线程 1:
'D:/ORADATA/LEUPHIS/ONLINELOG/O1_MF_1_45DCY21Y_.LOG'
ORA-00312: 联机日志 1 线程 1:
'D:/FLASH_RECOVERY_AREA/LEUPHIS/ONLINELOG/O1_MF_1_45DCY43F_.LOG'
检查flash recovery area的使用情况:
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES 参考资料:www.svn8.com
------------ ------------------ ------------------------- ---------------
CONTROLFILE .22 0 1
ONLINELOG 4.88 0 3
ARCHIVELOG 65.01 0 73
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
已选择6行。
计算flash recovery area已经占用的空间:
SQL> select sum(percent_space_used)*3/100 from v$flash_recovery_area_usage;
SUM(PERCENT_SPACE_USED)*3/100
-----------------------------
2.1033
SQL> show parameter db_recovery
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string D:/flash_recovery_area
db_recovery_file_dest_size big integer 2G
这里已经有2.1033G使用了,这说明我们刚开始设置的db_recovery_file_dest_size=2G不足,导致online redo log无法归档,在这里,我们通过设置db_recovery_file_dest_size参数,增大了flash recovery area来解决这个问题。
参考资料:www.svn8.com
SQL> alter system set db_recovery_file_dest_size=3G scope=both;
系统已更改。
SQL> alter database open;
数据库已更改。
ORA-16014 log string sequence# string not archived, no available destinations
Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.
Action: Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred.
Svn8.Com
本文来自:http://www.svn8.com/sql/Oracle/2009110512305.html