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-05-2017

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-22894 : cannot add constraint on existing unscoped REF columns of non-empty tables
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-32101 : cannot create OCI Environment
  • ora-02157 : no options specified for ALTER USER
  • ora-30051 : VERSIONS clause not allowed here
  • ora-04071 : missing BEFORE, AFTER or INSTEAD OF keyword
  • ora-13118 : invalid node_id [string]
  • ora-30659 : too many locations specified for external table
  • ora-23431 : wrong state: string
  • ora-22893 : constraint can be specified only for REF columns
  • ora-24034 : application string is already a subscriber for queue string
  • ora-06560 : pos, string, is negative or larger than the buffer size, string
  • ora-22921 : length of input buffer is smaller than amount requested
  • ora-00452 : foreground process unexpectedly terminated with error string
  • ora-29395 : cannot set the initial consumer group to string
  • ora-30932 : Reference node 'string' not contained in specified parent node 'string'
  • ora-25336 : Cannot contact instance string during Streams AQ operation
  • ora-19123 : fn:zero-or-one() called with a sequence containing more than one item
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-01879 : the hh25 field must be between 0 and 24
  • ora-01908 : EXISTS keyword expected
  • ora-27193 : sbtinfo2 did not return volume label
  • ora-28547 : connection to server failed, probable Oracle Net admin error
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-07278 : splon: ops$username exceeds buffer length.
  • ora-07822 : sspscm: SYS$CREMBX failure
  • ora-01155 : the database is being opened, closed, mounted or dismounted
  • ora-14646 : Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
  • ora-38959 : Failed to update block 0 to new version 10 format
  • ora-06975 : X.25 Driver: connect to host failed
  • 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.