Oracle 12c R2 Error Codes and Solution Suggestions from ORA-19200 to ORA-19400

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

ORA-19201: Datatype not supported

Cause: The particular datatype is not supported in the XMLGEN operator

Action: Specify only supported datatypes as arguments to the XMLGEN operator

ORA-19202: Error occurred in XML processingstring

Cause: An error occurred when processing the XML function

Action: Check the given error message and fix the appropriate problem

ORA-19203: Error occurred in DBMS_XMLGEN processingstring

Cause: An error occurred when processing the DBMS_XMLGEN functions

Action: Check the given error message and fix the appropriate problem

ORA-19204: Non-scalar value ‘string‘ is marked as XML attribute

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.

ORA-19205: Attribute ‘string‘ qualifies a non-scalar value in the select list

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.

ORA-19206: Invalid value for query or REF CURSOR parameter

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.

ORA-19207: scalar parameter string of XMLELEMENT cannot have an alias.

Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.

Action: Remove the AS clause of the scalar element.

ORA-19208: parameter string of function string must be aliased

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.

ORA-19209: invalid or unsupported formatting argument

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

ORA-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML()

Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.

Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns

ORA-19213: error occurred in XML processing at linesstring

Cause: An error occurred when processing the given lines in an XML function.

Action: Check the given error message and fix the appropriate problem.

ORA-19221: XPST0001 – XQuery static context component string not initialized

Cause: An unitialized static context component was encountered during the static analysis of the expression.

Action: initialize the given static context.

ORA-19222: XPDY0002 – XQuery dynamic context component string not initialized

Cause: An unitialized dynamic context component was encountered during the evaluation of the expression.

Action: Initialize the particular dynamic context component.

ORA-19223: XPST0003 – syntax error in XQuery expression

Cause: The given XQuery expression contains syntax errors.

Action: Fix the syntax error in the XQuery expression.

ORA-19224: XPTY0004 – XQuery static type mismatch: expected – string got – string

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.

ORA-19225: XPST0005 – XQuery static type error: expected non empty type got empty sequence

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.

ORA-19226: XPTY0006 – XQuery dynamic type mismatch: expected string got string

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.

ORA-19228: XPST0008 – undeclared identifier: prefix ‘string‘ local-name ‘string‘

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.

ORA-19229: XQST0009 – schema import not supported

Cause: A schema import was encountered in the query.

Action: remove the schema import.

ORA-19230: XPST0010 – unsupported axis string

Cause: An unsupported axis was encountered in the given expression.

Action: Remove the unsupported axis from the expression.

ORA-19231: XPST0011 –

ORA-19232: XQST0012 – imported schemas violate validity rules

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.

ORA-19233: XQST0013 – invalid pragma

Cause: A pragma was specified whose contents are invalid.

Action: Specify the pragma with the correct contents.

ORA-19234: XQST0014 – invalid or unsupported must-understand extension

Cause: The must-understand extension specified was either invalid or unsupported.

Action: remove the unsupported must-understand extension or fix the error.

ORA-19235: XQST0015 – unsupported must-understand extension

Cause: The XQuery flagger was enabled and the query contained a must-understand extension.

Action: remove the unsupported must-understand extension.

ORA-19236: XQST0016 – module declaration or import not supported

Cause: The given query had a module declaration or module import.

Action: Remove the import module or module declaration.

ORA-19237: XPST0017 – unable to resolve call to function – string:string

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.

ORA-19240: XPTY0020 – context item must be node in an axis expression

Cause: The context item that was used in the axis epression is not a node.

Action: Change the context item to be a node.

ORA-19241: XPDY0021 – cast to type string failed

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.

ORA-19242: XQST0022 – namespace declaration attribute must be a literal

Cause: The namespace declaration attribute was not a literal string.

Action: Fix the namespace declaration to be a literal string.

ORA-19243: XQTY0023 – invalid document node content in element constructor

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.

ORA-19244: XQTY0024 – invalid attribute node in element constructor

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.

ORA-19245: XQDY0025 – duplicate attribute name string

Cause: The content sequence of the element constructor contained more than one attribute that had the same name.

Action: Remove the duplicate attributes.

ORA-19246: validation failed – element string not found in in-scope element declarations

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.

ORA-19247: XQDY0027 – validation error

Cause: An error was encountered during the validation of the expression.

Action: Fix the validation error.

ORA-19248: XQTY0028 – invalid node in document constructor

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.

ORA-19249: XQDY0029 – value does not match facet of the target type

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.

ORA-19250: XQTY0030 – too many values to validate expression

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.

ORA-19251: XQST0031 – unsupported query version

Cause: The query version specified in the prolog was not supported.

Action: Supply the version of the query that is supported.

ORA-19252: XQST0032 – too many declarations for base URI

Cause: The query prolog contained multiple declarations for the base URI.

Action: Remove the duplicate definitions for the base URI.

ORA-19253: XQST0033 – too many declarations for namespace prefix string

Cause: The query prolog contained multiple declarations for the same namespace prefix.

Action: Remove the duplicate definitions for the namespace prefix.

ORA-19254: XQST0034 – too many declarations for function string

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.

ORA-19255: XQST0035 – too many declarations of string in imported schemas

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.

ORA-19256: XQST0036 – missing type definitions in imported module

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.

ORA-19257: XQST0037 – function or variable string in module already defined

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.

ORA-19258: XQST0038 – unsupported or duplicate default collation specified

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.

ORA-19259: XQST0039 – duplicate parameter name string in function declaration

Cause: The function declaration contained more than one parameter with the same name.

Action: Fix the function declaration to remove the duplicate parameters.

