Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US

Index > ORACLE Server Parameters > db_recovery_file_dest_size

db_recovery_file_dest_size

Oracle 11.1.0:

Parameter Name:db_recovery_file_dest_size
Description:database recovery files size limit
Type:TYPE=6 Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 10.2.0:

Parameter Name:db_recovery_file_dest_size
Description:database recovery files size limit
Type:TYPE=6 Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 10.1.0:

Parameter Name:db_recovery_file_dest_size
Description:database recovery files size limit
Type:TYPE=6 Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 9.2.0:

No such parmeter in Oracle 9.2.0.

Oracle 8.1.7:

No such parmeter in Oracle 8.1.7.

Oracle 8.0.6:

No such parmeter in Oracle 8.0.6.

Oracle 7.3.4:

No such parmeter in Oracle 7.3.4.

Related Error Messages:

ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
    Cause: There are two possible cause for this error: 1) The DB_RECOVERY_FILE_DEST parameter was in use when no DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was in use.

    Action: Correct the dependency parameter definitions and retry the command.

ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - %s)

    Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specfied was not valid.

    Action: Specify a valid number within the range.

ORA-19804: cannot reclaim %s bytes disk space from %s limit

    Cause: Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit.

    Action: There are five possible solutions: 1) Take frequent backup of recovery area using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing RMAN archivelog deletion policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.

ORA-19808: recovery destination parameter mismatch

    Cause: The value of parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All databases must have same recovery destination parameters.

    Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all instances.

ORA-19809: limit exceeded for recovery files

    Cause: The value of parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All databases must have same recovery destination parameters.

    Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all instances.

ORA-38776: cannot begin flashback generation - flash recovery area is disabled

    Cause: During a database mount, the RVWR process discovered that the flash recovery area was disabled. DB_RECOVERY_FILE_DEST must have been set null or removed from the INIT.ORA file while the database was unmounted.

    Action: Flashback database requires the flash recovery area to be enabled. Either enable the flash recovery area by setting the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE initialization parameters, or turn off flashback database with the ALTER DATABASE FLASHBACK OFF command.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ db_recovery_file_dest_size ] on the Oracle FAQ.

HOME | ASK QUESTION | ADD FAQ | SEARCH | E-MAIL US