Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: Normal exit.
Action: No action required.
Cause: A NULL pointer was detected as an internal error condition.
Action: This is a programming error by the caller of the XML parser. Contact someone who can fix the problem.
Cause: The operating system has run out of memory.
Action: Make more memory available to the program.
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.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services and report the error.
Cause: A name, quoted string, URL, or other document component was too long.
Action: Restrict the component to the maximum size shown.
Cause: An attempt was made to add an invalid node-type to a parent node.
Action: Correct the code.
Cause: The documented ended unexpectedly, perhaps due to truncation.
Action: Verify that the document is complete.
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.
Cause: An input Unicode (UCS2) datum was not aligned properly.
Action: UCS2 data consists of an array of shorts which must be aligned on an even-byte boundary.
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 are correct.
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.
Cause: Validity Constraint 2.8 failed:
"The Name in the document type declaration must match the element type of the root element."
<?xml version="1.0"?> <!DOCTYPE greeting [ <!ELEMENT greeting (#PCDATA)> ]> <salutation>Hello!</salutation>
The document's root element, salutation, does not match the root element declared in the DTD (greeting).
Action: Correct the document.
Cause: Validity Constraint 2.8 failed:
"Parameter-entity replacement text must be properly nested with markup declarations."
<?xml version="1.0"?> <!DOCTYPE greeting [ <!ENTITY % e "<!ELEMENT "> %e; greeting (#PCDATA)> ]> <greeting>Hello!</greeting>
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.
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.
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:"
Action: Correct the document.
Cause: Validity Constraint 3 failed:
The named element has no matching elementdecl in the DTD.
Action: Correct the document.
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.
Cause: Validity Constraint 3.1 failed.
Action: Correct the document.
Cause: Validity Constraint 3.2 failed:
"No element type may be declared more than once."
Action: Correct the DTD.
Cause: Validity Constraint 3.2.1 failed:
"Parameter-entity replacement text must be properly nested with parenthesized groups. For interoperability, if a parameter-entity reference appears in a choice, seq, or Mixed construct, its replacement text should not be empty, and neither the first nor last non-blank character of the replacement text should be a connector (| or ,).
<?xml version="1.0"?> <!DOCTYPE foo [ <!ELEMENT greeting (#PCDATA)> <!ENTITY % e "(#PCDATA|"> <!ELEMENT foo %e; greeting)> ]> <greeting>Hello!</greeting>
The parenthetical content of the 'e' entity may not be split up into sections: both open and close parentheses must be in the same declaration.
Action: Correct the DTD.
Cause: Validity Constraint 3.2.2 failed:
"The same name must not appear more than once in a single mixed-content declaration."
<!ELEMENT p (#PCDATA|a|b|c|d|a)>
'a' occurs more than once in the mixed-content declaration.
Action: Correct the DTD.
Cause: Validity Constraint 3.3.1 failed:
Given thing is not a Name
Action: Correct the document.
Cause: Validity Constraint 3.3.1 failed:
Given thing is not a Nmtoken
Action: Correct the document.
Cause: Validity Constraint 3.3.1 failed:
"No element type may have more than one ID attribute specified."
Action: Correct the document.
Cause: Validity Constraint 3.3.1 failed:
"An ID attribute must have a declared default of #IMPLIED or #REQUIRED."
Action: Correct the document.
Cause: Validity Constraint 3.3.1 failed:
"Values of this type must match one of the Nmtoken tokens in the declaration."
Action: Correct the document.
Cause: Validity Constraint 3.3.2 failed:
"If the default declaration is the keyword #REQUIRED, then the attribute must be specified for all elements of the type in the attribute-list declaration."
Action: Correct the document.
Cause: Validity Constraint 3.3.2 failed:
"If an attribute has a default value declared with the #FIXED keyword, instances of that attribute must match the default value."
Action: Correct the document.
Cause: Validity Constraint 4.1 failed:
"In a document with an external subset or external parameter entities with "standalone='no'", the Name given in the entity reference must match that in an entity declaration."
Action: Correct the document.
Cause: The attribute value must be an unparsed entity.
Action: Correct the document.
Cause: Entity's NDATA (notation) is undefined.
Action: Correct the document.
Cause: Notation is not known.
Action: Correct the document.
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; that is, ID values must uniquely identify the elements which bear them."
Action: Correct the document.
Cause: An ID was used twice; they must be unique.
Action: Correct the document.
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.
Cause: A general or parameter entity was declared more than once.
Action: This is a warning, not an error. The first entity declaration is in force, subsequent are ignored. Remove duplicate entity declarations or ignore the warning.
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).
Cause: The specified encoding was not known. It should be an IANA or Oracle encoding name.
Action: Use an appropriate encoding.
Cause: The file does not exist.
Action: Create an appropriate file.
Cause: Data could not be read from the file.
Action: Take appropriate action to allow data to be read.
Cause: A syntax error was found.
Action: Check the XML document line and correct it.
Cause: Bad syntax detected when processing a comment.
Action: Fix the comment syntax.
Cause: Bad syntax detected when processing CDATA. Proper format is '<![CDATA[' data ']]>'.
Action: Correct the CDATA syntax.
Cause: Bad syntax detected when processing a conditional section.
Action: Fix the conditional section syntax.
Cause: An unknown keyword was found in the DTD.
Action: Use a proper keyword.
Cause: Processing instruction starting with XML was found.
Action: Use another name for the processing instruction.
Cause: A syntax error was detected.
Action: Use proper syntax.
Cause: Attribute default was invalid.
Action: Default must be REQUIRED, IMPLIED, or FIXED.
Cause: A syntax error was detected in the comment.
Action: Use '--' only when specifying the end of the comment.
Cause: A syntax error was detected in the comment.
Action: Be sure to end the comment with '-->'.
Cause: A syntax error was detected in the CDATA section.
Action: Be sure to end the CDATA section with ']]>'.
Cause: A syntax error was detected in the PI section.
Action: Be sure to end the PI with '?>'.
Cause: An invalid multibyte character was found.
Action: Use only characters allowed by the XML specification.
Cause: An invalid Unicode character was found.
Action: Use only characters allowed by the XML specification.
Cause: An invalid native (ASCII/EBCDIC) character was found.
Action: Use only characters allowed by the XML specification.
Cause: An invalid digit was found in a character reference.
Action: Character references are either &#DDD; where D's are decimal// digits, or &#xHHH; where H's are hexadecimal digits.
Cause: Found ']]>' in character data.
Action: Do not use ']]>' in character data.
Cause: Found '<' in an attribute value.
Action: Do not use '<' in attribute values.
Cause: An error was received from the SAX callback function.
Action: Examine the additional error messages and take corrective action.
Cause: An external entity reference was found in an attribute value.
Action: Use only references to internal or character entities in attribute values.
Cause: An attribute occurred multiple times in the same start-tag or empty-element tag.
Action: Make sure that the attributes are unique.
Cause: An element tag was not ended properly.
Action: Make sure that the correct end element tag is used.
Cause: An entity is not declared.
Action: Declare the entity before referencing it.
Cause: An entity reference contained the name of an unparsed entity.
Action: Only reference parsed entities.
Cause: An entity reference contains a recursive reference to itself.
Action: Modify the contents of the entity reference to remove this recursion.
Cause: An XML input file has no contents.
Action: The XML file representing a document must contain at least one element.
Cause: An invalid character was found in a NAME or NMTOKEN.
Action: Use only the characters allowed for NAMES and NMTOKENS by the XML specification.
Cause: An invalid character was found in a NAME or NMTOKEN.
Action: Use only the characters allowed for NAMES and NMTOKENS by the XML specification.
Cause: A parameter entity reference was found in an improper location in the internal DTD subset.
Action: Use a parameter entity reference only where markup declarations can occur in the internal DTD subset, in the external DTD subset, or in an external entity.
Cause: Namespace prefix starting with XML was found.
Action: Use another name for the namespace prefix.
Cause: Namespace prefix is not declared.
Action: Declare the prefix in an attribute list.
Cause: Only versions 1.0 and 2.0 of the XML specification are supported.
Action: Use the 1.0 or 2.0 specification & set version# accordingly.
Cause: An invalid character was found in a public identifier.
Action: Use only the characters allowed for public identifiers by the XML specification.
Cause: A conditional section <![ keyword [ markup ]]> had invalid keyword, must be either "IGNORE" or "INCLUDE".
Action: Correct condition section usage in document.
Cause: A conditional section was not properly terminated with ]]>.
Action: Verify conditional nesting in document and correct.
Cause: The attribute type is not valid. Options are CDATA, ID, IDREF, IDREFS, ENTITY, ENTITIES, NMTOKEN, or NMTOKENS.
Action: Check and correct attribute declaration.
Cause: A start-element tag was improperly formed.
Action: Check and correct the start-element syntax.
Cause: An entity reference (general or parameter) was not formed properly.
Action: Form entity reference correctly as "&name;" or "%name;".
Cause: The ampersand character is used only to start entity or character references.
Action: To include an ampersand character as data, use the built-in & general entity.
Cause: An attribute defined in an element's start-tag must be enclosed in single ('') or double ("") quotes.
Action: Enclose the attribute value in quotes.
Cause: The less-than character ('<') is not permitted as data.
Action: Use the built-in entity < instead. Check for mismatched quotes ("') in case the '<' is part of subsequent markup.
Cause: After the close of the top-level element, more data was found.
Action: The end-element tag for the top-level element must be the last thing in the document.
Cause: In an external ID declaration, the public ID literal was not followed by the system ID literal as required.
Action: Provide with public *and* system IDs for 'PUBLIC' type.
Cause: Problems were encountered in the DTD declaration.
Action: Review the DTD and correct the problems.
Cause: Problems were encountered parsing an entity declaration.
Action: Check and correct the declaration syntax.
Cause: Problems were encountered parsing an external ID declaration.
Action: Check and correct the declaration syntax.
Cause: Problems were encountered parsing an attribute declaration.
Action: Check and correct the declaration syntax.
Cause: A condition section is not permitted in internal DTDs.
Action: Remove the condition section.
Cause: Markup included from an entity must nest/group properly. That is, open/close markup must occur within the same entity. For example:
<!DOCTYPE doc [ <!ENTITY e "</foo><foo>"> ]> <doc><foo>&e;</foo></doc>
Is invalid since foo's start-tag occurs in the top-level document, but the close-tag is provided by the "e" entity. Both start and end must be provided by the same source.
Action: Examples, such as the ones above, are not permitted.
Cause: An XML declaration was missing the required version#.
Action: Always provide a version#, which must come first in the declaration. XML is case sensitive, so only "version" (not "Version", and so on) is valid.
Cause: Problems were encountered parsing an XML declaration.
Action: Check and correct the declaration syntax.
Cause: The "standalone" parameter in the XML declaration had an invalid value.
Action: standalone must be set to either "yes" or "no". Case is sensitive, so "Yes", "YES", and so on, are invalid.00256 invalid element declaration
Cause: Problems were encountered parsing an element declaration.
Action: Check and correct the declaration.
Cause: The 'children' specification in an element declaration was invalid.
Action: Check and correct the declaration.
Cause: The 'Mixed' specification in an element declaration was invalid.
Action: Check and correct the declaration.
Cause: Problems were encountered parsing a notation declaration.
Action: Check and correct the declaration syntax.
Cause: The xml:space attribute must be declared as an enumeration with choices "default" and "preserve". For example, <!ATTLIST foo xml:space (default|preserve) 'preserve').
Action: Declare the special attribute as above.
Cause: The specified URL was invalid and could not be parsed.
Action: Correct the URL; consult RFC-2396.
Cause: An URL was encountered which requested a protocol not supported by the XML parser. Only HTTP and file are currently allowed.
Action: Make the data available through the filesystem or HTTP.
Cause: A TCP connection couldn't be opened to the named host.
Action: Verify the hostname and connectivity to the host.
Cause: An error occurred trying to send data over a TCP connection.
Action: Verify network connectivity, and so on.
Cause: An error occurred trying to read data from a TCP connection.
Action: Verify network connectivity, and so on.
Cause: The given language specification was invalid.
Action: Language specification has the format <language>_<territory>.<character set>. For example, "French_France".
Cause: The named relative URL couldn't be resolved against its parent.
Action: Make sure the relative makes sense in relation to its parent URL; see RFC-2396 sections 4, 5, and appendix C.
Cause: The provided access code was not in the valid range.
Action: The code should be one of the XMLACCESS_xxx codes defined in oraxml.h, in the range shown in the error message.
Cause: An attempt was made to set the access method callbacks, but all three functions were not provided.
Action: All three callback functions (open, close, and read) are required. They must all be provided, even if they are stub functions which do nothing.
Cause: An error was returned from the FTP server while trying to retrieve a file. See the specific message for details.
Action: Corrective action depends on the error.
Cause: The username/password combination was invalid for FTP login.
Action: Specify a valid pair.
Cause: The FTP server is unavailable for use.
Action: No action is possible from the client side. See server's error message.
Cause: The TCP/IP package could not be initialized.
Action: Check with system administrator to see if this is a configuration problem or a connectivity problem.
Cause: Some node types (DOCUMENT_NODE & DOCUMENT_TYPE_NODE) cannot be imported with importNode().
Action: No action required.
Cause: Output/data encoding must be set after initialization but BEFORE any parsing has taken place.
Action: Set encoding before parsing any documents.
Cause: An HTTP reply contained an invalid Mime header.
Action: Verify HTTP reply for accuracy. See RFC 2616.
Cause: A quoted string was started but not finished.
Action: Put a closing quote in the proper location.
Cause: The proxy specification for the given protocol was invalid.
Action: Check and correct the proxy specification. For HTTP, this is the environment variable "http_proxy".
Cause: The no_proxy specification was invalid.
Action: Check and correct it. no_proxy is a comma- or space-separated list of machine or domain names, with an optional port part. If no port part is present, then it applies to all ports on that domain.
Cause: An HTTP protocol error occurred.
Action: Corrective action depends on the error.
Cause: The specified encoding is known but not supported by the parser.
Action: Try a different encoding.
Cause: A parser context which had a shared DTD set was used to parse a document which also contained a DTD. You cannot use both a shared DTD and and internal/external one.
Action: If a shared DTD is to be used, then the documents parsed must not contain or reference a DTD.
Cause: The input document was detected to be ASCII (or EBCDIC) based, but no encoding was specified in the XMLDecl and the default input coding was not ASCII (or EBCDIC) based, so could not be applied.
Action: Add an explicit encoding specification to the XMLDecl so the default input encoding is not needed, or pick a default encoding which matches the input document.
Cause: The name attribute was not found in the attribute-set element.
Action: Add a name attribute for this element.
Cause: The XPATH evaluation returns an error.
Action: Check specified XPATH expression to determine the error.
Cause: The child node is of invalid type or has invalid name for this particular location in stylesheet, rendering the stylesheet as invalid XSLT.
Action: Fix the stylesheet by using valid nodes only.
Cause: Attribute is found but its value is not the expected value.
Action: Set the attribute value to the correct value.
Cause: An input parameter passed into this function is null when it is not supposed to.
Action: Make sure the caller function is not passing null for this parameter.
Cause: An expected token is not found.
Action: Check the input string to make sure the expected token is present.
Cause: A closing '}' is expected.
Action: Add the closing '}' to the input string or remove the extra opening '{'.
Cause: Namespace prefix is used but not declared.
Action: Either declare the namespace or don't use this namespace prefix.
Cause: The expected attribute for this node is not found.
Action: Need to add this attribute to the node.
Cause: XPATH context could not be initialized.
Action: Check the initialization function LpxsutInitXpathCtx().
Cause: The expected element is not found.
Action: Check the initialization function LpxsutInitXpathCtx().
Cause: This feature is not supported.
Action: Do not use this feature.
Cause: The content of XML PI node might be invalid.
Action: Make necessary changes to make the node valid according to spec.
Cause: The content of XML comment node might be invalid.
Action: Make necessary changes to make the node valid according to spec.
Cause: An internal error occurred in the code.
Action: Contact the appropriate developer.
Cause: This extension function is not supported.
Action: Either contact the appropriate developer for more information or don't use this extension function.
Cause: The value for the specified attribute is invalid.
Action: Consult the XSL spec; use only legal values.
Cause: The named decimal-format is undefined (the name "#default" means the default format).
Action: Define the desired decimal-format before trying to use it.
Cause: The named decimal-format was declared more than once.
Action: Make sure there is only a single declaration.
Cause: The node specified is not of expected type.
Action: Use only the nodes of legal type.
Cause: The element to which an attribute was being added is non-empty and hence can not add anymore attributes to it.
Action: Modify the XSLT stylesheet so that all the attributes are added to an element before anything else is added to it. If you absolutely can not do that then select your output method to be DOM based rather then a stream or SAX based output which you are using presently.
Cause: User is trying to process an XML file with out selecting any mechanism for output.
Action: User must select one of the output mechanisms (SAX/DOM/Stream) before attempting to process the XML file.
Cause: Either an import,include or document() function tried to open a document and failed.
Action: Make sure that document is present and can be opened.
Cause: apply-imports was used even when there was no current template possibly with in for-each.
Action: Make sure that apply-imports are invoked only if there is a current template and it is not in a xsl:for-each.
Cause: An internal error has occurred in XPATH.
Action: Contact the appropriate developer.
Cause: An invalid QName was passed to the XPATH parser.
Action: See whether there are any invalid QNames in the XSL file.
Cause: An invalid axis name was passed to the XPATH parser.
Action: See whether all axis names in the XSL file are correct.
Cause: An unmatched quote was found in the XSL file.
Action: Check for unmatched quotes in the XSL file.
Cause: The namespace URI may not be valid.
Action: Make sure that the name space URIs are valid.
Cause: May be out of memory.
Action: Try increasing virtual memory.
Cause: An object of incorrect type was passed to the XPATH/XSL function.
Action: Do the required conversion before passing in an object of type which is different from the expected type.
Cause: Right square bracket missing in the XSL file.
Action: Check for unmatched square bracket in the XSL file.
Cause: Right parenthesis missing in the XSL file.
Action: Check for unmatched parenthesis in the XSL file.
Cause: An unexpected token was encountered while parsing the expression/pattern.
Action: Check the syntax of the expressions/patterns.
Cause: Variable reference may not be valid.
Action: Check whether the variable references are valid.
Cause: The function is not supported at this time or the name is invalid.
Action: Check the function names. If valid and this error occurs, then avoid using them at this time.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
