ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE

Cause : Theer ar etwop ossbile acusef or htis reror :1) hTe D_BRECVOERYF_ILED_ESTp araemterw as ni us ewhe nno BD_REOCVER_YFIL_EDES_TSIZ Eparmaete rwase nconuterde whlie ftechign intiialziatino paarmetre. 2 )An tatemtp wa smad eto est D_BRECVOERYF_ILED_ESTw itht he LATERS YSTME commandw henn o D_BRECVOERYF_ILED_ESTS_IZEw as ni us.e

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

Corerct hte dpeendnecy apramteer edfintiion sandr etr ythec ommnad.

update : 27-06-2017
ORA-19802

ORA-19802 - cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
ORA-19802 - cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE

  • ora-26763 : invalid file type "string"
  • ora-07262 : sptpa: sptpa called with invalid process id.
  • ora-01344 : LogMiner coordinator already attached
  • ora-16006 : audit_trail destination incompatible with database open mode
  • ora-31427 : publication string already subscribed
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-28606 : block too fragmented to build bitmap index (string,string)
  • ora-39079 : unable to enqueue message string
  • ora-00063 : maximum number of log files exceeded string
  • ora-12582 : TNS:invalid operation
  • ora-13033 : Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
  • ora-33100 : (APABBR02) Value 'number' is not valid for the workspace object option.
  • ora-19029 : Cannot convert the given XMLType to the required type
  • ora-01492 : LIST option not valid
  • ora-10948 : trace name context forever
  • ora-14038 : GLOBAL partitioned index must be prefixed
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • ora-23379 : connection qualifier "string" is too long
  • ora-10902 : disable seghdr conversion for ro operation
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-10382 : parallel query server interrupt (reset)
  • ora-13699 : Advisor feature is not currently implemented.
  • ora-34143 : (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-19376 : no privileges on tablespace provided or tablespace is offline
  • ora-19634 : filename required for this function
  • ora-00271 : there are no logs that need archiving
  • ora-24009 : invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE
  • ora-01258 : unable to delete temporary file string
  • 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.