Oracle Error Messages: January 2012

DRG-11870: Response From WAIS Server Too Large -- Extra Lines Ignored

DRG-11870: Response From WAIS Server Too Large -- Extra Lines Ignored

Cause: Response from WAIS caused buffer overflow USER_AGENT_ERROR

Action: The user agent takes proper actions

DRG-11869: Premature End Of File Detected

DRG-11869: Premature End Of File Detected

Cause: Detected end of file is unexpected USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11868: Too Many Redirections

DRG-11868: Too Many Redirections

Cause: The web server setup configured too many redirections USER_AGENT_ ERROR

Action: The user agent client should take proper actions

DRG-11867: Method Not Suited For Automatic Redirection

DRG-11867: Method Not Suited For Automatic Redirection

Cause: Telling client things are ok USER_AGENT_ERROR

Action: The user agent takes proper actions

DRG-11866: Please Try `ftp: or or Instead Of `file: or or

DRG-11866: Please Try `ftp: or or Instead Of `file: or or

Cause: wrong access scheme is used. USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11865: News Server Replies

DRG-11865: News Server Replies

Cause: News Server is responding USER_AGENT_ERROR

Action: The user agent takes proper actions

DRG-11864: Unknown Access Authentication Scheme

DRG-11864: Unknown Access Authentication Scheme

Cause: The server is using an unkown access authentication scheme USER_ AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11863: Bad, Incomplete, Or Unknown Response

DRG-11863: Bad, Incomplete, Or Unknown Response

Cause: The server is mumbering something not understandable USER_AGENT_ ERROR

Action: The user agent takes proper actions

DRG-11862: This Is Probaly A HTTP Server 0.9 Or Less

DRG-11862: This Is Probaly A HTTP Server 0.9 Or Less

Cause: A very old web server USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11861: CSO-server Replies

DRG-11861: CSO-server Replies

Cause: Telling client things are ok USER_AGENT_ERROR

Action: The user agent takes proper actions

DRG-11860: Connection Establishment Interrupted

DRG-11860: Connection Establishment Interrupted

Cause: Connection operation was interupped USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11859: Data Transfer Interrupted

DRG-11859: Data Transfer Interrupted

Cause: Processing of URL request was interrupted USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11858: Gopher Server Replies

DRG-11858: Gopher Server Replies

Cause: Gopher server responds to the agent request. USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11857: Server Timed Out

DRG-11857: Server Timed Out

Cause: Server operation timed out USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11856: FTP Server Doesn t Reply

DRG-11856: FTP Server Doesn t Reply

Cause: No response from FTP server during operation. USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11855: FTP Server Replies

DRG-11855: FTP Server Replies

Cause: FTP server responds to the agent request USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11854: No File Name Found Or File Not Accessible

DRG-11854: No File Name Found Or File Not Accessible

Cause: Unable to open the file specified USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11853: No Host Name Found

DRG-11853: No Host Name Found

Cause: The host name is not specicied in URI. USER_AGENT_ERROR

Action: The user agent client takes proper action.

DRG-11852: Can t Locate Remote Host

DRG-11852: Can t Locate Remote Host

Cause: connection to remote host failed USER_AGENT_ERROR

Action: The user agent client takes proper actions

DRG-11851: Cache Related Warning

DRG-11851: Cache Related Warning

Cause: Arbitrary information about cache to be presented to logger. HTTP_ CACHE_ERROR = 99

Action: The user agent client must not take any automated action.

DRG-11850: Transformation Applied

DRG-11850: Transformation Applied

Cause: Telling cache manager, content encoding or media type has been changed in cache. HTTP_CACHE_ERROR = 14

Action: The user agent takes proper actions

DRG-11849: Heuristic Expiration

DRG-11849: Heuristic Expiration

Cause: Cache freshness lifetime and response age both greater than 24 hours. HTTP_CACHE_ERROR = 13

Action: The user agent client takes proper actions

DRG-11848: Disconnected Operation

DRG-11848: Disconnected Operation

Cause: The cache is intentionally disconnected for a time period. HTTP_CACHE_ ERROR = 12

Action: The user agent client takes proper actions

DRG-11847: Revalidation Failed

DRG-11847: Revalidation Failed

Cause: User agent s attempt to revalidate a stale response failed. HTTP_CACHE_ ERROR = 11

Action: The user agent client takes proper actions

DRG-11846: Response Is Stale

DRG-11846: Response Is Stale

