Oracle Error Messages: 01/01/12

DRG-11801: Continue

DRG-11801: Continue

Cause: Enquire user to decide if continue is necessary HTTP_ERROR = 100

Action: Upon positive response, continue the original operation

DRG-11733: more than one translation for the term in the specified language

DRG-11733: more than one translation for the term in the specified language

Cause: the term has more than one translation in the specified language

Action: specified a translation

DRG-11732: phrase does not have any translations

DRG-11732: phrase does not have any translations

Cause: you tried to drop translations which does not exists

Action: none

DRG-11731: translation does not exist

DRG-11731: translation does not exist

Cause: you tried to drop a translation which does not exist

Action: none

DRG-11730: relation does not exist

DRG-11730: relation does not exist

Cause: you tried to drop a relation which does not exist

Action: none

DRG-11729: phrase does not have any narrower terms of this type

DRG-11729: phrase does not have any narrower terms of this type

Cause: you tried to drop a relation which does not exist

Action: none

DRG-11728: phrase does not have any broader terms of this type

DRG-11728: phrase does not have any broader terms of this type

Cause: you tried to drop a relation which does not exist

Action: none

DRG-11727: phrase does not have any related terms

DRG-11727: phrase does not have any related terms

Cause: you tried to drop a relation which does not exist

Action: none

DRG-11726: phrase is not a preferred term

DRG-11726: phrase is not a preferred term

Cause: you tried to remove the preferred term relation from a phrase which is not a preferred term.

Action: none

DRG-11725: phrase does not have any synonyms

DRG-11725: phrase does not have any synonyms

Cause: you tried to nominate a phrase with no synonyms to be the preferred term, or you tried to drop SYN from a phrase with no synonyms

Action: none

DRG-11724: phrase string already exists

DRG-11724: phrase string already exists

Cause: phrase with same name exists

Action: use another name

DRG-11723: phrase cannot be NULL

DRG-11723: phrase cannot be NULL

Cause: you tried to add a NULL phrase to the thesaurus

Action: specify a valid phrase

DRG-11722: invalid language specification

DRG-11722: invalid language specification

Cause: language specification cannot be more than 10 characters

Action: reduce language specification to less or equal to 10 char

DRG-11721: thesaurus string is empty

DRG-11721: thesaurus string is empty

Cause: no entries in thesaurus

Action: add some entries or drop the thesaurus

DRG-11720: too many synonyms per synonym ring

DRG-11720: too many synonyms per synonym ring

Cause: too many synonyms for a single preferred term

Action: introduce further distinctions to deepen the hierarchy

DRG-11719: Broader Term hierarchy too deep

DRG-11719: Broader Term hierarchy too deep

Cause: The broader term hierarchy in this thesaurus is too deep

Action: flatten the hierarchy for best results

DRG-11718: multiple Preferred Terms for term string

DRG-11718: multiple Preferred Terms for term string

Cause: There are multiple preferred terms for this term

Action: Correct thesaurus

DRG-11717: attempt to add Related Term string to non-Preferred Term string

DRG-11717: attempt to add Related Term string to non-Preferred Term string

Cause: only a PT can have RTs

Action: attach the RT

DRG-11716: attempt to add Narrower Term string for non-Preferred Term string

DRG-11716: attempt to add Narrower Term string for non-Preferred Term string

Cause: only a PT can have NTs

Action: attach the NT to the preferred term

DRG-11715: attempt to add a BT relation between 2 KB categories string and string

DRG-11715: attempt to add a BT relation between 2 KB categories string and string

Cause: BT relation cannot be between two existing knowledge base categories

Action: redesign the BT hierarchy

LSX-00121: value is not valid restriction of parent s length

LSX-00121: value is not valid restriction of parent s length

Cause: There was an error in that length was among the members of {facets} of {base type definition} and {value} was not equal to the {value} of the parent length.

Action: Make {value} the same as parent s.

LSX-00120: value is not valid restriction of parent s maxLength

LSX-00120: value is not valid restriction of parent s maxLength

Cause: There was an error in that maxLength was among the members of {facets} of {base type definition} and {value} was greater than the {value} of the parent maxLength.

Action: Increase the {value} of maxLength.

LSX-00119: value is not valid restriction of parent s minLength

LSX-00119: value is not valid restriction of parent s minLength

Cause: There was an error in that minLength was among the members of {facets} of {base type definition} and {value} was less than the {value} of the parent minLength.

Action: Increase the {value} of minLength.

LSX-00118: fixed facet value cannot be changed

LSX-00118: fixed facet value cannot be changed

Cause: The value of a fixed facet in the base type definition should remain the same.

Action: Remove the fixed facet specification in the parent s type for the erroneous facet component.

