Atikh's DBA blog
  • Home
  • Oracle
  • MySQL
  • MongoDB
  • PostgreSQL
  • Snowflake
  • About Me
  • Contact Us

ORA-19804, ORA-19809: limit exceeded for recovery files

 Atikh Shaikh     Backup and Recovery, oracle, Oracle 12c, RMAN     No comments   

I was taking backup of database as image copy of size 200G, I faced ORA errors like ORA-19809, ORA-19804 as shown below


RMAN> run
{
allocate channel ch1 type disk;
backup as copy SECTION SIZE 800M database;
release channel ch1;
}2> 3> 4> 5> 6>

using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: SID=2330 device type=DISK

Starting backup at 07-JAN-19
channel ch1: starting datafile copy
input datafile file number=00013 name=+DATA/TECH_DB/DATAFILE/tech_tbs_data.277.996526534
backing up blocks 1 through 153600
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch1 channel at 01/07/2019 05:52:11
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 322123595776 bytes disk space from 107374182400 limit

RMAN> 


Below is the solution for the same
I found database size is 200GB and FRA size is set 100GB only, which caused this error

commands to check size of FRA

SQL> show parameter db_recovery

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      +FLASH
db_recovery_file_dest_size           big integer 100G
SQL>


Command to check size of database and usage of FRA

SQL > select sum(bytes)/1024/1024/1024 as "Size Of DB" from dba_data_files;
              Size Of DB
-------------------------
                      200

SQL> col NAME for a10
SQL> SELECT NAME, round(space_limit/1024/1024/1024,2) TOTAL_GB, round(space_used/1024/1024/1024,2) USED_GB, round((space_limit-space_used+space_reclaimable)/1024/1024/1024,2) AVAILABLE_GB, ROUND((space_used-space_reclaimable)/space_limit * 100,1) PERCENT_FULL FROM v$recovery_file_dest;

NAME         TOTAL_GB    USED_GB AVAILABLE_GB PERCENT_FULL
---------- ---------- ---------- ------------ ------------
+FLASH            100       1.09        99.42           .6


I have changed size of the FRA using DB_RECOVERY_FILE_DEST_SIZE to 250GB, then it worked without any issue.

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE =250G SCOPE=BOTH


Once this is done fire RMAN backup command, it will initiate the backup and will not through this error.
  • Share This:  
  •  Facebook
  •  Twitter
  •  Instagram
  •  Pin
  •  linkedin
  •  reddit
Email ThisBlogThis!Share to XShare to Facebook
Newer Post Older Post Home

0 comments:

Post a Comment

Author

Atikh Shaikh
View my complete profile

Categories

  • MongoDB (18)
  • Oracle 12c (30)
  • Oracle12cR2 New Feature (3)
  • PostgreSQL (20)
  • RMAN (10)
  • Snowflake (8)
  • mysql (23)
  • oracle (74)

Blog Archive

  • ►  2018 (38)
    • ►  November (25)
    • ►  December (13)
  • ▼  2019 (33)
    • ▼  January (15)
      • Data Types in MongoDB
      • Oracle : RMAN Introduction
      • ORA-00265: instance recovery required, cannot set ...
      • Oracle : Starting with RMAN Commands
      • Oracle RMAN : Incremental Backups
      • MongoDB 4.0 New Features
      • Oracle RMAN : File Section for backup of large dat...
      • ORA-19804, ORA-19809: limit exceeded for recovery ...
      • Oracle RMAN: Fast Incremental Backups
      • The DUAL table in oracle
      • Oracle : Drop Pluggable Database (PDB) in 12c/19c/...
      • Oracle : The oerr Utility (Oracle Error)
      • Oracle RMAN : Incrementally Updated Backups
      • MySQL 8.0 New Features
      • Postgres spooling file and other command line options
    • ►  February (6)
    • ►  March (2)
    • ►  April (5)
    • ►  May (5)
  • ►  2020 (5)
    • ►  April (1)
    • ►  May (2)
    • ►  July (2)
  • ►  2021 (8)
    • ►  June (3)
    • ►  July (3)
    • ►  August (1)
    • ►  December (1)
  • ►  2022 (33)
    • ►  May (3)
    • ►  June (10)
    • ►  July (3)
    • ►  August (4)
    • ►  September (8)
    • ►  October (3)
    • ►  November (2)
  • ►  2023 (14)
    • ►  February (1)
    • ►  April (5)
    • ►  May (2)
    • ►  June (1)
    • ►  September (1)
    • ►  October (1)
    • ►  December (3)
  • ►  2024 (5)
    • ►  January (2)
    • ►  March (3)
  • ►  2025 (6)
    • ►  March (1)
    • ►  April (3)
    • ►  May (2)

Popular Posts

  • ORA-29283: invalid file operation: unexpected "LFI" error (1509)[29437]
    I was trying to export the schema in my windows PC, it got stuck with below error    C:\Users\shaik\Videos\technodba exp>expdp userid...
  • Oracle 23ai : Use of NOVALIDATE Constraints in IMPDP
    While performing impdp operations in the Oracle database, Oracle performs validation checks for every constraint on the imported table, that...
  • PostgreSQL : How to get data directory location for PostgreSQL instance
    Sometimes, you start working on a PostgreSQL instance but forget about the data directory, here we will discuss different methods to know th...
  • ERROR 1221 (HY000): Incorrect usage of DB GRANT and GLOBAL PRIVILEGES
    In previous articles, we have learned about user creation and grants  in MySQL in detail, but there are a few privileges called global priv...
  • Oracle Dataguard Broker Configuration (DGMGRL)
    Data Guard Broker is a command-line interface that makes managing primary and standby databases easy. DBA can use a single command to switch...

Labels

oracle Oracle 12c mysql PostgreSQL MongoDB oracle 19c Oracle23c oracle19c Orale PDB-CDB oracle12c python AWS Oracle ASM Virtualbox pluggable database storage engine

Pages

  • Disclaimer
  • Privacy Policy

Follow TechnoDBA

Copyright © Atikh's DBA blog | Powered by Blogger