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 : 27-06-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-14152 : invalid number of partitions specified in PARTITIONS clause
  • ora-12523 : TNS:listener could not find instance appropriate for the client connection
  • ora-01585 : error identifying backup file string
  • ora-32060 : channel failure
  • ora-27159 : failure setting process scheduling priority
  • ora-07702 : unrecognized device type in archive text
  • ora-15091 : operation incompatible with open handle in this session
  • ora-27300 : OS system dependent operation:string failed with status: string
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-19583 : conversation terminated due to error
  • ora-22931 : MOVE of nested table to a different tablespace not supported
  • ora-12815 : value for INSTANCES must be greater than 0
  • ora-19252 : XQ0032 - too many declarations for base URI
  • ora-25149 : Columns of UROWID type may not be indexed
  • ora-12926 : FORCE LOGGING option already specified
  • ora-13008 : the specified date format has an invalid component
  • ora-34296 : (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
  • ora-01603 : illegal grouping size in clause "string" of string
  • ora-24506 : invalid attempt to change character set id on env handle
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-24157 : duplicate variable name string
  • ora-36831 : (XSLMGEN01) View token cannot be NA
  • ora-19958 : potential deadlock involving DIAG process
  • ora-00282 : UPI string call not supported, use ALTER DATABASE RECOVER
  • ora-07400 : slemtr: translated name for the message file is too long.
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-08114 : can not alter a fake index
  • ora-24402 : error occured while creating connections in the pool
  • ora-38201 : assert if pin during flush
  • ora-16565 : duplicate property, syntax error at "string"
  • 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.