ORA-28275: Multiple mappings for user nickname to LDAP distinguished name exist.

Cause : The given user nickname maps to more than one LDAP distinguished name.

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

Make sure user nickname is unique within the enterprise.

update : 26-04-2017

ORA-28275 - Multiple mappings for user nickname to LDAP distinguished name exist.
ORA-28275 - Multiple mappings for user nickname to LDAP distinguished name exist.

  • ora-39091 : unable to determine logical standby and streams status
  • ora-14172 : invalid ALTER TABLE EXCHANGE SUBPARTITION option
  • ora-09342 : Detached process terminated by Oracle during shutdown abort
  • ora-10936 : trace name context forever
  • ora-23366 : integer value string is less than 1
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-12446 : Insufficient authorization for administration of policy string
  • ora-10266 : Trace OSD stack usage
  • ora-39126 : Worker unexpected fatal error in string [string] string
  • ora-24096 : invalid message state specified
  • ora-12411 : invalid label value
  • ora-22807 : cannot resolve to a scalar type or a collection type
  • ora-24756 : transaction does not exist
  • ora-21300 : objects option not installed
  • ora-21603 : property id [string] is invalid
  • ora-08454 : more than one S symbol specified in picture mask
  • ora-30177 : invalid flag used in a format specification
  • ora-30011 : Error simulated: psite=string, ptype=string
  • ora-30343 : level name is not unique within this dimension
  • ora-14195 : ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object
  • ora-01309 : invalid session
  • ora-12619 : TNS:unable to grant requested service
  • ora-23456 : flavor string does not contain "string"
  • ora-00474 : SMON process terminated with error
  • ora-16571 : Data Guard configuration file creation failure
  • ora-04013 : number to CACHE must be less than one cycle
  • ora-02170 : FREELIST GROUPS storage option not allowed
  • ora-00057 : maximum number of temporary table locks exceeded
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-23341 : user function required
  • 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.