启动数据库时报ORA-03113错误,遂查看alert log。
cd ~/app/oracle/diag/rdbms/orcl/orcl/trace/
tail -100 alert_orcl.log
发现如下错误:
Errors in file /home/oracle/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_5192.trc:
296 ORA-19815: WARNING: db_recovery_file_dest_size of 4070572032 bytes is 100.00% used, and has 0 remaining bytes available.
297 ************************************************************************
298 You have following choices to free up space from recovery area:
299 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
300 then consider changing RMAN ARCHIVELOG DELETION POLICY.
301 2. Back up files to tertiary device such as tape using RMAN
302 BACKUP RECOVERY AREA command.
303 3. Add disk space and increase db_recovery_file_dest_size parameter to
304 reflect the new space.
305 4. Delete unnecessary files using RMAN DELETE command. If an operating
306 system command was used to delete files, then use RMAN CROSSCHECK and
307 DELETE EXPIRED commands.
308 ************************************************************************
309 ARCH: Error 19809 Creating archive log file to '/home/oracle/app/oracle/flash_recovery_area/ORCL/archivelog/2014_04_04/o1_mf_1_546_%u_.arc'
310 Errors in file /home/oracle/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_5192.trc:
311 ORA-16038: log 3 sequence# 546 cannot be archived
312 ORA-19809: limit exceeded for recovery files
用RMAN解决:
rman target /
startup mount
delete force archivelog until time 'sysdate - 1';
startup;
本文记录了启动数据库时遇到ORA-03113及ORA-19815错误的情况,并详细展示了通过查看alertlog定位问题所在的过程。针对recovery area空间不足的问题,提供了使用RMAN进行清理的具体步骤。
3041

被折叠的 条评论
为什么被折叠?



