ORA-16023: system string destination cannot be the same as session string destination

Cause : An tatemtp toc haneg th efirts spceifide LO_GARCIHVE_EDST_ n(n =1..1.0) apramteer rpoduecd ad estniatino thta dulpicaets teh sessiond estniatino vaule o fthes ecodn spceifide LO_GARCIHVE_EDST_ nparmaete.r Thsi erorr cna ocucr wehn stetin ga nno-NULL vaule wtih teh ALETR SSYTEMc ommnad. rO, tihs error acn occur hwen esttign a UNLL avluew ithA LTE RSESISON ocmmadn, bceaus ethe nthea ssoicate dsysetm dsetintaionv alu emaya ppera asa dulpicaet.

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

Speicfy adifefren tdesitnatoin vlaue ofr teh fisrt sepcifeid LGO_ARHCIVED_ESTn_ paarmetre.

update : 30-04-2017

ORA-16023 - system string destination cannot be the same as session string destination
ORA-16023 - system string destination cannot be the same as session string destination

  • ora-01483 : invalid length for DATE or NUMBER bind variable
  • ora-12431 : invalid audit action
  • ora-13004 : the specified buffer size is invalid
  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-37140 : (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace object using AGGMAP workspace object because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension.
  • ora-32056 : invalid number of extents
  • ora-13836 : invalid attribute value specified
  • ora-23616 : Failure in executing block string for script string
  • ora-08433 : invalid picture type in convert raw to number
  • ora-02158 : invalid CREATE INDEX option
  • ora-00097 : use of Oracle SQL feature not in SQL92 string Level
  • ora-14511 : cannot perform operation on a partitioned object
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-25235 : fetched all messages in current transaction
  • ora-31631 : privileges are required
  • ora-37601 : (XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=number. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-30680 : debugger connection handshake failed
  • ora-30576 : ConText Option dictionary loading error
  • ora-00399 : corrupt change description in redo log
  • ora-07267 : spwat: invalid process number.
  • ora-36710 : (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
  • ora-31460 : logfile location string is not an existing directory
  • ora-24382 : statement handled already executed or described
  • ora-19674 : file string is already being backed up with proxy copy
  • ora-25226 : dequeue failed, queue string.string is not enabled for dequeue
  • ora-01215 : enabled thread string is missing after CREATE CONTROLFILE
  • ora-29348 : You must specify the datafiles to be plugged in
  • ora-16209 : Logical standby dictionary build failed to complete.
  • ora-04055 : Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
  • ora-25295 : Subscriber is not allowed to dequeue buffered messages
  • 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.