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

db_recovery_file_dest

Oracle 11.1.0:

Parameter Name:db_recovery_file_dest
Description:default database recovery file location
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 10.2.0:

Parameter Name:db_recovery_file_dest
Description:default database recovery file location
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 10.1.0:

Parameter Name:db_recovery_file_dest
Description:default database recovery file location
Type:CHAR 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-01269: Destination parameter string is too long
    Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter was too long.

    Action: Replace the destination value for the specified parameter with a shorter character string.

ORA-16018: cannot use %s with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST

    Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1...10) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.

    Action: Eliminate any incompatible parameter definitions.

ORA-16019: cannot use %s with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

    Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1...10) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter.

    Action: Eliminate any incompatible parameter definitions.

ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST

    Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.

    Action: No action is required.

ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set

    Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error, including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archivelog file creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archivelog file creation was attempted.

    Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER SYSTEM SET command.

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-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-19812: cannot use %s without DB_RECOVERY_FILE_DEST

    Cause: There are three possible cause for this error: 1) The indicated parameter was in use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching the initialization parameter. 2) An attempt was made to set indicated the parameter with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST was in use. 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when the indicated parameter was in use.

    Action: Eliminate any incompatible parameter definitions.

ORA-19815: WARNING: %s of %s bytes is %s%% used, and has %s remaining bytes available.

    Cause: DB_RECOVERY_FILE_DEST is running out of disk space.

    Action: One of the following: 1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 2. Backup files to tertiary device using RMAN. 3. Consider changing RMAN retention policy. 4. Consider changing RMAN archivelog deletion policy. 5. Delete files from recovery area using RMAN.

ORA-19816: WARNING: Files may exist in %s that are not known to database.

    Cause: One of the following events caused this:1. A database crash happened during file creation.2. A backup control file was restored.3. The control file was re-created.4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.

    Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If the file header is corrupted, then delete those files using an OS utility.Do not use messages 19817; it is used for simulating lock failureDo not use messages 19818; it is used for space reclaimation before backup

ORA-38709: Recovery Area is not enabled.

    Cause: An ALTER DATABASE FLASHBACK ON command failed because the Recovery Area was not enabled.

    Action: Set DB_RECOVERY_FILE_DEST to a location and retry.

ORA-38775: cannot disable flash recovery area - flashback database is enabled

    Cause: An attempt was made to set DB_RECOVERY_FILE_DEST to null while flashback database was enabled. Flashback database requires DB_RECOVERY_FILE_DEST to be set.

    Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable flashback database, then disable the flash recovery area.

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.

ORA-38786: Flash recovery area is not enabled.

    Cause: An attempt was made to perform a command that requires Flash recovery area to be enabled.

    Action: Set DB_RECOVERY_FILE_DEST to an appropriate location and retry.

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

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