ORA-19010: Cannot insert XML fragments

Cause : MX Lrfgaemtn sog trfmoe txartcoNedc naon tebi snreet dniott ehd tabasa.e

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

oCvnre tht erfgaemtni tn o arpporeX LMd comune teboferi snreitno.

update : 25-04-2017

ORA-19010 - Cannot insert XML fragments
ORA-19010 - Cannot insert XML fragments

  • ora-03297 : file contains used data beyond requested RESIZE value
  • ora-00026 : missing or invalid session ID
  • ora-04044 : procedure, function, package, or type is not allowed here
  • ora-19674 : file string is already being backed up with proxy copy
  • ora-13225 : specified index table name is too long for a spatial index
  • ora-10281 : maximum time to wait for process creation
  • ora-12663 : Services required by client not available on the server
  • ora-02055 : distributed update operation failed; rollback required
  • ora-24016 : cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string
  • ora-24143 : invalid evaluation context name
  • ora-31486 : cannot support column string in this configuration
  • ora-00965 : column aliases not allowed for '*'
  • ora-37143 : (XSSQLMDQ03) string is not a valid analytic workspace name.
  • ora-12719 : operation requires database is in RESTRICTED mode
  • ora-36810 : (XSTBLFUNC05) Analytic workspace object number does not exist.
  • ora-12426 : invalid audit option
  • ora-13625 : %s is an invalid advisor object type.
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-19652 : cannot apply offline-range record to datafile string: file is fuzzy
  • ora-36406 : (VCACHE00) 'number' is an invalid value for the VARCACHE option. The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-12827 : insufficient parallel query slaves available
  • ora-37076 : (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.
  • ora-12158 : TNS:could not initialize parameter subsystem
  • ora-13349 : polygon boundary crosses itself
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-36380 : (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.
  • ora-13014 : a topology identifier outside the range of 1 to 8 was specified
  • ora-12855 : cannot run parallel or insert direct load in a loopback
  • ora-38495 : data type for the stored attribute string is inconsistent.
  • ora-24379 : invalid user callback type
  • 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.