SYMPTOM
On primary database side, ORA errors in alert log:
Errors in file /u01/app/oracle/diag/rdbms/testdb001/TESTDB001/trace/TESTDB001_arc4_10114.trc:
ORA-07286: cannot obtain device information.
ARC4: FAL archive failed with error 7286. See trace for details
Errors in file /u01/app/oracle/diag/rdbms/testdb001/TESTDB001/trace/TESTDB001_arc4_10114.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
On standby database side, ORA errors in alert log
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 536870912 bytes disk space from 214748364800 limit
ORA-19815: WARNING: db_recovery_file_dest_size of 214748364800 bytes
is 100.00% used and has 0 remaining bytes available.
We have following choices to free up space from recovery area:
- If we are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY.
- RMAN-BACKUP RECOVERY AREA command.
- Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE parameter to reflect the new space.
- Use RMAN CROSSCHECK and DELETE EXPIRED commands.
CAUSES
Standby database archive log retention policy is not configured properly.
RMAN> show all;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
SOLUTION
Change the archive log retention policy on standby side.
RMAN>CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
