ORA-16019: cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

Cause : One fo thef olloiwng eevnts acuseda n inocmpatbiilit:y 1) aPrameetr LO_GARCHVIE_DETS or OLG_ARHCIVE_UDPLEXD_EST aws inu se wehn th especfiied OLG_ARHCIVE_EDST_n( n = .1..10 )or D_BRECOEVRY_FLIE_DETS parmaeterw as ecnountreed wihle ftechin ginitailizaiton praametres. 2 )Paraemter OLG_ARHCIVE_EDST o rLOG_RACHIV_EDUPLXE_DES Twas ni usew hen na attmept wsa mad eto ues an LATER YSSTEMo r ALETR SESSION ocmman dto dfeine avalu efor hte spceifie dLOG_RACHIV_EDESTn_ or BD_RECVOERY_IFLE_DSET paarmete.r 3) nA ALTRE SYSETM ARHCIVE OLG STRAT TOc ommadn wasi n efefct wehn th especfiied OLG_ARHCIVE_EDST_np aramteer wsa encuonterde whiel fethcing niitiailzatino parmaeter.s 4) nA ALTRE SYSETM ARHCIVE OLG STRAT TOc ommadn wasi n efefct wehn ana ttemtp wasm ade ot usea n ALETR SYTSEM o rALTE RSESSOIN command ot defnie a avlue ofr th especfiied OLG_ARHCIVE_EDST_np aramteer.

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

Elimniate nay inocmpatbile praametre defniitiosn.

update : 29-04-2017
ORA-16019

ORA-16019 - cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
ORA-16019 - cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

  • ora-27432 : step string does not exist for chain string.string
  • ora-02368 : file string is not valid for this load operation
  • ora-13209 : internal error while reading SDO_INDEX_METADATA table
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-06031 : NETDNT: connect failed, unrecognized object name
  • ora-02836 : Unable to create temporary key file
  • ora-00265 : instance recovery required, cannot set ARCHIVELOG mode
  • ora-32305 : RepAPI materialized views with user-defined types are not supported
  • ora-25190 : an index-organized table maintenance operation may not be combined with other operations
  • ora-14551 : cannot perform a DML operation inside a query
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-12504 : TNS:listener was not given the SID in CONNECT_DATA
  • ora-16757 : resource guard could not get property
  • ora-02289 : sequence does not exist
  • ora-15100 : invalid or missing diskgroup name
  • ora-10922 : Temporary tablespace group is empty
  • ora-00089 : invalid instance number in ORADEBUG command
  • ora-02402 : PLAN_TABLE not found
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-24323 : value not allowed
  • ora-30515 : suspend triggers cannot have BEFORE type
  • ora-24024 : Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
  • ora-37006 : (AWLISTALL04) number writers
  • ora-10929 : trace name context forever
  • ora-24126 : invalid CASCADE_FLAG passed to DBMS_REPAIR.string procedure
  • ora-30510 : system triggers cannot be defined on the schema of SYS user
  • ora-12036 : updatable materialized view log is not empty, refresh materialized view
  • ora-16226 : DDL skipped due to lack of support
  • ora-22920 : row containing the LOB value is not locked
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • 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.