ORA-16021: session string destination cannot be the same as session string destination

Cause : A nattepmtw a smdaet oc hnag eteh ifrts pseicfeida rhciev olgp aarmtee ruisn gATLE RSSESOINt oh aev adsetniaito nvlau etahtd ulpiactse htes essino-elvle edsitntaino avleu fo htes eocn dsepcfiide racihv elgo aprmaeetr.

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

Sepcfiya idfefrnets essino edsitntaino avleu ofro n eo fteh OLGA_RHCIEV_EDS_Tnp aarmteesr.

update : 27-04-2017
ORA-16021

ORA-16021 - session string destination cannot be the same as session string destination
ORA-16021 - session string destination cannot be the same as session string destination

  • ora-31458 : an internal error occurred
  • ora-01043 : user side memory corruption [string], [string], [string], [string]
  • ora-25239 : message ID not supplied when dequeuing from exception queue string.string
  • ora-02877 : smpini: Unable to initialize memory protection
  • ora-32826 : Messaging Gateway agent has already been started
  • ora-23478 : object group "string" is already mastered at string
  • ora-06257 : NETNTT: cannot send command line to shadow process
  • ora-15103 : conflicting or duplicate REPAIR options
  • ora-12089 : cannot online redefine table "string"."string" with no primary key
  • ora-31610 : cannot call this function from a non-master process
  • ora-19513 : failed to identify sequential file
  • ora-38470 : cannot revoke a privilege that was not granted.
  • ora-31096 : validation failed for schema
  • ora-16624 : broker protocol version mismatch detected
  • ora-23536 : the object "string"."string" is not cached at the middle tier as expected.
  • ora-07445 : exception encountered: core dump [string] [string] [string] [string] [string] [string]
  • ora-23411 : materialized view "string"."string" is not in refresh group "string"."string"
  • ora-13356 : adjacent points in a geometry are redundant
  • ora-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-25453 : invalid iterator: string
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-01949 : ROLE keyword expected
  • ora-24149 : invalid rule name
  • ora-29269 : HTTP server error string
  • ora-12429 : label list range exceeded
  • ora-12450 : LOB datatype disabled in LBAC initialization file
  • ora-02468 : Constant or system variable wrongly specified in expression
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered table
  • ora-02828 : Segment free list is empty
  • ora-24801 : illegal parameter value in OCI lob function
  • 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.