Cause: The the user agent knows the returned reponse is stale. HTTP_CACHE_ ERROR = 10

Action: The user agent client takes proper actions.

DRG-11845: No Partial Update

DRG-11845: No Partial Update

Cause: Reserved HTTP_ERROR = 506

Action: Reserved

DRG-11844: HTTP Version Not Supported

DRG-11844: HTTP Version Not Supported

Cause: The HTTP version in the request header is rejected by the server. HTTP_ ERROR = 505

Action: The user agent takes proper actions

DRG-11843: Gateway Timeout

DRG-11843: Gateway Timeout

Cause: Upstream server did not timely respond to the gateway server. HTTP_ ERROR = 504

Action: The user agent takes proper actions

DRG-11842: Service Unavailable

DRG-11842: Service Unavailable

Cause: Server overloaded or in maintenance mode. HTTP_ERROR = 503

Action: If retry-after header is in the response, retry the request.

DRG-11841: Bad Gateway

DRG-11841: Bad Gateway

Cause: In serving the request, the server received invalid response from gateway. HTTP_ERROR = 502

Action: The user agent takes proper actions

DRG-11840: Not Implemented

DRG-11840: Not Implemented

Cause: The server can t support a request feature which has yet to be implemented. HTTP_ERROR = 501

Action: The user agent takes proper actions

DRG-11839: Internal Server Error

DRG-11839: Internal Server Error

Cause: The server encountered internal error in fulfilling the request. HTTP_ ERROR = 500

Action: The user agent takes proper actions

DRG-11838: Proxy Reauthentication Required

DRG-11838: Proxy Reauthentication Required

Cause: Reserved HTTP_ERROR = 419

Action: Reserved

DRG-11837: Reauthorization Required

DRG-11837: Reauthorization Required

Cause: Reserved HTTP_ERROR = 418

Action: Reserverd

DRG-11836: Expectation Failed

DRG-11836: Expectation Failed

Cause: Server can not meet the user agent s expectation. HTTP_ERROR = 417

Action: The user agent takes pro

DRG-11835: Requested Range Not Satisfiable

DRG-11835: Requested Range Not Satisfiable

Cause: The byte range request can not be satisfied by the resource extent. HTTP_ ERROR = 416

Action: The user agent reads content-range header in the response.

DRG-11834: Unsupported Media Type

DRG-11834: Unsupported Media Type

Cause: The server is refusing the request because of media type HTTP_ERROR = 415

Action: The user agent takes proper actions

DRG-11833: Request-URI Too Big

DRG-11833: Request-URI Too Big

Cause: The server is refusing to accept the URI which is too big. HTTP_ERROR = 414

Action: The user agent takes proper actions

DRG-11832: Request Entity Too Large

DRG-11832: Request Entity Too Large

Cause: Request rejected because request entity is too large. HTTP_ERROR = 413

Action: If Retry-After header found, the user agent should retry.

DRG-11831: Precondition Failed

DRG-11831: Precondition Failed

Cause: Telling the user agent that the resource failed preconditions HTTP_ERROR 412

Action: The user agent takes proper actions

DRG-11830: Length Required

DRG-11830: Length Required

Cause: The server must receive a content-length header. HTTP_ERROR = 411

Action: The user agent takes proper actions

DRG-11829: Gone

DRG-11829: Gone

Cause: The resource is no longer available and no forwarding address. HTTP_ ERROR = 410

Action: The user agent takes proper actions

DRG-11828: Conflict

DRG-11828: Conflict

Cause: The request conflicts with the current state of the URI HTTP_ERROR = 409

Action: The user agent takes proper actions

LSX-00157: ~S is abstract and cannot be used in an instance document

LSX-00157: ~S is abstract and cannot be used in an instance document

Cause: The element declaration or the type definition was abstract.

Action: When an element is declared to be abstract, a member of that element s substitution group must appear in the instance document. When an element s corresponding type definition is declared as abstract, all instances of that element must use xsi:type to indicate a derived type that is not abstract.

LSX-00156: type is final and no derivations are allowed

LSX-00156: type is final and no derivations are allowed

Cause: Derivation from a type that is declared to be final occurred.

Action: Remove the final declaration from the base type.

LSX-00155: invalid use of attribute ref

LSX-00155: invalid use of attribute ref

Cause: If the item s parent is not lamp;lt;lamp;nbsp;schemalamp;gt; and the attribute ref is present, then the element simpleType and the attributes form and type must be absent.

