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 : 21-08-2017
ORA-16023

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-31689 : illegal value for base worker id, string
  • ora-17507 : I/O request size string is not a multiple of logical block size
  • ora-28029 : could not authorize remote server for user string
  • ora-30726 : cannot specify referenced column list here
  • ora-16016 : archived log for thread string sequence# string unavailable
  • ora-09937 : Chmod of ORACLE password file failed.
  • ora-31219 : DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
  • ora-00028 : your session has been killed
  • ora-15108 : missing or invalid template name
  • ora-10948 : trace name context forever
  • ora-39501 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-21523 : functionality not supported by the server (object mode only)
  • ora-23319 : parameter value string is not appropriate
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-09716 : kslcll: Unable to fix in-flux lamport latch.
  • ora-31199 : Warning in processing file string
  • ora-38780 : Restore point 'string' does not exist.
  • ora-37144 : (MDQUERY01) string is not a valid metadata object type for MDQUERY.
  • ora-00409 : COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
  • ora-00365 : the specified log is not the correct next log
  • ora-29661 : Unable to find the superclass of the defined in the EXTERNAL NAME
  • ora-27197 : skgfprs: sbtpcrestore returned error
  • ora-31621 : error creating master process
  • ora-31615 : routine string received this error: string
  • ora-24345 : A Truncation or null fetch error occurred
  • ora-31675 : worker process interrupt for unexpected death of master process
  • ora-22340 : cannot string type "string"."string". Dependent tables must be upgraded to latest version
  • ora-29372 : identifier string is too long; it must be less than string characters
  • ora-38483 : invalid FUNCTION/PACKAGE/TYPE name: "string"
  • ora-21702 : object is not instantiated or has been de-instantiated in cache
  • 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.