Description:
LSX-00342 value of attribute “base” must be a complex type definition
Cause:
If the “complexContent” alternative is chosen, then the type definition resolved to by the actual value of the attribute “base” must be a complex type definition.
Description:
LSX-00333 literal “string” is not valid with respect to the pattern
Cause:
Literal is not valid with respect to the pattern.
Description:
LSX-00340 improper namespace value for the imported element
Cause:
If the namespace attribute is present, then its actual value must not match the actual value of the enclosing schema’s targetNamespace attribute. If the namespace attribute is not present, then the enclosing schema must have a targetNamespace attribute.
Description:
LSX-00341 ENTITY or ENTITIES type may only be used in attributes
Cause:
For compatibility, ENTITY or ENTITIES should be used only on attributes.
Description:
QSM-02116 multiple master sites
Cause:
The capability in question is not supported when the materialized view references multiple remote objects that reside at different remote instances.
Description:
QSM-02148 many to many subquery joins require 9.0 compatibility or higher
Cause:
You have specified a many to many join in your materialized view while running in less than 9.0 compatibility mode.
Description:
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:”
Action: Correct the document.
Description:
LPX-00210 expected ‘character‘ instead of ‘character‘
Cause:
A syntax error was detected.
Description:
LPX-00242 invalid use of ampersand (‘&’) character (use &)
Cause:
The ampersand character is used only to start entity or character references.
Description:
LPX-00275 can’t set output/data encoding AFTER parsing
Cause:
Output/data encoding must be set after initialization but BEFORE any parsing has taken place.