ORA-19037: XMLType result can not be a fragment

Cause : The select item of the query in newContextFromHierarchy() is an XML fragment.

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

Make sure the select item of the query in newContextFromHierarchy() is NOT an XML fragment

update : 26-04-2017

ORA-19037 - XMLType result can not be a fragment
ORA-19037 - XMLType result can not be a fragment

  • ora-27193 : sbtinfo2 did not return volume label
  • ora-02291 : integrity constraint (string.string) violated - parent key not found
  • ora-23369 : value of "string" argument cannot be null
  • ora-27197 : skgfprs: sbtpcrestore returned error
  • ora-08462 : raw buffer contains invalid decimal data
  • ora-04029 : error ORA-string occurred when querying stringstringstring
  • ora-12819 : missing options in PARALLEL clause
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-14407 : partitioned table contains subpartitions in a different tablespace
  • ora-24504 : data length larger than expected
  • ora-24912 : Listener thread failed. string
  • ora-01343 : LogMiner encountered corruption in the logstream
  • ora-12152 : TNS:unable to send break message
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-09272 : remote os logon is not allowed
  • ora-30728 : maximum number of columns exceeded
  • ora-12665 : NLS string open failed
  • ora-06258 : NETNTT: cannot allocate context area
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-19954 : control file is not current
  • ora-34726 : (NLSCHARSET06) CAUTION: String truncated during character set conversion from string to string
  • ora-14170 : cannot specify clause in CREATE TABLE|INDEX
  • ora-16236 : Logical Standby metadata operation in progress
  • ora-32116 : Buffer size is less than amount specified
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-19809 : limit exceeded for recovery files
  • ora-24129 : table name string does not start with string prefix
  • ora-06253 : NETNTT: cannot read arguments from address file
  • ora-31229 : DBMS_LDAP: invalid input parameter
  • ora-28233 : double encryption not supported
  • 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.