Action: Remove the prohibited items.

LSX-00154: attribute use must have its value set to optional

LSX-00154: attribute use must have its value set to optional

Cause: If default and use are both present, use must have its value set to optional.

Action: Remove the default attribute or change the value of the use attribute.

LSX-00153: invalid combination of default and fixed attributes

LSX-00153: invalid combination of default and fixed attributes

Cause: It is an error for a declaration to contain both fixed and default attributes.

Action: Remove either the default or the fixed attributes.

LSX-00152: only minOccurs , maxOccurs , or id is allowed

LSX-00152: only minOccurs , maxOccurs , or id is allowed

Cause: If the item s parent is not lamp;lt;lamp;nbsp;schemalamp;gt; and ref is present, then complexType, simpleType , key , keyref , unique , nillable , default , fixed, form , block , and type must be absent.

Action: Remove the prohibited attribute.

LSX-00151: invalid combination of attributes ref and name

LSX-00151: invalid combination of attributes ref and name

Cause: If the item s parent is not lamp;lt;lamp;nbsp;schemalamp;gt;, then either the ref or the name attribute must be present, but not both. Top-level elements or attributes must have a name.

Action: Specify either the ref or name attribute.

LSX-00150: attributeGroup reference shouldn t have children

LSX-00150: attributeGroup reference shouldn t have children

Cause: A reference-to-attributeGroup element has children. It is suppose to be empty except for annotations.

Action: Remove the children.

LSX-00149: duplicated ID specified in ~S

LSX-00149: duplicated ID specified in ~S

Cause: An attempt was made to specify two distinct members of {attribute uses}with {attribute declaration}s, both of whose {type definition}s are from ID or are derived from ID.

Action: Declare only one member of the {attribute uses} whose {type definition} is from ID or will be derived from ID.

LSX-00148: annotation must come first in ~S

LSX-00148: annotation must come first in ~S

Cause: annotation element must be the first in the content.

Action: Make annotation the first element.

LSX-00147: ~1S cannot contain ~2S

LSX-00147: ~1S cannot contain ~2S

Cause: An invalid schema component exists in the current declaration.

Action: Remove the schema component.

LSX-00146: element or attribute is improperly defined

LSX-00146: element or attribute is improperly defined

Cause: An element or attribute definition must have either its type attribute set or must have one of its children be a simpleType or complexType element but both conditions cannot exist.

Action: Remove the erroneous condition.

LSX-00145: attribute ~1S invalid derived value ~2S

LSX-00145: attribute ~1S invalid derived value ~2S

Cause: A derivedBy attribute had an invalid value. Choices are extension or restriction.

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

LSX-00144: attribute ~1S invalid derivation-restriction value ~2S

LSX-00144: attribute ~1S invalid derivation-restriction value ~2S

Cause: An attribute which specifies a derivation-restriction setting (block, content, final) had an invalid value. Choices are #all , extension , or restriction .

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

LSX-00143: element ~S must have type or ref

LSX-00143: element ~S must have type or ref

Cause: A Schema element was declared but was neither type or reference.

Action: One of type or reference must be specified.

LSX-00142: invalid sub-element ~1S for element ~2S

LSX-00142: invalid sub-element ~1S for element ~2S

Cause: There was an invalid sub-element in the content of either the attribute or the element declaration. This was because the sub-element was either at the wrong position or out of context.

Action: Remove the sub-element or move it to the correct position.

LSX-00141: ID type may only be used in attributes

LSX-00141: ID type may only be used in attributes

Cause: For backward compatibility with DTD, ID type may only be used in attributes.

Action: Remove the ID type.

LSX-00136: maxOccurs is less than minOccurs

LSX-00136: maxOccurs is less than minOccurs

Cause: The value of the maxOccurs specification is less than the value of the minOccurs specification.

Action: Correct minOccurs or maxOccurs .

LSX-00135: invalid min or max Occurs for lamp;lt;lamp;nbsp;alllamp;gt; element, must be 0 or 1

LSX-00135: invalid min or max Occurs for lamp;lt;lamp;nbsp;alllamp;gt; element, must be 0 or 1

Cause: minOccurs has a value other than 0 or 1 or maxOccurs has a value other than 1.

Action: Specify 0 or 1 for minOccurs or maxOccurs .

LSX-00134: attribute ~1S has invalid qualification ~2S

LSX-00134: attribute ~1S has invalid qualification ~2S

