ORA-28234: key length too short

Cause : Thek ey pseciifed si to oshotr fo rthea lgoirthm .DESr equries akeyo f a tleats 8 ybtes .Trilpe DSE reuqire sa kye ofl eas t16 ybtesi n tow-ke ymod eand2 4 btyes ni there-kye moed.

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

Speicfy alonegr kye.

update : 25-05-2017

ORA-28234 - key length too short
ORA-28234 - key length too short

  • ora-01488 : invalid nibble or byte in the input data
  • ora-16056 : backup control file archival requires proper syntax
  • ora-06504 : PL/SQL: Return types of Result Set variables or query do not match
  • ora-29521 : referenced name string could not be found
  • ora-37131 : (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE.
  • ora-23375 : feature is incompatible with database version at string
  • ora-24041 : propagation schedule exists for QUEUE string and DESTINATION string
  • ora-02327 : cannot create index on expression with datatype string
  • ora-27084 : unable to get/set file status flags
  • ora-00302 : limit of string logs exceeded
  • ora-14118 : CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-26513 : push error: master proc. string$RP.string failed for trans:string seq:string
  • ora-30041 : Cannot grant quota on the tablespace
  • ora-24777 : use of non-migratable database link not allowed
  • ora-13050 : unable to construct spatial object
  • ora-24048 : cannot create QUEUE_TABLE, user does not have access to AQ object types
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-38956 : Target platform string not cross platform compliant
  • ora-26677 : Streams downstream capture process string cannot proceed
  • ora-38429 : invalid datatype for a stored attribute: string
  • ora-24789 : start not allowed in recursive call
  • ora-00317 : file type string in header is not log file
  • ora-06916 : CMX: error in data read (t_datain)
  • ora-13751 : "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set".
  • ora-12637 : Packet receive failed
  • ora-06745 : TLI Driver: listener already running
  • ora-07658 : slsprom:$QIOW read failure
  • ora-27150 : attempt to notify process of pending oradebug call failed
  • ora-16055 : FAL request rejected
  • ora-16809 : multiple warnings detected for the database
  • 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.