Flash Recovery Area Full - Database Fails to Open ORA-16038 [ID 337258.1]
| Flash Recovery Area Full - Database Fails to Open ORA-16038 [ID 337258.1] | |||||
| 修改时间 23-FEB-2012 类型 PROBLEM 状态 MODERATED | |||||
In this Document
Symptoms
Cause
Solution
References
| This 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 - Enterprise Edition - Version: 10.1.0.2 and later [Release: 10.1 and later ]Information in this document applies to any platform.
Symptoms
Database startup fails:ORA-16038: log one sequence 3144 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312 online log 1 thread 1 <path to redo log file>
In the alert.log:
ORA-16014 signalled during: ALTER DATABASE open ...
ORA-19815: WARNING: db_recovery_file_dest_size of xxx bytes is 100.00% used, and has 0 remaining bytes available.
Cause
Using the default Oracle-Suggested strategy as implemented by EM in Oracle10gR1
Retention policy changed from the default redundancy of 1 to recovery window of 15 days
When the retention policy is changed to recovery window or to a redundancy > 1, RMAN cannot satisfy the retention policy if there is only one copy of database and it is recovered to the latest point in time. In order to satisfy the
retention policy, it keeps all the incrementals and archivelogs since database creation
Solution
1) Increase the parameter db_recovery_file_dest_size
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=Xg SCOPE=BOTH;
-- Replace X with a number larger than the current and ensure is sufficient space in the destination
2) Stop using the db_recovery_file_dest by unsetting the parameter.
(This assumes you never really wanted to use this option)
SQL> alter system set db_recovery_file_dest='';
3. Backup and delete archivelogs
RMAN> backup archivelog all delete input;
It is the dba's responsibility to ensure that the FRA size is sufficient to account for their retention policy.