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-05-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-02210 : no options specified for ALTER TABLE
  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • ora-19320 : Host name not specified in HTTP URL
  • ora-25329 : AQ array operations not allowed on 8.0 queues
  • ora-16790 : the value of the configurable property is invalid
  • ora-24352 : invalid COBOL display type passed into OCI call
  • ora-39309 : schema sync operation failed
  • ora-16599 : Data Guard broker detected a stale configuration
  • ora-19029 : Cannot convert the given XMLType to the required type
  • ora-00292 : parallel recovery feature not installed
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-06523 : Maximum number of arguments exceeded
  • ora-01545 : rollback segment 'string' specified not available
  • ora-28049 : the password has expired
  • ora-27155 : could not execute file
  • ora-03216 : Tablespace/Segment Verification cannot proceed
  • ora-26664 : cannot create STREAMS process string
  • ora-31090 : invalid database schema name "string"
  • ora-06514 : PL/SQL: The remote call cannot be handled by the server
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-16775 : target standby database in broker operation has potential data loss
  • ora-30727 : duplicate referential constraint for a REF column
  • ora-01374 : _log_parallelism_max greater than 1 not supported in this release
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-26677 : Streams downstream capture process string cannot proceed
  • ora-25401 : can not continue fetches
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-35020 : (QFCHECK02) The analytic workspace and EIF file definitions of workspace object have mismatched dimensioning.
  • ora-26527 : local store callback init phase failed for 'string.string'
  • 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.