You are here: Home // Oracle 11g
ORA-19035: Invalid select item of the query in newContextFromHierarchy()
ORA-19035: Invalid select item of the query in newContextFromHierarchy()
Database version: Oracle 11g Release 2 (11.2)
Cause: The query does not have a number select item followed by an XMLType select item only.
Solution: Make sure the result set of the query used in the newContextFromHierarchy() must have only two selected items: the first item must be number type and the second item must be...
Tags: ora, Oracle 11g Release 2
ORA-19034: Type not supported during schema generation
ORA-19034: Type not supported during schema generation
Database version: Oracle 11g Release 2 (11.2)
Cause: The object type contained a type that is not supported for schema generation.
Solution: Use a different type or do not generate a schema.
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19033: schema specified in the XML document does not match the schema parameter
ORA-19033: schema specified in the XML document does not match the schema parameter
Database version: Oracle 11g Release 2 (11.2)
Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the ’schema’ parameter.
Solution: Change the schema parameter to match the schema specified in the XML document.
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19032: Expected XML tag string got string
ORA-19032: Expected XML tag string got string
Database version: Oracle 11g Release 2 (11.2)
Cause: When converting XML to object, a wrong tag name was present
Solution: Pass a valid canonical XML that can map to the given object type
Read More →
Tags: ora, Oracle 11g Release 2
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
Database version: Oracle 11g Release 2 (11.2)
Cause: The passed in XML tag does not match any in the object type
Solution: Pass a valid canonical XML that can map to the given object type
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19030: Method invalid for non-schema based XML Documents.
ORA-19030: Method invalid for non-schema based XML Documents.
Database version: Oracle 11g Release 2 (11.2)
Cause: The method can be invoked on only schema based xmltype objects.
Solution: Don’t invoke the method for non schema based xmltype objects.
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19029: Cannot convert the given XMLType to the required type
ORA-19029: Cannot convert the given XMLType to the required type
Database version: Oracle 11g Release 2 (11.2)
Cause: The passed in XMLType could not be convert to the required type
Solution: Binary XMLtype instances or other objects cannot be converted to the required object or collection types.
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19028: Invalid ADT parameter passed to toObject() function
ORA-19028: Invalid ADT parameter passed to toObject() function
Database version: Oracle 11g Release 2 (11.2)
Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.
Solution: Pass an object of the correct type to toObject().
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19026: EXTRACTVALUE can only retrieve value of leaf node
ORA-19026: EXTRACTVALUE can only retrieve value of leaf node
Database version: Oracle 11g Release 2 (11.2)
Cause: Given XPath does not point to a leaf node.
Solution: Rewrite the query so that a leaf node is returned.
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19025: EXTRACTVALUE returns value of only one node
ORA-19025: EXTRACTVALUE returns value of only one node
Database version: Oracle 11g Release 2 (11.2)
Cause: Given XPath points to more than one node.
Solution: Rewrite the query so that exactly one node is returned.
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19024: Cursor expression must be named
ORA-19024: Cursor expression must be named
Database version: Oracle 11g Release 2 (11.2)
Cause: The value of context passed to GETXML was invalid.
Solution: Rewrite the query so that the value of context passed to GETXML is valid.
Read More →
Tags: ora, Oracle 11g Release 2
ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE
ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE
Database version: Oracle 11g Release 2 (11.2)
Cause: The first argument passed to the update value operator was not an XMLTYPE.
Solution: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.
Read More →
Tags: ora, Oracle 11g Release 2