ORA-28271: No permission to read user entry in LDAP directory service.

Cause : ORACLE server does not have read permission on user nickname's X.500 user entry.

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

Make sure ORACLE server is using right SSL credentials to connect to LDAP directory services. Make sure permissions for LDAP user entries are right.

update : 28-04-2017
ORA-28271

ORA-28271 - No permission to read user entry in LDAP directory service.
ORA-28271 - No permission to read user entry in LDAP directory service.

  • ora-08002 : sequence string.CURRVAL is not yet defined in this session
  • ora-01256 : error in locking database file string
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-01180 : can not create datafile 1
  • ora-28117 : integrity constraint violated - parent record not found
  • ora-22898 : existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
  • ora-29536 : badly formed source: string
  • ora-16815 : incorrect redo transport setting for AlternateLocation for standby database "string"
  • ora-01422 : exact fetch returns more than requested number of rows
  • ora-29970 : Specified registration id does not exist
  • ora-19671 : media management software returned invalid proxy handle
  • ora-13636 : The specified value provided for parameter string is not valid for this advisor.
  • ora-30152 : File does not exist
  • ora-39171 : Job is experiencing a resumable wait. string
  • ora-13388 : invalid value for dst_spec parameter
  • ora-01724 : floating point precision is out of range (1 to 126)
  • ora-22609 : error string during initialization of FDO
  • ora-09341 : scumnt: unable to mount database
  • ora-25017 : cannot reference NEW ROWID for movable rows in before triggers
  • ora-30973 : invalid Path Table option for XML Index
  • ora-12322 : unable to mount database (link name string)
  • ora-07625 : smsget: $MGBLSC failure
  • ora-29293 : A stream error occurred during compression or uncompression.
  • ora-14026 : PARTITION and CLUSTER clauses are mutually exclusive
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-16019 : cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
  • ora-00312 : online log string thread string: 'string'
  • ora-00130 : invalid listener address 'string'
  • ora-02274 : duplicate referential constraint specifications
  • ora-32136 : Cannot perform operation on an invalid stream
  • 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.