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

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

  • ora-24122 : invalid block range specification
  • ora-12994 : drop column option only allowed once in statement
  • ora-35578 : (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
  • ora-08323 : scnmin: close of bias lock failed
  • ora-25315 : unsupported configuration for propagation of buffered messages
  • ora-25218 : enqueue failed, delay must be zero for queue string.string
  • ora-27142 : could not create new process
  • ora-03211 : The segment does not exist or is not in a valid state
  • ora-19239 : XP0019 - step expression must return sequence of nodes
  • ora-30433 : 'string.string' is not a summary
  • ora-26571 : %s.string.string: number of arguments (string) does not match replication catalog
  • ora-06043 : NETDNT: message send failure
  • ora-07257 : spdcr: translation error expanding program name.
  • ora-40251 : no support vectors were found
  • ora-08499 : Warning: picture mask options 'string' ignored by UTL_PG
  • ora-16511 : messaging error using ksrget
  • ora-13862 : Statistics aggregation for client identifier string is not enabled
  • ora-09265 : spwat: error temporarily suspending process
  • ora-26536 : refresh was aborted because of conflicts caused by deferred transactions
  • ora-33012 : (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
  • ora-39006 : internal error
  • ora-24130 : table string does not exist
  • ora-00284 : recovery session still in progress
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-01415 : too many distinct aggregate functions
  • ora-29528 : invalid Java call in trigger string
  • ora-31107 : Action failed as resource "string" is locked by name lock
  • ora-24005 : must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
  • ora-25508 : database is not mounted
  • ora-30646 : schema for external table type must be SYS
  • 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.