| Oracle® XML Developer's Kit Programmer's Guide, 11g Release 1 (11.1) Part Number B28394-01 |
|
|
View PDF |
| Oracle® XML Developer's Kit Programmer's Guide, 11g Release 1 (11.1) Part Number B28394-01 |
|
|
View PDF |
This section lists error messages that may be encountered in applications that use Oracle XDK for Java. These are divided into these principal sections:
See Also:
http://www.w3.org/TR/xquery/#id-errors for the XQuery error messagesThese error messages may occur during the execution of XML interfaces.
These error messages are in the range XML-20000 through XML-20999.
An expected token was not found in the input data.
Action: Check/update the input data to fix the syntax error.
Cause: An expected keyword was not found in the input data.
Action: Check/update the input data to the correct keyword.
Cause: An expected keyword was not found in the input data.
Action: Check/update the input data to the correct keyword.
Cause: More text was found after the end-tag of the root element.
Action: The end-tag of the root element can be followed only by comments, PI, or white space. Remove the extra text after the end-tag.
Cause: The element declaration was missing the required content model spec See Production [45] in XML 1.0 2nd Edition.
Action: Add the required content spec to the element declaration.
Cause: The content model in the element declaration was invalid, the content particle requires an element name. See Production [48] in XML 1.0 2nd Edition.
Action: Add the element name to fix the content spec syntactically.
Cause: The target names "XML: xml", and so on are reserved for standardization in future versions of XML specification. See Production [17] in XML 1.0 2nd Edition.
Action: If the PI is meant to be XML declaration, make sure the declaration occurs at the very beginning of the file. Otherwise, change to name of the PI.
Cause: The notation name used in the unparsed entity declaration did not match the name in a declared notation. See Production [76] in XML 1.0 2nd Edition.
Action: Add the notation declaration to the DTD.
Cause: The attribute type was missing the attribute-list declaration. One of the following types CDATA, ID, IDREF, IDREFS, ENTITY, ENTITIES, NMTOKEN, or NMTOKENS must be added. See Production [52], [53] in XML 1.0 2nd Edition.
Action: Check and correct attribute declaration.
Cause: The required white space was missing.
Action: Add white space to fix the syntax error.
Cause: An invalid character was used in the entity value, the characters'&', '%' and (" or ' based on the value delimiters) are invalidSee Production [9] in XML 1.0 2nd Edition.
Action: Use entity or character references instead of the characters For example, & or & can be used instead of '&'
Cause: A syntax error in comment due to the use of "--"See Production [15] in XML 1.0 2nd Edition.
Action: Fix the comment, and use "--" only as part of end of comment "-->"
Cause: "]]>" is not allowed in text, it is used only as end marker forCDATA Section. See Production [14] in XML 1.0 2nd Edition.
Action: Fix the text content by using > or char ref for '>'
Cause: White space is not allowed in the contentspec before the occurrenceindicator. For example, <!ELEMENT x (a,b) *> is not valid. See Production [47], [48] in XML 1.0 2nd Edition.
Action: Fix the contentspec by removing the extra space
Cause: Occurrence is not allowed in mixed content declaration.For example, <!ELEMENT x (#PCDATA)?> is not valid. See Production [51] in XML 1.0 2nd Edition.
Action: Fix the syntax to remove the occurrence indicator.
Cause: Content list is not allowed in mixed-content declaration. For example, <!ELEMENT x (#PCDATA | (a,b))> is not valid.See Production [51] in XML 1.0 2nd Edition.
Action: Fix the syntax to remove the content list.
Cause: Duplicate element name was found in mixed-content declaration. For example, <!ELEMENT x (#PCDATA | a | a)> is not valid. See Production [51] in XML 1.0 2nd Edition.
Action: Remove the duplicate element name.
Cause: failed: The Name in the document type declaration must match the element type of the root element. For example: <?xml version="1.0"?> <!DOCTYPE greeting [ <!ELEMENT greeting (#PCDATA)> ]> <salutation>Hello!</salutation> The document's root element, salutation, does not match the root element declared in the DTD (greeting).
Action: Correct the document.
Cause: Element was declared twice in the DTD.
Action: Remove the duplicate declaration.
Cause: failed: No element type may have more than one ID attribute specified.
Action: Correct the document, by removing the duplicate ID attribute decl
Cause: failed: An ID attribute must have a declared default of #IMPLIED or #REQUIRED.
Action: Fix the attribute declaration.
Cause: failed: If the default declaration is the keyword #REQUIRED, then the attribute must be specified for all elements of the type in the attribute-list declaration.
Action: Fix the input document by specifying the required attribute.
Cause: Values of type ID must match the Name production. A name must not appear more than once in an XML document as a value of this type; i.e., ID values must uniquely identify the elements which bear them.
Action: Fix the input document by removing the duplicate ID value.
Cause: failed "Values of type IDREF must match value of some ID attribute.
Action: Fix the document by adding an ID corresponding the to the IDREF, or removing the IDREF
Cause: failed: Values of this type must match one of the Nmtoken tokens in the declaration.
Action: Fix the attribute value to match one of the enumerated values.
Cause: failed: If an attribute has a default value declared with the #FIXED keyword, instances of that attribute must match the default value.
Action: Update the attribute value to match the fixed default value.
Cause: The declared default value must meet the lexical constraints o the declared attribute type.
Action: Use one of REQUIRED, IMPLIED, or FIXED for attribute default decl.
Cause: The element does not allow text in content. An element is valid if there is a declaration matching element decl where the Name matches the element type, and one of the following holds:
The declaration matches children and the sequence of child elements belongs to the language generated by the regular expression in the content model, with optional white space (characters matching the nonterminal S) between the start-tag and the first child element, between child elements, or between the last child element and the end-tag. Note that a CDATA section containing only white space does not match the nonterminal S, and hence cannot appear in these positions.
Action: Fix the content by removing unexpected text.
Cause: The element has invalid content. An element is valid if there is a declaration matching element decl where the Name matches the element type, and one of the following holds:
1. The declaration matches children and the sequence of child elements belongs to the language generated by the regular expression in the content model, with optional white space (characters matching the nonterminal S) between the start-tag and the first child element, between child elements, or between the last child element and the end-tag. Note that a CDATA section containing only white space does not match the non-terminal S, and hence cannot appear in these positions.
2. The declaration matches Mixed and the content consists of character data and child elements whose types match names in the content model.
Action: Fix the content by removing unexpected elements.
Cause: The element has invalid content. An element is valid if there is a declaration matching elementdecl where the Name matches the element type, and one of the following holds:
1. The declaration matches children and the sequence of child elements belongs to the language generated by the regular expression in the content model, with optional white space (characters matching the non-terminal S) between the start-tag and the first child element, between child elements, or between the last child element and the end-tag. Note that a CDATA section containing only white space does not match the nonterminal S, and hence cannot appear in these positions.
2. The declaration matches Mixed and the content consists of character data and child elements whose types match names in the content model.
Action: Fix the content by removing unexpected elements.
Cause: Parameter-entity replacement text must be properly nested with markup declarations. That is to say, if either the first character or the last character of a markup declaration (markup decl above) is contained in the replacement text for a parameter-entity reference, both must be contained in the same replacement text.
Action: Fix the entity value.
Cause: The Name in an element's end-tag must match the element type in the start-tag.
Action: Fix the end-tag or start-tag to match the other.
Cause: No attribute name may appear more than once in the same start-tag o rempty-element tag.
Action: Remove the duplicate attribute.
Cause: An invalid character was used in the attribute value, the characters'&', '<' and (" or ' based on the value delimiters) are invalid. See Production [10] in XML 1.0 2nd Edition.
Action: Use entity or character references instead of the characters For example, & or & can be used instead of '&'
Cause: Attribute values cannot contain direct or indirect entity references to external entities.
Action: Fix document to remove reference to external entity in attribute.
Cause: An entity reference must not contain the name of an unparsed entity.Unparsed entities may be referred to only in attribute values declared to be of type ENTITY or ENTITIES.
Action: Fix document to remove reference to unparsed entity in content.
Cause: Invalid attribute type was used in the attribute-list declaration. One of the following types CDATA, ID, IDREF, IDREFS, ENTITY, ENTITIES, NMTOKEN, or NMTOKENS must be added. See Production [52], [53] in XML 1.0 2nd Edition. failed.
Action: Check and correct attribute declaration.
Cause: Characters referred to using character references must match the production for Char.
Action: Fix the document by removing the invalid character or char-ref.
Cause: A parsed entity must not contain a recursive reference to itself, either directly or indirectly.
Action: Fix the document.
Cause: Values of this type must match one of the Nmtoken tokens in the declaration, and must be valid Nmtoken"
Action: Fix the attribute value.
Cause: Invalid character used in public identifier. See Production [12], [13] in XML 1.0 2nd Edition.
Action: Fix the public identifier.
Cause: The prefix was not defined in any namespace declaration in scope.
Action: Add a namespace declaration to define the prefix.
Cause: Values of type ENTITY must match the Name production, values of type ENTITIES must match Names; each Name must match the name of an unparsed entity declared in the DTD.
Action: Fix the attribute value to refer to an unparsed entity.
Cause: Values of this type must match one of the notation names included in the declaration; all notation names in the declaration must be declared.
Action: Fix the notation name in the unparsed entity declaration.
Cause: The element declaration referred to by an attribute declaration was not found in the DTD.
Action: Fix the DTD by adding the element declaration.
Cause: Warning regarding duplicate entity declaration.
Action: No action required.
Cause: NDATA declaration was found in parameter entity declaration. It is allowed only in general unparsed entity declaration. See Production [72], [74] in XML 1.0 2nd Edition.
Action: Fix the entity declaration.
Cause: Warning regarding duplicate attribute declaration.
Action: No action required.
Cause: Only one notation declaration can declare a given Name.
Action: Fix the document by removing the duplicate notation.
Cause: The attribute declaration was not found in the DTD.
Action: Fix the DTD by adding the attribute declaration.
Cause: The element declaration was not found in the DTD.
Action: Fix the DTD by adding the element declaration.
Cause: The entity declaration was not found in the DTD.
Action: Fix the DTD by adding the element declaration.
Cause: The document returned by createDocument function of NodeFactory was invalid, either it was null or instance of an unsupported class.
Action: Fix NodeFactory implementation to return an instance of XMLDocument or its subclass.
Cause: The SAX feature supplied was not a valid feature name.
Action: Refer to documentation for a valid list of features.
Cause: The value supplied for the SAX feature was not valid.
Action: Refer to documentation for a valid list of features and their corresponding values.
Cause: The SAX property supplied was not a valid property name.
Action: Refer to documentation for a valid list of properties.
Cause: The value supplied for the SAX property was not valid.
Action: Refer to documentation for a valid list of properties and their corresponding values.
Cause: An error occurred while opening the supplied URL.
Action: Verify the URL, and take appropriate action to allow data to be read.
Cause: The input data contained bytes that are not valid w.r.t to UTF8encoding scheme.
Action: Fix the input data.
Cause: The XML Parser does not support 5-byte UTF8 encoding scheme. It is also possible that invalid UTF8 characters were misinterpreted as5-byte UTF8 encoding.
Action: If the data contains invalid UTF8 bytes, fix the input, otherwise if 5-byte UTF8 supported is required, please contact Oracle Support.
Cause: The XML Parser does not support 6-byte UTF8 encoding scheme. It is also possible that invalid UTF8 characters were misinterpreted as6-byte UTF8 encoding.
Action: If the data contains invalid UTF8 bytes, fix the input, otherwise if 6-byte UTF8 supported is required, please contact Oracle Support.
Cause: Invalid XML character was found in the input data.
Action: Fix the input data.
Cause: The encoding of the data (either by auto-detection or user supplied)didn't match the encoding specified in the XML declaration.
Action: Fix the XML declaration to match the encoding of the data.
Cause: The XML Parser does not support the specified encoding.
Action: If the support for the encoding is required, please contact Oracle Support.
Cause: An invalid instance of InputSource was returned by the EntityResolverAn InputSource can be invalid if the none of Reader, InputStream, andSystemId were initialized or if the SystemId was invalid.
Action: Fix the EntityResolver class to return a valid instance of InputSource
These error messages are in the range XML-21000 through XML-21999.
Cause: An invalid size or count was passed to a DOM function.
Action: Correct the argument passed to a valid value.
Cause: An invalid index was passed to a DOM function.
Action: Correct the argument passed to a valid value specified by the bounds in the error message.
Cause: The DOM operation was trying to a add an ancestor node as a child. This can lead to inconsistencies in the tree, so it is not allowed.
Action: Check the application to fix the usage.
Cause: The DOM specification does not allow the parent-child combinationused in the DOM operation.
Action: Refer to DOM specification to fix the usage.
Cause: The XML well-formedness requires that the document node have onlyone element node as its child. The application tried adding addinga second element node.
Action: Fix usage in the application.
Cause: The attribute list (instance of NamedNodeMap) can contain onlyattribute nodes.
Action: Fix usage of NamedNodeMap.
Cause: The node being added was created by a different document. The DOMspecification does not allow use of nodes across documents.
Action: Use importNode or adoptNode to move a node from one document to another, before adding it.
Cause: The qualified or local name passed was invalid.
Action: Fix the name to contain only valid
Cause: The node of the specified type cannot have value.
Action: Fix usage of DOM functions.
Cause: The descendants of entity or entity reference nodes are read-onlynodes, and modification is not allowed.
Action: Fix usage of DOM functions.
Cause: DTD and all its content is read-only and cannot be modified.
Action: Fix usage of DOM functions.
Cause: An attempt was made to remove an attribute that does not belong thecurrent element.
Action: Fix usage in application.
Cause: An attempt was made to remove an node that does not belong thecurrent node as a child.
Action: Fix usage in application.
Cause: The DOM parameter was not recognized.
Action: See documentation for a valid list of parameters.
Cause: The DOM parameter was not recognized.
Action: See documentation for a valid list of parameters.
Cause: An attempt was made to add an attribute that belonged theanother element.
Action: Fix usage in application.
Cause: The namespace for xml, and xmlns prefixes is fixed, and usage mustmatch these.
Action: Correct the namespace for the prefixes, namespaces are xml = http://www.w3.org/XML/1998/namespace xmlns = http://www.w3.org/2000/xmlns/
Cause: The qualified name passed to a DOM function was invalid.
Action: Fix the qualified name.
Cause: The DOM tree has conflicting namespace declarations for the sameprefix. Such a DOM tree cannot be serialized.
Action: Fix the DOM tree, before printing it.
Cause: The object was detached, no operations are supported ona detached object. The object can be a Range or iterator object
Action: Fix the usage in application.
Cause: The boundary specified in the range was invalid. The selectioncan be partial only for text nodes.
Action: Fix the usage in the application.
Cause: The range operation is not supported on the node type specified.
Action: Refer to DOM documentation for restrictions of node types for each range operation.
Cause: The event type passed was invalid.
Action: Fix usage in the application.
Cause: The application tried to set prefix on a node on which prefix is notallowed
Action: Fix usage in the application.
Cause: The application tried to import a node of type DOCUMENT orDOCUMENT FRAGMENT.
Action: Fix usage in the application.
Cause: The application tried to import a node of type other than ELEMENT orATTRIBUTE.
Action: Fix usage in the application.
Cause: A node contains an invalid character, eg. CDATA section contain a termination character - ]]>
Action: Set appropriate DOMConfiguration parameter.
Cause: Namespace fixup cannot be performed on this node - ]]>
Action: Set namespace normalization to false.
These error messages are in the range XML-22000 through XML-22999.
Cause: A required child was not found.
Action: After error mesgfreeze is over, throws an error (without the required child element, it can do nothing).
Cause: a required child is missing.
Action: without the required child, it can do nothing, so throws an error.
Cause: the "select" attribute and sequence constructor should be mutually exclusive for this instruction.
Action: None. Throw an error.
Cause: the "use" attribute and sequence constructor should be mutually exclusive for this instruction.
Action: None. Throw an error.
These error messages are in the range XML-23000 through XML-23999.
Cause: This was an error returned by the XPath/XQuery datamodel or XPathF&O.
Action: Check the XPath expression.
Cause: This error was caused by using the kindtest schema-element or schema-attribute. These are not supported for this release.
Action: Remove usage of schema-element or schema-attribute kindtest
Cause: During the evaluation phase, there was a type error as thevalue did not match a required type specified by the matchingrules in XPath 2.0 SequenceType Matching.
Action: Modify the stylesheet to reflect the correct type.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
Cause: This was an XPath 2.0 F&O specification error.
Action: Check the XPath expression.
These error messages are in the range XML-24000 through XML-24099.
Cause: An unexpected error occoured during processing
Action: Report the error
Cause: [cvc-assess-attr.1] The attribute were not expected for owner element
Action: Add the attribute declaration to the type of the owner element
Cause: [cvc-assess-elt.1.1.1.1]The element declaration required by processorfor validation was absent.
Action: Add the element declaration to schema, or change the instance document to comply to schema.
Cause: [cvc-assess-elt.1.1.1.2] The element declaration required by context was missing in schema
Action: Add the element declaration to schema
Cause: [cvc-assess-elt.1.1.1.3] The context-determined declaration was not skip and the declaration that matches the element could not be foundin schema
Action: Add the element declaration to schema or change the context-determined declaration to skip
Cause: [cvc-attribute.1] Attribute declaration was absent from element declaration
Action: Add the attribute declaration to schema.
Cause: [cvc-attribute.2] Missing type definition for the attribute declaration
Action: Specify a data type for the attribute declaration.
Cause: [cvc-attribute.3] Invalid attribute value with respect to its type
Action: Correct the attribute value in instance.
Cause: [cvc-au] Attribute's normalized value was not the same as the fixedvalue declared.
Action: Change attribute value to the required value.
Cause: [cvc-complex-type.1] The type of this element was specified as abstract.
Action: Remove the abstract attribute from the type definition.
Cause: [cvc-complex-type.2.1] The content type was specified empty while the actual content was not.
Action: Make the content empty or modify the content type of this element.
Cause: [cvc-complex-type.2.2] Element was declared with simple content, but instance had element children.
Action: Use only character content for this element.
Cause: [cvc-complex-type.2.3] Characters appeared in the content of element with element-only content.
Action: Use only element children for this element.
Cause:[cvc-complex-type.2.5] More than one attributes with type ID or its derivation matched attribute wildcard.
Action: Do not use more than one attriubtes with ID or ID derived type.
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid with respect to string type.
Action: Correct the value to satisfy the declared type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid with respect to boolean type.
Action: Correct the value to satisfy boolean type, valid values are "0: 1", "true", and"false".
Cause: [cvc-datatype-valid.1.2.2] Characters could not be parsed into a decimal value.
Action: Correct the data value to satisfy decimal type.
Cause: [cvc-datatype-valid.1.2.2] Characters could not be parsed into a float value.
Action: Correct the value to satisfy string type
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid double format as specified in IEEE 754-1985.
Action: Correct the value to satisfy double format.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in correct extended date time format defined in ISO 8601.
Action: Correct the value to satisfy format PnYnMnDTnHnMnS.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid calendar date format specified in ISO 8601.
Action: Correct the value to satisfy CCYY-MM-DD format.
Comments: cvc-datatype-valid.1.2.2
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid combined data time format as specified in ISO 8601
Action: Correct the value to satisfy format CCYY-MM-DDThh:mm:ss with optional timezoon.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid time format as specified in ISO 8601.
Action: Correct the value to satisfy foramt DDThh:mm:ss with optional timezone.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid right-truncated date format, as specified in ISO 8601.
Action: Correct the value to satisfy format CCYY-MM.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid right-truncateddate format, as specified in ISO 8601.
Action: Correct the value to satisfy format CCYY.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid left-truncateddate format, as specified in ISO 8601.
Action: Correct the value to required foramt --MM-DD.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid left-truncated date format, as specified in ISO 8601.
Action: Correct the value to required format ---DD.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid left-and-right-truncated date format, as specified in ISO 8601.
Action: Correct the value to required format --MM--.
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid hex encoded binary.
Action: Correct the value to satisfy hexBinary type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid with respect to base64 encoding.
Action: Correct the value to satisfy base64 binary encoding.
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid format as specified in RFC 2396 and RFC 2732.
Action: Correct the value to satisfy anyURI type
Cause: [cvc-datatype-valid.1.2.2] Characters were not in valid QName format.
Action: Correct the value to satisfy QName type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for NOTATION type.
Action: Correct the value to satisfy NOTATION type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid normalizedStringvalue.
Action: Correct the value to satisfy normalizedString type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for token type.
Action: Correct the value to satisfy token type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for language type.
Action: Correct the value to satisfy language type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for NMTOKEN type.
Action: Correct the value to satisfy NMTOKEN type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid list of NMTOKEN type.
Action: Correct the value to satisfy NMTOKENS type.
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for Name type.
Action: Correct the value to satisfy Name type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for NCName type.
Action: Correct the value to satisfy NCName type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for ID type.
Action: Correct the value to satisfy ID type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for IDREF type.
Action: Correct the value to satisfy IDREF type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for ENTITY type
Action: Correct the value to satisfy ENTITY type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid list ofENTITY value.
Action: Correct the value to satisfy ENTITIES type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for integertype.
Action: Correct the value to satisfy integer type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for nonPositiveInteger type.
Action: Correct the value to satisfy nonPositiveInteger type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for negativeInteger type.
Action: Correct the value to satisfy negativeInteger type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for long type.
Action: Correct the value to satisfy long type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for int type.
Action: Correct the value to satisfy int type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for short type.
Action: Correct the value to satisfy short type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for byte type.
Action: Correct the value to satisfy byte type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for nonNegativeInteger type.
Action: Correct the value to satisfy nonNegativeInteger type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for unsignedlong type.
Action: Correct the value to satisfy unsignedlong type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value of unsignedInt.
Action: Correct the value to satisfy unsignedInt type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for unsignedShort type.
Action: Correct the value to satisfy unsignedShort type
Cause: [cvc-datatype-valid.1.2.2] Characters were not valid value for unsignedByte type.
Action: Correct the value to satisfy unsignedByte type
Cause: [cvc-datatype-valid.1.2.3] Characters were invalid with respect to any member type of union.
Action: Correct data value to satisfy at least one member type
Cause:[cvc-elt.2] Element declared abstract was used in instance document.
Action: Do not declare the element as abstract.
Cause: [cvc-elt.3.1] There was an attriube xsi:nil, which was not allowed because the element declaration was not nillable.
Action: Remove xsi:nil attribute from the the element
Cause: [cvc-elt.3.2.1] Element was specified nil but had character or element children.
Action: Remove any element content or remove nil attribute.
Cause: [cvc-elt.3.2.2] Element had an fixed value while the content in instance was empty.
Action: Remove nil attribute from element.
Cause: [cvc-elt.4.1] The value of xsi:type attribute was not a QName.
Action: Change the value to a valid QName that references to a type.
Cause: [cvc-elt.4.2] The referenced type specified by xsi:type was absent.
Action: Correct the value of xsi:type so it points to a valide type definition.
Cause: [cvc-elt.4.3] The type referenced by xsi:type was not derived from original type.
Action: Modify the reference type defintion so it satisfy the constraint, or use another type that is derived from original type.
Cause: [cvc-enumeration-valid] The value was not one in the enumeration constraint.
Action: Use valid value specified in enumeration.
Cause: [cvc-facet-valid] The given data value violates the constraining facet.
Action: Correct the data value.
Cause: [cvc-fractionDigits-valid] The given number violated the fractionDigits constraining facet.
Action: Use fewer fraction digits.
Cause: [cvc-id.1] There is no ID binding in the ID/IDREF table for validation root
Action: Define the ID for the ID reference
Cause: [cvc-id.2] Same ID was defined more than once.
Action: Eliminate duplicate ID attributes.
Cause: [cvc-identity-constraint] The document contained duplicate key sequence thatviolated uniqueness constraint.
Action: Correct the document to make key sequence unique, or modify xpath to avoid it.
Cause: [cvc-identity-constraint.4.2.1] There were empty key sequences in key constraint.
Action: Make sure every element in target node set has a non-empty key sequence.
Cause: [cvc-identity-constraint.4.2.3] The element selected as a member in a key sequence was nillable, which is not allowed.
Action: Modify the schema to make corrsponding element declaration not nillable.
Cause: [cvc-identity-constraint.4.3] A keyref referenced to empty key sequence.
Action: Make sure every key sequence for keyref is has a corresponding key sequence for referenced key.
Cause: [cvc-length-valid] The length of the value was not the same as specified in length facet.
Action: Use data value with correct length.
Cause: [cvc-maxExclusive-valid] The data value was out of boundary specified in maxExclusive facet.
Action: Correct the data value.
Cause: [cvc-maxInclusive-valid] The data value was out of boundary specified in maxInclusive facet.
Action: Correct the data value.
Cause: [cvc-maxLength-valid] The length of the data value was greater than maxLength.
Action: Make the data value's length smaller than maxLength.
Cause: [cvc-minExclusive-valid] The data value was out of lower boundary of value range.
Action: Use data valude that is greater to minExclusive.
Cause: [cvc-minInclusive-valid] The data value was too small.
Action: Use data value not smaller than the value of minInclusive.
Cause: [cvc-minLength-valid] The length of value was smaller than that specified in minLength.
Action: Use data value with length greater than or equals to minLength.
Cause: [cvc-particle.1.1] The wildcard particle's minOccurs had not been met.
Action: Have more elements in the content that match the wildcard.
Cause: [cvc-particle.1.2] The element particle's minOccurs had not been met.
Action: Have more elements that match the element declaration or members in its substitution group.
Cause: [cvc-particle.1.3] The model group particle's minOccurs had not been met.
Action: Have more elements in the content that match the model group.
Cause: [cvc-pattern-valid] The literal did not match the pattern constraining facet.
Action: Correct the lexical data to match pattern facet.
Cause: [cvc-resolve-instance.1] Could not resolve the type reference to a type definition
Action: Add the type definition to schema
Cause: [cvc-resolve-instance.2] Could not resolve attributre reference to an attribute declaraton.
Action: Add the attribute declaration to schema.
Cause: [cvc-resolve-instance.3] Could not resolve element reference to an element declaraton
Action: Add the element declaration to schema
Cause: [cvc-resolve-instance.4] Could not resolve the attribute group reference to an attribute group definition.
Action: Define the attribute group definition in schema
Cause: [cvc-resolve-instance.5] Could not resolve the model group reference to a model group definition
Action: Define the model group in schema
These error messages are in the range XML-24100 through XML-24199.
Cause: Element in XML Schema document did not have Schema namespace.
Action: Specify XML Schema namespace http://www.w3.org/2001/XMLSchema
Cause: [schema_reference.2] Processor could not find schema from given schema location
Action: Fix the schema location
Cause: [schema_reference.3] Processor was unable to retrieve schema based on given namespace.
Action: Fix the schema namespace
Cause: [src-annotation] More than one annotation elements appeared in component.
Action: Remove extra annotation.
Cause: [src-annotation] Annotation was not the first element in component.
Action: Move annotation to the begining of component content.
Cause: The attribute wildcard appeared before attribute declarations.
Action: Move attribute wildcard to the end of declaration.
Cause: [src-attribute.1] More than one anyAttributes were declared.
Action: Remove extra attribute wildcards.
Cause: [src-attribute.1] Both default and fixed attriubtes were present in attriubte declaration.
Action: Remove either default or fixed attribute.
Cause: [src-attribute.2] Both default and use were present, and value for use is not optional.
Action: Remove either default or use value.
Cause: [src-attribute.3.1] Neither name nor ref attribute was present in declaration.
Action: Add name or ref to the declaration.
Cause: [src-attribute.3.1] Name and ref attribute were both present in attribute declaration.
Action: Add name or ref to the declaration.
Cause: [src-attribute.3.2] The attribute was a reference, and form, type or simpleType child were specified.
Action: Either change ref to name, or remove form, type and/or childrens.
Cause: [src-attribute.4] Both type attribute and simpleType child were present.
Action: Remove either type reference or type definition.
Cause: [src-attribute_group.2] Attriubes wildcards defined were not expressible with a wildcard.
Action: Remove inexpressible attribute wildcards.
Cause: [src-attribute_group.3] Attriubte group were circularly referenced outside redefine
Action: Remove circular reference
Cause: group were circularly referenced outside redefine.
Action: Remove circular reference
Cause: [src-ct.1] Derived a complexType with complex content from simple type
Action: Change base type to complex type
Cause: [src-ct.2] A complexType with simpleContent was derived from a complexType with complex content
Action: Change base type to simple type (if derivation is extension) or simpleContent complex type.
Cause: [src-element.2.2] Element reference also had complexType, simpleType, key, keyrefunique children or nillable, form, default, block, or type attribute.
Action: Remove conflict attributes or children.
Cause: [src-element.3] Element declaration had both complexType, simpleType children.
Action: Remove either simpleType or complexType child.
Cause: [src-import.1.1] The namespce of import was the same as the target namespace of importing schema
Action: Change import to inclusion.
Cause: [src-import.1.2] Imported namespace was specified but absent imported schema.
Action: Remove namespace attribute in element import, or add target namespac to the imported schema.
Cause: [src-import.3.1] Specified namespace was different from actual targetNamespace impported.
Action: Correct the namespace attribute in import element.
Cause: [src-import.3.2] Specified a no-namespace schema, but actual schema had targetNamespace.
Action: Remove the imported schema's targetNamespace attribute
Cause: [src-include.1] Processor was unable to include a schema from given location.
Action: Check correctness of URL and URL resolver
Cause: [src-include.2.1] Tried to include a achema with different targetNamespace.
Action: Use import instead of include.
Cause: [src-include.2.2] A schema without targetNamespace tried to include a schema with targetNamespace.
Action: Use import instead of include
Cause: [src-list-itemType-or-simpleType] Both itemType attribute and simpleType child were present in list simple type declaration.
Action: Remove either itemType attribute or simpleType child.
Cause: [src-qname] Prefix of a qname was present, but did not map to any in-scope namespace.
Action: Declare a namespace corresponding to the prefix.
Cause: Redefined schema's targetNamespace was not the same as the targetNamespace of redefining schema.
Action: Correct the targetNamespace in redefined schema.
Comments: src-redefine.3.1
Cause: [src-redefine.3.2] A no-namespace schema tried to redefine a schema with namespace
Action: Remove the targetNamespace attribute from redefined schema.
Cause: [src-redefine.5] A simpleType or complexType was present in redefine, but the derivation was not restriction.
Action: Change the type redefinition, make it a restriction.
Cause: [src-redefine.5] A simpleType or complexType was present in redefine, but its base type was not itself.
Action: Change the base type to redefine itself.
Cause: [src-redefine.6.1.1] A group was present in redefine and it had more than onereferences to itself in its content.
Action: Remove extra self references in the group redefinition.
Cause: [src-redefine.6.1.2] A minOccurs or maxOccurs with value other than 1 was specified in a group self reference in redefine.
Action: Remove the minOccurs or maxOccurs attribute.
Cause: [src-redefine.6.2.2] A group presented in redefine, without self reference but was nota valid restriction of its original group.
Action: Modify the content of the group, make it a valid restriction of its original.
Cause: [src-redefine.7.1] An attributeGroup was present in redefine and it had more than oneself references in its content.
Action: Remove extra self references.
Cause: [src-redefine.7.2.2] An attributeGroup presented in redefine, without self reference but was not a valid restriction of its original.
Action: Modify the content of the attribute group, make it valid restriction of its original.
Cause:[src-restriction-base-or-simpleType]
Cause: [src-simple-type.2] Both base and simpleType were absent in simple type restriction
Action: Add either base attribute or simpleType child.
Cause: [src-simple-type.3] Missing itemType attribute or simpleType child in list definition.
Action: Add either itemType or simpleType child
Cause: [src-simple-type.3] Both itemType attribute and simpleType child were present inlist definition
Action: Remove either itemType or simpleType child.
Cause: [src-simple-type.4] Some member types in union type made references to the union type
Action: Remove the circular references
Cause: [src-single-facet-value] Same facet other than enumeration and pattern had been specified more than once, which is not allowed.
Action: Remove extra facets.
These error messages are in the range XML-24200 through XML-24399.
Cause: [ag-props-correct.1] There were more than one attribute declarations with same namespace and name in attribute group definition.
Action: Remove duplicate attribute declarations.
Cause: [ag-props-correct.2] There were more than one attribute declarations with type ID.
Action: Change to other types for such attriubte declarations
Cause: [a-props-correct.2] The fixed value or default value did not satisfy the attribute's type
Action: Use type valid default for fixed value.
Cause: [a-props-correct.3] Attribute with ID type had either fixed or default value constraint.
Action: Remove value constraint.
Cause: [au-props-correct.2] Attriubte reference specified a fixed value which is not the same as that in referenced declaration.
Action: Correct the fixed value to the same as specified in attribute declaration
Cause: [au-props-correct.2] Attriubte reference specified a default value, while the referenced declaration had a fixed value.
Action: Remove default value form attribute reference.
Cause: [c-fields-xpaths.1] The value of xpath was not valid xpath expression as specified in XPath 1.0.
Action: Use correct xpath
Cause: [c-fields-xpaths.2] The value of xpath did not satisfied field's restricted xpath syntax.
Action: Correct the xpath expression
Cause: [cos-all-limited] Some elements in a All group had maxOccurs greater than one.
Cause: All group was contained in another model group
Action: Make all group at the top of a content type
Comments: cos-all-limited
Cause: [cos-applicable-facets] All group was contained in another model group
Action: Make all group at the top of a content type
Cause: [cos-applicable-facets] A facet not applicable to the simple type was used.
Action: Remove the facet.
Cause: [cos-aw-intersect] Two wilcards in an attribtue group had different negative namespaces
Action: Use only one wildcard with negative namespace
Cause: [cos-ct-derived-ok.1] Base type's final prevented the derivation.
Action: Remove the derivation method from the value of final in base type
Cause: [cos-ct-derived-ok.2] There was no derivation chain from base type to derived type.
Action: Fix the derivation chaining.
Cause: [cos-ct-extends.1.4.2.1] The content type of an extension of a complex type was empty
Action: Add particle to the content type of extension.
Cause: [cos-ct-extends.1.4.2.2.2] Base type's content type was not empty and was not the same as the content type specified.
Action: Match the specified content type with that in base type.
Cause: More than one elements in the content had same name and namespace, butdid not refer to same type.
Action: Make type references the same for all elements equal in name and namespace
Comments: cos-element-consistent
Cause:[cos-equiv-derived-ok-rec]
Cause: [cos-list-of-atomic] The itemType of a list type was itself a list.
Action: Use atomic or union type as the itemType of list.
Cause: [cos-no-circular-union] Union's name and namespace matched one of its memberType.
Action: Remove any circular references
Cause: [cos-nanambig] particles in a content type violated UPA (Unique Particle Attrition)constraint.
Action: Make content type particle unambiguous.
Cause: [cos-st-derived-ok] Derivation was restriction but restriction was in base type's final.
Action: Remove restriction from base type's final.
Cause: [cos-st-derived-ok] The derivation violated the "type derivaton OK (simple)" constraint.
Action: Make the derivation satisfy the constraint.
Cause: [cos-st-restricts.1.1] base type is list,
Cause: [cos-st-restricts.1.1] Tried to directly restrict anySimipleType.
Cause: [cos-valide-default] Element had default constraint but its mixed content type was not emtiable.
Action: Remove default value constraint.
Cause: [cos-valide-default] Element had default value constraint but its content type was element only or empty.
Action: Remove default value constraint.
Cause: [cos-valide-default] Element's default value constraint was invalid to its type.
Action: Correct the default value or remove it.
Cause: [c-props-correct] Number of fields were different between keyref and referenced key.
Action: Ensure that keyref and referenced key have same number of fields.
Cause: [ct-props-correct] Complex type was derived from simple type, but derivation was not extension.
Action: Change restriction to extension.
Cause: [ct-props-correct] Type was in its own derivation chain.
Action: Remove recursive derivation.
Cause: [derivation-ok-restriction.1] Complex type was restricted from a simple type.
Action: Change the restriction from a complex type.
Cause: [derivation-ok-restriction.2] The attribute in restriction was not allowed for base type.
Action: Correct the restriction of attribute use.
Cause: [derivation-ok-restriction.3] Restriction's attribute uses was not a subset of basetype's attribute uses.
Action: Correct the restriction of attribute uses.
Cause: [derivation-ok-restriction.4] Restriction had an attribute wildard that did not corrspond to any attribute wildcard in base type.
Action: Correct the derivation.
Cause: [derivation-ok-restriction.5.1] Content type was simple, but the base type has complex content that is not mixed or not emptiable.
Action: Change the content type from simple to element only.
Cause: [derivation-ok-restriction.5.2] Content type was empty, but the base type had simple content or not emptiable complex content.
Action: Change the content type from simple to element only.
Cause: [enumeration-required-notation] NOTATION type was used without enumeration facet.
Action: Specify enumeration facet for NOTATION.
Cause: [enumeration-valid-restriction] Some value in enumeration was not valid in respect to the type.
Action: Correct invalid values.
Cause: [e-props-correct.2] Default value was invalid in respect to the type of element.
Action: Correct the default value.
Cause: [e-props-correc.3] The type of the element was not a validly derivation from the type ofelement's substitutionGroup.
Action: Correct the type or remove substitutionGroup.
Cause: [e-props-correct.4] Type was ID or its derivation whild there was a value constraint.
Action: Remove value constraint.
Cause: [fractionDigits-totalDigits] The value for fractionDigits was greater than totalDigits.
Action: Make fractionDigits smaller or equal to totalDigits.
Cause: [length-minLength-maxLength] Both length and either minLength or maxLength were specified.
Action: Remove length facet.
Cause: [length-valid-restriction] Specified a length that was not the same as the length in base type.
Action: Remove length facet.
Cause: [maxExclusive-valid-restriction] Restricted maxExclusive was greater thant its original in base type.
Cause: [maxInclusive-maxExclusive] Specified a minInclusive that was greater or equal to maxExclusive.
Action: Make minInclusive smaller than maxExclusive.
Cause: [maxLength-valid-restriction] Specified a maxLength greater than orginal in base type.
Action: Sepcify a smaller maxLength to make it valid restriction.
Cause: [mg-props-correct] Circular model group references.
Action: Remove circular references in model group definition.
Cause: [minExclusive-less-than-equals-to-maxExclusive] minExclusive was bigger than maxExclusive.
Action: Use smaller value for minExclusive.
Cause: [minExclusive-less-than-maxInclusive] inExclusive specified was greater than or equal to maxInclusive.
Action: Specify smaller minExclusive.
Cause: [minExclusive-valid-restriction] Restriction's minExclusive was less than base type's minExclusive
Action: Specify greater value for minExclusive.
Cause: [minExclusive-valid-restriction] Restriction's minExclusive was less than base type's minInclusive
Action: Specify greater value for minExclusive
Cause: [minExclusive-valid-restriction] Restriction's minExlcusive was greater than base type's maxInclusive
Action: Specify smaller value for minExclusive
Cause: [minExclusive-valid-restriction] Restriction's minExclusive was greater than or equals to base type's maxExclusive
Action: Specify smaller value for minExclusive.
Cause: [minInclusive-less-than-equal-to-maxInclusive] Specified a minInclusive that was greater than maxInclusive
Action: Specify smaller value for minInclusive.
Cause: [minInclusive-minExclusive]] Restriction specified both minInclusive and minExclusive.
Action: Remove either minInclusive or minExclusive.
Cause: [minInclusive-valid-restriction] Restriction's minInclusive was less than or equal to minInclusive in base type.
Action: Use minInclusive larger than that of base type.
Cause: [minInclusive-valid-restriction] Restriction's minInclusive was less than minExclusivein base type.
Action: Use minInclusive larger than or equal to the minExclusive of base type.
Cause: [minInclusive-valid-restriction] Restriction's minInclusive was greater than maxInclusive in base type.
Action: Use minInclusive smaller than or equal to the maxInclusive of base type.
Cause: Restriction's minInclusive was greater than or equal to maxEnclusive in base type.
Action: Use minInclusive smaller than the maxEnclusive of base type.
Comments: minInclusive-valid-restriction
Cause: [minLength-less-than-equal-to-maxLength] minLength in restriction is greater than base type's maxLength.
Action: Make minLength within the length range of base type.
Cause: [minLength-valid-restriction] Value of minLength is smaller than that of base type in restriction.
Action: Use bigger value for minLength.
Cause: [no-xmlns] Declared an attribute with name xmlns.
Action: Remove such declaraton.
Cause: [no-xsi] The schema's target namespace matched http://www.w3.org/2001/XMLSchema-instance
Action: Use other target namespace.
Cause: [n-props-correct] The minOccurs of particle was greater than the maxOccurs.
Action: Use smaller value for minOccurs.
Cause: [ p-props-correct] The maxOccurs of particle was less than 1.
Action: Use greater value for maxOccurs.
Cause: [n-props-correct] The Notation declaration had incorrect properties.
Action: Fix Noation declaration.
Cause: [range-ok] Range of restriction was not within the range of parent particle.
Cause: Restriction did not satisfy constraint: Particle Derivation OK (Sequence:Choice -- MapAndSum)
Comments: rcase-MapAndSum
Cause: [rcase-NameAndTypeOK] Restriction did not satisfy constraint: Particle Restriction OK
Cause: [rcase-NSCompat] Restriction did not satisfy constraint: Particle Restriction OK
Cause: [rcase-NSRecurseCheckCardinality] Restriction did not satisfy constraint: Particle Restriction OK
Cause: [rcase-NSSubset] Restriction did not satisfy constraint: Particle Restriction OK(Any:Any -- NSSubset)
Cause: [ rcase-Recurse] Restriction did not satisfy constraint: Particle Restriction OK(All:All, Seqiemce"Sequence:-- Recurse)
Cause: [rcase-RecurseLax] The wildcard was not validly restricted from another wildcard.
Cause: Restriction violated constraint: Particle Derivation OK (Sequence:All--RecurseUnordered)
Action: Fix the restriction.
Comments: rcase-RecurseUnordered
Cause: [sch-props-correct] There were two schema components with same name and namespace.
Action: Remove duplicate definitions.
Cause: [w-props-correct] The namespace constraint was not a restriction of its super
Action: Correct namespace constraint.
Cause: [totalDigits-valid-restriction] Restriction specified a totalDigits with value greater than that in base type.
Action: Use smaller value for totalDigits.
These error messages are in the range XML-30000 through XML-30999.
Cause: Error occurred while processes execution is ignored
Action: None required
Cause: Component being wrapped by pipeline process is causing error
Action: Might need to fix input xml content
Cause: URL provided as base url is invalid
Action: Fix base url provided
Cause: Param with name target is missing or invalid
Action: Please add param target pointing to the target output label
Cause: Element procdef is missing
Action: Please add process definition to pipedoc
Cause: The dependent process does not provide a valid ContentHandler
Action: Please implement the getContentHandler API in your Process.
Cause: Component output and input don't match in terms of document/docfrag
Action: Fix the pipedoc to use components which are compatible
Cause: Process whose output label matched target label is not available
Action: Create a process in the pipedoc, where the output label matches the label of the target param
Cause: A dependent process output label has not been named correctly, or a dependent process is missing
Action: Please make sure every dependent input has a corresponding output
These error messages are in the range XML-32000 through XML32999.
Cause: There was more than one instance of <schemaBindings> declaration in the annotation element of the <schema> element.
Action: Update the annotation to remove duplicate <schemaBinding> declaration.
Cause: There was more than one instance of <class> declaration in the annotation element of the node.
Action: Update the annotation to remove duplicate <class> declaration.
Cause: A failure occurred because the name attribute in the <class> declaration contained a package prefix.
Action: Update the className in <class> declaration.
Comments: The package prefix is inherited from the current value of package.
Cause: A failure occurred because the property customization was not specified correctly.
Action: Update the <property> customization.
Cause: A failure occurred because the property customization was notspecified correctly.
Action: Update the <javaType> customization.
Cause: A failure occurred because the baseType customization was not specified correctly.
Action: Update the <baseType> customization.
Cause: A failure occurred because multiple "baseType" customizations were declared.
Action: Remove one of the <baseType> customization declaration.
Cause: A failure occurred because multiple "javaType" customizations were declared.
Action: Remove one of the <javaType> customization declaration.
Cause: A failure occurred because an invalid value was specified onthe globalBindings customization declaration.
Action: Check and correct the globalBindings customization value.
Cause: A failure occurred because an invalid value was specified on the schemaBindings cusotmization.
Action: Check and correct the schemaBindings customization value.
These error messages may occur during the execution of TXU interfaces.
These error messages are in the range TXU-0100 through TXU-0199.
Cause: There is not a placeholder for the parameter in the query
Action: Supply a parameter whose id can be found as an associated placeholder in the associated query
Cause: Attributes 'col' and 'constant' cannot coexist
Action: Remove either 'col' or 'constant' attribute
Cause: The document lacks an expected node
Action: Supply the missing node
Cause: The element lacks a required attribute of 'col' or 'constant'
Action: Supply either 'col' or 'constant' attribute
Cause: An error occurred during the SQL execution
Action: Resolve the error in the SQL statement
Cause: The SQL query returned no data
Action: Supply data or modify your query
Cause: An attempt to process an unsupported datatype was made
Action: Change the datatype to a supported one
Cause: The size-unit attribute is specified but maxsize is not.
Action: Supply the maxsize attribute, too
Cause: The length of the text data is too long
Action: Shorten the data so it fits in the limit, or enlarge the maxsize attribute and ensure the database column is large enough
Cause: A column in the data section is not declared in the columns section
Action: Modify the column name to a declared one
Cause: A column is declared but the data is missing.
Action: Supply the col element whose name attribute matches the column name
Cause: The query parameter refers to an undeclared column
Action: Specify a declared column
Cause: A column with a query cannot have the specified attribute
Action: Remove either the attribute or query
These error messages are in the range TXU-0300 through TXU-0399.
Cause: The document could not be located
Action: Modify the document location or supply the document at the location
Cause: An I/O error happened when reading the file
Action: Resolve the I/O problem
Cause: The archive file could not be located
Action: Ensure that the CLASSPATH includes TransX correctly and only once
Cause: The schema definition of DLF could not be located
Action: Obtain an unbroken copy of a TransX archive
Cause: The path for the archive could not be determined
Action: Ensure that the CLASSPATH includes TransX correctly and only once
Cause: The operation was attempted without a database connection
Action: Open a connection first
Cause: The table name is not provided
Action: Specify a table name
Cause: The data dictionary is corrupted
Action: Restore the data dictionary
These error messages are in the range TXU-0400 through TXU-0499.
Cause: An internal assertion was not successful
Action: Contact Oracle customer support
Cause: An internal assertion was not successful
Action: Contact Oracle customer support
Cause: An internal assertion was not successful
Action: Contact Oracle customer support
These error messages may occur during the execution of the XSU interfaces.
These error messages are in the range XSUK-0001 through XSUK-0099.
These error messages are in the range XSUE-0000 through XSUE-0099.
These error messages are in the range XSUE-0100 through XSUE-0199.
These error messages are in the range XSUE-0200 through XSUE-0299.
