ORA-19031: XML element or attribute string does not match any in type string.string

Cause : The passed in XML tag does not match any in the object type

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

Pass a valid canonical XML that can map to the given object type

update : 30-04-2017

ORA-19031 - XML element or attribute string does not match any in type string.string
ORA-19031 - XML element or attribute string does not match any in type string.string

  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-01719 : outer join operator (+) not allowed in operand of OR or IN
  • ora-12640 : Authentication adapter initialization failed
  • ora-31052 : Cannot delete ACL with other references
  • ora-14251 : Specified subpartition does not exist
  • ora-14643 : Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-02168 : invalid value for FREELISTS
  • ora-23385 : replication parallel push string argument not valid
  • ora-15204 : database version string is incompatible with diskgroup string
  • ora-13213 : failed to generate spatial index for window object
  • ora-01195 : online backup of file string needs more recovery to be consistent
  • ora-13635 : The value provided for parameter string cannot be converted to a number.
  • ora-01695 : error converting rollback segment string to version 8.0.2
  • ora-02720 : osnfop: shmat failed
  • ora-38730 : Invalid SCN/TIMESTAMP expression.
  • ora-26725 : cannot downgrade apply handlers
  • ora-33625 : (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.
  • ora-03262 : the file is non-empty
  • ora-33447 : (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.
  • ora-31213 : DBMS_LDAP: PL/SQL - Invalid LDAP mod option.
  • ora-14252 : invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
  • ora-02252 : check constraint condition not properly ended
  • ora-29813 : non-supported object type with associate statement
  • ora-25008 : no implicit conversion to LOB datatype in instead-of trigger
  • ora-29911 : null scan context returned by ODCIIndexStart() routine
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-01158 : database string already mounted
  • ora-01317 : Not attached to a Logminer session
  • ora-00444 : background process "string" failed while starting
  • ora-31019 : Recursive deletion snapshot too old for string/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.