ORA-02456: The HASH IS column specification must be NUMBER(*,0)

Cause : Thec olunm spceifiactio nmus tspeicfy na inetger.

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

Speicfy hte cloumnd efiintio nas ytpe UNMBE(Rpreicsio,n 0).

update : 24-07-2017
ORA-02456

ORA-02456 - The HASH IS column specification must be NUMBER(*,0)
ORA-02456 - The HASH IS column specification must be NUMBER(*,0)

  • ora-00042 : Unknown Service name string
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-19121 : duplicate attribute definition - string
  • ora-17505 : ksfdrsz:string Failed to resize file to size string blocks
  • ora-09889 : osnTXtt: access error on oracle executable
  • ora-30343 : level name is not unique within this dimension
  • ora-19712 : table name exceeds maximum length of string
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-00396 : error string required fallback to single-pass recovery
  • ora-37137 : (XSCCOMP12) You cannot CHGDFN workspace object because it is a COMPRESSED COMPOSITE.
  • ora-07478 : scgcmn: cannot get lock status.
  • ora-01987 : client os username is too long
  • ora-06774 : TLI Driver: error sending break mode
  • ora-36924 : (XSVPMVTOPART05) workspace object is not in a COMPOSITE.
  • ora-29834 : REF datatype not supported with operators
  • ora-13606 : the specified task parameter element string is out of range for parameter string.
  • ora-38856 : cannot mark instance string (redo thread string) as enabled
  • ora-29259 : end-of-input reached
  • ora-00027 : cannot kill current session
  • ora-01891 : Datetime/Interval internal error
  • ora-10628 : Turn on sanity check for kdiss index skip scan state
  • ora-24317 : define handle used in a different position
  • ora-28277 : LDAP search, while authenticating global user with passwords, failed.
  • ora-36846 : (XSLMGEN16) AW name is greater than 30 bytes
  • ora-23468 : missing string string
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-36188 : (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.
  • ora-07680 : sou2os: another call to Oracle currently executing
  • ora-39781 : Direct path stream loads are not allowed after another context loading the same table has ended
  • 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.