Oracle Error Messages

LPX-00212: comment must not contain --

LPX-00212: comment must not contain --

Cause: A syntax error was detected in the comment.

Action: Use -- only when specifying the end of the comment.

LPX-00211: attribute default must be REQUIRED, IMPLIED, or FIXED

LPX-00211: attribute default must be REQUIRED, IMPLIED, or FIXED

Cause: Attribute default was invalid.

Action: Default must be REQUIRED, IMPLIED, or FIXED.

LPX-00210: expected ~1c instead of ~2c

LPX-00210: expected ~1c instead of ~2c

Cause: A syntax error was detected.

Action: Use proper syntax.

LPX-00209: PI names starting with XML are reserved

LPX-00209: PI names starting with XML are reserved

Cause: Processing instruction starting with XML was found.

Action: Use another name for the processing instruction.

LPX-00208: unknown DTD keyword ~s

LPX-00208: unknown DTD keyword ~s

Cause: An unknown keyword was found in the DTD.

Action: Use a proper keyword.

LPX-00207: expected ( at the start of conditional section

LPX-00207: expected ( at the start of conditional section

Cause: Bad syntax detected when processing a conditional section.

Action: Fix the conditional section syntax.

LPX-00206: invalid CDATA section

LPX-00206: invalid CDATA section

Cause: Bad syntax detected when processing CDATA. Proper format is lamp;lt;lamp;nbsp; (CDATA( data ((lamp;gt; .

Action: Correct the CDATA syntax.

LPX-00205: expected lamp;lt;lamp;nbsp; -- at the start of comment

LPX-00205: expected lamp;lt;lamp;nbsp; -- at the start of comment

Cause: Bad syntax detected when processing a comment.

Action: Fix the comment syntax.

LPX-00204: syntax error

LPX-00204: syntax error

Cause: A syntax error was found.

Action: Check the XML document line and correct it.

LPX-00203: could not read from ~s (error ~u)

LPX-00203: could not read from ~s (error ~u)

Cause: Data could not be read from the named input.

Action: Take appropriate action to allow data to be read.

LPX-00202: could not open ~s (error ~u)

LPX-00202: could not open ~s (error ~u)

Cause: The named input (file, URL, etc) does not exist.

Action: Make sure the named input is available and can be opened.

LPX-00201: unknown encoding ~s

LPX-00201: unknown encoding ~s

Cause: The specified encoding was not known. It should be an IANA or Oracle encoding name.

Action: Use an appropriate encoding.

LPX-00200: could not convert from encoding ~1s to ~2s

LPX-00200: could not convert from encoding ~1s to ~2s

Cause: The conversion cannot be made between the specified encodings.

Action: Choose a data encoding which can represent all expected input encoding (such as a Unicode-based encoding, UTF-8 or UTF-16).

LPX-00125: duplicate entity ~S (ignored)

LPX-00125: duplicate entity ~S (ignored)

Cause: Warning returned by XmlDomGetDecl when original document did not contain an XMLDecl

Action: This is a warning, not an error. The value XMLERR_NO_DECL is used by the programmer to detect whether a document had an XMLDecl or not. It does not indicate a problem.

LPX-00124: attribute value should be one or more tokens

LPX-00124: attribute value should be one or more tokens

Cause: An attribute with tokenized type (IDREFS, ENTITIES, NMTOKENS) did not contain any tokens.

Action: Value must contain one or more tokens, separated by spaces.

LPX-00123: duplicate ID ~S

LPX-00123: duplicate ID ~S

Cause: An ID was used twice, they must be unique.

Action: Correct the document.

LPX-00122: undefined ID ~S in IDREF

LPX-00122: undefined ID ~S in IDREF

Cause: Validity Constraint 3.3.1 failed: 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: Correct the document.