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 : 27-04-2017

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

  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • ora-28575 : unable to open RPC connection to external procedure agent
  • ora-15205 : requested mirror side unavailable
  • ora-24127 : TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
  • ora-06560 : pos, string, is negative or larger than the buffer size, string
  • ora-07636 : smsdbp: $MGBLSC failure
  • ora-16601 : site contains required resources that are disabled
  • ora-22307 : operation must be on a user-defined type
  • ora-02784 : Invalid shared memory ID specified
  • ora-25292 : Buffer operations are not supported on the queue
  • ora-01083 : value of parameter "string" is inconsistent with that of other instances
  • ora-06265 : NETNTT: break protocol error
  • ora-00712 : cannot rename system tablespace
  • ora-31202 : DBMS_LDAP: LDAP client/server error: string
  • ora-12679 : Native services disabled by other process but required
  • ora-12354 : secondary object being dropped
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • ora-04015 : ascending sequences that CYCLE must specify MAXVALUE
  • ora-19597 : file string blocksize string does not match set blocksize of string
  • ora-12150 : TNS:unable to send data
  • ora-25266 : didnt try to dequeue by message id. with the signature
  • ora-07237 : slemcl: invalid file handle, seals do not match.
  • ora-25331 : cannot downgrade because there are commit-time queue tables
  • ora-34143 : (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.
  • ora-19610 : directory block string is corrupt
  • ora-24054 : cannot propagate to an Oracle 8.0.3 release or lower release
  • ora-29704 : cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release
  • ora-12554 : TNS:current operation is still in progress
  • ora-16215 : history metadata inconsistency
  • ora-29532 : Java call terminated by uncaught Java exception: string
  • 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.