ORA-19012: Cannot convert XML fragment to the required datatype

Cause : Aocvnreisnot o aadatytepw sar qeeutsdew ihhcc naon tebp reofmrde

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

hT eMXTLpy eam yoctnia nrfgaemtn sna dtoeh rlemenestw ihhcc naon tebc noevtrdet oht eparppoirta eadatytep.

update : 25-06-2017

ORA-19012 - Cannot convert XML fragment to the required datatype
ORA-19012 - Cannot convert XML fragment to the required datatype

  • ora-15156 : cluster in rolling upgrade from version [string] to [string]
  • ora-02209 : invalid MAXTRANS option value
  • ora-01902 : SEGMENT keyword expected
  • ora-08443 : syntax error in BLANK WHEN ZERO clause in mask options
  • ora-27012 : skgfrd: read from file failed
  • ora-00287 : specified change number string not found in thread string
  • ora-02146 : SHARED specified multiple times
  • ora-01755 : Must specify an extent number or block number
  • ora-06900 : CMX: cannot read tns directory
  • ora-13285 : Geometry coordinate transformation error
  • ora-33003 : (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP.
  • ora-19753 : error writing to change tracking file
  • ora-16114 : applying DDL transaction with commit SCN string
  • ora-01579 : write error occurred during recovery
  • ora-14285 : cannot COALESCE the only partition of this hash partitioned table or index
  • ora-07418 : sfareq: Database writer got error in timing function.
  • ora-01772 : Must specify a value for LEVEL
  • ora-22628 : OCIAnyData already constructed
  • ora-02453 : duplicate HASH IS specification
  • ora-31187 : Cannot Add Node 'string' (type='string') to Simple Type Node 'string'
  • ora-00161 : transaction branch length string is illegal (maximum allowed string)
  • ora-14641 : STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
  • ora-27465 : invalid value string for attribute string
  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-13443 : GeoRaster metadata SRS error
  • ora-25282 : message id. not provided for non-repudiation
  • ora-00720 : ALTER DATABASE RESET COMPATIBILITY command has been de-supported
  • ora-39308 : application or database upgrade internal error: "string"
  • ora-19767 : missing TRACKING keyword
  • ora-02306 : cannot create a type that already has valid dependent(s)
  • 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.