Cause: An attribute that specifies qualification (form, attributeFormDefault, elementFormDefault) was invalid; it must be one of qualified or unqualified .

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

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.

LPX-00054: LPU initialization failed, error ~u

LPX-00054: LPU initialization failed, error ~u

Cause: The LPU (URL Parser or Loader) package initialization failed.

Action: Internal error, contact Oracle Support Services and report the error.

LPX-00053: LML initialization failed

LPX-00053: LML initialization failed

Cause: The LML (Low-Level Memory manager) package initialization failed.

Action: Internal error, contact Oracle Support Services and report the error.

LPX-00052: LEH initialization failed

LPX-00052: LEH initialization failed

Cause: The LEH (Library Exception Handling) package initialization failed.

Action: Internal error, contact Oracle Support Services and report the error.

LPX-00051: NLS initialization failed

LPX-00051: NLS initialization failed

Cause: The NLS (National Language Support) package initialization failed.

Action: Internal error, contact Oracle Support Services and report the error.

LPX-00050: initialization error: NLS mismatch

LPX-00050: initialization error: NLS mismatch

Cause: A language ID was specified without the matching global area.

Action: Internal error, contact Oracle Support Services and report the error.

LPX-00019: property ~s unknown

LPX-00019: property ~s unknown

Cause: An unexpected error has occured in a subsystem used by XML. Subcode is the error code returned by that failing subsystem.

Action: Contact Oracle Support Services and report the error and subcode.

LPX-00018: internal error nested open strings

LPX-00018: internal error nested open strings

Cause: An internal error has occurred.

Action: Contact Oracle Support Services and report the error.

LPX-00017: ~1sNodeName: lamp;lt;lamp;nbsp;~2Slamp;gt;

LPX-00017: ~1sNodeName: lamp;lt;lamp;nbsp;~2Slamp;gt;

Cause: More error message boilerplate.

Action: No action required. This is not an error message.

LPX-00014: context is not clean

LPX-00014: context is not clean

Cause: An operation was performed on a context that has already been used (so is not clean ).

Action: Some functions must be performed on a newly initialized context before being used for parsing. For example, setting a shared DTD. Change the code and do the call before parsing.

LPX-00013: wrong node type

LPX-00013: wrong node type

Cause: The wrong node type was given as argument to a DOM call.

Action: Review the failing function call, consult the documentation, and make sure the node types passed as correct.

LPX-00012: Unicode data alignment error

LPX-00012: Unicode data alignment error

Cause: An input Unicode (UCS2) datum was not aligned properly.

Action: UCS2 data consists of an array of shorts (ub2) which must be aligned on an even-byte boundary.

LPX-00008: invalid memory callback

LPX-00008: invalid memory callback

Cause: The memory callback structure passed to xmlinit was missing the allocate or free functions (or both).

Action: Provide both functions in the callback structure.

LPX-00007: unexpected end-of-file encountered

LPX-00007: unexpected end-of-file encountered

Cause: The documented ended unexpectedly, perhaps due to truncation.

Action: Verify that the document is complete.

LPX-00006: invalid child type for parent node

LPX-00006: invalid child type for parent node

Cause: An attempt was made to add an invalid node-type to a parent node.

Action: Correct the code.

LPX-00005: ~1s buffer overflow, maximum size is ~2u bytes

LPX-00005: ~1s buffer overflow, maximum size is ~2u bytes

Cause: A name, quoted string, URL, or other document component was too long.

Action: Restrict the component to the maximum size shown.

LPX-00004: internal error ~s

LPX-00004: internal error ~s

Cause: An internal error has occurred.

Action: Contact Oracle Support Services and report the error.

LPX-00003: duplicate entry in hash table

LPX-00003: duplicate entry in hash table

Cause: An internal error has occurred (a key was requested to be placed in a hash table but was already there).

Action: Contact Oracle Support Services and report the error.

LPX-00002: out of memory

LPX-00002: out of memory

Cause: The operating system has run out of memory.

Action: Make more memory available to the program.

LPX-00001: NULL pointer

LPX-00001: NULL pointer

Cause: A NULL pointer was detected as an internal error condition.

Action: This is a programming error by the caller of the XML parser. Please contact someone who can fix the problem.

DRG-11827: Request Timeout

DRG-11827: Request Timeout

Cause: The server is tired of waiting for the requst HTTP_ERROR = 408

Action: The user agent repeat the request

DRG-11826: Proxy Authentication Required

DRG-11826: Proxy Authentication Required

