ORA-19271: XP0051 - invalid atomic type definition

Cause : The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type.

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

Use the correct atomic type name.

update : 27-04-2017

ORA-19271 - XP0051 - invalid atomic type definition
ORA-19271 - XP0051 - invalid atomic type definition

  • ora-36810 : (XSTBLFUNC05) Analytic workspace object number does not exist.
  • ora-06419 : NETCMN: server can not start oracle
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-24065 : propagation for QUEUE string and DESTINATION string already disabled
  • ora-28667 : USING INDEX option not allowed for the primary key of an IOT
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-27500 : inter-instance IPC error
  • ora-29315 : tablespace 'string' has been recreated
  • ora-32124 : Illegal attribute passed
  • ora-22163 : left hand and right hand side collections are not of same type
  • ora-01529 : error closing file 'string'
  • ora-15114 : missing or invalid ASM file name
  • ora-37023 : (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.
  • ora-26669 : parameter string inconsistent with parameter string
  • ora-13801 : invalid value for SQLTUNE_CATEGORY parameter
  • ora-29836 : failed to validate referenced operators
  • ora-19225 : XP0005 - XQuery static type error: expected non empty type got empty sequence
  • ora-39953 : the range value specified is beyond allowed range
  • ora-12653 : Authentication control function failed
  • ora-25265 : specified signature for a queue which does not support reciever non-repudiation
  • ora-29910 : invalid callback operation
  • ora-00306 : limit of string instances in this database
  • ora-38466 : user does not have privileges to CREATE/MODIFY expressions
  • ora-39147 : cannot migrate Data Pump queue table ownership to this instance
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-39601 : Hash key is required.
  • ora-09282 : sllfrb: error reading records
  • ora-10263 : Don't free empty PGA heap extents
  • ora-29952 : cannot issue DDL on a domain index partition marked as LOADING
  • ora-13528 : name (string) is already used by an existing baseline
  • 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.