ORA-19227: XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.

Cause : The inptu node fro atomiztaion conatined a ytpe annoattion thta denote da complxe type wtih non-mxied compelx contetn.

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

Fix thei nput exrpession ot fn:dat ato be an ode tha tdoes no tcontainn on-mixe dcomplexc ontent.

update : 29-06-2017
ORA-19227

ORA-19227 - XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
ORA-19227 - XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.

  • ora-19553 : device name string is invalid
  • ora-24165 : invalid rule engine object privilege: string
  • ora-16038 : log string sequence# string cannot be archived
  • ora-12161 : TNS:internal error: partial data received
  • ora-23361 : materialized view "string" does not exist at master site
  • ora-12700 : invalid NLS parameter value (string)
  • ora-30358 : summary and materialized view are not in same schema
  • ora-32057 : invalid lock mode
  • ora-09311 : slsleep: error temporarily suspending process
  • ora-13480 : the Source Type is not supported
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-28651 : Primary index on IOTs can not be marked unusable
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-02242 : no options specified for ALTER INDEX
  • ora-19249 : XP0029 - value does not match facet of the target type
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-01923 : CASCADE aborted, objects locked by another user
  • ora-19686 : SPFILE not restored due to string
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-08267 : destroy_ora_addr: cannot close nameserver
  • ora-16792 : configuration property value is inconsistent with database setting
  • ora-06538 : statement violates string RESTRICT_REFERENCES pragma
  • ora-10918 : TABLESPACE GROUP name cannot be the same as tablespace name
  • ora-22816 : unsupported feature with RETURNING clause
  • ora-19378 : invalid mode
  • ora-12201 : TNS:encountered too small a connection buffer
  • ora-19753 : error writing to change tracking file
  • ora-16807 : unable to change database protection mode
  • ora-14006 : invalid partition name
  • ora-19591 : backup aborted because job time exceeded duration time
  • 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.