Cause: The client must authenticate itself with the proxy. HTTP_ERROR = 407

Action: The user agent takes proper actions

DRG-11825: Not Acceptable

DRG-11825: Not Acceptable

Cause: Requested resource is not acceptable according to request header HTTP_ ERROR = 406

Action: The user agent should query the user for the next action.

DRG-11824: Method Not Allowed

DRG-11824: Method Not Allowed

Cause: The user agent specified method not allowed HTTP_ERROR = 405

Action: The user agent reads allow header to decide alternatives.

DRG-11823: Not Found

DRG-11823: Not Found

Cause: The server can not find the requested URI HTTP_ERROR = 404

Action: The user agent takes proper actions

DRG-11822: Forbidden

DRG-11822: Forbidden

Cause: The server refuses to fulfil the request from client HTTP_ERROR = 403

Action: The user agent takes proper actions

DRG-11821: Payment Required

DRG-11821: Payment Required

Cause: Reserved for future use. HTTP_ERROR = 402

Action: The user agent takes proper actions

DRG-11820: Unauthorized

DRG-11820: Unauthorized

Cause: The request requires further authentication. HTTP_ERROR = 401

Action: The user agent takes proper actions

DRG-11819: Bad Request

DRG-11819: Bad Request

Cause: The URL syntax is incorrect. Request rejected by server. HTTP_ERROR = 400

Action: The user agent takes proper actions

DRG-11818: Temporary Redirect

DRG-11818: Temporary Redirect

Cause: The resource is temporarily under a different URI. HTTP_ERROR = 307

Action: The takes proper actions

DRG-11817: Proxy Redirect

DRG-11817: Proxy Redirect

Cause: Proxy redirection. Not used HTTP_ERROR = 306

Action: Outdated due to HTTP evolution

DRG-11816: Use Proxy

DRG-11816: Use Proxy

Cause: The client should use specified proxy to repeat the request HTTP_ERROR 305

Action: The user agent takes proper actions

DRG-11815: Not Modified

DRG-11815: Not Modified

Cause: Response to conditional GET, indicating document not modified. HTTP_ ERROR = 304

Action: The user agent takes proper actions

DRG-11814: See Other

DRG-11814: See Other

Cause: The URI can be found using GET METHOD under a different URI HTTP_ ERROR = 303

Action: The user agent takes proper actions

DRG-11813: Moved Temporarily

DRG-11813: Moved Temporarily

Cause: The URI resides temporarily under a different URI. HTTP_ERROR = 302

Action: The user agent takes proper actions

DRG-11812: Moved Permanently

DRG-11812: Moved Permanently

Cause: The URI has been assigned a new permanent URI HTTP_ERROR = 301

Action: The user agent takes proper actions

DRG-11811: Multiple Choices

DRG-11811: Multiple Choices

Cause: Telling client multiple choices of resources is possible HTTP_ERROR = 300

Action: The user agent takes proper actions

DRG-11810: Partial Update OK

DRG-11810: Partial Update OK

Cause: Telling client document is partially updated HTTP_ERROR = 207

Action: The user agent takes proper actions

DRG-11809: Partial Content

DRG-11809: Partial Content

Cause: Telling client document content is a patial content HTTP_ERROR = 206

Action: The user agent takes proper actions

DRG-11808: Reset Content

DRG-11808: Reset Content

Cause: Telling client to reset the document view HTTP_ERROR = 205

Action: The user agent takes proper actions

DRG-11807: No Content

DRG-11807: No Content

Cause: request has been fulfilled but no new information found HTTP_ERROR = 204

Action: The user agent takes proper actions

DRG-11806: Non-authoritative Information

DRG-11806: Non-authoritative Information

Cause: The returned metainformation is not the definitive set HTTP_ERROR = 203

Action: The user agent knows the information is Non-authoritative

DRG-11805: Accepted

DRG-11805: Accepted

Cause: Telling client things are accepted but not commited HTTP_ERROR = 202

Action: The user agent takes proper actions

DRG-11804: Created

DRG-11804: Created

Cause: Telling client things are created HTTP_ERROR = 201

Action: The user agent takes proper actions

DRG-11803: OK

DRG-11803: OK

Cause: Telling client things are ok HTTP_ERROR = 200

Action: The user agent takes proper actions

DRG-11802: Switching Protocols

DRG-11802: Switching Protocols

Cause: Telling client a protocol switching just happened HTTP_ERROR = 101

Action: The user agent takes proper actions

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.