ORA-19260: XQST0040 – invalid namespace node in element constructor

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.

ORA-19261: XQDY0041 – non empty URI in QName

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.

ORA-19262: XQST0042 – namespace constructor not inside an element constructor

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.

ORA-19263: XQST0043 – duplicate namespace prefix string

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.

ORA-19264: XQDY0044 – invalid namespace in attribute constructors

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.

ORA-19265: XQST0045 – invalid or unknown prefix string in function declaration

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.

ORA-19266: XQST0046 – invalid URI

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.

ORA-19267: module string not found

Cause: The module with the given target URI could not be found.

Action: Fix the prolog to import only available modules.

ORA-19268: XQST0048 – namespace string does not match target namespace string

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.

ORA-19269: XQST0049 – variable string defined multiple times

Cause: The module defined or imported the same variable multiple times.

Action: Fix the import or the module definition to remove duplicate definitions.

ORA-19270: XPDY0050 – treat failed – expected string got string

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.

ORA-19271: XPST0051 – invalid atomic type definition

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.

ORA-19272: XQDY0052 – invalid atomic value in attribute or element constructor

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.

ORA-19273: XQST0053 – empty string in namespace declaration

Cause: An empty string was used in a namespace declaration.

Action: Fix the namespace declaration to have a non-empty string.

ORA-19274: XQST0054 – variable initialization failed due to circularity

Cause: A circular definition was encountered when the variable was initialized.

Action: Remove the circularity in the initialization.

ORA-19275: XQST0055 – schema path string not found in list of in-scope schema definitions

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.

ORA-19276: XPST0005 – XPath step specifies an invalid element/attribute name: (string)

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.

ORA-19277: XPST0005 – XPath step specifies an item type matching no node: (string)

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.

ORA-19278: Invalid value: (string) for type: (string)

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.

ORA-19280: XQuery dynamic type mismatch: expected atomic value – got node

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.

ORA-19282: XQST0068 – It is a static error if a Prolog contains more than one xmlspace declaration

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.

ORA-19284: Encoding specification in version declaration not supported

Cause: The query contained an encoding specification.

Action: Remove the encoding specification.

ORA-19285: FODC0002 – error retrieving resource

Cause: The URI provided could not be resolved to a valid resource.

Action: Provide a valid URI for a resource.

ORA-19286: XPST0017 – unable to resolve call to function – string

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-19287: XPST0017 – invalid number of arguments to function – string:string

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-19288: XPST0017 – invalid number of arguments to function – string

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-19289: XQST0034 – function string:string declared or defined multiple times

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.

ORA-19290: XQST0069 – more than one empty order declaration declared in the prolog

Cause: A prolog had more than one empty order declaration.

Action: Fix the prolog to have just one empty order declaration.

ORA-19291: XPST0081 – specified QName cannot be expanded into a namespace URI

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.

ORA-19300: Error occurred in uri processingstring

Cause: An error occurred when processing the URL

Action: Check the given error message and fix the appropriate problem

ORA-19320: Host name not specified in HTTP URL

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

ORA-19321: Could not open HTTP connection to host (string): port (string)

Cause: A HTTP connection could not be opened to the host

Action: Specify a valid host name and port to connect to

ORA-19322: An error occurred while reading from host (string): port (string)

Cause: An error occurred while reading from the HTTP host

Action: Specify a valid host name and port to read from

ORA-19323: Invalid url string

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.

ORA-19331: Last argument to CREATE_DBURI operator must be a column

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.

ORA-19332: Invalid column in the CREATE_DBURI operator

Cause: The argument to the CREATE_DBURI operator can only be a column.

Action: Specify a valid column name for the operator

ORA-19333: Invalid flags for the CREATE_DBURI operator

Cause: The flags argument given to the DBURI operator is invalid

Action: Specify a valid flag value (TEXT) for the DBURI operator

ORA-19334: Invalid column specification for CREATE_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.

ORA-19335: Invalid format type object

Cause: An invalid format type object was specified for the XML function

Action: Specify a valid format type object

ORA-19336: Missing XML root element

Cause: The XML being generated does not have an enclosing root element.

Action: The XML generated must have a root element

ORA-19361: ONLINE option not allowed with this type of index

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.

ORA-19371: invalid update 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.

ORA-19372: invalid update condition

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.

ORA-19373: invalid staging table or tablespace

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.

ORA-19374: invalid staging table

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

ORA-19375: no CREATE TABLE privilege on schema “string“

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

ORA-19376: no privileges on tablespace provided or tablespace is offline

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

ORA-19377: no “SQL Tuning Set” with name like “string” exists for owner like “string“

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

ORA-19378: invalid mode

Cause: The user specified an invalid mode argument to the capture function.

Action: Provide a mode argument that was defined in the dbmssqlt file

ORA-19379: invalid time_limit or repeat_interval

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.

ORA-19380: invalid plan filter

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.

ORA-19381: cannot create staging table in SYS schema

Cause: The user attempted to create a staging table in the sys schema

Action: Create the table in another schema.

ORA-19384: cannot pack into staging table from previous version

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.

ORA-19385: staging table is empty

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.

ORA-19386: target object already exists for tuning task “string“

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.

ORA-19387: “SQL Tuning Set” “string” belongs to another tuning task

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.

ORA-19388: operation not supported for “SQL Tuning Set” type

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.

ORA-19389: LOB types are not supported for SQL binds

Cause: A LOB type was provided in a SQL bind list.

Action: Replace the LOB binds with legal bind types or try another SQL.

ORA-19390: The profile type is not valid

Cause: The profile type is not valid.

Action: Check the available profile types.

ORA-19400: System type conflict with object SYS.string

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.