Oracle 12c R2 Error Codes and Solution Suggestions from ORA-19000 to ORA-19200
- ORA-19000: missing RELATIONAL keyword
Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.
Action: Supply the RELATIONAL keyword in the storage clause
Cause: An invalid storage option was specified for the XMLType.
Action: Supply a valid storage option.
Cause: A XML schema URL must be specified in the storage option.
Action: Specify a URL for the XMLSchema.
Cause: A root element in the XMLSchema must be specified if the XML schema is given.
Action: Specify a root element in the XML schema.
Cause: A duplicate storage option for the XMLType column was specified
Action: Specify a single storage option for an XMLType column
Cause: A duplicate storage option for the XMLType column was specified
Action: Specify a single storage option for an XMLType column
Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option
Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column
Cause: The given XML document conformed to a different schema than expected.
Action: Insert/Update only the XML documents that conform to that particular schema.
Cause: An invalid version of the XMLType was found.
Action: This is possibly due to data corruption or an internal error or running an older client against a newer version of the database. Ensure that the version of the client can understand the XMLType in the database.
Cause: The XMLSchema keyword is missing
Action: Specify the XMLSchema URL and element name.
Cause: XML fragments got from extractNode cannot be inserted into the database.
Action: Convert the fragment into a proper XML document before insertion.
Cause: The string result asked for is too big to return back
Action: Get the result as a lob instead
Cause: A conversion to a datatype was requested which cannot be performed
Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.
Cause: An attempt was made to create a VARRAY column which contains a XMLType
Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead
Cause: An invalid XML identifer was detected during XML generation
Action: Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification
Cause: Attributes specified using the “@” identifier can only occur before any other element definition when creating XML
Action: Change the order of the types so that the attributes occur in the begining
Cause: Attribute values can only be simple scalar values
Action: Use only simple datatypes for attribute values
Cause: A tag name was found to have an invalid XML character during XML generation.
Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.
Cause: The value of context passed to GETXML was invalid.
Action: Rewrite the query so that the value of context passed to GETXML is valid.
Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table
Action: You can only dereference the attributes of a base table XMLType column
Cause: The XMLOptimizationCheck variable was enabled and an unrewritten XML construct was detected. This prevents execution of the XML construct.
Action: Ensure that the XML construct is being optimized. See the trace file for further information. Disable the XMLOptimizationCheck variable if you want the unoptimized XML operation to be executed.
Cause: The first argument passed to the update value operator was not an XMLTYPE.
Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.
Cause: The value of context passed to GETXML was invalid.
Action: Rewrite the query so that the value of context passed to GETXML is valid.
Cause: Given XPath points to more than one node.
Action: Rewrite the query so that exactly one node is returned.
Cause: Given XPath does not point to a leaf node.
Action: Rewrite the query so that a leaf node is returned.
Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.
Action: Pass an object of the correct type to toObject().
Cause: The passed in XMLType could not be convert to the required type
Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types.
Cause: The method can be invoked on only schema based xmltype objects.
Action: Don’t invoke the method for non schema based xmltype objects.
Cause: The passed in XML tag does not match any in the object type
Action: Pass a valid canonical XML that can map to the given object type
Cause: When converting XML to object, a wrong tag name was present
Action: Pass a valid canonical XML that can map to the given object type
Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the ‘schema’ parameter.
Action: Change the schema parameter to match the schema specified in the XML document.
Cause: The object type contained a type that is not supported for schema generation.
Action: Use a different type or do not generate a schema.
Cause: The query did not have a number select item followed by an XMLType select item only.
Action: Ensure that the result set of the query used in the newContextFromHierarchy() function has only two selected items: the first item must be number type and the second item must be XMLType.
Cause: The result set of the query used in the newContextFromHierarchy() function did not have the same property as the result set generated by a CONNECT BY query.
Action: Ensure that the query used in the newContextFromHierarchy() function is a CONNECT BY query or that the query returns a result set having the same property as the result set generated by a CONNECT BY query.
Cause: The select item of the query in the newContextFromHierarchy() function was an XML fragment.
Action: Ensure that the select item of the query in the newContextFromHierarchy() function is not an XML fragment.
Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy().
Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy().
Cause: The keyword is reserved for future use as a builtin function.
Action: Change the name mentioned above to a different one.
Cause: The given XML document had a different root element than expected.
Action: Insert/Update only the XML documents that conform to that particular schema and element.
Cause: The given comment string expression has two consecutive ‘-‘s.
Action: Modify comment string to eliminate one or both of the consevutive ‘-‘s.
Cause: The given enclosing tag matched ‘xml’ in some case combination
Action: Modify the enclosing tag so that it is not xml in any case combination.
Cause: An XMLROOT function has an operand that is also an XMLROOT function.
Action: Modify the query so that there are no multiply nested XMLROOT functions.
Cause: An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small.
Action: Modify the query so that the character length specified is larger.
Cause: An XMLSerialize function was called with an invalid value for the caracter set id.
Action: Modify the query so that the character set id is valid.
- ORA-19046: Out-of-line table cannot be shared by two top-level tables (table ‘string.string‘ and the current table being created).
Cause: An attempt was made to share an out-of-line table between two top-level tables.
Action: Use the existing top-level XML table.
Cause: An attempt was made to combine storage specification for a particular VARRAY with STORE ALL VARRAYS clause.
Action: Either specify storage for individual VARRAYs or use the STORE ALL VARRAYS clause.
Cause: An attempt was made to store all varrays as tables or LOBs in tableProps.
Action: Do not specify varray store as tables or LOBs in tableProps.
Cause: Error while trying to insert into an XMLType table using fast path insert.
Action: Set event 19049 to disable fast path insert and try again.
Cause: The option, DISABLE XML EXCHANGE, was specified in a CREATE TABLE statement.
Action: Do not specify DISABLE XML EXCHANGE in a CREATE TABLE statement.
Cause: The operation failed due to an internal error.
Action: This is an internal error. Contact Oracle Support Services.
Cause: An attempt was made to enable XML exchange for a binary XML column or table with a conflicting binary XML column or table.
Action: Use the XML exchange option only if at least one of the two involved tables is empty.
Cause: An attempt was made to disable XML exchange on a table that does not have XML exchange enabled.
Action: Use the disable XML exchange option only if the table already has XML exchange enabled.
Cause: An attempt was made to perform a disallowed operation on a token set object for binary XML support.
Action: Do not perform the attempted operation on an XML token set object.
Cause: An attempt was made to perform some Granular Token Set related operations on a non-binary XML table or on an older binary XML table.
Action: Do not perform the attempted operation unless tables support Granular Token Set options.
Cause: An attempt was made to enable XML exchange on a table that had XML exchange already enabled.
Action: Use the disable XML exchange option only if the table has XML exchange disabled.
Cause: An attempt was made to use granular token tables with schema-based storage.
Action: Use non-schema based storage for granular token tables.
Cause: The tablespace contained an XML token set object that was used by a binary XML table in a different tablespace and dropping it would cause some data to be lost.
Action: Move the XML token set object to a different tablespace.
Cause: The tablespace contained an XML token set object but the metadata could not be read since the XDB default tablespace was offline. By dropping the tablespace, some data may be lost.
Action: Bring XDB default tablespace online.
Cause: The two tables specified in the EXCHANGE had different XML token sets. By exchanging partitions, some data might get corrupted.
Action: Enable XML EXCHANGE between the tables.
Cause: The user default tablespace was full.
Action: Increase the size of the user default tablespace.
Cause: Either the table was in SYSTEM tablespace or it was partitioned and the default tablespace was SYSTEM. Granular token tables are forbidden on SYSTEM tablespace.
Action: Move the table to a different tablespace or change the default tablespace if the table is partitioned.
Cause: An XML exchange was performed with the same table.
Action: Do not enable XML exchange with the same table.
Cause: XML EXCHANGE was not allowed in global temporary tables or external tables.
Action: Do not use a global temporary table or external table.
Cause: The table was not an XMLTable or did not have an XMLType column stored as BINARY XML.
Action: Use an XMLType or XMLTable stored as BINARY XML.
Cause: STORE AS CLOB was not specified with XMLType on the sharded table.
Action: Specify the STORE AS CLOB clause in the query.
Cause: An attempt was made to add or modify a column with an unsupported type for a granular token set enabled table.
Action: Do not use user-defined Abstract Data Types (ADTs) or an ANYDATA column with granular token sets.
Cause: The table was not used with a granular token set.
Action: Use an XMLType stored as BINARY XML with a granular token set.
- ORA-19075: Failed to move the token table indexes. Run dbms_csx_admin.RebuildTokenTablesIndexes before using the table.
Cause: An attempt to move the indexes to the given tablespace failed.
Action: Run dbms_csx_admin.RebuildTokenTablesIndexes.
- ORA-19076: cannot move the XML token set to tablespace where the table owner does not have privileges
Cause: The table owner did not have privileges in the given tablespace.
Action: Use a tablespace where the table owner has privileges.
Cause: The keyword PASSING or RETURNING was missing.
Action: Specify the PASSING or RETURNING keyword.
Cause: The keyword CONTENT was missing.
Action: Specify the CONTENT keyword.
Cause: The string literal containing the XQuery expression was missing.
Action: Specify the XQuery expression as a string literal.
Cause: The keyword VALUE was missing.
Action: Specify the VALUE keyword.
Cause: The XQueryX expression was not assigned the expected attribute.
Action: Specify a valid XQueryX.
Cause: The XQueryX expression did not contain a text node as expected.
Action: Specify a valid XQueryX.
Cause: The XQueryX expression did not contain the node as expected.
Action: Specify a valid XQueryX.
Cause: The given XQuery expression contains an unsupported construct.
Action: Specify a valid XQueryX.
Cause: The keyword WHITESPACE was missing.
Action: Specify the WHITESPACE keyword.
Cause: The keyword RETURNING was missing.
Action: Specify the RETURNING keyword.
Cause: The program specified an XQuery expression that is not supported.
Action: Rewrite the XQuery with a expression that is supported.
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
Cause: The error function was called during evaluation of the XQuery expression.
Action: Check the detailed error message for the possible causes.
Cause: The trace function was called during evaluation of the XQuery expression.
Action: Check the log file for the trace message.
Cause: An error occurred during the parsing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
Cause: More than one context item was specified as input to the XMLQuery function.
Action: Specify a single context item for the XMLQuery function.
Cause: The query prolog contained multiple xmlspace declarations.
Action: Remove the duplicate xmlspace declarations.
Cause: The given predefined namespace was being redefined in a namespace declaration.
Action: Remove the namespace declaration that redefines the predefined namespace prefix.
Cause: More than one default namespace declaration used the given namespace URI.
Action: Remove the duplicate default namespace definition.
Cause: More than one attribute with the same name.
Action: Remove the duplicate attribute definition.
Cause: The program specified an XQuery declaration that is not supported.
Action: Rewrite the XQuery with a declaration that is supported.
Cause: sequence with more than one item was passed into fn:zero-or-one() function
Action: correct input argument to fn:zero-or-one() function
Cause: sequence containing no items was passed into fn:one-or-more() function
Action: correct input argument to fn:one-or-more() function
Cause: sequence containing zero or more than one item was passed into fn:exactly-one() function
Action: correct input argument to fn:exactly-one() function
- ORA-19126: XQuery extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces
Cause: No expression was enclosed in curly braces for the extension expression or the pragma content was not recognized.
Action: Correct inputs to extension expression.
- ORA-19127: XQST0067: XQST0067: A static error is raised if a Prolog contains more than one construction declaration
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19128: XQST0068: A static error is raised if a Prolog contains more than one boundary-space declaration
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19129: XQST0069: A static error is raised if a Prolog contains more than one empty order declaration
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19130: XQST0070: A static error is raised if the predefined namespace prefix xml or xmlns is redeclared by a namespace declaration or namespace declaration attribute
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19131: XQST0071: A static error is raised if the namespace declaration attributes of a direct element constructor do not have distinct names
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19132: XQDY0072: It is a dynamic error if the result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19133: XQST0073: It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 … Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19134: XQDY0074: It is a dynamic error if the value of the name expression in a computed element constructor cannot be converted to an expanded QName (for example, because it contains a namespace prefix not found in statically known namespaces.)
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19135: XQST0075: An implementation that does not support the Validation Feature must raise a static error if it encounters a validate expression
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19136: XQST0076: It is a static error if a collation subclause in an order by clause of a FLWOR expression does not identify a collation that is present in statically known collations
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19137: XQST0079: It is a static error if an extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19138: The target type of a cast or castable expression must be an atomic type that is in the in-scope schema types and is not xs:NOTATION or xs:anyAtomicType, optionally followed by the occurrence indicator “?”; otherwise a static error is raised
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19139: XPST0081: It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19140: XPST0083: It is a static error if the target type of a cast expression or constructor function is xs:QName or a type derived from xs:QName or xs:NOTATION, and the argument of the cast expression or constructor function is not a string literal
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19141: XQDY0084: It is a dynamic error if the element validated by a validate statement does not have a top-level element declaration in the in-scope element declarations, if validation mode is strict
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19143: XQTY0086: It is a type error if the typed value of a copied element or attribute node is namespace-sensitive when construction mode is preserve and copy-namespaces mode is no-preserve
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19145: XQST0087: It is a static error if the encoding specified in a Version Declaration does not conform to the definition of EncName specified in [XML 1.0]
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19146: XQST0088: It is a static error if the literal that specifies the target namespace in a module import or a module declaration is of zero length
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19147: XQST0089: It is a static error if a variable bound in a for clause of a FLWOR expression, and its associated positional variable, do not have distinct names (expanded QNames)
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19148: XQST0090: It is a static error if a character reference does not identify a valid character in the version of XML that is in use
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19149: XQDY0091: An implementation may raise a dynamic error if an xml:id error, as defined in [XML ID], is encountered during construction of an attribute named xml:id
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19150: XQDY0092: An implementation may raise a dynamic error if a constructed attribute named xml:space has a value other than preserve or default
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19151: XQST0093: It is a static error to import a module M1 if there exists a sequence of modules M1 … Mi … M1 such that each module directly depends on the next module in the sequence (informally, if M1 depends on itself through some chain of module dependencies.)
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
Cause: The given XQuery variable does not begin with the ‘$’ sign
Action: Fix the variable name to start with the “$” sign.
Cause: The type of the argument that was passed to the given function was not valid.
Action: Fix the argument to be of a type supported by the given function.
- ORA-19162: XPTY0004 – XQuery type mismatch: invalid argument types ‘string‘, ‘string‘ for function ‘string‘
Cause: The type of the arguments that were passed to the given function was not valid.
Action: Fix the arguments to be of a type appropriate for the given function.
- ORA-19163: XPTY0004 – XQuery type mismatch: argument type mismatch: expected – ‘string‘ got – ‘string‘ for function ‘string‘
Cause: The type of the arguments that were passed to the given function was not valid.
Action: Fix the arguments to be of a type appropriate for the given function.
- ORA-19164: XQST0085 – It is a static error if the namespace URI in a namespace declaration attribute is a zero-length string, and the implementation does not support [XML Names 1.1].
Cause: There was a zero-length URI in namespace declaration.
Action: Fix the namespace declaration.
Cause: There was a zero-length URI in namespace declaration.
Action: Fix the namespace declaration.
Cause: There was a zero-length URI in namespace declaration.
Action: Fix the namespace declaration.
Cause: There was a zero-length URI in namespace declaration.
Action: Fix the namespace declaration.
Cause: There was a zero-length URI in namespace declaration.
Action: Fix the namespace declaration.
Cause: There was a zero-length URI in namespace declaration.
Action: Fix the 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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
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 during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19192: XQST0047: It is a static error if multiple module imports in the same Prolog 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-19193: XQST0045: It is a static error if the function name in a function declaration is in one of the following namespaces: http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://www.w3.org/2005/04/xpath-datatypes
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
- ORA-19194: XQDY0026: It is a dynamic error if the result of the content expression of a computed processing instruction constructor contains the string “?>”
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
Cause: An invalid policy was specified in ora:contains.
Action: Rename the policy name, policy schema name, or do not specify any policy to pick up default policy.
Cause: The table or view specified in fn:collection was of XMLType.
Action: XMLType table or view is not allowed in the form of fn:collection(‘oradb:/schema/table/ROW/column’). It has to be a relational table or view.
Cause: The column to be retrieved was not found or was not of XMLType.
Action: The column to be retrieved in the form of fn:collection(‘oradb:/schema/table/ROW/column’) or fn:collection(‘oradb:/schema/table/ROW[predicate]/column’) has to be of XMLType.
- ORA-19198: Column not found or invalid column specified in the predicate with this form of fn:collection
Cause: The column specified in the predicate was not found or was not allowed.
Action: The column specified in the predicate in the form of fn:collection(‘oradb:/schema/table/ROW[predicate]/column’) cannot be of XMLType.
Cause: An XQuery expression contained too many levels of nesting parentheses.
Action: Reduce the level of nesting parentheses.
Cause: All input arguments must be valid columns
Action: Specify a valid list of columns