用10g从8i的数据库里面导出用户数据,然后导入10g数据库中,结果中途报错,就中止了倒入,然后redolog就被占满了就出了这么个报错,数据库mount后无法open,还好不是什么大问题,网上搜了搜就解决了,万幸万幸![ORA-16014 ORA-16014](http://www.sinaimg.cn/uc/myshow/blog/misc/gif/E___6706EN00SIGG.gif)
![ORA-16014 ORA-16014](http://www.sinaimg.cn/uc/myshow/blog/misc/gif/E___6706EN00SIGG.gif)
PS:这些DBA视图好烦啊,好多参数啊,肿么记啊 肿么记.
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-16014: log 1 sequence# 29 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/oracle/database/oradata/test/redo01.log'
SQL> select status from v$instance;
STATUS
------------
MOUNTED
SQL> show parameter db_recovery_file
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string /oracle/product/10.2.0/flash
_recovery_area
db_recovery_file_dest_size big integer 2G
SQL> show parameter db_recovery
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string D:/oracle/product/10.2.0/flash
_recovery_area
db_recovery_file_dest_size big integer 2G
SQL> alter system set db_recovery_file_dest_size=3G scope=both;
系统已更改。
SQL> alter database open;
数据库已更改。
(1).检查flash recovery area的使用情况:
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE 0 0 0
ONLINELOG 0 0 0
ARCHIVELOG 6.36 0 4
BACKUPPIECE .22 0 1
IMAGECOPY 63.68 0 5
FLASHBACKLOG .51 .25 2
已选择6行。
SQL>
(2).计算flash recovery area已经占用的空间:
SQL> select sum(percent_space_used)*3/100 from v$flash_recovery_area_usage;
SUM(PERCENT_SPACE_USED)*3/100
-----------------------------
2.1231
可以看到,这里已经有2.1231G使用了,这说明我们刚开始设置的db_recovery_file_dest_size=2G不足,导致online redo log无法归档,
在这里,我们通过设置db_recovery_file_dest_size参数,增大了flash recovery area来解决这个问题。
(3).也可以通过删除flash recovery area中不必要的备份来释放flash recovery area空间来解决这个问题:
1, delete obsolete;
2, crosscheck backupset;
delete expired backupset;