Oracle 12c R2 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: n/a
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.
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: n/a
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.
Cause: An outline already exists, either with the specified name, or for the specified SQL text.
Action: n/a
- ORA-18005: CREATE ANY OUTLINE privilege is required for this operation
- ORA-18006: DROP ANY OUTLINE privilege is required for this operation
- ORA-18007: ALTER ANY OUTLINE privilege is required for this operation
- 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.
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.
Cause: User failed to specify the CATEGORY keyword
Action: Re-issue the command with the CATEGORY keyword included
- ORA-18011: the outline specified in the FROM clause does not exist
- ORA-18012: select_catalog_role role is required for this operation
- ORA-18013: timed out while waiting for resource string
- ORA-18014: deadlock detected while waiting for resource string
- 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
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
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
Cause: Prolog contained more than one revalidation declaration.
Action: None
Cause: The insertion sequence of an INSERT expression contained an attribute following a node that was not an attribute node.
Action: None
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
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
Cause: The target expression of a DELETE expression did not return a sequence of zero or more nodes.
Action: None
Cause: In a REPLACE expression, the target expression returned a nonempty result that did not consist of a single element, attribute, text,
Action: None
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
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
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
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
Cause: In a TRANSFORM expression, a source expression in the copy clause did not return a single node.
Action: None
Cause: In a TRANSFORM expression, the MODIFY clause modified a node that was not created by the COPY clause.
Action: None
Cause: A node was the target of more than one RENAME expression within the same query.
Action: None
Cause: A node was the target of more than one REPLACE expression (without VALUE OF being specified) within the same query.
Action: None
Cause: A node was the target of more than one REPLACE VALUE OF expression within the same query.
Action: None
Cause: A function that was declared to be external but not updating returned a nonempty pending update list.
Action: None
Cause: A function that was declared to be both external and updating returned a nonempty data model instance.
Action: None
Cause: Node was deleted that had no parent before execution of the query began.
Action: None
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
Cause: INSERT expression specified the insertion of an attribute node into a document node.
Action: None
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
Cause: Effect of a set of updating expressions introduced conflicting namespace bindings into an element node.
Action: None
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
Cause: Revalidation declaration in a Prolog specified a revalidation mode that is not supported by the current implementation.
Action: None
Cause: Target expression of an INSERT, REPLACE, or RENAME expression evaluated to an empty sequence.
Action: None
Cause: Function declaration specified both UPDATING and a return type.
Action: None
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
Cause: INSERT expression specified the insertion of an attribute node before or after a child of a document node.
Action: None
Cause: The first operand of fn:put was not a node of a supported kind.
Action: None
Cause: The second operand of fn:put was not a valid lexical representation of the xs:anyURI type.
Action: None
Cause: Updating expression was specified as top-level XMLQuery expression.
Action: Use XQuery TRANSFORM expression to copy input value and modify it.
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.
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.
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.
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.
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.
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.
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.
Cause: It was a static error if, during the static analysis phase, the query was found to contain a stop word option that referred to a stop word list that was not found in the statically known stop word lists.
Action: Ensure that the stop word list exists.
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.
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.
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.
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.
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.
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: n/a
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: n/a
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.
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: n/a
Cause: There was no XML full-text index to evaluate the XQuery full text expression filtering XML documents that were stored in an XMLType table or column.
Action: Create an XML full-text index on the XML documents stored in an XMLType table or column and ensure that the XQuery full text expression can be evaluated by an XML full-text index.
Cause: The XMLTABLE column expression used the XMLTYPE(SEQUENCE) BY REF clause which requires XMLType input to the XMLTABLE row expression to use the PASSING BY REF clause.
Action: Specify the PASSING BY REF clause for XMLType input to the XMLTABLE row expression.
Cause: Output of the XMLTABLE column expression was passed to an XMLTABLE row expression with PASSING BY REF clause.
Action: Specify the XMLTABLE column expression using XMLTYPE(SEQUENCE) BY REF clause.
Cause: An XML document that was not stored in an XMLType table or column was passed to an XMLTABLE row expression using the PASSING BY REF clause.
Action: Ensure that only XML documents that are stored in an XMLType table or column can be passed in as input to XMLTABLE row expression using the PASSING BY REF clause.
Cause: An attempt was made to use an XQuery full text expression option that is not supported.
Action: Avoid using an XQuery full text expression option which is not supported.
Cause: During the static analysis phase, the query was found to contain a thesaurus option that referred to a thesaurus that was not found in the statically known thesauri. This is a static error.
Action: Avoid using unknown thesaurus.
- ORA-18183: FTST0019 more than one match option of any given match option group is used within a single FTMatchOptions.
Cause: Within the single FTMatchOptions, there was more than one match option of any given match option group. This is a static error.
Action: Avoid using more than one match option of any given match option group is used within a single FTMatchOptions.
Cause: Because wildcards were in effect, the query string violated wildcard syntax. This is a dynamic error.
Action: Fix wildcard syntax when wildcards is in effect.
Cause: The query string was not parsed correctly.
Action: Check the syntax of the query string.
Cause: The input MDX (MultiDimensional eXpression) string was empty.
Action: Correct the input MDX (MultiDimensional eXpression) string.