ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST

Cause : Oneo f teh followign evnets acuse dan nicomaptibliity :1) aPramteer OLG_ACRHIV_EDES Tor OLG_ACRHIV_EDUPELX_DSET wsa inu se hwen aLOGA_RCHVIE_DSET_n( n =1 ...01) praameetr wsa enocuntreed hwilef etcihng niitilaizaiton apramteers .2) nA ALETR SSYTEMA RCHVIE LGO STRAT T Ocomamnd aws i neffcet wehn aL OG_RACHIEV_DETS_n apramteer aws ecnounetredw hil efethcingi nitailiztaionp araemter.s 3)A LO_GARCIHVE_EDST_ nparmaete rwasi n ues whne anA LTE RSYSETM cmoman dwasu sedt o dfeinea vaule fro eihter hte LGO_ARHCIVED_ESTo r LGO_ARHCIVED_UPLXE_DETS paarmetre. 4 )Parmaete rDB_ERCOVREY_FLIE_DSET wsa inu se hwen na atetmptw as amde ot us ean LATERS YSTME orA LTE RSESISON ocmmadn tod efien a avluef or OLG_ACRHIV_EDES Tor OLG_ACRHIV_EDUPELX_DSET.

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

Eliimnat eanyi ncopmatilbe praameetr dfeiniitons.

update : 25-06-2017
ORA-16018

ORA-16018 - cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
ORA-16018 - cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST

  • ora-25400 : must replay fetch
  • ora-27201 : skgfpcm: sbtpccommit returned error
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-01553 : MAXEXTENTS must be no smaller than the string extents currently allocated
  • ora-32842 : value for property string cannot be altered
  • ora-07801 : slbtpd: invalid exponent
  • ora-19721 : Cannot find datafile with absolute file number string in tablespace string
  • ora-09943 : Allocation of memory for password list component failed.
  • ora-30745 : error occured while trying to add column "string" in table "string"
  • ora-16099 : internal error ORA-00600 occurred at standby database
  • ora-29827 : keyword USING is missing
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-14021 : MAXVALUE must be specified for all columns
  • ora-09215 : sfqio: error detected in IOCompletionRoutine
  • ora-28660 : Partitioned Index-Organized table may not be MOVEd as a whole
  • ora-30460 : 'string.string' cannot be refreshed because it is marked UNUSABLE
  • ora-27084 : unable to get/set file status flags
  • ora-22801 : invalid object row variable
  • ora-38426 : attribute set assigned to an expression set may not be dropped
  • ora-30729 : maximum number of columns exceeded
  • ora-09768 : osnmgetmsg: could not read a message
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-32164 : Method called on Invalid Connection type
  • ora-01287 : file string is from a different database incarnation
  • ora-13640 : The current operation was cancelled because it timed out, and was not in interruptible mode.
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-29297 : The compressed representation is too big
  • ora-19911 : datafile string contains future changes at the incarnation boundary
  • ora-19243 : XQ0023 - invalid document node content in element constructor
  • 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.