Oracle 12c R2 Error Codes and Solution Suggestions from ORA-19200 to ORA-19400
- ORA-19200: Invalid column specification
Cause: All input arguments must be valid columns
Action: Specify a valid list of columns
Cause: The particular datatype is not supported in the XMLGEN operator
Action: Specify only supported datatypes as arguments to the XMLGEN operator
Cause: An error occurred when processing the XML function
Action: Check the given error message and fix the appropriate problem
Cause: An error occurred when processing the DBMS_XMLGEN functions
Action: Check the given error message and fix the appropriate problem
Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by ‘@’. In this case, a non-scalar value was prefixed with ‘@’
Action: Remove the ‘@’ sign, or make the value a scalar.
Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.
Action: Remove the ‘@’ sign, or make the previous value a scalar.
Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.
Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.
Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
Action: Remove the AS clause of the scalar element.
Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.
Action: Specify an alias for the expression using the AS clause.
Cause: An invalid or unsupported formatting argument was supplied
Action: Change the formatting argument to legal supported values
- ORA-19210: column ‘string‘, specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table ‘string‘
Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table.
Action: Change the column specified to be a column in the table
- ORA-19211: column ‘string‘, specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
Cause: The column specified using setKeyColumn() was a non-scalar type column.
Action: Change the column specified to be a scalar column in the table
Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.
Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns
Cause: An error occurred when processing the given lines in an XML function.
Action: Check the given error message and fix the appropriate problem.
Cause: An unitialized static context component was encountered during the static analysis of the expression.
Action: initialize the given static context.
Cause: An unitialized dynamic context component was encountered during the evaluation of the expression.
Action: Initialize the particular dynamic context component.
Cause: The given XQuery expression contains syntax errors.
Action: Fix the syntax error in the XQuery expression.
Cause: The expression could not be used because it’s static type is not appropriate for the context in which it was used.
Action: Fix the expression to be of the required type or add appropriate cast functions around the expression.
Cause: The static type assigned to an expression other than the () expression must not be the empty type.
Action: Fix the expression so it does not return empty sequences.
Cause: The expression could not be used because it’s dynamic type did not match the required type as specified by XQuery sequencetype matching rules.
Action: Fix the expression to return the expected type or use appropriate cast functions.
- ORA-19227: XPTY0007 – fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
Cause: The input node for atomization contained a type annotation that denoted a complex type with non-mixed complex content.
Action: Fix the input expression to fn:data to be a node that does not contain non-mixed complex content.
Cause: The given identifier refers to either a type name, function name, namespace prefix, or variable name that is not defined in the static context.
Action: Fix the expression to remove the identifier, or declare the appropriate variable, type, function or namespace.
Cause: A schema import was encountered in the query.
Action: remove the schema import.
Cause: An unsupported axis was encountered in the given expression.
Action: Remove the unsupported axis from the expression.
Cause: The imported schemas did not satisfy the conditions for schema validity specified in the XMLSchema specification.
Action: Fix the imported schemas to satisfy the validity rules.In particular, the definitions must be valid, complete, and unique — that is, the pool of definitions must not contain two or more schema components with the same name and target namespace.
Cause: A pragma was specified whose contents are invalid.
Action: Specify the pragma with the correct contents.
Cause: The must-understand extension specified was either invalid or unsupported.
Action: remove the unsupported must-understand extension or fix the error.
Cause: The XQuery flagger was enabled and the query contained a must-understand extension.
Action: remove the unsupported must-understand extension.
Cause: The given query had a module declaration or module import.
Action: Remove the import module or module declaration.
Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
- ORA-19238: XPTY0018 – It is a type error if the result of the last step in a path expression contains both nodes and atomic values
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19239: XPTY0019 – It is a type error if the result of an step (other than the last step) in a path expression contains an atomic value
Cause: The step expression returned a sequence containing an atomic value.
Action: Fix the path expression to return only nodes.
Cause: The context item that was used in the axis epression is not a node.
Action: Change the context item to be a node.
Cause: The value inside a cast expression could not be cast to the required type.
Action: Fix the input to the cast expression to be of a castable type.
Cause: The namespace declaration attribute was not a literal string.
Action: Fix the namespace declaration to be a literal string.
Cause: The content sequence in an element constructor contained a document node.
Action: Change the content of the element constructor so that it does not contain a document node.
Cause: The content sequence in an element constructor contained an attribute node following a node that was not an attribute node.
Action: Change the content sequence of the element constructor so that it does not contain the attribute node.
Cause: The content sequence of the element constructor contained more than one attribute that had the same name.
Action: Remove the duplicate attributes.
Cause: The validation mode was strict and the element-constructor contained an element name that was not present in the in-scope element declarations.
Action: Fix the validation mode to be lax or import the schema definition that contains the required element declaration.
Cause: An error was encountered during the validation of the expression.
Action: Fix the validation error.
Cause: The content sequence in a document constructor contained either a document or an attribute node.
Action: Fix the content so it does not contain any of the above node types.
Cause: The input value to a cast expression did not satisfy the facets of the target type.
Action: Fix the value to conform to the facets of the target type.
Cause: The argument of a validate expression returned more than one element or document node.
Action: Fix the argument of the validate expression to return a single element or document node.
Cause: The query version specified in the prolog was not supported.
Action: Supply the version of the query that is supported.
Cause: The query prolog contained multiple declarations for the base URI.
Action: Remove the duplicate definitions for the base URI.
Cause: The query prolog contained multiple declarations for the same namespace prefix.
Action: Remove the duplicate definitions for the namespace prefix.
Cause: The query module contained more than one function, either declared or imported, which have the same expanded QName.
Action: Remove the duplicate function definitions.
Cause: Two schemas were imported that defined the same name in the same symbol space and in the same scope.
Action: Fix the schema imports to remove the name conflict.
Cause: A module was imported, which contains references to type names that are not defined in the in-scope type definitions inside the module.
Action: Fix the module definintion to include the in-scope type definition.
Cause: A module being imported contained the function or variable that is already declared in the static context of the importing module.
Action: Remove the conflicting declarations.
Cause: The query prolog prolog either specified more than one default collation or the collation specified was not supported.
Action: Remove the duplicate definition or specify a supported collation.
Cause: The function declaration contained more than one parameter with the same name.
Action: Fix the function declaration to remove the duplicate parameters.
Cause: The content sequence in an element constructor contained a namespace node node following a node that was not a namespace node.
Action: Remove the namespace node in the element constructor.
Cause: The name expression in a computed processing instruction or computed namespace constructor returned a QName whose URI part was not empty.
Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part.
Cause: The enclosing expression of a computed namespace constructor was not a computed element constructor.
Action: Fix the namespace constructor to be inside an element constructor.
Cause: Two or more computed namespace constructors within the same computed element constructor attempted to bind the same namespace prefix.
Action: Remove the duplicate namespace definitions.
Cause: A computed attribute constructor returned a QName that is in the pre-defined XML namespace (corresponding to namespace prefix xmlns).
Action: Change the namespace for the computed attribute constructor.
Cause: The declared function name in a function declaration had no namespace prefix or had one of the predefined namespace prefixes other than local.
Action: Fix the function declaration to have the correct prefix.
Cause: The given URI contained a lexical form that was not valid according to the definition of xs:anyURI in XML Schema.
Action: Fix the URI.
Cause: The module with the given target URI could not be found.
Action: Fix the prolog to import only available modules.
Cause: The module contained a function or variable whose namespace did not match the target namespace of the module.
Action: Fix the namespace of the function or variable to match the target namespace of the module.
Cause: The module defined or imported the same variable multiple times.
Action: Fix the import or the module definition to remove duplicate definitions.
Cause: The type of the operand to the treat expression did not match the required type.
Action: Fix the input operand to be of the correct type.
Cause: The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type.
Action: Use the correct atomic type name.
Cause: The content of the element or attribute constructor included an atomic value that could not be cast into a string.
Action: Fix the content to contain atomic values that can be cast to a string.
Cause: An empty string was used in a namespace declaration.
Action: Fix the namespace declaration to have a non-empty string.
Cause: A circular definition was encountered when the variable was initialized.
Action: Remove the circularity in the initialization.
Cause: The ElementTest specified a schema path that could not be found in the list of in-scope schema definitions.
Action: Include the appropriate schema that can be used to resolve the ElementTest.
Cause: The XPath step specified invalid element or attribute name that did not match any nodes according to the input XML schema or structure.
Action: Correct the element or attribute name as the name may be mis-spelled.
Cause: The XPath step specified an item type that did not match any nodes according to the input XML schema or structure.
Action: Correct the item type defintion as node of such type does not exit in the input XML schema or structure.
Cause: The value was invalid for the type.
Action: Correct the value or change the type.
- ORA-19279: XPTY0004 – XQuery dynamic type mismatch: expected singleton sequence – got multi-item sequence
Cause: The XQuery sequence passed in had more than one item.
Action: Correct the XQuery expression to return a single item sequence.
Cause: A node was passed in to the expression where an atomic value was expected.
Action: Correct the XQuery expression to return an atomic value.
- ORA-19281: XQST0055 – It is a static error if a Prolog contains more than one copy-namespaces declaration
Cause: The query prolog contained multiple copy-namespaces declarations.
Action: Remove the duplicate copy-namespaces declarations.
Cause: The query prolog contained multiple xmlspace declarations.
Action: Remove the duplicate xmlspace declarations.
- ORA-19283: XQST0031 – It is a static error if the version number specified in a version declaration is not supported by the implementation.
Cause: The query contained a version declaration not supported by this implementation.
Action: Change the version declaration to 1.0 which is the version supported by this implementation.
Cause: The query contained an encoding specification.
Action: Remove the encoding specification.
Cause: The URI provided could not be resolved to a valid resource.
Action: Provide a valid URI for a resource.
Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
Cause: Multiple functions declared or imported by a module had the same expanded QName and the same number of arguments.
Action: Fix the function declaraction or definition to remove duplicates.
Cause: A prolog had more than one empty order declaration.
Action: Fix the prolog to have just one empty order declaration.
Cause: The namespace prefix of the QName could not be expanded into a namespace URI by using the statically known namespaces.
Action: Use a namespace prefix that can be resolved into a namespace URI from the statically known namespaces.
- ORA-19292: XQST0057: It is a static error if a schema import binds a namespace prefix but does not specify a target namespace other than a zero-length string
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19293: XQST0058: It is a static error if multiple schema imports specify the same target namespace
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19294: XQST0059: It is a static error if an implementation is unable to process a schema or module import by finding a schema or module with the specified target namespace
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19295: XQST0060: It is a static error if the name of a function in a function declaration is not in a namespace (expanded QName has a null namespace URI)
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19296: XQDY0061: It is a dynamic error if the operand of a validate expression is a document node whose children do not consist of exactly one element node and zero or more comment and processing instruction nodes, in any order
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19297: XQDY0064: It is a dynamic error if the value of the name expression in a computed processing instruction constructor is equal to “XML” (in any combination of upper and lower case
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19298: XQST0065: A static error is raised if a Prolog contains more than one ordering mode declaration
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19299: XQST0066: A static error is raised if a Prolog contains more than one default element/type namespace declaration, or more than one default function namespace declaration
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
Cause: An error occurred when processing the URL
Action: Check the given error message and fix the appropriate problem
Cause: A host name was not specified in the HTTP url
Action: Specify a host name in the HTTP url when creating the URL string
Cause: A HTTP connection could not be opened to the host
Action: Specify a valid host name and port to connect to
Cause: An error occurred while reading from the HTTP host
Action: Specify a valid host name and port to read from
Cause: The URL must be a valid URL string
Action: Specify a valid url string
- ORA-19330: Type ‘string‘.’string‘ not installed. Please install the type before using the CREATE_DBURI operator
Cause: The type required for the CREATE_DBURI operator has not been installed correctly.
Action: Read the installation notes to install the type correctly.
Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.
Action: Specify a valid column name in the query.
Cause: The argument to the CREATE_DBURI operator can only be a column.
Action: Specify a valid column name for the operator
Cause: The flags argument given to the DBURI operator is invalid
Action: Specify a valid flag value (TEXT) for the DBURI operator
Cause: All columns must be valid and pointing to the same table or view
Action: Specify valid list of columns that are from the same table or view.
Cause: An invalid format type object was specified for the XML function
Action: Specify a valid format type object
Cause: The XML being generated does not have an enclosing root element.
Action: The XML generated must have a root element
Cause: The ONLINE option was specified to validate the structure of a system-generated metadata index
Action: The ONLINE option can not be used with system-generated metadata indexes such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query without using the ONLINE option.
Cause: The user attempted to call load_sqlset with an update option that is different than REPLACE and ACCUMULATE.
Action: Adjust the update option and retry the operation.
Cause: The user attempted to call load_sqlset with an invalid update condition.
Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME) and retry the operation.
Cause: The user attempted to create a staging table and specified an invalid staging table (or one that already exists) or tablespace
Action: Check the arguments and try again.
Cause: The user specified an invalid staging table to one of the pack, unpack, or remap stgtab routines, or the user does not have the correct privileges on the staging table
Action: Provide a correct staging table or grant the appropriate privileges
Cause: The user tried to create a staging table when he is missing the CREATE TABLE privilege on the specified schema.
Action: Grant the privilege to the user and retry
Cause: The user tried to create a staging table on a tablespace on which he does not have any space allocated, or it is offline
Action: Allocate space on the tablespace, bring it online, and retry
Cause: The user specified a filter to a pack/unpack function for the SQL Tuning Set that targets no STS in the SYS schema or the staging table, respectively
Action: Provide a different filter after checking the state of the system
Cause: The user specified an invalid mode argument to the capture function.
Action: Provide a mode argument that was defined in the dbmssqlt file
Cause: Either a NULL value was specified for the time_limit or the repeat_interval value, or the repeat_interval value was greater than the time_limit value.
Action: Provide a non-NULL value and ensure that time_limit value is greater than or equal to the repeat_interval value.
Cause: The user specified an invalid filter for the plan when calling the select_sqlset table function.
Action: Adjust the the filter to be one of the following values and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED.
Cause: The user attempted to create a staging table in the sys schema
Action: Create the table in another schema.
Cause: An attempt was made to perform a pack operation on a staging table from a previous version.
Action: Create a staging table in the current version and retry the operation.
Cause: An attempt was made to perform an operation on an empty staging table.
Action: Check the staging table to ensure that it has rows.
Cause: An attempt was made to set a target object for a tuning task when one had already been set.
Action: Create a new task if another target object is needed.
Cause: The user attempted to tune a task-managed SQL Tuning Set belonging to one task within the scope of another task.
Action: Check the SQL Tuning Set and retry the operation.
Cause: The attempted operation was unsupported for the type of the given SQL Tuning Set.
Action: Check the SQL Tuning Set and retry the operation.
Cause: A LOB type was provided in a SQL bind list.
Action: Replace the LOB binds with legal bind types or try another SQL.
Cause: The profile type is not valid.
Action: Check the available profile types.
Cause: The user had an object with the same name as one of the system types. The system types were not initialized properly.
Action: Remove the conflicting object and rerun migration.