ORA-28279: Error reading ldap_directory_access init parameter.

Cause : ldap_directory_access parameter is not specified corrrectly.

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

Make sure spfile.ora has ldap_directory_access set correctly. Possible correct values are PASSWORD, SSL and NONE.

update : 29-04-2017

ORA-28279 - Error reading ldap_directory_access init parameter.
ORA-28279 - Error reading ldap_directory_access init parameter.

  • ora-32058 : operation restricted to SYSDBA users
  • ora-27452 : %s is an invalid name for a database object.
  • ora-23536 : the object "string"."string" is not cached at the middle tier as expected.
  • ora-14637 : cannot merge a subpartition with itself
  • ora-40213 : contradictory values for settings: string, string
  • ora-00404 : Convert file not found: 'string'
  • ora-13143 : invalid POLYGON window definition
  • ora-32005 : error while parsing size specification [string]
  • ora-24054 : cannot propagate to an Oracle 8.0.3 release or lower release
  • ora-13361 : not enough sub-elements within a compound ETYPE
  • ora-31204 : DBMS_LDAP: PL/SQL - Invalid LDAP Session.
  • ora-02142 : missing or invalid ALTER TABLESPACE option
  • ora-19656 : cannot backup, copy, or delete online log string
  • ora-10654 : Table is of type temporary or external
  • ora-12545 : Connect failed because target host or object does not exist
  • ora-26501 : RepAPI operation failure
  • ora-39206 : A parallel degree of string is invalid.
  • ora-39754 : FULL PARTITIONED OUTER JOIN is not supported
  • ora-12202 : TNS:internal navigation error
  • ora-31901 : the current operation was cancelled by the user
  • ora-03299 : cannot create dictionary table string
  • ora-33262 : (DBERR01) Analytic workspace string does not exist.
  • ora-13051 : failed to initialize spatial object
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-13346 : the coordinates defining an arc are collinear
  • ora-19527 : physical standby redo log must be renamed
  • ora-01451 : column to be modified to NULL cannot be modified to NULL
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-30956 : invalid option for XML 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.