ORA-09271: szlon: error verifying user name

Cause : Username may be too long

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

See OSD error accompanying this message

update : 24-04-2017

ORA-09271 - szlon: error verifying user name
ORA-09271 - szlon: error verifying user name

  • ora-39124 : dump file name "string" contains an invalid substitution variable
  • ora-01143 : cannot disable media recovery - file string needs media recovery
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-16056 : backup control file archival requires proper syntax
  • ora-14186 : number of sub-partitions of LOCAL index must equal that of the underlying table
  • ora-27101 : shared memory realm does not exist
  • ora-15163 : cluster not in rolling downgrade
  • ora-01074 : cannot shut down ORACLE; inside a login session - log off first
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-25229 : error on transformation of message string string
  • ora-38477 : attribute set cannot be derived from an evolved type or a subtype.
  • ora-27160 : process requested to perform operation
  • ora-28290 : Multiple entries found for the same Kerberos Principal Name
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-12712 : new character set must be a superset of old character set
  • ora-31613 : Master process string failed during startup.
  • ora-24094 : invalid transformation, target type does not match that of the queue
  • ora-19275 : XP0055 - schema path string not found in list of in-scope schema definitions
  • ora-29823 : object being analyzed is not a table
  • ora-25310 : Subscriber is Notification only; dequeue not supported
  • ora-00155 : cannot perform work outside of global transaction
  • ora-13022 : polygon crosses itself
  • ora-31442 : operation timed out while acquiring lock on string
  • ora-39086 : cannot retrieve job information
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-02451 : duplicate HASHKEYS specification
  • ora-04021 : timeout occurred while waiting to lock object stringstringstringstringstring
  • ora-39702 : database not open for UPGRADE or DOWNGRADE
  • ora-01560 : LIKE pattern contains partial or illegal character
  • 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.