LSX-00117: minLength should not be greater than maxLength

LSX-00117: minLength should not be greater than maxLength

Cause: The value of minLength must be less than or equal to the value of maxLength.

Action: Correct either minLength or maxLength .

LSX-00116: mutually exclusive facets are not allowed

LSX-00116: mutually exclusive facets are not allowed

Cause: Mutual exclusiveness violations were found for facets. For example, both length and either minLength or maxLength are not allowed to be facets.

Action: Remove the facets that are at fault.

LSX-00114: facet ~S not in schema schema

LSX-00114: facet ~S not in schema schema

Cause: Facets are not defined in the XMLSchema namespace.

Action: Remove illegal facet declarations.

LSX-00113: facet ~1S has invalid value ~2S

LSX-00113: facet ~1S has invalid value ~2S

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

Action: Remove illegal characters.

LSX-00112: facet ~S duplicated

LSX-00112: facet ~S duplicated

Cause: A facet (other than enumeration ) was specified more than once.

Action: Only the enumeration facet may be used more than once for a type.

LSX-00111: type ~S contains invalid facets

LSX-00111: type ~S contains invalid facets

Cause: A specified facet was invalid for a type. Each datatype has a different set of facets which may apply.

Action: Use only applicable facets for the type.

LSX-00110: facet ~S should have single value attribute

LSX-00110: facet ~S should have single value attribute

Cause: A facet declaration did not have a value attribute.

Action: Each facet declaration must contain one and only one value attribute.

LSX-00106: duplicate attribute ~S

LSX-00106: duplicate attribute ~S

Cause: Attribute declaration is not unique within its scope.

Action: Rename the attribute.

LSX-00105: duplicate attribute group ~S

LSX-00105: duplicate attribute group ~S

Cause: Attribute group declaration is not unique within its scope.

Action: Rename the attribute group.

LSX-00104: duplicate type ~S

LSX-00104: duplicate type ~S

Cause: Type definition is not unique within its scope.

Action: Rename the type.

LSX-00103: duplicate group ~S

LSX-00103: duplicate group ~S

Cause: Group declaration is not unique within its scope.

Action: Rename the group.

LSX-00102: duplicate element ~S

LSX-00102: duplicate element ~S

Cause: Element declaration is not unique within its scope.

Action: Rename the element.

LSX-00027: property ~s unknown

LSX-00027: property ~s unknown

Cause: The named validation property was unknown.

Action: Refer to the documentation for the complete list of validation properties.

LSX-00026: unknown attribute ~S

LSX-00026: unknown attribute ~S

Cause: The name of attribute is unknown to the schema processor in the current scope.

Action: Correct the name of attribute if it s misspelled.

LSX-00025: unknown group ~S

LSX-00025: unknown group ~S

Cause: The name of group is unknown to the schema processor in the current scope.

Action: Correct the name of group if it s misspelled.

LSX-00024: unknown attribute group ~S

LSX-00024: unknown attribute group ~S

Cause: The name of attribute group is unknown to the schema processor in the current scope.

Action: Correct the name of attribute group if it s misspelled.

LSX-00023: unknown namespace URI ~S

LSX-00023: unknown namespace URI ~S

Cause: Namespace URI is unknown to the schema processor.

Action: Correct the namespace URI if it s misspelled.

LSX-00022: unknown namespace prefix ~S

LSX-00022: unknown namespace prefix ~S

Cause: Prefix in a QName is undefined in the current scope.

Action: Correct the prefix name if it s misspelled.

LSX-00021: undefined element ~S

LSX-00021: undefined element ~S

Cause: Element is undefined in the specified namespace.

Action: If the element name is misspelled, correct the spelling.

LSX-00020: unknown type ~S

LSX-00020: unknown type ~S

Cause: A specified type was unknown (not defined in any loaded Schemas).

Action: Make sure the type was defined and that the type usage referenced the correct Schema.

LSX-00018: invalid schema context

LSX-00018: invalid schema context

Cause: An invalid schema context was provided to the processor. Multiple schema documents were loaded and assembled into the schema context. At least one of them is not fully valid with respect to a schema corresponding to the Schema for Schemas.

Action: Check the errors reported when schema documents were loaded, mapped, or validated. Correct errors found in the identified schema documents and reload them into a new schema context. Then provide the new schema context to the processor.

LSX-00016: schema and instance document have incompatible character sets

LSX-00016: schema and instance document have incompatible character sets

Cause: Parsed schema components were in a simple-type character set while the parsed instance document data was not. A simple-type character set is single-byte, not shift sensitive, and has no linguistic specials in use.

Action: Reinitialize the schema global context with appropriate parser context settings, i.e. pass a parser context with its output encoding set to be a multibyte or Unicode character set.