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 : 19-08-2017

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-09966 : falure in translation while expanding ?/dbs/lk for lock file
  • ora-06407 : NETCMN: unable to set up break handling environment
  • ora-16239 : IMMEDIATE option not available without standby redo logs
  • ora-12523 : TNS:listener could not find instance appropriate for the client connection
  • ora-13777 : invalid list of attribute names
  • ora-06402 : NETCMN: error receiving break message
  • ora-19586 : %s k-byte limit is too small to hold piece directory
  • ora-16147 : standby database referenced by multiple archive log destinations
  • ora-12515 : TNS:listener could not find a handler for this presentation
  • ora-14007 : missing LESS keyword
  • ora-01340 : NLS error
  • ora-29336 : Internal error [string] [string] from DBMS_PLUGTS
  • ora-07401 : sptrap: cannot restore user exception handlers.
  • ora-01417 : a table may be outer joined to at most one other table
  • ora-32511 : cannot create watchpoint in memory needed by watchpointing code
  • ora-19562 : file string is empty
  • ora-02057 : 2PC: string: bad two-phase recovery state number string from string
  • ora-10701 : Dump direct loader index keys
  • ora-23306 : schema string does not exist
  • ora-22341 : cannot assign supertype instance to subtype
  • ora-28002 : the password will expire within string days
  • ora-29353 : The transportable list is too long.
  • ora-13209 : internal error while reading SDO_INDEX_METADATA table
  • ora-10583 : Can not recovery file string renamed as missing during test recovery
  • ora-08432 : raw data has invalid floating point data
  • ora-10663 : Object has rowid based materialized views
  • ora-09353 : Windows 32-bit Two-Task driver unable to open event semaphore
  • ora-30037 : Cannot perform parallel DML after a prior DML on the object
  • ora-01538 : failed to acquire any rollback segment
  • ora-24158 : invalid table alias
  • 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.