Oracle 11g Error Codes and Solution Suggestions from ORA-18000 to ORA-18200
- ORA-18000: invalid outline name
- Cause: The parser detected a missing or invalid outline name
- Action: None
- ORA-18001: no options specified for ALTER OUTLINE
- Cause: The parser detected that no clause was specified on the command Our performance tests, which are not typical as they exercise all branches of the code, have shown approximately a 30% performance increase line for ALTER OUTLINE.
- Action: Re-issue the command, specifying a valid ALTER OUTLINE clause.
- ORA-18002: the specified outline does not exist
- Cause: Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream.
- Action: None
- ORA-18003: an outline already exists with this signature
- Cause: The signature generation algorithm generates signatures that are are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case.
- Action: Either re-issue the statement that led to the outline being created with some whitespace added or force the outline to be created in a different category.
- ORA-18004: outline already exists
- Cause: An outline already exists, either with the specified name, or for the specified SQL text.
- Action: None
- ORA-18008: cannot find OUTLN schema
- Cause: The database creation script that creates this schema must not have been executed.
- Action: Review the log files to see what happened when the database was created.
- ORA-18009: one or more outline system tables do not exist
- Cause: Either the database creation script that creates these tables was not executed or a user accidently deleted the table
- Action: Review the log files to see what happened when the database was created.
- ORA-18010: command missing mandatory CATEGORY keyword
- Cause: User failed to specify the CATEGORY keyword
- Action: Re-issue the command with the CATEGORY keyword included
- ORA-18015: invalid source outline signature
- Cause: User imported an 8i outline into a 9i database without updating signatures
- Action: execute dbms_outln.update_signatures
- ORA-18100: XUST0001 – Updating expression in a wrong position
- Cause: An updating expression was used in a position other than one of the following:
- – The topmost expression in the body of a query.
- – The MODIFY clause of a TRANSFORM expression.
- – The RETURN clause of a FLWOR expression.
- – The RETURN clauses of a TYPESWITCH expression in which every RETURN clause contains an updating expression, an empty expression ( ), or a call to the fn:error function.
- – The THEN and ELSE clauses of a conditional statement in which both the then and else clauses contain either an updating expression, an empty expression ( ), or a call to the fn:error function.
- – An operand of a comma expression in which each operand is either an updating expression, an empty expression ( ), or a call to the fn:error function.
- – The content of a parenthesized expression.
- – The body of a function declaration in which the keyword UPDATING is specified.
- Action: None
- ORA-18101: XUST0002 – Non-updating expression in a wrong position
- Cause: A non-updating expression other than an empty expression ( ) or a call to the fn:error function was used in one of the following positions:
- – The MODIFY clause of a TRANSFORM expression.
- – The top-level expression in the body of a function declaration in which the keyword UPDATING is specified.
- Action: None
- ORA-18102: XUST0003 – Repeated revalidation declaration
- Cause: Prolog contained more than one revalidation declaration.
- Action: None
- ORA-18103: XUTY0004 – Invalid attribute node in the insertion sequence
- Cause: The insertion sequence of an INSERT expression contained an attribute following a node that was not an attribute node.
- Action: None
- ORA-18104: XUTY0005 – Invalid target expression for INSERT
- Cause: In an INSERT expression where INTO, AS FIRST INTO, or AS LAST INTO was specified, the target expression returned a nonempty result that did not consist of a single element or document node.
- Action: None
- ORA-18105: XUTY0006 – Invalid target expression for INSERT
- Cause: In an INSERT expression where BEFORE or AFTER was specified, the target expression returned a nonempty result that did not consist element, text, comment, or processing instruction node.
- Action: None
- ORA-18106: XUTY0007 – Invalid target expression for DELETE
- Cause: The target expression of a DELETE expression did not return a sequence of zero or more nodes.
- Action: None
- ORA-18107: XUTY0008 – Invalid target expression for REPLACE
- Cause: In a REPLACE expression, the target expression returned a nonempty result that did not consist of a single element, attribute, text,
- Action: None
- ORA-18108: XUDY0009 – Invalid target expression for REPLACE
- Cause: In a REPLACE expression where VALUE OF was not specified, the node returned by the target expression did not have a parent.
- Action: None
- ORA-18109: XUTY0010 – Invalid replacement sequence for REPLACE
- Cause: In a REPLACE expression where VALUE OF was not specified and the target was an element, text, comment, or processing instruction node, the replacement sequence did not consist of zero or more element, text, comment, or processing instruction nodes.
- Action: None
- ORA-18110: XUTY0011 – Invalid replacement sequence for REPLACE
- Cause: In a REPLACE expression where VALUE OF was not specified and the target is an attribute node, the replacement sequence did not consist of zero or more attribute nodes.
- Action: None
- ORA-18111: XUTY0012 – Invalid target expression for RENAME
- Cause: In a RENAME expression, the target expression returned a nonempty result that did not consist of a single element, attribute, or processing instruction node.
- Action: None
- ORA-18112: XUTY0013 – Invalid COPY expression for TRANSFORM
- Cause: In a TRANSFORM expression, a source expression in the copy clause did not return a single node.
- Action: None
- ORA-18113: XUDY0014 – Modified node was not created by the COPY clause
- Cause: In a TRANSFORM expression, the MODIFY clause modified a node that was not created by the COPY clause.
- Action: None
- ORA-18114: XUDY0015 – Duplicate RENAME for the same target node
- Cause: A node was the target of more than one RENAME expression within the same query.
- Action: None
- ORA-18115: XUDY0016 – Duplicate REPLACE for the same target node
- Cause: A node was the target of more than one REPLACE expression (without VALUE OF being specified) within the same query.
- Action: None
- ORA-18116: XUDY0017 – Duplicate REPLACE for the same target node
- Cause: A node was the target of more than one REPLACE VALUE OF expression within the same query.
- Action: None
- ORA-18117: XUDY0018 – External not updating function returns an updated value
- Cause: A function that was declared to be external but not updating returned a nonempty pending update list.
- Action: None
- ORA-18118: XUDY0019 – External updating function returns an invalid value
- Cause: A function that was declared to be both external and updating returned a nonempty data model instance.
- Action: None
- ORA-18119: XUDY0020 – Deleted node has no parent
- Cause: Node was deleted that had no parent before execution of the query began.
- Action: None
- ORA-18120: XUDY0021 – The result XDM instance violates XDM constraints
- Cause: XDM instance resulting from applying all the updates in a query violated constraint specified in [XQuery/XPath Data Model (XDM)]. In this case, none of the updates in the query were made effective.
- Action: None
- ORA-18121: XUTY0022 – Invalid attribute insertion into a document node
- Cause: INSERT expression specified the insertion of an attribute node into a document node.
- Action: None
- ORA-18122: XUDY0023 – Updating expression introduces a namespace conflict
- Cause: An INSERT, REPLACE, or RENAME expression affected an element node by introducing a new namespace binding that conflicted with one of its existing namespace bindings.
- Action: None
- ORA-18123: XUDY0024 – Updating expression introduces a namespace conflict
- Cause: Effect of a set of updating expressions introduced conflicting namespace bindings into an element node.
- Action: None
- ORA-18124: XUDY0025 – Invalid QName for processing instruction RENAME
- Cause: Target of a RENAME expression was a processing instruction node, and the new name expression returned a QName with a nonempty namespace prefix.
- Action: None
- ORA-18125: XUST0026 Revalidation mode string is not supported
- Cause: Revalidation declaration in a Prolog specified a revalidation mode that is not supported by the current implementation.
- Action: None
- ORA-18126: XUDY0027 – Invalid target expression
- Cause: Target expression of an INSERT, REPLACE, or RENAME expression evaluated to an empty sequence.
- Action: None
- ORA-18127: XUST0028 – Updating function should not have a return type
- Cause: Function declaration specified both UPDATING and a return type.
- Action: None
- ORA-18128: XUDY0029 – INSERT expression target node doesn’t have a parent
- Cause: In an INSERT expression where BEFORE or AFTER was specified, a node returned by the target expression did not have a parent.
- Action: None
- ORA-18129: XUDY0030 – Invalid insertion of an attribute node
- Cause: INSERT expression specified the insertion of an attribute node before or after a child of a document node.
- Action: None
- ORA-18130: FOUP0001 – Invalid ‘fn:put’ first operand
- Cause: The first operand of fn:put was not a node of a supported kind.
- Action: None
- ORA-18131: FOUP0002 – Invalid ‘fn:put’ second operand
- Cause: The second operand of fn:put was not a valid lexical representation of the xs:anyURI type.
- Action: None
- ORA-18150: SQL input value cannot be modified in updating expression
- Cause: Updating expression was specified as top-level XMLQuery expression.
- Action: Use XQuery TRANSFORM expression to copy input value and modify it.
- ORA-18160: FTST0001 – FTMildNot operator not supported
- Cause: An attempt was made to use the mild not option when the FTMildNot operator was not supported. An implementation that does not support the FTMildNot operator must raise a static error if a full-text query contains a mild not.
- Action: Do not use the FTMildNot full-text query operator.
- ORA-18161: FTST0002 – FTUnaryNot operator not supported
- Cause: An implementation that enforces one of the restrictions on FTUnaryNot must raise a static error if a full-text query does not obey the restriction.
- Action: Do not use the FTUnaryNot full-text query operator.
- ORA-18162: FTST0003 – FTUnit and FTBigUnit not supported
- Cause: An implementation that does not support one or more of the choices on FTUnit and FTBigUnit must raise a static error if a full-text query contains one of those choices.
- Action: Do not use the FTUnit or FTBigUnit option.
- ORA-18163: FTST0004 – FTScope not supported
- Cause: An implementation that does not support the FTScope operator must raise a static error if a full-text query contains a scope.
- Action: Do not use the FTScope full-text query operator.
- ORA-18164: FTST0005 FTTimes not supported
- Cause: An implementation that does not support the FTTimes operator must raise a static error if a full-text query contains a times.
- Action: Do not use the FTTimes full-text query operator.
- ORA-18165: FTST0006 FTStopwordOption not supported
- Cause: An implementation that restricts the use of FTStopwordOption must raise a static error if a full-text query contains a stop word option that does not meet the restriction.
- Action: Do not use the FTStopwordOption full-text query operator.
- ORA-18166: FTST0007 FTIgnoreOption not supported
- Cause: An implementation that restricts the use of FTIgnoreOption must raise a static error if a full-text query contains an ignore option that does not meet the restriction.
- Action: Do not use the FTIgnoreOption full-text query operator.
- ORA-18167: FTST0008 stop word list not found
- Cause: It is a static error if, during the static analysis phase, the query is found to contain a stop word option that refers to a stop word list that is not found in the statically known stop word lists.
- Action: Please make sure the stop word list exist.
- ORA-18168: FTST0009 language option not supported
- Cause: It may be a static error if, during the static analysis phase, the query is found to contain a language identifier in a language option that the implementation does not support. The implementation may choose not to raise this error and instead provide some other implementation-defined behavior.
- Action: Do not use the language full-text query option.
- ORA-18169: FTST0010 FTOrder not succeeding FTWindow or FTDistance operator
- Cause: It is a static error if, during the static analysis phase, an expression is found to use an FTOrder operator that does not appear directly succeeding an FTWindow or an FTDistance operator and the implementation enforces this restriction.
- Action: Do not use the FTOrder succeeding FTWindow or FTDistance full-text query operator.
- ORA-18170: FTST0011 FTWindow and FTDistance restriction
- Cause: An implementation may restrict the use of FTWindow and FTDistance to an FTOr that is either a single FTWords or a combination of FTWords involving only the operators && and ||. If it a static error if, during the static analysis phase, an expression is found that violates this restriction and the implementation enforces this restriction.
- Action: Follow FTWindow and FTDistance restriction.
- ORA-18171: FTST0012 FTContent not supported
- Cause: An implementation that does not support the FTContent operator must raise a static error if a full-text query contains one.
- Action: Do not use FTContent full-text query operator.
- ORA-18172: FTST0013 more than one language encountered
- Cause: It is a static error if, during the static analysis phase, an implementation that restricts the use of FTLanguageOption to a single language, encounters more than one distinct language option.
- Action: Do not use more than one language in FTLanguag full-text option.
- ORA-18173: FTST0014 score computation restriction
- Cause: An implementation may constrain the form of the expression used to compute scores. It is a static error if, during the static analysis phase, such an implementation encounters a scoring expression that does not meet the restriction.
- Action: None
- ORA-18174: FTST0015 FTCaseOption restriction
- Cause: It is a static error if, during the static analysis phase, an implementation that restricts the choices of FTCaseOption encounters the “lowercase” or “uppercase” option.
- Action: None
- ORA-18175: FTDY0016 weights invalid
- Cause: It is a dynamic error if an implementation that does not support negative weights encounters a weight expression that does not meet the restriction.
- Action: Do not use invalid weights value.
- ORA-18176: FTDY0017 mild not selection containings StringExclude
- Cause: It is a dynamic error if an implementation encounters a mild not selection, one of whose operands evaluates to an AllMatches that contains a StringExclude
- Action: None