ORA-24960: the attribute string is greater than the maximum allowable length of number

Cause : Th eusre attemtpedt o apssa n tatrbiut ethta i sto ologn

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

Shrote nth espceifeid tatrbiut ean drerty hte poertaio.n

update : 24-04-2017
ORA-24960

ORA-24960 - the attribute string is greater than the maximum allowable length of number
ORA-24960 - the attribute string is greater than the maximum allowable length of number

  • ora-03208 : partitioned type must be specified for a non-composite object
  • ora-31194 : Resource string is already deleted
  • ora-36222 : (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object
  • ora-01121 : cannot rename database file string - file is in use or recovery
  • ora-29296 : invalid encoded string
  • ora-29893 : indextypes without column data do not need the given data type
  • ora-07232 : slemcc: fclose error.
  • ora-31164 : cannot load object-relational XML attribute using direct path
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-22859 : invalid modification of columns
  • ora-02364 : error writing to file: string
  • ora-10371 : disable TQ hint
  • ora-14008 : missing THAN keyword
  • ora-22343 : Compilation error for type invalidated by ALTER TYPE
  • ora-24327 : need explicit attach before authenticating a user
  • ora-16558 : the database specified for switchover is not a standby database
  • ora-09818 : Number is too large
  • ora-14327 : Some index [sub]partitions could not be rebuilt
  • ora-13230 : failed to create temporary table [string] during R-tree creation
  • ora-29392 : cpu parameters for level string for plan string must be zero
  • ora-14271 : table is not partitioned by Composite Range method
  • ora-31218 : DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn.
  • ora-22632 : AnyDataSet parameter is not valid for the current operation
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-30369 : maximum number of columns is 32
  • ora-30082 : datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
  • ora-25142 : default storage clause specified twice
  • ora-31105 : User does not own lock "string"
  • ora-14624 : DEFAULT subpartition must be last subpartition specified
  • ora-12618 : TNS:versions are incompatible
  • 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.