ORA-19815 when backup failed - flashbacklog space is not released (Doc ID 2184075.1)

Last updated on OCTOBER 26, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

ORA-19815: WARNING: db_recovery_file_dest_size of xxxxxxxxx bytes is xx.xx% used, and has xxxxxxxxx remaining bytes available.
Wed Aug 31 11:29:26 2016
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
  then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
  BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
  reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
  system command was used to delete files, then use RMAN CROSSCHECK and
  DELETE EXPIRED commands.
************************************************************************

Below SQL returns a value for SRESERVED:

SQL> select * from x$kccirt;

ADDR                   INDX        INST_ID   CON_ID   SRESERVED   STAMP
----------------       ---------- ---------- ---------- -------------  ----------
00007F6D4875B118  0            1            0            57899220992  921852425
00007F6D4875B118  1            1            0            0                 0

That means this is the amount of space that would have been taken by an RMAN backup or archivelog backup of RFS of a lof or so on... but that operation failed but space was not returned for some unknown reason.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms