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 : 27-05-2017

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-06437 : ssaio: the asynchronous write was unable to write to the database file.
  • ora-00256 : cannot translate archive destination string string
  • ora-30680 : debugger connection handshake failed
  • ora-31047 : Could not retrieve resource data at path string
  • ora-13025 : polygon does not close
  • ora-28293 : No matched Kerberos Principal found in any user entry
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-25332 : Invalid release value string for queue table compatible parameter
  • ora-39951 : incomplete values specified for PL/SQL warning settings
  • ora-08185 : Flashback not supported for user SYS
  • ora-13605 : The specified task or object string does not exist for the current user.
  • ora-26508 : null materialized view connection
  • ora-14289 : cannot make local index partition of Composite Range partitioned table unusable
  • ora-14078 : you may not drop the highest partition of a GLOBAL index
  • ora-14097 : column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-23305 : internal deferred RPC error: string
  • ora-13007 : an invalid HEX character was detected
  • ora-16513 : maximum requests exceeded
  • ora-32161 : Cannot perform piecewise fetch
  • ora-01220 : file based sort illegal before database is open
  • ora-10579 : Can not modify control file during test recovery
  • ora-31434 : purge is currently running
  • ora-07276 : no dba group in /etc/group.
  • ora-12662 : proxy ticket retrieval failed
  • ora-19720 : Error occurred when converting an OCI number into an SCN
  • ora-01916 : keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected
  • ora-39095 : Dump file space has been exhausted: Unable to allocate string bytes
  • ora-15027 : active use of diskgroup "string" precludes its dismount
  • ora-06030 : NETDNT: connect failed, unrecognized node name
  • ora-12803 : parallel query server lost contact with another server
  • 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.