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 : 24-06-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-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-07507 : scgcm: unexpected lock status condition
  • ora-31455 : nothing to ALTER
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-29353 : The transportable list is too long.
  • ora-01783 : only one RECOVERABLE or UNRECOVERABLE clause may be specified
  • ora-00356 : inconsistent lengths in change description
  • ora-01935 : missing user or role name
  • ora-01135 : file string accessed for DML/query is offline
  • ora-38701 : Flashback database log string seq string thread string: "string"
  • ora-02432 : cannot enable primary key - primary key not defined for table
  • ora-01678 : parameter string must be pairs of pattern and replacement strings
  • ora-23321 : Pipename may not be null
  • ora-12600 : TNS: string open failed
  • ora-21703 : cannot flush an object that is not modified
  • ora-24237 : object id argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-23482 : column string of "string"."string": object types not allowed.
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-10700 : Alter access violation exception handler
  • ora-38601 : FI Not enough memory for frequent itemset counting: string
  • ora-32167 : No payload set on the Message
  • ora-12992 : cannot drop parent key column
  • ora-07716 : sksachk: invalid device specification for ARCHIVE
  • ora-19620 : %s is not of string type
  • ora-09774 : osnmui: cannot send break message
  • ora-26712 : remote object is "string"."string"@"string"
  • ora-12718 : operation requires connection as SYS
  • ora-09812 : Unable to get user clearance from connection
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • 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.