Flash Recovery Area Full - Database Fails to Open ORA-16038

Subject:	Flash Recovery Area Full - Database Fails to Open ORA-16038
	Doc ID:	Note:337258.1	Type:	PROBLEM
	Last Revision Date:	24-JAN-2006	Status:	MODERATED

In this Document
  Symptoms
  Cause
  Solution
  References

---

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) 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.1.0
This problem can occur on 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

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. Change retention policy to redundancy =1
EM ==> CONFIGURE BACKUP SETTINGS ==> RETENTION POLICY

2. Run delete obsolete job:
EM ==> MANAGE CURRENT BACKUPS ==> DELETE ALL OBSOLETE

References

Note 280709.1 - Creating a Disk only backup script to achieve a recovery window using oracle recommended strategy in flash recovery area
Note 293418.1 - ORA-19815: WARNING: DB_RECOVERY_FILE_DEST_SIZE 100.00% USED