ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set

Cause : An tatemtp wa smad eto rceat ea flie i nDB_ERCOVREY_FLIE_DSET wehn D_BRECVOERYF_ILED_ESTw as ont ste. Tehre rae nmubero f psosibel casues fo thsi erorr, nicluidng:1 ) AL OG_RACHIEV_DETS_n apramteer aws sepcifeid uisng aLOCTAIONa ttrbiutew hos evaleu wa sDB_ERCOVREY_FLIE_DSET adn ana rchvielo gfil ecretaionw as tatemtped.2 ) SATNDB_YARCIHVE_EDST apramteer aws sepcifeid uisng aLOCTAIONa ttrbiutew hos evaleu wa sDB_ERCOVREY_FLIE_DSET adn ana rchvielo gfil ecretaionw as tatemtped.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Speicfy avaldi detsinaiton ofr D_BRECVOERYF_ILED_ESTi n iintiailzatoin praameetr flie o rwit htheA LTE RSYSETM STE command.

update : 19-08-2017
ORA-19801

ORA-19801 - initialization parameter DB_RECOVERY_FILE_DEST is not set
ORA-19801 - initialization parameter DB_RECOVERY_FILE_DEST is not set

  • ora-22320 : missing user version string
  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • ora-32019 : The parameter SPFILE cannot be updated in the server parameter file.
  • ora-29286 : internal error
  • ora-30400 : identical JOIN KEY clauses
  • ora-30031 : the suspended (resumable) statement has been aborted
  • ora-00290 : operating system archival error occurred. See error below
  • ora-09218 : sfrfs: failed to refresh file size
  • ora-19738 : cannot find language information for character set: 'string'
  • ora-12718 : operation requires connection as SYS
  • ora-25265 : specified signature for a queue which does not support reciever non-repudiation
  • ora-24393 : invalid mode for creating connection pool
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-19113 : trace function called during evaluation: string
  • ora-06017 : NETASY: message receive failure
  • ora-16582 : could not edit instance specific property
  • ora-19851 : OS error while managing auxiliary database string
  • ora-36968 : (XSRELTBL11) workspace object must be a relation.
  • ora-07670 : $IDTOASC failed translating a secrecy category
  • ora-00321 : log string of thread string, cannot update log file header
  • ora-14082 : new partition name must differ from that of any other partition of the object
  • ora-12436 : no policy options specified
  • ora-14159 : duplicate subpartition name
  • ora-01484 : arrays can only be bound to PL/SQL statements
  • ora-30695 : JDWP message format problem
  • ora-32577 : username must be SYS or SYSTEM
  • ora-25186 : INCLUDING clause specified for index-organized table without OVERFLOW
  • ora-07842 : sllfcl: SYS$CLOSE failure
  • ora-19705 : tag value exceeds maximum length of string characters
  • ora-07626 : smsget: sga already mapped
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.