Oracle Error Messages

LSX-00133: attribute use has invalid value ~S

LSX-00133: attribute use has invalid value ~S

Cause: A use attribute had an invalid value. Choices for use are default , fixed, optional , prohibited , or required .

Action: Change the attribute to one of the above values.

LSX-00132: attribute ~1S has invalid occurrences value ~2S

LSX-00132: attribute ~1S has invalid occurrences value ~2S

Cause: A minOccurs or maxOccurs attribute had an invalid value (not a integer or less than zero).

Action: Use a legal occurs value.

LSX-00130: attribute processContents has invalid value ~S

LSX-00130: attribute processContents has invalid value ~S

Cause: Attribute processContents in the any element or anyAttribute declaration has an invalid value.

Action: Specify one of the following values: lax, skip, or strict.

LSX-00126: facet ~1S has invalid value ~u

LSX-00126: facet ~1S has invalid value ~u

Cause: Facet value contained illegal characters or its value was out of range.

Action: Remove illegal characters.

LSX-00125: restriction element is improperly defined

LSX-00125: restriction element is improperly defined

Cause: A restriction element either must have its base attribute set or have one of its children be a simpleType element, but both conditions cannot exist.

Action: Remove the erroneous condition.

LSX-00124: list element is improperly defined

LSX-00124: list element is improperly defined

Cause: A list element either must have its itemType attribute set or have one of its children be a simpleType element, but both conditions cannot exist.

Action: Remove the erroneous condition.

LSX-00123: base type is required

LSX-00123: base type is required

Cause: Missing base type declaration in the type definition.

Action: Define a base type.

LSX-00122: value is not valid restriction of parent s whiteSpace

LSX-00122: value is not valid restriction of parent s whiteSpace

Cause: There was an error in that whiteSpace was among the members of {facets} of {base type definition} and at least one of the following conditions was true: 1 {value} is replace or preserve and {value} of the parent whiteSpace is collapse 2 {value} is preserve and the {value} of the parent whiteSpace is replace

Action: Change the {value} of whiteSpace.

LPX-00106: attribute ~1S of element ~2S is undefined

LPX-00106: attribute ~1S of element ~2S is undefined

Cause: Validity Constraint 3.1 failed:

Action: Correct the document.

LPX-00105: element ~S is not empty as required by the DTD

LPX-00105: element ~S is not empty as required by the DTD

Cause: Validity Constraint 3 failed: The named element is declared as EMPTY in the DTD but contains sub-elements in the document.

Action: Correct the document.

LPX-00104: element ~S is not declared in the DTD

LPX-00104: element ~S is not declared in the DTD

Cause: Validity Constraint 3 failed: The named element has no matching elementdecl in the DTD

Action: Correct the document.

LPX-00103: document structure does not match DTD

LPX-00103: document structure does not match DTD

Cause: Validity Constraint 3 failed: An element is valid if there is a declaration matching elementdecl where the Name matches the element type, and one of the following holds: * The declaration matches EMPTY and the element has no content * 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 each pair of child elements. * The declaration matches Mixed and the content consists of character data and child elements whose types match names in the content model. * The declaration matches ANY, and the types of any child elements have been declared.

Action: Correct the document.

LPX-00102: standalone document declaration should be no

LPX-00102: standalone document declaration should be no

Cause: Validity Constraint 2.9 failed: Standalone document declaration must have the value no if any external markup declarations contain declarations of: * attributes with default values - or * entities - or * attributes with values subject to normalization - or * element types with element content

Action: Correct the document.

LPX-00101: parameter-entity markup cannot be split up

LPX-00101: parameter-entity markup cannot be split up

Cause: Validity Constraint 2.8 failed: Parameter-entity replacement text must be properly nested with markup declarations. *Example: lamp;lt;lamp;nbsp;?xml version= 1.0 ?lamp;gt; lamp;lt;lamp;nbsp; DOCTYPE greeting ( lamp;lt;lamp;nbsp; ENTITY % e lamp;lt;lamp;nbsp; ELEMENT lamp;gt; %e; greeting (#PCDATA)lamp;gt; (lamp;gt; lamp;lt;lamp;nbsp;greetinglamp;gt;Hello lamp;lt;lamp;nbsp; or greetinglamp;gt; *Explanation: The parameter entity e contains markup which may not be split up; the entire ELEMENT (or ATTLIST or ENTITY) definition must be present in one piece.

Action: Correct the document.

LPX-00100: root element ~1S does not match DTD root ~2s

LPX-00100: root element ~1S does not match DTD root ~2s

Cause: Validity Constraint 2.8 failed: The Name in the document type declaration must match the element type of the root element. *Example: lamp;lt;lamp;nbsp;?xml version= 1.0 ?lamp;gt; lamp;lt;lamp;nbsp; DOCTYPE greeting ( lamp;lt;lamp;nbsp; ELEMENT greeting (#PCDATA)lamp;gt; (lamp;gt; lamp;lt;lamp;nbsp;salutationlamp;gt;Hello lamp;lt;lamp;nbsp; or salutationlamp;gt; *Explanation: The document s root element, salutation, does not match the root element declared in the DTD (greeting).

Action: Correct the document.