ORA-28026: user with same external name already exists

Cause : The external name specified for the user being created or altered already exists for another user.

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

External names must be unique among users. Specify another.

update : 24-05-2017
ORA-28026

ORA-28026 - user with same external name already exists
ORA-28026 - user with same external name already exists

  • ora-36630 : (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-13913 : The threshold cannot be set when SYSAUX is offline.
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-06815 : TLI Driver: could not link SPX and IPX streams
  • ora-12592 : TNS:bad packet
  • ora-00313 : open failed for members of log group string of thread string
  • ora-13525 : error with computing space usage for sysaux occupant
  • ora-14324 : values being added already exist in DEFAULT partition
  • ora-06440 : ssaio: the asynchronous read returned incorrect number of bytes
  • ora-14019 : partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
  • ora-00404 : Convert file not found: 'string'
  • ora-16136 : Managed Standby Recovery not active
  • ora-19716 : error processing format string to generate name for backup
  • ora-02050 : transaction string rolled back, some remote DBs may be in-doubt
  • ora-30006 : resource busy; acquire with WAIT timeout expired
  • ora-10854 : Sets poll count used for AQ listen code under RAC
  • ora-27303 : additional information: string
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-17505 : ksfdrsz:string Failed to resize file to size string blocks
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-39766 : invaid stream specified for column array conversion
  • ora-22370 : incorrect usage of method string
  • ora-14086 : a partitioned index may not be rebuilt as a whole
  • ora-16229 : PDML child string string string for parent string string string cannot be skipped.
  • ora-16114 : applying DDL transaction with commit SCN string
  • ora-22876 : this user-defined type is not allowed or it cannot be used in this context
  • ora-24125 : Object string.string has changed
  • ora-02440 : Create as select with referential constraints not allowed
  • ora-37082 : Invalid percent
  • 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.