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-06-2017
ORA-28275

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-09314 : sltln: error translating logical name
  • ora-30101 : unknown parameter name 'string'
  • ora-30347 : a table name is required to qualify the column specification
  • ora-16019 : cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-26006 : Incorrect bind variable in column string's sql expression - string
  • ora-19738 : cannot find language information for character set: 'string'
  • ora-12673 : Dedicated server: context not saved
  • ora-13752 : User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
  • ora-33002 : (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.
  • ora-07568 : slspool: $OPEN failure
  • ora-32734 : Error occurred when sending Oradebug command to remote DIAGs
  • ora-19010 : Cannot insert XML fragments
  • ora-29907 : found duplicate labels in primary invocations
  • ora-08003 : sequence string.NEXTVAL exceeds internal limits
  • ora-32811 : subscriber string already exists
  • ora-40109 : inconsistent logical data record
  • ora-14172 : invalid ALTER TABLE EXCHANGE SUBPARTITION option
  • ora-19109 : RETURNING keyword expected
  • ora-28356 : invalid open wallet syntax
  • ora-40282 : invalid cost matrix
  • ora-16166 : LGWR network server failed to send remote message
  • ora-00443 : background process "string" did not start
  • ora-27001 : unsupported device type
  • ora-02200 : WITH GRANT OPTION not allowed for PUBLIC
  • ora-13502 : Cannot rename SYSAUX tablespace
  • ora-01878 : specified field not found in datetime or interval
  • ora-21610 : size [string] is invalid
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-29870 : specified options are only valid for altering a domain index
  • 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.