ORA-21614: constraint violation for attribute number [string]

Cause : Constraints on the attribute were violated

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

Correct the value (of the attribute) so that it satisfies constraints

update : 23-06-2017

ORA-21614 - constraint violation for attribute number [string]
ORA-21614 - constraint violation for attribute number [string]

  • ora-38438 : getVarchar not possible due to "string" datatype in the attribute set
  • ora-32606 : missing NAV keyword in MODEL clause
  • ora-06601 : LU6.2 Driver: Invalid database ID string
  • ora-16112 : log mining and apply stopping
  • ora-27211 : Failed to load Media Management Library
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-22875 : cannot drop primary key of an object table whose object identifier is primary key based
  • ora-09282 : sllfrb: error reading records
  • ora-31018 : Error deleting XML document
  • ora-36406 : (VCACHE00) 'number' is an invalid value for the VARCACHE option. The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-07572 : szrfc: insufficient rolename buffer space
  • ora-16796 : one or more properties could not be imported from the database
  • ora-13371 : invalid position of measure dimension
  • ora-02422 : missing or invalid schema element
  • ora-40223 : data mining model import failed, job name=string, error=string
  • ora-12715 : invalid character set specified
  • ora-13830 : SQL profile with category string already exists for this SQL statement
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-27202 : skgfpen: sbtpcend returned error
  • ora-19910 : can not change recovery target incarnation in control file
  • ora-01035 : ORACLE only available to users with RESTRICTED SESSION privilege
  • ora-23502 : valid directory for offline instatiation is not specified
  • ora-34296 : (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
  • ora-24371 : data would not fit in current prefetch buffer
  • ora-00031 : session marked for kill
  • ora-01953 : command no longer valid, see ALTER USER
  • ora-31437 : duplicate change set string
  • ora-28103 : adding a policy to an object owned by SYS is not allowed
  • 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.