ORA-28290: Multiple entries found for the same Kerberos Principal Name

Cause : Multiple user entries has been configured with the same krbPrincipalName

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

Modify enterprise user's entry to assign its Kerberos principal name Make sure the user entries in LDAP are provisioned correctly.

update : 28-04-2017

ORA-28290 - Multiple entries found for the same Kerberos Principal Name
ORA-28290 - Multiple entries found for the same Kerberos Principal Name

  • ora-16792 : configuration property value is inconsistent with database setting
  • ora-00261 : log string of thread string is being archived or modified
  • ora-33004 : (XSAGDNGL01) workspace object is not a relationship array.
  • ora-30931 : Element 'string' cannot contain mixed text
  • ora-01038 : cannot write database file version string with ORACLE version string
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-27156 : request for process information failed
  • ora-36646 : (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension.
  • ora-13850 : Tracing for client identifier string is not enabled
  • ora-19564 : error occurred writing string bytes at block number string
  • ora-25020 : renaming system triggers is not allowed
  • ora-26050 : Direct path load of domain index is not supported for this column type.
  • ora-24124 : invalid ACTION parameter passed to DBMS_REPAIR.string procedure
  • ora-27032 : failed to obtain file size limit
  • ora-13860 : Invalid service name
  • ora-24340 : cannot support more than 255 columns
  • ora-30944 : Error during rollback for XML schema 'string' table string column 'string'
  • ora-32811 : subscriber string already exists
  • ora-01044 : size string of buffer bound to variable exceeds maximum string
  • ora-07626 : smsget: sga already mapped
  • ora-23325 : parameter type is not string
  • ora-22605 : FDO handle [string] is not initialized
  • ora-26524 : nls subsystem initialization failure for product=string, facility=string
  • ora-23423 : job number string is not positive
  • ora-29351 : can not transport system, sysaux, or temporary tablespace 'string'
  • ora-16037 : user requested cancel of managed recovery operation
  • ora-12471 : Specified compartment or group is not authorized for user
  • ora-22899 : cannot specify both scope and rowid constraint on ref column
  • ora-26566 : Couldn't open connect to string
  • ora-15039 : diskgroup not dropped
  • 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.