ORA-28274: No ORACLE password attribute corresponding to user nickname exists.

Cause : LDAPu ser netry ocrresopndin gto uesr nikcnamed oes ont haev a OARCLE apsswodr attirbuteo r th eattrbiute si noti nitilaized.

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

Makes ure suer etnriesi n LDPA arec orretcly porvisinoed wtih correct ROACLEp asswrod atrtibut evaluse.

update : 18-08-2017

ORA-28274 - No ORACLE password attribute corresponding to user nickname exists.
ORA-28274 - No ORACLE password attribute corresponding to user nickname exists.

  • ora-02267 : column type incompatible with referenced column type
  • ora-14460 : only one COMPRESS or NOCOMPRESS clause may be specified
  • ora-08003 : sequence string.NEXTVAL exceeds internal limits
  • ora-31693 : Table data object string failed to load/unload and is being skipped due to error: string
  • ora-32581 : missing or invalid password
  • ora-01088 : cannot shut down ORACLE while active processes exist
  • ora-16785 : the database is not in ARCHIVELOG mode
  • ora-02854 : Invalid number of request buffers
  • ora-38485 : invalid object type for the user-defined function
  • ora-08186 : invalid timestamp specified
  • ora-10941 : trace name context forever
  • ora-09709 : soacon: failed to accept a connection.
  • ora-29530 : could not create shortened name for string
  • ora-22858 : invalid alteration of datatype
  • ora-06443 : ssvpstev: Incorrect parameter passed to function call
  • ora-04064 : not executed, invalidated string
  • ora-31497 : invalid value specified for first_scn
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • ora-12655 : Password check failed
  • ora-07568 : slspool: $OPEN failure
  • ora-08274 : Out of memory for environment variable
  • ora-26745 : cursors (string) are not sufficient
  • ora-14327 : Some index [sub]partitions could not be rebuilt
  • ora-12921 : database is not in force logging mode
  • ora-39054 : missing or invalid definition of the SQL output file.
  • ora-07801 : slbtpd: invalid exponent
  • ora-19647 : non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
  • ora-26007 : invalid value for SETID or OID column
  • ora-03230 : segment only contains string blocks of unused space above high water mark
  • 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.