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 : 18-08-2017
ORA-28026

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

  • ora-07505 : scggt: $enq parent lock unexpected return
  • ora-29520 : name string resolved to a class in schema string that could not be accessed
  • ora-19331 : Last argument to CREATE_DBURI operator must be a column
  • ora-01141 : error renaming data file string - new file 'string' not found
  • ora-16205 : DDL skipped due to skip setting
  • ora-12518 : TNS:listener could not hand off client connection
  • ora-30972 : invalid ALTER INDEX option for XML Index
  • ora-09777 : osnpbr: cannot send break message
  • ora-30046 : Undo tablespace string not found in control file.
  • ora-15102 : invalid POWER expression
  • ora-00568 : Maximum number of interrupt handlers exceeded
  • ora-38785 : Media recovery must be enabled for guaranteed restore point.
  • ora-01374 : _log_parallelism_max greater than 1 not supported in this release
  • ora-08236 : smsget: cannot share subcube with listener
  • ora-23395 : object "string"."string" of type "string" does not exist or is invalid
  • ora-22626 : Type Mismatch while constructing or accessing OCIAnyData
  • ora-29862 : cannot specify FORCE option for dropping non-domain index
  • ora-01291 : missing logfile
  • ora-22859 : invalid modification of columns
  • ora-13119 : invalid edge_id [string]
  • ora-38432 : EVALUATE operator only allowed on an expression column
  • ora-06315 : IPA: Invalid connect string
  • ora-24153 : rule set string.string already exists
  • ora-12015 : cannot create a fast refresh materialized view from a complex query
  • ora-19679 : RMAN configuration number string is outside valid range of 1 through string
  • ora-14319 : DEFAULT cannot be specified with other values
  • ora-02713 : osnprd: message receive failure
  • ora-31663 : metadata remap name can not be defaulted
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • ora-01101 : database being created currently mounted by some other instance
  • 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.