ORA-19812: cannot use string without DB_RECOVERY_FILE_DEST

Cause : Three rae htre epossibel cuasef ort hi serorr:1 ) hTe nidiacte dpaarmeetr aws ni ues wehn on D_BREOCVEYR_FLIE_EDSTp armaetre wsa ecnoutnerde wihlef ethcin gth eintiiailzaitonp armaetre. )2 A natetmp twa smaed t ose tinidcaetd hte apraemte rwiht teh ATLERS YSETM ocmmnad hwenn o BD_RCEOVREY_IFLED_ES Twa sinu se .3)A n tatepmt aws amdet o lcea rDBR_ECVOER_YFIEL_DSET iwtht heA LTRE SSYTE Mcomman dwhne teh idnictaedp armaetre wsa i nus.e

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

Elmiintae nay nicopmatbilep armaetre dfeintiiosn.

update : 19-08-2017
ORA-19812

ORA-19812 - cannot use string without DB_RECOVERY_FILE_DEST
ORA-19812 - cannot use string without DB_RECOVERY_FILE_DEST

  • ora-27086 : unable to lock file - already in use
  • ora-31527 : could not find source column string for CDC change table string.string
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-00960 : ambiguous column naming in select list
  • ora-28137 : Invalid FGA audit Handler
  • ora-03002 : operator not implemented
  • ora-36970 : (XSRELTBL12) workspace object must be a self-relation.
  • ora-37156 : (string)
  • ora-01515 : error dropping log group string: no such log
  • ora-24058 : cannot downgrade QUEUE_TABLE that has propagation in a prepared state
  • ora-09986 : wrong number of bytes read from SGA definition file
  • ora-32314 : REFRESH FAST of "string"."string" unsupported after deletes/updates
  • ora-01939 : only the ADMIN OPTION can be specified
  • ora-09285 : sllfop: unrecognizable processing option, incorrect format
  • ora-24369 : required callbacks not registered for one or more bind handles
  • ora-01217 : logfile member belongs to a different logfile group
  • ora-39172 : Cannot remap transportable tablespace names with compatibility of string.
  • ora-29900 : operator binding does not exist
  • ora-25256 : consumer cannot be specified with a single-consumer queue or an exception queue
  • ora-19852 : error creating services for auxiliary instance string (error string)
  • ora-02711 : osnpvalid: write to validation channel failed
  • ora-14260 : incorrect physical attribute specified for this partition
  • ora-07208 : sfwfb: failed to flush dirty buffers to disk.
  • ora-30000 : missing either trim specification or char expression in TRIM
  • ora-01619 : thread string is mounted by another instance
  • ora-13224 : zero tolerance specified for layer in USER_SDO_GEOM_METADATA
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-00277 : illegal option to the UNTIL recovery flag string
  • ora-12205 : TNS:could not get failed addresses
  • ora-32622 : illegal multi-cell reference
  • 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.