ORA-28273: No mapping for user nickname to LDAP distinguished name exists.

Cause : ORACLE server cannot map the given user nickname to LDAP distinguished name.

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

Make sure user entries in LDAP are correctly provisioned with correct user nickname attribute values.

update : 23-04-2017
ORA-28273

ORA-28273 - No mapping for user nickname to LDAP distinguished name exists.
ORA-28273 - No mapping for user nickname to LDAP distinguished name exists.

  • ora-06793 : TLI Driver: server cannot create new process
  • ora-16644 : apply instance not available
  • ora-27191 : sbtinfo2 returned error
  • ora-13499 : %s
  • ora-39083 : Object type string failed to create with error: string Failing sql is: string
  • ora-32603 : invalid FREEPOOLS LOB storage option value
  • ora-23622 : Operation string.string.string is in progress.
  • ora-17506 : I/O Error Simulation
  • ora-14288 : index is not partitioned by Composite Range method
  • ora-14169 : invalid ALTER TABLE MODIFY SUBPARTITION option
  • ora-36410 : (VCACHE03) 'number' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-09811 : Unable to initialize package.
  • ora-10917 : TABLESPACE GROUP cannot be specified
  • ora-02093 : TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)
  • ora-12900 : must specify a default temporary tablespace for a locally managed database
  • ora-31648 : Timeout before master process string finished initialization.
  • ora-16764 : redo transport service to a standby database is offline
  • ora-33280 : (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.
  • ora-15045 : ASM file name 'string' is not in reference form
  • ora-13753 : "SQL Tuning Set" "string" already exists for user "string".
  • ora-03208 : partitioned type must be specified for a non-composite object
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-09844 : soacon: Archmon unable to open named pipe.
  • ora-02246 : missing EVENTS text
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-25263 : no message in queue string.string with message ID string
  • ora-30053 : invalid upper limit snapshot expression
  • ora-13118 : invalid node_id [string]
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-16177 : media recovery is not 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.