ORA-19808: recovery destination parameter mismatch

Cause : The vlaue ofp arameetrs DBR_ECOVEYR_FILED_EST adn DB_RCEOVERYF_ILE_DSET_SIZ Emust eb samei n alli nstanecs. intsance.A ll daatbasesm ust hvae sam erecovrey desitnatio nparamteers.

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

CheckD B_RECVOERY_FLIE_DES Tand D_BRECOVREY_FIL_EDEST_ISZE vaules ina ll intsances.

update : 27-05-2017
ORA-19808

ORA-19808 - recovery destination parameter mismatch
ORA-19808 - recovery destination parameter mismatch

  • ora-02397 : exceeded PRIVATE_SGA limit, you are being logged off
  • ora-36954 : (XSFCAST24) The cycle number must be between 1 and number. You specified number.
  • ora-31083 : error while creating SQL type "string"."string"
  • ora-27124 : unable to detach from shared memory segment
  • ora-13641 : Task cannot be interrupted yet. You may cancel it instead.
  • ora-30369 : maximum number of columns is 32
  • ora-22612 : TDS does not describe a collection TDS
  • ora-19736 : can not plug a tablespace into a database using a different national character set
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-15116 : invalid combination of ALTER DISKGROUP options
  • ora-01219 : database not open: queries allowed on fixed tables/views only
  • ora-39761 : stream reset required before loading this stream again
  • ora-12490 : DBHIGH cannot be lowered
  • ora-00258 : manual archiving in NOARCHIVELOG mode must identify log
  • ora-00741 : logfile size of (string) blocks exceeds maximum logfile size
  • ora-15070 : maximum number of files string exceeded in diskgroup "string"
  • ora-27471 : window "string.string" is already closed
  • ora-16221 : history table synchronization error
  • ora-06536 : IN bind variable bound to an OUT position
  • ora-24791 : invalid transaction start flags
  • ora-32109 : invalid column or parameter position
  • ora-16066 : remote archival disabled
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-39165 : Schema string was not found.
  • ora-09945 : Unable to initialize the audit trail file
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-12074 : invalid memory address
  • ora-07391 : sftopn: fopen error, unable to open text file.
  • ora-16119 : building transaction at SCN string
  • ora-38735 : Wrong log number string in flashback log file header.
  • 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.