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 : 16-08-2017
ORA-28290

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

  • ora-01212 : MAXLOGMEMBERS may not exceed string
  • ora-07642 : smprtset: $CMKRNL failure
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-29961 : too many warnings occurred in the execution of ODCIIndex DDL routine
  • ora-31698 : Error stack buffer size must be specified and must be greater than 0.
  • ora-30486 : invalid window aggregation group in the window specification
  • ora-03254 : unable to execute the sql in read only database
  • ora-06006 : NETASY: dialogue execute failure
  • ora-06400 : NETCMN: No default host string specified
  • ora-29282 : invalid file ID
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-08332 : rollback segment #string specified not available
  • ora-26673 : duplicate column name string
  • ora-01172 : recovery of thread string stuck at block string of file string
  • ora-00031 : session marked for kill
  • ora-32140 : cannot peform this operation on stream
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-32579 : password for SYSTEM already specified
  • ora-16402 : ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
  • ora-13761 : invalid filter
  • ora-03250 : Cannot mark this segment corrupt
  • ora-00101 : invalid specification for system parameter DISPATCHERS
  • ora-19682 : file string not in block media recovery context
  • ora-29910 : invalid callback operation
  • ora-36961 : Oracle OLAP is not available.
  • ora-23534 : missing column in materialized view container table "string"."string"
  • ora-24197 : JAVA stored procedure throws JAVA exceptions
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-22833 : Must cast a transient type to a persistent type
  • 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.