SQL10000 - SQL19999

SQL10002N The password supplied is too long.

Explanation

The length of the password is expected to be 18 characters or less. However, if the password is to be verified for an APPC conversation, it must be 8 characters or less.

User response

Ensure that the password is not longer than the limit allowed.

sqlcode: -10002

sqlstate: 28000

SQL10003C There are not enough system resources to process the request. The request cannot be processed.

Explanation

The database manager could not process the request due to insufficient system resources. The resources that can cause this error include:

The amount of memory in the system.
The number of message queue identifiers available in the system.
The number of connections at the cluster caching facility (CF).

User response

Stop the application. Possible solutions include:

Remove background processes.
Terminate other applications using the resources listed in this message's Explanation.
If you are using Remote Data Services, increase the Remote Data Services heap size (rsheapsz) in the server and client configuration because at least one block is used per application.
NOTE: This is applicable only for releases of DB2 prior to Version 2.
Decrease the values of the configuration parameters that define allocation of memory, including ASLHEAPSZ if UDFs are involved in the failing statement.
Avoid accessing large files or use non-buffered I/O. To use non-buffered I/O, set the DB2 registry variable DB2NTNOCACHE to YES.
Deactivate another connected database before activating this database.

sqlcode: -10003

sqlstate: 57011

SQL10004C An I/O error occurred while accessing the database directory.

Explanation

Either the system database directory or the local database directory cannot be accessed. This error may occur not only when the system is cataloging or uncataloging a database but also when the system is accessing a database that is cataloged in the directory.

The command cannot be processed.

User response

Run LIST DB DIRECTORY ON <path> (where path is where the databases were created).
If you are successfully able to list the databases with the above command, then only the instance level directory is having problems.
- Move all the files under <inst_home>/sqllib/sqldbdir to another location (note: cataloging information will be lost).
- Recatalog the databases on the same path. Test by running LIST DB DIRECTORY.
If you were unable to list databases with the LIST DB DIRECTORY ON <path> command, then the local database directories are the problem. Restore the databases that were cataloged there from backup versions and catalog them.

sqlcode: -10004

sqlstate: 58031

SQL10005N The mode parameter `parameter` in the CONNECT TO statement is not valid. It must be SHARE for shared access, EXCLUSIVE for exclusive use or EXCLUSIVE MODE ON SINGLE NODE for exclusive use on single node. For DB2 Connect connections, only SHARE mode is supported. EXCLUSIVE MODE ON SINGLE NODE is only supported in MPP configuration.

Explanation

The mode parameter of the CONNECT TO statement must be SHARE for shared, EXCLUSIVE for exclusive use or EXCLUSIVE MODE ON SINGLE NODE for exclusive use on single node. If connecting to a database usingDB2 Connect , only shared access is allowed. EXCLUSIVE MODE ON SINGLE NODE is only supported in MPP configuration.

The command cannot be processed.

User response

Resubmit the command with a valid mode parameter.

SQL10007N Message `msgno` could not be retrieved. Reason code: `code`.

Explanation

The requested message <msgno> could not be retrieved from the message file. Reason code <code> is one of the following:

The environment variable DB2INSTANCE is either not set, or is set to an invalid instance. Correct it and try again.
The message file was found, but the file could not be opened because of permissions. Check the file permissions of the files under the message directory.
The message file could not be found. Either the file does not exist, or the directory the message file should be in does not exist. Check that either a default directory or a directory with the same name as the 'LANG' environment variable exists under the message directory.
The requested message does not exist in the message file. Either the message file is outdated, or it is the wrong one.
Either DB2CODEPAGE is set to a code page which the database does not support, or the client's locale is not supported by the database.
An unexpected system error occurred. Try execution again. If problem persists, contact your IBM representative.
Not enough memory. An attempt to get private memory failed. Try again.

User response

Reissue the command after verifying the following:

Ensure that the DB2INSTANCE environment variable is set to the correct literal string for the username attempting this command.
Ensure that correct home directory is specified for the username attempting this command (i.e., in the /etc/passwd file).
Ensure that the LANG environment variable is set to the correct value for the installed language, or is set to 'C', on the username attempting this command.
Even if the message file is outdated, you can still find up-to-date information about the message in the database server documentation.

If all of these things have been verified and the error still occurs, reinstall DB2.

SQL10009N The codeset `codeset` and/or territory `territory` that has been specified is not valid.

Explanation

This version of the database manager does not support the active codeset or territory or both, as specified by the Create Database command.

The command cannot be processed.

User response

Refer to the Create Database command in the Administration Guide for details of valid codeset and territory pairs supported by the database manager.

SQL10010N The specified library, `name`, was loaded, but the function `function` could not be executed.

Explanation

The function routine within the library cannot be found.

The command cannot be processed.

User response

Ensure the library is built correctly. Make sure that the function routine is exported through the 'export file'.
You might have to reinstall the database manager instance or the database manager product.

Federated system users: If the function name is "UnfencedWrapper_Hook" or "FencedWrapper_Hook", then verify that you specified the correct library name on the CREATE WRAPPER statement. Specify the library name that does not end in "U" or "F". For example, to create the DRDA wrapper on AIX, specify library 'libdb2drda.a', but not 'libdb2drdaU.a' or 'libdb2drdaF.a.'. If the wrapper library is supplied by a vendor, then contact the vendor to get an updated version of the wrapper library.

sqlcode: -10010

sqlstate: 42724

SQL10011N An interrupt was received while loading the specified library `name`.

Explanation

When loading the library, the command was interrupted, perhaps by the interrupt key (usually Ctrl+Break or Ctrl+C).

Ensure that the library or program name is specified correctly.

sqlcode: -10014

sqlstate: 42724

SQL10015N There are not enough system resources to load the specified library `name`.

Explanation

There is not enough memory to load the library module.

User response

Stop the application. Possible solutions are:

Remove background processes.
Decrease the values of the configuration parameters that define the allocation of memory.
Install more memory.

sqlcode: -10015

sqlstate: 42724

SQL10017N The SQL CONNECT RESET statement is not allowed in a this context.

Explanation

The remote procedure contains an SQL CONNECT RESET statement.

User response

Remove the SQL CONNECT RESET statement and retry the remote procedure.

sqlcode: -10017

sqlstate: 38003

SQL10018N The disk is full. Processing was ended.

Explanation

The disk is full. During the export to a PC/IXF file, either the PC/IXF data file is on a fixed disk, or the PC/IXF data file and the database are on the same file system , or the PC/IXF data file and the message file are on the same file system.

The EXPORT utility stops processing. The exported data is not complete.

User response

Provide more space on the disk or specify that the data file be located on a different file system than the database or the message file and resubmit the command.

SQL10019N The database cannot be accessed in the specified path.

Explanation

The database cannot be accessed for one of the following reasons:

The path does not contain a database image.
Permissions on the path are incorrect.

User response

Ensure that the path references a valid database and that the permissions are correct.

sqlcode: -10019

sqlstate: 58031

SQL10021N The file permissions do not allow write access to the database.

Explanation

A write operation was attempted to a database residing on a file system which does not allow write access.

The statement cannot be processed.

User response

Verify that the file permissions for the file system on which the database resides allow write access.

SQL16000N An XQuery expression cannot be processed because the `context-component` component of the static context has not been assigned. Error QName=err:XPST0001.

Explanation

Static analysis of an expression relies on a component of the static context, context-component, that has not been assigned a value.

The XQuery expression cannot be processed.

User response

Assign a value to the context-component.

sqlcode: -16000

sqlstate: 10501

SQL16001N An XQuery expression starting with token `token` cannot be processed because the focus component of the dynamic context has not been assigned. Error QName=err:XPDY0002.

Explanation

Evaluation of the expression starting with token token requires that the focus component of the dynamic context be assigned. The token is being considered as the beginning of a path expression which does not have an associated context item or context sequence. This might be the result of not defining or retrieving a sequence as a context for the path expression. Other common causes for this error:

The value in token token was intended to be a literal string but delimiting quotations characters are missing.
The value in token token was intended to be a function but the opening and closing parentheses are missing.

The XQuery expression cannot be processed.

User response

Investigate occurrences of token token in the XQuery expression. Correct the XQuery expression around an occurrence of this token to assign a focus component or make other changes so that the token is no longer expecting an assigned focus component.

sqlcode: -16001

sqlstate: 10501

SQL16002N An XQuery expression has an unexpected token `token` following `text`. Expected tokens may include: `token-list`. Error QName=err:XPST0003.

Explanation

The token that follows text is not valid where it occurs in the expression. The token-list includes one or more possible tokens that are valid replacements for the unexpected token.

The XQuery expression cannot be processed.

User response

Use the correct syntax for the expression.

sqlcode: -16002

sqlstate: 10505

SQL16003N An expression of data type `value-type` cannot be used when the data type `expected-type` is expected in the context. Error QName=err:XPTY0004.

Explanation

An XQuery expression includes a value of the type value-type in a context where the expected type is expected-type.

The XQuery expression cannot be processed.

The following rules apply to types that are used in expressions:

The operands of a range expression must each be convertible to a single integer.
The operands of a union, intersect, or except operator must contain items that are nodes only.
The operands of an arithmetic expression cannot be sequences of length greater than one.
The operands of a node comparison must be either single nodes or empty sequences.
In general, atomization must not result in more than one atomic value.
When atomization is applied to a comparison expression, the result of atomization must be single atomic values, where the value of the first atomized operand is comparable with the value of the second atomized operand.
When atomization is applied to a name expression, the result of atomization must be a single atomic value of type xs:QName, xs:string, or xdt:untypedAtomic.
The content sequence of a document node constructor cannot contain attribute nodes.
When (item(), item()+) appears as the value-type, a sequence of 2 or more items is being used in an expression where a single item is expected.
The orderspec values in an order by clause must be convertible to a common type.
A value that is bound to a variable must match the declared type (if a type is declared).
The cast of a value of source type value-type to target type expected-type must be a supported cast. In cases where SQL processing invokes XQuery to perform a cast from an XML data type to an SQL data type other than XML, an XQuery cast is performed with a temporary derived XML schema type that is generated using a name based on the SQL data type and associated size restrictions. For example, the target-type token value is "VARCHAR_50" for an XMLCAST to VARCHAR(50) and "DECIMAL_9_2" for an XMLCAST to DECIMAL(9,2).

User response

Specify a value of the correct type.

sqlcode: -16003

sqlstate: 10507

SQL16004N The fn:data function cannot be applied explicitly or implicitly to an XQuery node for which the type annotation denotes a complex type with element-only content. Error QName=err:FOTY0012.

Explanation

An XQuery expression attempted to apply the fn:data function to an XQuery node either explicitly or implicitly as a result of atomization. However, because the type annotation of the node denotes a complex type with element-only content, the typed value of the node is undefined. The fn:data function raises a type error when applied to a node whose type is undefined.

XQuery expressions use atomization to convert items into atomic values in expressions such as: arithmetic expressions, comparison expressions, function calls with arguments whose expected types are atomic, cast expressions, constructor expressions for various kinds of nodes, order by clauses in FLWOR expressions, type constructor functions, source expressions in replace value of expressions, and new name expressions in rename expressions. Processing any of these these expressions will implicitly invoke the fn:data function which could result in this error.

The XQuery expression cannot be processed.

User response

Try one of the following actions:

Replace the call to the fn:data function with a function call that is appropriate for complex types with element only content.
Call the fn:data function on a node that is annotated as a simple type, or as a complex type that contains mixed content.
If the context of an XQuery expression requires a sequence of atomic values, ensure that the sequence consists only of items that can be atomized.

sqlcode: -16004

sqlstate: 10507

SQL16005N An XQuery expression references an element name, attribute name, type name, function name, namespace prefix, or variable name `variable-name` that is not defined within the static context. Error QName=err:XPST0008.

Explanation

During the static analysis phase, the static context is used to resolve element names, attribute names, type names, function names, namespace prefixes, and variable names. If an expression uses an undefined-name that is not found in the static context, a static error is raised.

The XQuery expression cannot be processed.

User response

User response

Try one of the following actions:

Verify that you are passing the correct number of parameters to the function call.
If the function call uses a function name with no prefix, verify that the local name of the function matches a function that is in the default function namespace, or use the correct prefix.

sqlcode: -16014

sqlstate: 10502

SQL16015N An element constructor contains an attribute node named "`node-name`" that follows an XQuery node that is not an attribute node. Error QName=err:`error-name`.

Explanation

The sequence used for constructing element content contains an attribute node named node-name that follows an XQuery node that is not an attribute node. The particular context where this occurs is based on the error QName.

err:XQTY0024: The content sequence of an element constructor contains an attribute node named node-name that follows an XQuery node that is not an attribute node. Attribute nodes can only occur at the beginning of the content sequence.
err:XUTY0004: The content of an insertion sequence based on the source expression of an insert expression contains an attribute node named node-name that follows an XQuery node that is not an attribute node. Attribute nodes can only occur at the beginning of the insertion sequence.

The XQuery expression cannot be processed.

User response

Perform one of the following actions:

If type-name is the target data type of a cast expression, change the operand to a string literal or specify a different target data type.
If type-name is used as the name of a constructor function, change the argument to a string literal or use a different constructor function.

sqlcode: -16023

sqlstate: 10503

SQL16024N The prefix `prefix-name` cannot be redeclared or cannot be bound to the URI http://www.w3.org/XML/1998/namespace. Error QName=err:XQST0070.

Explanation

A namespace declaration or a namespace declaration attribute cannot redeclare the predefined namespace prefixes "xml" or "xmlns".

If the namespace prefix prefix-name is one of these predefined namespace prefixes, it is being used in a namespace declaration or namespace declaration attribute, which is not allowed.
If the prefix name is not "xml" or "xmlns", the declaration of the prefix prefix-name specifies the namespace URI associated with the prefix "xml", which can only be bound to the namespace prefix "xml".

The XQuery expression cannot be processed.

User response

Perform one of the following actions:

If the prefix name is "xml" or "xmlns", change the prefix name to a different namespace prefix.
If the prefix name is not "xml" or "xmlns", change the namespace URI specified in the declaration of the namespace prefix.
Remove any namespace declaration or namespace declaration attribute that specifies the prefix prefix-name.

If the target data type is xs:NOTATION, xs:anySimpleType, or xdt:anyAtomicType, specify a different target data type or remove the cast or castable expression.
If the target data type is not defined by the in-scope XML types, specify a data type that is in-scope or change the XML schema to include the data type.
If the target data type is not atomic, specify a different target data type or remove the cast or castable expression.

sqlcode: -16033

sqlstate: 10507

Explanation

The function function name requires that the argument specify an SQL result table with a single column of data type XML. For db2-fn:xmlcolumn this is done by specifying a column within a table or view with the SQL data type XML. For db2-fn:sqlquery, the SQL query provided as an argument must specify a single column in the outer fullselect that has an SQL data type of XML.

User response

Correct the argument of function function name to return a single column with SQL data type XML.

sqlcode: -16040

sqlstate: 10608

SQL16041N An implicit or explicit invocation of the fn:boolean function in the XQuery expression could not compute the effective boolean value of the sequence. Error QName=err:FORG0006.

Explanation

This error occurs if the effective boolean value of the sequence operand of an explicit or implicit invocation of the fn:boolean function cannot be computed for the sequence operand. The effective boolean value can be computed only if the sequence operand is one of the following sequences:

An empty sequence
A sequence where the value of the first item is a node
A singleton sequence with a value of type xs:string, xdt:untypedAtomic, or a type derived from one of these types
A singleton sequence with a value of any numeric type or derived from any numeric type

The XQuery expression cannot be processed.

User response

Determine the possible expressions within the XQuery expression where an effective boolean value is calculated either implicitly or explicitly. An implicit invocation of the fn:boolean function can occur when processing the following types of expressions:

Logical expressions (and, or)
An fn:not function invocation
The where clause of a FLWOR expression
Certain types of predicates, such as a[b]
Conditional expressions, such as if
Quantified expressions (some, every)

Ensure that the sequence operand of each effective boolean value calculation would have a valid sequence operand (one described in the explanation).

sqlcode: -16041

sqlstate: 10608

SQL16042N The name expression in a computed processing instruction constructor cannot be equal to "XML" in any combination of upper and lower case characters. Error QName=err:XQDY0064.

Explanation

The NCName that results from the name expression of a computed processing instruction constructor cannot be equal to the string of characters XML in any combination of upper or lower case characters.

The XQuery expression cannot be processed.

User response

Modify the name expression to result in an NCName that is not equal to XML.

sqlcode: -16042

sqlstate: 10508

Explanation

Declaring more than one declaration-type declaration in a prolog results in an error. The declaration-type declaration type is one of the following declarations that can be specified in an XQuery prolog:

copy-namespaces
ordering
default element namespace
default function namespace
construction
boundary-space
default empty order

This error could be returned for a variety of error QNames such as err:XQST0055, err:XQST0065, err:XQST0066, err:XQST0067, err:XQST0068, and err:XQST0069.

The XQuery expression cannot be processed.

User response

Remove the extra declaration of type declaration-type from the prolog.

sqlcode: -16048

sqlstate: 10502

SQL16049N The lexical value `value` is not valid for the `date-type` data type in the function or cast. Error QName=err:FOCA0002.

Explanation

A cast expression or function call includes a value that does not have the correct lexical form for the type-name data type.

The XQuery expression cannot be processed.

User response

Try one of the following actions:

If the error results from a function invocation, verify that the string parameters used for QNames or local names have the correct lexical form.
If the error results from a cast expression, verify that the source value is not one of the special float or double values NaN, INF, or -INF.

sqlcode: -16049

sqlstate: 10602

SQL16051N The value "`value`" of data type "`source-type`" is out of range for an implicit or explicit cast to target data type "`target-type`". Error QName=err:`error-name`.

SQL16061N The value `value` cannot be constructed as, or cast (using an implicit or explicit cast) to the data type `data-type`. Error QName=err:FORG0001.

Explanation

An XQuery expression attempted to use the value value as a data-type value but the value is not valid for the data type. The following situations might cause this error:

A value was passed to a constructor function that required a value of data type data-type.
A value was explicitly passed to a cast function or specified in a cast expression with a target data type of datatype.
An expression that included value implicitly cast the value to the target data type of data-type. Many XQuery expressions use implicit casting to process the expressions. For example, implicit casting is used in general comparisons of numeric values that require the values to be of data type xs:double.
In cases where SQL processing invokes XQuery to perform a cast from an XML value value to an SQL data type other than XML, an XQuery cast is performed with a temporary derived XML schema type that is generated using a name based on the SQL data type and associated size restrictions. For example, the data-type token value is "VARCHAR_50" for an XMLCAST to VARCHAR(50) and "DECIMAL_9_2" for an XMLCAST to DECIMAL(9,2).

The XQuery expression cannot be processed.

User response

Try one of the following actions:

Use a value in the constructor or cast expression that is valid for the data type data-type.
If the error occurs in an expression that casts from one primitive type to another, verify that casting from the source type to the target type is supported. If the cast is not supported, either remove the expression or cast the value to a different data type.
Check for expressions that would result in implicit casting with values that may not conform to the data type of the implicit cast and add conditions to the expression to avoid the error.

sqlcode: -16061

sqlstate: 10608

SQL16062N The argument passed to the function fn:zero-or-one is not valid because the sequence contains more than one item. Error QName=err:FORG0003.

SQL16066N The argument passed to the aggregate function `function-name` is not valid. Error QName=err:FORG0006.

Explanation

The argument that was passed to the aggregate function function-name is not valid because the argument does not meet any of the conditions that are required for arguments to the function function-name.

User response

Try one of the following actions:

If the function is fn:avg, verify that the following conditions are met: If the input sequence contains duration values, the values must be either all xdt:yearMonthDuration values or all xdt:dayTimeDuration values. If the input sequence contains numeric values, the values must all be promotable to a single common type that is one of the four numeric types, xdt:yearMonthDuration or xdt:dayTimeDuration or one if its subtypes.
If the function is fn:max or fn:min, verify that the following conditions are met: All items in the input sequence must be numeric or derived from a single base type for which the gt operator (for fn:max) or lt operator (for fn:min) is defined. If the input sequence contains numeric values, the values must all be promotable to a single common type and the values in the sequence must have a total order. If the input sequence contains duration values, the values must be either all xdt:yearMonthDuration values or all xdt:dayTimeDuration values.
If the function is fn:sum, verify that the following conditions are met: All items in the input sequence must be numeric or derived from a single base type. The type must support addition. If the input sequence contains numeric values, the values must all be promotable to a single common type. If the input sequence contains duration values, the values must be either all xdt:yearMonthDuration values or all xdt:dayTimeDuration values.

sqlcode: -16069

sqlstate: 10609

SQL16070N The replacement string argument `value` passed to the function fn:replace is not valid. Error QName=err:FORX0004.

Explanation

The value that was specified for the replacement string parameter in a call to the function fn:replace is not valid because the value includes one or more of the following invalid characters:

A “$” character that is not immediately followed by a digit 0-9 and not immediately preceded by a “\”.
A “\” character that is not part of a “\\” pair or immediately followed by a “$” character.

The statement cannot be processed.

User response

Possible ways to avoid this length limitation include:

Change the value in the XML document to a length no greater than size bytes, possibly by using the fn:substring function.
Avoid using the value in the XQuery operation or function name that limits the length.

User response

Change the expression in the modify clause of the transform expression to ensure that no two expression-type expressions have the same target node.

sqlcode: -16083

sqlstate: 10704

SQL16084N An assigned value in the copy clause of a transform expression is not a sequence with exactly one item that is a node. Error QName=err:XUTY0013.

Explanation

If token1 is "attribute", then token2 is the name of an attribute that has occurred more than once in a target element, after applying the updating expressions in the transform expression.

The XQuery expression cannot be processed.

User response

Correct the transform expression to ensure that the resulting instance of the XDM is correct.

If token1 is "attribute" ensure that any updating expressions involving attributes do not use the name of an attribute that already exists in the target element and is not deleted or replaced within the same transform.

sqlcode: -16087

sqlstate: 10707

SQL16088N An `expression-type` expression has a binding of a namespace prefix `prefix-string` to namespace URI `uri-string`, introduced to an element named `element-name`, that conflicts with an existing namespace binding of the same prefix to a different URI in the in-scope namespaces of that element node. Error QName=err:XUDY0023.

Explanation

An expression-type expression has introduced a new namespace binding for prefix prefix-string using URI uri-string into an element node named element-name that conflicts with one of the existing namespace bindings of the in-scope namespaces of that node. The element node could be the target in the updating expression or the parent of the target in the updating expression. For example, an insert expression might insert an attribute into an existing element. If the QName of the inserted attribute binds prefix P to some URI, but an in-scope namespace of the element node binds the same prefix P to a different URI, a conflict is detected and this error is raised.

User response

If the expression-type expression is intentionally introducing a new namespace binding, modify the expression so that it uses a namespace prefix that is different from all existing prefixes of the in-scope namespaces of the element named element-name. Alternatively, modify the expression so that the binding of prefix-string uses the same URI as the existing namespace binding of the in-scope namespaces of the element named element-name.

sqlcode: -16088

sqlstate: 10708

SQL16089N An `expression-type` expression and possibly other updating expressions in the modify clause of a transform expression introduce conflicting namespace bindings into an element named `element-name`. The prefix `prefix-string` is bound to `uri-string1` while another binding of the same prefix uses a different namespace URI. Error QName=err:XUDY0024.

Explanation

The combined effect of the updating expressions in the modify clause of a transform expression has been to introduce conflicting namespace bindings into element node named element-name. For example, two attributes might have been inserted whose QNames have the same namespace prefix but different namespace URIs.

If expression-type is 'insert' or 'replace' the conflicting namespace bindings may be between 2 attribute nodes in the sequence of attribute nodes in the insertion sequence or replacement sequence. The conflict could also be with a namespace binding introduced to the element element-name for an attribute node that was inserted, replaced or renamed by another updating expression in the same modify clause of the transform expression.

If expression type is 'rename', the namespace binding for the new name conflicts with a namespace binding also introduced to the element element-name for a node that was inserted, replaced or renamed by another updating expression in the same modify clause of the transform expression.

User response

If the expression-type expression is intentionally introducing a new namespace binding, modify the expression so that it uses a namespace prefix that is different from all other prefixes used in the updating expressions of the same transform expression that have the element named element-name as the target or parent of an attribute node target. Alternatively, modify the expression so that the binding of prefix-string uses the same URI as the other namespace bindings used in the updating expressions of the same transform expression that have the element named element-name as the target or parent of an attribute node target.

sqlcode: -16089

sqlstate: 10708

Explanation

While processing an XML document or XML schema the XML parser expected to find data of a certain type and found a value that could not be converted to that type.

If the data type is listed as 'datetime' the data type is one of the date or time data types such as date, time, duration, gDay, gMonth, gMonthDay, gYear.

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16105

sqlstate: 2200M

SQL16106N Invalid XML facet specified for data type `type-name` of the node.

Explanation

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16110

sqlstate: 2200M

SQL16111N XML Document contains an invalid CDATA section. Reason code = `reason-code`.

Explanation

While parsing an XML document the parser encountered an invalid or ill formed CDATA section indicated by reason-code. Possible reason codes are:

There are nested CDATA sections,
A CDATA section is not terminated
a CDATA section contains the sequence ']]<'
a CDATA section is found outside the root element.

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16111

sqlstate: 2200M

SQL16112N XML schema contains an element or attribute definition in error because 'name' or 'ref' was missing and required. Reason code = `reason-code`.

Explanation

While processing an XML schema the XML parser encountered an incorrect element or attribute definition. Value for reason-code corresponds to one of the following reasons:

A globally declared attribute in an XML schema had no name. All globally declared attributes must have a name.
An attribute declared in an XML schema without a name or a ref. All attributes must have a name or a ref.
A globally declared element in an XML schema had no name. All globally declared elements must have a name.
An attribute declared in an XML schema without a name or a ref.. All elements must have a name or a ref.

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16112

sqlstate: 2200M

SQL16113N XML document or XML schema contains an attribute `attribute-name` that is in error. Reason code = `reason-code`.

Explanation

While parsing an XML document the parser encountered an attribute that is not correctly defined or used. Possible reasons given by reason-code are:

1: The attribute had both a name and a ref specified. An attribute may have either a name or a ref but not both.
2: The attribute has previously been declared within the same scope. Attribute names must be unique within their scope.
3: The attribute should be qualified and was not
4: The attribute was qualified and should not have been
5: The attribute is already defined in a base and should not appear in derivation by extension
6: The ID attribute was referenced but never declared
7: The attribute does not match its defined enumeration or notation list
8: The values for the attribute must be names or name tokens
9: The attribute does not support multiple values
10: No data type validator was found for this attribute
11: The attribute must not be changed by normalization in a standalone document
12: The value of the attribute is invalid. Prefixed namespace bindings may not be empty
13: This attribute is a top level attribute and it could not be found
14: An attribute list in a DTD is missing the type definition for the attribute type, which must be one of the following: 'CDATA', 'ID', 'IDREF', 'IDREFS', 'ENTITY', 'ENTITIES', 'NMTOKEN', or 'NMTOKENS'.
15: The attribute refers to an unknown entity
16: The content of the attribute is invalid. The content must conform to the format (annotation?, (simpletype?))
17: The attribute has a default value. That value must be specified in a standalone document.
18: The attribute has already been used in the element. An attribute name must be unique within it's parent element.
19: The attribute has both 'fixed' and 'default' facets specified for it. Either one or the other can be specified but not both.
20: The value of the attribute did not match any of the allowable enumerated values for that attribute.
21: The attribute is not defined within the element
22: The attribute has an invalid value
23: The attribute was not defined in the associated schema.
24: The attribute was not declared
25: There is a bad ID value for this attribute
26: The attribute is required but was not found
27: The simple type of the attribute is not found
28: The value of the attribute does not match a 'fixed' value.

The only valid 'constraining' facet for a boolean data type is PATTERN
An invalid facet tag was encountered
The value of an 'enumeration' facet in a derived object is not from the value space of the corresponding base object.
The value of a 'whiteSpace' facet must be one of 'preserve', 'replace', or 'collapse'
The value of a 'whiteSpace' facet must not be 'preserve' or 'replace' if the value of the 'whiteSpace' facet of the corresponding base type is 'collapse'
The value of a 'whitespace' facet of a derived object must not be 'preserve' if the value of the whitespace facet of the corresponding base object is 'replace'

1: There is an invalid child following the RESTRICTION or EXTENSION element in a simpleContent definition.
2: There is an invalid child following the RESTRICTION or EXTENSION element in a complexContent definition.
3: The BASE attribute was not specified for the RESTRICTION or EXTENSION. Every derivation by RESTRICTION or EXTENSION must include an identification of the base type for that derivation.
4: Derivation by RESTRICTION or EXTENSION is prohibited by the base type or by XML schema.
5: The schema contains a forbidden restriction of 'any'. Valid restrictions for 'any' include 'choice', 'sequence', 'all', and 'element'
6: The schema contains a forbidden restriction of 'all'. Valid restrictions for 'all' include 'choice', 'sequence', and 'element'
7: The schema contains a forbidden restriction of 'choice'. Valid restrictions for 'choice' include 'sequence', 'all', and 'leaf'
8: The schema contains a forbidden restriction of 'sequence'. Valid restrictions for 'sequence' include 'element'.
9: The schema attempts to use a simple type in a derivation by RESTRICTION for a complexType
10: The schema attempts to use a simple type with a value of 'final' in a derivation by EXTENSION.

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16155

sqlstate: 2200M

SQL16156N XML document has a primary document entity that could not be opened. System Id=`system-id`.

Explanation

1: The XML declaration strings must be in the order 'version', 'encoding', and 'standalone'.
2: The declaration must start <?xml, not <?XML. The string 'xml' must be in lower case.
3: The XML or text declaration must start at the first column of the first line.
4: The XML declaration must include the 'version=' string.
5: The XML declaration is required and not present.
6: The specified XML version is unsupported, or invalid.
7: The specified document encoding was invalid or contradicts the automatically sensed encoding.
8: The XML declaration is not terminated.
9: The value of the standalone attribute is invalid or unsupported.
10: Only attributes 'version', encoding', and 'standalone' are supported.

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16168

sqlstate: 2200M

SQL16169N XML document contained an element or attribute name that is invalid with respect to namespaces. Reason code = `reason-code`.

Explanation

While parsing an XML document, the parser encountered an invalid XML element or attribute name caused by namespaces. The reason-code indicates which of the following conditions was found.

When namespaces are enabled, a name can only have one colon character.
When namespaces are enabled the colon cannot be the first or last character.
When namespaces are enabled colons are not allowed in names except to separate the name from the namespace prefix.
If namespaces are enabled, it is invalid for an attribute of type ID, IDREF, IDREFS, ENTITY, ENTITIES, or NOTATION to contain a colon.

The REQUIRED setting is inconsistent
The derived type cannot be validly derived from the base type
The value is not fixed or has a different value from the base
The target namespace is invalid with respect to a base wildcard constraint, or the base has no wildcard.
Cannot modify the 'use' attribute of the derived type if the base attribute use is prohibited.

Found an invalid child following the simpleContent child in the complexType
Found an invalid child following the complexContent child in the complexType

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16183

sqlstate: 2200M

SQL16184N XML document contains duplicate annotation for type `type-name`.

Explanation

While parsing an XML document, duplicate annotation for the type type-name was encountered. A type can be annotated at most once.

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16184

sqlstate: 2200M

SQL16185N XML document contains a syntax error. Reason code = `reason-code`.

Explanation

While parsing an XML document the parser encountered a syntax error. Possible reasons given by reason-code are:

1: Expected [ to follow INCLUDE or IGNORE
2: The document contains a top level complexType with no name
3: The 'standalone=' string is only allowed in the main XML entity
4: The 'encoding=' string is required in a text declaration
5: The Root element is different from DOCTYPE
6: ID attributes must be #IMPLIED or #REQUIRED
7: Attributes of type ENTITY/ENTITIES must refer to an external, unparsed, entity
8: No character data is allowed by the content model
9: Element types cannot be duplicated in mixed content models
10: The content attribute must be 'textOnly' if you specify a type attribute
11: Next element declarations are only allowed in elementOnly content
12: Element reference are only allowed in mixed or elementOnly content
13: Can only have one of 'type' and 'ref' attributes
14: The type of the element has already been declared
15: Illegal xml:space declaration
16: Error in content of <schema> element information item
17: Attribute declarations may not contain both a type and simpleType declaration
18: Ref cannot appear with any of 'type', 'abstract', 'block', 'final', 'nilable', 'default', or 'fixed'
19: Ref is present and simpleType/form/type found
20: The base type specified in the complexContent element must itself be a complexType.
21: 'anyAttribute' elements can contain at most one 'annotation' element in their children
22: The namespace of an <import> element must be different from the targetNamespace of the <import>ing schema
23: If the namespace on an <import> element is not present, the <import>ing schema must have a targetNamespace
24: The content of a complexType that is derived by restriction is empty, but the base type is not empty and cannot be made empty using a derivation by restriction.
25: The content type is not a valid restriction of the content type of the base
26: The {item type definition} must have {variety} of atomic or union (where all member types must be atomic)
27: The {member type definition} must all have {variety} of atomic or list
28: The child of a model group definition must not specify either the minOccurs or maxOccurs attribute
29: A group whose content is 'all' must only appear as the content type of a complex type definition.
30: When a model group has {compositor} 'all' which constitutes the {content type} of a complex type, minOccurs=maxOccurs=1
31: In an 'all' schema component, the value of minOccurs/maxOccurs of an element must be '0' or '1'
32: The intentional intersection of {attribute wildcard}s must be expressible
33: The base type definition does not have any attributes
34: An attribute wildcard is present in the derived type, but not in the base
35: The attribute wildcare in the derived type is not a valid subset of that in the base
36: The wildcard attribute in the derived type must be identical to, or stronger than, the one in the base
37: A simpleType child of a <redefine> must have a restriction element as a child
38: The base attribute of the restriction child of a simpleType must be the same as the redefine simpleType's name attribute.
39: A complexType child of a <redefine> must have a restriction of extension element as a grandchild.
40: The base attribute of a restriction/extension must be the same as the complexType
41: If a group child of a <redefine> element contains a group referencing itself, it must have exactly one reference.
42: If an attributeGroup of a <redefine> element contains a reference to itself, such reference must be exactly 1
43: The content of an identity constraint must match (annotation?, selector, field+)
44: The XPath expression is either missing or empty
45: An <xs:all> model group that is part of a complex type definition must constitute the entire content type of the complex type definition.
46: An <annotation> can only contain <appinfo> and <documentation> elements
47: The root element name of an XML schema should be 'schema'
48: Repetition of individual elements is not legal for mixed content models
49: Bad default attribute declaration
50: Expected default attribute declaration
51: Attribute list syntax error
52: Not valid after content
53: No root element in DOCTYPE
54: Unterminated DOCTYPE declaration
55: Text declaration not legal here
56: Conditional section in internal subset
57: A parameter entity propagated out of the internal or external subset
58: Parameter entity references are not allowed inside markup in the internal subset
59: An entity propagated out of the content section into Miscellaneous
60: External entities cannot be referred to from attribute values
61: If 'default' and 'use' are both present, 'use' must have the value 'optional'
62: Only numeric character entities or special character entities are legal here
63: The schemaLocation attribute does not contain pairs of values
64: Partial markup in parameter entity replacement text in a complete declaration
65: The start and the end tag were in different entities
66: The document contained a recursive entity expansion
67: Facets are inconsistent with base type
68: Whitespace must not occur between externally declared elements with element content in a standalone document.
69: Partial markup in parameter entity replacement text.
70: Field matches more than one value within the scope of its selector; fields must match unique values
71: Non-whitespace characters are not allowed in schema elements other than 'appinfo' and 'documentation'
72: The index given was beyond the max attribute index
73: The passed AttTypes value is not known
74: The passed DefAttType value is not known
75: The binary operation node had a unary node type
76: The content type must be mixed or children
77: PCDATA nodes are not valid here
78: The unary operation node had a binary node type
79: Unknown content model type
80: Unknown content spec type
81: The parent element has no content spec node
82: The creation reason enum has an unknown value
83: The enumerator contain no more element
84: The auto encoding enum has an unknown value
85: Unbalanced start/end tags found, cannot continue
86: Wildcard's occurrence range not a restriction of base wildcard's range
87: Wildcard is not a subset of corresponding wildcard in base
88: Group's occurrence range not a restriction of base wildcard's range
89: There is not a complete function mapping between the particles
90: There is not a complete functional mapping between the particles
91: Invalid content spec node type
92: Empty string encountered
93: String contains whitespace only
94: More than one decimal points encountered
95: Invalid chars encountered
96: Null pointer encountered
97: Occurrence range of a group is not a valid restriction of occurrence range of base group
98: There is not a complete functional mapping between the particles
99: The document contained an unterminated character reference
100: The number of entity expansions exceeded the allowed limit
101: This type of attribute cannot have an empty value
102: Complex type definition representation is ok - <restriction> must have a <simpleType> child
103: The element name/uri in the restriction does not match that of the corresponding base element
104: Selectors cannot select attributes
105: Not allowed to have '|' at the beginning of an XPath value
106: Not allowed to have '||' in an XPath value
107: Missing attribute name in XPath
108: Not allowed to have double colon in the XPath expression
109: Expected step following token 'AXISNAME_CHILD::'
110: Expected step following '//' in XPath
111: Expected step following '/' in XPath
112: '/' not allowed after '//' in XPath
113: '//' only allowed after '.' At the beginning of an XPath
114: Not allowed to have '/' at the beginning of an XPath value
115: Not allowed to select the root of an XPath
116: Empty XPath expression
117: The XPath expression cannot end with '|'
118: Invalid character following '.' in XPath
119: XPath token not supported
120: Enabling the NEL options
121: No scheme was found in the URI
122: The derived complexType has content while the base type is empty
123: The parser expected to find an XML notation name and did not.
124: An unterminated notation declaration was found
125: The parser did not find a document encoding but one was required.
126: The document contained more end tags than start tags

1: The element is nillable in the restriction but not in the base
2: The element is either not fixed, or is fixed but does not have the same value as the base
3: The disallowed substitutions for the element are not a superset of those of the base
4: The element has a type that does not derive from the base
5: The element belongs to a group of a variety different from that of the base
6: The key for the identity constraint of the element is not found
7: The element is declared with a type that is abstract. Use xsi:type to specify a type that is not abstract
8: The element has a blocking constraint and does not permit substitution
9: The element cannot have both a type attribute and a child with a type that is a simpleType or complexType
10: The element must have a fixed or default value and must have a simple or mixed simple content model
11: The element must have a schemaLocation attribute specified
12: The namespace of the element must be from the schema namespace
13: The element has a type which does not derive from the type of the element at the head of the substitution group.
14: The element is globally declared and cannot have a ref attribute
15: No content specification expression was found for the element
16: Expected ',' or ')' characters or close parenthesis in the content model of the element
17: The element cannot have 'xmlns' as a prefix
18: The element has already been declared
19: The element cannot have element children within simple type content.
20: The element has a simpletype but no data type validator was found
21: The element has a key that matches an element that has nillable set to true
22: There is a duplicate key value declared for the identity constraint of the element
23: There is a duplicate unique value declared for the identify constraint of the element
24: The element has a key with no value
25: There are not enough values specified for the unique identify constraint of the element
26: The element was used in the DOCTYPE but never declared
27: The content model for the element is ambiguous
28: The particle of the content type is not emptiable but the content type of the element is mixed.
29: Content for the element is different from the fixed attribute value in the schema declaration of the element
30: There is a circular substitution group for the element
31: The element is not valid for the associated content model
32: The value of the element is 'xsi:nil'. This is inconsistent with the elements declaration as non-nillable.
33: The element is untyped
34: The specified element must be qualified
35: The specified element cannot be qualified
36: The specified element was not empty yet specified xsi:nil=true. Any element specifying xsi:nil=true should be empty.
37: The element is not defined.
38: The element has both 'fixed' and 'default' facets specified for it. Either one or the other can be specified but not both.

User response

Correct the XML document and try the operation again.

sqlcode: -16208

sqlstate: 2200M

SQL16209N XML document requires specification of a member of the substitution group for abstract element `element-name`.

Explanation

The derived element has fewer identify constraints than the base element
The derived element has an identity constraint that does not appear on the base element.

Parsing or validation did not complete.

User response

Correct the base element or the derived element in the XML document and try the operation again.

sqlcode: -16224

sqlstate: 2200M

SQL16225N XML document contains a namespace of `namespace-uri` that is not allowed by a wildcard in the base type.

Explanation

While parsing an XML document, the parser encountered an invalid namespace caused by a type which is derived from a base type with an "any" element that has an element definition with a namespace URI that does not match namespace-uri.

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16225

sqlstate: 2200M

SQL16226N XML schema contains an invalid group specification for group `group-name`. Reason code = `reason-code`.

Explanation

While processing an XML schema the XML parser encountered an invalid group specification. Possible reasons given by reason-code are:

The group must contain (all | choice | sequence)
The group contains a reference to a group being redefined that must have minOccurs = maxOccurs = 1.
The attribute group specification does not match (annotation?.((attribute | attributeGroup)*, anyAttribute?))

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16226

sqlstate: 2200M

SQL16227N XML document contains object "`object-type`" named "`uri`:`object-name`" that was not found in the schema.

Explanation

While parsing an XML document, the parser encountered an object of type object-type with name uri:object-name that could not be found in the XML schema.

User response

Correct the XML document or the XML schema and try the operation again.

Parsing or validation did not complete.

sqlcode: -16227

sqlstate: 2200M

Explanation

While parsing an XML document, the parser encountered an invalid data type declaration. Possible reasons given by reason-code are:

There is no validator for the data type type-name
It is an incorrect data type.

Parsing or validation did not complete.

User response

Correct the XML document and try the operation again.

sqlcode: -16234

sqlstate: 2200M

SQL16235N XML document contained a value `value` that is out of range. Range value 1=`rvalue1`. Range value 2=`rvalue2`. Reason code = `reason-code`.

Explanation

While parsing an XML document the parser encountered an invalid value. Possible reasons given by reason-code are:

The value value is less than the maximum negative value rvalue1.
The value value is greater than the maximum positive value rvalue1.
The number value is outside the allowed range of rvalue1 to rvalue2.
The number value is required to have an exponent.

Parsing or validation did not complete.

User response

Correct the out of range value in the XML document and try the operation again.

sqlcode: -16235

sqlstate: 2200M

SQL16236N Error encountered processing regular expression. Reason code = `reason-code`. Possible token = `token`.

Explanation

While processing a regular expression an error was encountered. The reason-code provides further information regarding the error along with a description of the possible token token if it is not empty.

1: There was an invalid category name token in the regular expression.
2: There was an unknown option in the regular expression.
3: There was an unknown keyword token in the regular expression.
4: ComplementRanges - Argument must be a RangeToken
5: Reference number must be more than zero.
6: Unknown token type.
7: Invalid child index.
8: Invalid or zero length replace pattern.
9: Invalid Unicode hex notation or Unicode code point.
10: The range end code point token is less than the start code point.
11: Invalid regular expression syntax. Expected to find a string or character listed in token.
12: Overflow in a hex notation.
13: An unexpected character was found in a regular expression.
14: Invalid reference number.
15: A character is required after the back slash character ('\').
16: Unexpected end of the pattern in a modifier group, conditional group, or a character class.
17: A back reference, an anchor, a lookahead, or a lookbehind is expected in a conditional pattern.
18: There are more than three choices in a conditional group.
19: A character in U+0040 to u+005f must follow \c.
20: Unexpected meta character.
21: Unknown property.
22: Unknown name of a POSIX character class.
23: Invalid use of '-' character in a regular expression.
24: An anchor is not in the correct position in the regular expression.
25: An expression is used that is not supported in the current option setting.
26: An invalid quantifier was used in token. Possible problems are an expected digit, expected '}' character, invalid quantity, a minimum quantity that exceeds the maximum quantity, or a quantity value overflow.
27: token is not a valid character range.
28: token is an invalid escape character.
29: Internal regular expression processing error. Error code token. Retry and if problem occurs again contact IBM support with this message and the value of token.

A rowset name is not specified or is not fully qualified.
Any mapping must specify either a target column or a condition. Neither a target column nor a condition is specified.
Processing of XML content is specified, but no target column specified. Mapping indicates that the content from the XML document is to be truncated, normalized or transformed via an expression but the mapping does not indicate where the processed content is to be stored.

The XML schema document can be determined by matching uri to the SCHEMALOCATION column of catalog view SYSCAT.XSROBJECTCOMPONENTS.

The XML schema is not enabled for decomposition.

User response

Modify the annotations in the XML schema. Possible actions based on the reason-code include:

Specify a rowset name or fully qualify the rowset name.
Specify either a target column or a condition.
Specify a target column for XML content that has associated processing specified.

Consult annotated XML schema documentation on the specified annotation to make sure that all required components have supplied values.

sqlcode: -16246

sqlstate: 225DE

SQL16247N Source XML type `source-data-type` cannot be mapped to target SQL type `target-data-type` in the annotation at or near line `lineno` in XML schema document `uri`.

Explanation

Annotation at or around line lineno in XML schema document uri maps a XML schema type source-data-type to an incompatible SQL type target-data-type. The XML schema document can be determined by matching uri to the SCHEMALOCATION column of catalog view SYSCAT.XSROBJECTCOMPONENTS.

The XML schema is not enabled for decomposition.

User response

Consult annotated XML schema documentation on compatibility between XML schema types and SQL types. Correct the annotation appropriately.

sqlcode: -16247

sqlstate: 225DE

SQL16248N Error in annotation at or near line `lineno` in XML schema document `uri`. Additional information for the error includes `errordetails`.

Explanation

The annotated XML schema document uri contains an error in the annotation at or near line number lineno. Types of errors include: invalid value, unknown elements or attributes inside an annotation, mal-formed XML. Any available additional information on the type of error or the erroneous value is provided in errordetails.

The XML schema document can be determined by matching uri to the SCHEMALOCATION column of catalog view SYSCAT.XSROBJECTCOMPONENTS.

The XML schema is not enabled for decomposition.

User response

Consult annotated XML schema documentation for list of legal annotations and their syntax. Correct or remove the unknown annotation.

sqlcode: -16248

sqlstate: 225DE

SQL16249N The db2-xdb:expression or db2-xdb:condition annotation `annotation-string` at or near line `lineno` in XML schema document `uri` is invalid according to reason code `reasoncode`.

Explanation

The identified db2-xdb:expression or db2-xdb:condition annotation is not valid, as indicated by one of the following reason codes:

String length of the specified expression exceeded the maximum allowed.
The number of occurrences of the keyword $DECOMP_CONTENT or $DECOMP_ELEMENTID in the expression exceeded the maximum of 10 occurrences.

A value specified in the annotated schema for db2-xdb:locationPath is not valid. Possible values for reason code include:

Some element or attribute has a namespace prefix that is not mapped to a URI. All namespace prefixes used in the location path must have been associated with a namespace in the XML schema document containing the annotation specifying this location path.
Invalid syntax for a location path.
The specified path does not match any possible path from a root node to a location where the element or attribute may appear in an instance document.
An element or attribute name in the locationPath does not correspond to any element or attribute name in the XML schema.
The number of location steps in the location path exceeds the maximum allowed.

The XML schema document can be determined by matching uri to the SCHEMALOCATION column of catalog view SYSCAT.XSROBJECTCOMPONENTS.

The XML schema is not enabled for decomposition.

User response

Modify the annotations in the XML schema. Possible actions based on the reason-code include:

Ensure that namespace prefixes in the db2-xdb:locationPath are correct or add a declaration for the missing namespace.
Ensure that the syntax of the value for db2-xdb:locationPath is valid syntax for a location path.
Ensure that the value for db2-xdb:locationPath corresponds to a possible path from the root node to the element or attribute at the end of the location path.
Make sure all element and attribute names in the locationPath correspond to valid element and attribute names in the XML schema.
Consult annotated XML schema documentation regarding the limits for db2-xdb:locationPath and reduce the number of location steps in the location path to within the limit.

sqlcode: -16254

sqlstate: 225DE

SQL16255N A db2-xdb:rowSet value `rowset-name` used at or near line `lineno` in XML schema document `uri` conflicts with a db2-xdb:table annotation with the same name.

Explanation

The annotated XML schema contains a db2-xdb:table annotation which declares a table or a nickname named rowset-name, but the annotated XML schema does not have any db2-xdb:rowSet annotation declaration to associate rowset-name to any table or nickname. If a rowset is not declared in any db2-xdb:table annotation, it is implicitly associated to a table or nickname with the same name qualified by the value of db2-xdb:defaultSQLSchema. The annotated XML schema cannot use a db2-xdb:rowSet annotation that relies on an implicit association between a rowset and a table or a nickname with the same name of rowset-name, and at the same time declare a table or nickname named rowset-name using a db2-xdb:table annotation. The XML schema document can be determined by matching uri to the SCHEMALOCATION column of catalog view SYSCAT.XSROBJECTCOMPONENTS.

The XML schema is not enabled for decomposition.

User response

Correct the annotated XML schema by adding a db2-xdb:rowSet child element to the db2-xdb:table element with name rowset-name. This will explicitly associate the rowset to the table or nickname.

sqlcode: -16255

sqlstate: 225DE

SQL16256N XML schema is missing a global complexType required to enable for decomposition.

Explanation

The XML schema has no global elements of complexType which would serve as a potential root element for instance documents. The XML schema must contain at least one global element of complexType in order to be enabled for decomposition.

The XML schema is not enabled for decomposition.

User response

Ensure that the XML schema contains at least one global element of complexType before attempting to enable the XML schema for decomposition.

sqlcode: -16256

sqlstate: 225DE

SQL16257N Feature `feature-number` at or near line `lineno` in XML schema document `uri`, is not supported for decomposition. Any additional information on the error includes `error-details`.

Explanation

An unsupported feature was detected, as indicated by one of the following feature numbers:

A mapping to a column of a type not supported by decomposition. Consult annotated XML schema documentation for the allowed target column types.
A mapping of an element in a choice model group containing a condition or expression.
A mapping of an element or attribute to a nickname identifying a table at a data source that is not DB2 for LUW. Any nickname referenced in an annotated XML schema must identify a table that is at a DB2 for LUW data source.
The annotated xml schema contains a reference to a table whose code page is different from the database code page. Decomposition is not supported in a configuration where any of the target tables are in a different code page from that of the database.

User response

Add an annotation that maps a column of the specified rowset to some XML element or attribute. If the rowset is not intended to be a target for decomposition, remove references to the rowset from the annotated XML schema.

sqlcode: -16262

sqlstate: 225DE

SQL16263N The rowSet name `string` at or near line `lineno` in the XML schema document `uri` is not used in any mapping.

Explanation

The rowSet name string at line lineno in the XML schema document uri must be specified in at least one mapping in the XML shema.

User response

Ensure that the rowSet name string is specified in mapping at least one element or attribute in the XML schema.

sqlcode: -16263

sqlstate: 225DE

SQL16264N The rowSet name `string` at or near line `lineno` in the XML schema document `uri` cannot be used more than once under `annotation-name`.

Explanation

A rowSet name can be used only once under annotation-name. It can participate in only one hierarchy of operation orders.

User response

Verify that using the same rowSet name under multiple instances of the element db2-xdb:order under annotation-name is part of your design.

If by design, combine the affected db2-xdb:order elements such that the resulting order is consistent with the required order of insertion.

sqlcode: -16264

sqlstate: 225DE

SQL16265N The XML document cannot be decomposed using XML schema `xsrobject-name` which is not enabled or is inoperative for decomposition.

Explanation

The XML schema identified by xsrobject-name is not in the correct state to perform decomposition. The XML schema could be in one of the following states:

Not enabled for decomposition (possibly never enabled)
Disabled for decomposition
Inoperative for decomposition because of changes to the definitions of one or more tables specified in the annotations.

Decomposition can only be performed using XML schemas that are enabled for decomposition.

XML decomposition was not started.

User response

Ensure that the XML schema is enabled for decomposition before attempting to use it for decomposition of an XML document. The decomposition status of an XML schema can be checked by selecting the DECOMPOSITION column of SYSCAT.XSROBJECTS for the XML schema identified by xsrobject-name.

sqlcode: -16265

sqlstate: 225D1

SQL16266N An SQL error occurred during decomposition of document `docid` while attempting to insert data. Information returned for the error includes SQLCODE `sqlcode`, SQLSTATE `sqlstate`, and message tokens `token-list`.

Explanation

An SQL error occurred during decomposition of an XML document with document identifier docid. The error occurred while attempting an SQL insert operation based on some piece of data from the XML document. Some possible causes: format of data is incompatible with the target column's data type; length of data exceeds column size; providing null value for a column defined as non-null. The sqlcode, sqlstate and message token list (each token is separated by the vertical bar character) are provided. The message tokens may be truncated. See the corresponding message for the sqlcode for further explanation of the error.

The XML document docid was not decomposed.

User response

Check the message associated with the SQLCODE. Follow the action suggested by that message. See the db2diag log file for complete information about the error condition.

sqlcode: -16266

sqlstate: 225D2

SQL16267N An XML value `string` at or near line `lineno` in document `docid` is not valid according to its declared XML schema type `type-name` or is outside the supported range of values for the XML schema type.

Explanation

The specified XML value string is not supported as a value of data type type-name. This error could occur for one of the following reasons:

The XML value is not in the value space of the XML schema type type-name. In this case, the XML document is not valid according to the XML schema that is used for decomposition.
The XML value is outside the range of values supported in DB2 for the XML schema type type-name. In this case, the XML value cannot be inserted into its currently mapped column. However, the lexical representation of the XML value can be inserted if the value is mapped to a column of character type.

The XML document docid was not decomposed.

User response

Consult the W3C recommendation on XML schema to determine the value space of the XML schema type. Validate that the XML document is consistent with the annotated XML schema you are using for decomposition. If the value appears to be in the value space for the type, check the range limits for the value in DB2 as documented in the XQuery Reference. If the XML value is out of range for the data type, map the elements or attributes that contains such values to a character string column. If the XML schema requires correction, it must be registered again in the XML schema respository (XSR) and enabled for decomposition. Then retry the decomposition.

sqlcode: -16267

sqlstate: 225D3

SQL16268N The special numeric values INF, -INF, or NaN found at or near `lineno` of document `docid` cannot be assigned to a column.

Explanation

Decomposition processing found one of the special numeric values INF, -INF, or NaN at or near line number lineno in the document with identifier docid. These special values for XML schema floating point types are not valid values for assignment to numeric columns.

The XML document docid was not decomposed.

User response

Possible methods of resolution:

Substitute any occurrence in the instance document of XML schema floating point special values with a valid DB2 floating point value
Map the XML floating point to a character column, instead of a double or float column
Write special purpose user-defined functions that can be called using the expression annotation to transform these values into a numeric value that can be assigned to a numeric column.

sqlcode: -16268

sqlstate: 225D4

SQL16269N Element "`namespace`:`elementname`" at or near line "`lineno`" in document "`docid`" is not recognized.

Explanation

The element namespace:elementname at or near line lineno in document docid is not recognized based on the annotated XML schema in use for decomposition. Possible causes:

The element was not defined in the registered annotated XML schema
A member of a substitution group appears in the instance document, in a position where the group head appears in the XML schema
Another element of compatible type was substituted in the instance document for the element expected at that position according to the XML schema.

The XML document docid was not decomposed.

User response

Check that the XML document docid is consistent with the annotated XML schema you are using for decomposition. One method of checking is to run XML decomposition again with validation turned on to ensure that document is valid. You should also check for use of features that are not supported for decomposition, such as substitution groups and xsi:type.

If the annotated XML schema requires correction, it must be registered again in the XML schema respository (XSR) and enabled for decomposition.

sqlcode: -16269

sqlstate: 225D5

SQL16270N Element "`namespace`:`elementname`" at or near line "`lineno`" in document "`docid`" is not valid in the context where it was found.

Explanation

The location with respect to the root element in the XML document of the element namespace:elementname at or near line lineno in document docid does not correspond to its position relative to the root as specified in the annotated XML schema used for decomposition or the element might be unreachable because it violates the cardinality specified in the annotated XML Schema.

The XML document docid was not decomposed.

User response

If the annotated XML schema requires correction, it must be registered again in the XML schema respository (XSR) and enabled for decomposition.

sqlcode: -16270

sqlstate: 225D5

SQL16271N Unknown attribute "`namespace`:`attributename`" at or near line "`lineno`" in document "`docid`".

Explanation

The specified attribute encountered in the document is not found the in the annotated XML schema you are using for decomposition.

The XML document docid was not decomposed.

User response

Check that the XML document is consistent with the annotated XML schema you are using for decomposition. One method of checking is to run XML decomposition again with validation turned on to ensure that document is valid.

If the annotated XML schema requires correction, it must be registered again in the XML schema respository (XSR) and enabled for decomposition.

sqlcode: -16271

sqlstate: 225D5

SQL16272N Annotated XML schema requires migration from version `xdbversion` to the current version.

Explanation

The generated meta data for the annotated XML schema is from version xdbversion which is not valid for the current version of DB2. Decomposition cannot be performed for XML documents using this annotated XML schema until it has been migrated to the current version.

Decomposition of the XML document was not started.

User response

Run db2xdbmig to migrate the meta data to the current version and then try the decomposition operation again.

sqlcode: -16272

sqlstate: 225D6

SQL16273N For the XML document, `docid`, the XML schema identifier `xml-schema-id` contains no valid mappings for root element `namespace`:`element-name` or its descendants.

Explanation

Possible reasons for this error condition include:

The root element namespace:element-name has a mapping to a rowSet and column, but is of simpleType. In this case, decomposition of a document containing only the root element is trivial and using annotated XML schema decomposition is not necessary.
Some mappings for the root element namespace:element-name and its descendants specified an incorrect locationPath.
None of the element or attribute declarations for the root element namespace:element-name and its descendants have annotations.

The XML document docid was not decomposed.

User response

Check the annotations in the registered XML schema for the possible errors indicated in this message's Explanation. Additionally, check that the mapped items, as reflected by the data in the column MAPPINGDESCRIPTION of the view SYSCAT.XDBMAPSHREDTREES for the row corresponding to xml-schema-id, are as intended. Correct any erroneous annotations, register the XML schema again, and try decomposing the document again.

sqlcode: -16273

sqlstate: 225D7

SQL16274N An SQL error occurred while preparing to insert data for rowset `rowsetname`. Information returned for the error includes SQLCODE `sqlcode`, SQLSTATE `sqlstate`, and message tokens `token-list`.

Explanation

An SQL error occurred preparing to perform the operation on the table or nickname associated with the specified rowset rowsetname based on the annotated XML schema. Some possible causes are:

The syntax of a db2-xdb:expression or a db2-xdb:condition specified for the rowset is not a valid SQL expression or predicate.
A declared parameter for an SQL function or user-defined function invoked in an expression or predicate is incompatible with the type of the argument passed to the function.

An annotated XML schema can contain at most one occurrence of the annotation string.

User response

Combine the contents of the multiple string annotations into a single annotation, and ensure that the resulting annotation does not contain any duplicate information.

sqlcode: -16277

sqlstate: 225DE

SQL16278W One or more documents could not be decomposed. The number of documents successfully decomposed was `number-successful`. The number of documents attempted was `number-attempted`.

Explanation

Error conditions prevented one or more documents from being decomposed. For more details on the status of each document, refer to the result_report output parameter.

User response

To decompose the XML documents that were not successfully decomposed:

Review the error message information in the result_report output parameter. If necessary, see the db2diag log file for more details about each error. The pertinent entries in the db2diag log file are identified by the document ID.
Correct the errors described in the result_report parameter.
Rerun the decompose procedure as follows:
- If you specified a positive commit_count value, resubmit the procedure only for the documents that were not successfully decomposed.
- If you specified a commit_count value of 0, use one of the following options:
  - Perform a rollback, and then invoke the procedure for all the documents.
  - Commit the changes, and then invoke the procedure only for the documents that were not successfully decomposed.
See the db2diag log file for more details about the error if the warning was returned by the EVMON_FORMAT_UE_TO_TABLES procedure. The RESULTREPORT has been dumped to file "db2EvmonErrReport_applid.xml" in the sqllib/db2dump/evmon directory. Correct the problems described in the RESULTREPORT and try to decompose the document again.

sqlcode: +16278

sqlstate: 01H53

SQL16280N The XSLT processor returned the following error: `error-message`.

Explanation

The XSLT processor returned the error text error-message because it cannot transform the XML document. There may be a problem with the XML document itself, with the associated stylesheet document, or with the parameter document.

Explanation

An SQL/JSON expression resulted in an SQL/JSON array, object or multiple matches. An SQL/JSON array or object cannot be converted to an SQL type.

User response

Specify an SQL/JSON expression that returns a scalar value.

sqlcode: -16413

sqlstate: 2203F

SQL10000 - SQL19999

SQL10002N The password supplied is too long.

Explanation

User response

SQL10003C There are not enough system resources to process the request. The request cannot be processed.

Explanation

User response

SQL10004C An I/O error occurred while accessing the database directory.

Explanation

User response

Explanation

User response

SQL10007N Message msgno could not be retrieved. Reason code: code.

Explanation

User response

SQL10009N The codeset codeset and/or territory territory that has been specified is not valid.

Explanation

User response

SQL10010N The specified library, name, was loaded, but the function function could not be executed.

Explanation

User response

SQL10011N An interrupt was received while loading the specified library name.

Explanation

User response

SQL10012N An unexpected operating system error was received while loading the specified library name.

Explanation

User response

SQL10013N The specified library name could not be loaded.

Explanation

User response

SQL10014N The invoking program name name specified is not valid.

Explanation

User response

SQL10015N There are not enough system resources to load the specified library name.

Explanation

User response

SQL10017N The SQL CONNECT RESET statement is not allowed in a this context.

Explanation

User response

SQL10018N The disk is full. Processing was ended.

Explanation

User response

SQL10019N The database cannot be accessed in the specified path.

Explanation

User response

SQL10021N The file permissions do not allow write access to the database.

Explanation

User response

SQL16000N An XQuery expression cannot be processed because the context-component component of the static context has not been assigned. Error QName=err:XPST0001.

Explanation

User response

SQL16001N An XQuery expression starting with token token cannot be processed because the focus component of the dynamic context has not been assigned. Error QName=err:XPDY0002.

Explanation

User response

SQL16002N An XQuery expression has an unexpected token token following text. Expected tokens may include: token-list. Error QName=err:XPST0003.

Explanation

User response

SQL16003N An expression of data type value-type cannot be used when the data type expected-type is expected in the context. Error QName=err:XPTY0004.

Explanation

User response

SQL16004N The fn:data function cannot be applied explicitly or implicitly to an XQuery node for which the type annotation denotes a complex type with element-only content. Error QName=err:FOTY0012.

Explanation

User response

SQL16005N An XQuery expression references an element name, attribute name, type name, function name, namespace prefix, or variable name variable-name that is not defined within the static context. Error QName=err:XPST0008.

Explanation

User response

SQL16006N XML schemas cannot be imported. Error QName=err:XQST0009.

Explanation

User response

SQL16007N The XQuery path expression references an axis axis-type that is not supported. Error QName=err:XQST0010.

Explanation

User response

SQL16008N XQuery library modules cannot be declared or imported. Error QName=err:XQST0016.

Explanation

User response

SQL16009N An XQuery function named function-name with number-of-parms parameters is not defined in the static context. Error QName=err:XPST0017.

Explanation

User response

SQL16010N The result of the last step in an XQuery path expression contains both nodes and atomic values. Error QName=err:XPTY0018.

Explanation

SQL10007N Message `msgno` could not be retrieved. Reason code: `code`.

SQL10009N The codeset `codeset` and/or territory `territory` that has been specified is not valid.

SQL10010N The specified library, `name`, was loaded, but the function `function` could not be executed.

SQL10011N An interrupt was received while loading the specified library `name`.

SQL10012N An unexpected operating system error was received while loading the specified library `name`.

SQL10013N The specified library `name` could not be loaded.

SQL10014N The invoking program name `name` specified is not valid.

SQL10015N There are not enough system resources to load the specified library `name`.

SQL16000N An XQuery expression cannot be processed because the `context-component` component of the static context has not been assigned. Error QName=err:XPST0001.

SQL16001N An XQuery expression starting with token `token` cannot be processed because the focus component of the dynamic context has not been assigned. Error QName=err:XPDY0002.

SQL16002N An XQuery expression has an unexpected token `token` following `text`. Expected tokens may include: `token-list`. Error QName=err:XPST0003.

SQL16003N An expression of data type `value-type` cannot be used when the data type `expected-type` is expected in the context. Error QName=err:XPTY0004.

SQL16005N An XQuery expression references an element name, attribute name, type name, function name, namespace prefix, or variable name `variable-name` that is not defined within the static context. Error QName=err:XPST0008.

SQL16007N The XQuery path expression references an axis `axis-type` that is not supported. Error QName=err:XQST0010.

SQL16009N An XQuery function named `function-name` with `number-of-parms` parameters is not defined in the static context. Error QName=err:XPST0017.

SQL16015N An element constructor contains an attribute node named "`node-name`" that follows an XQuery node that is not an attribute node. Error QName=err:`error-name`.

SQL16016N The attribute name `attribute-name` cannot be used more than once in an element constructor. Error QName=err:XQDY0025.

SQL16018N For the target data type `type-name`, a string literal is not specified as the operand of a cast expression or as the argument of a constructor function. Error QName=err:XPST0083.

SQL16021N The XQuery version declaration specifies a number `version-number` that is not supported. Error QName=err:XQST0031.

SQL16022N A value of type `value-type` is not valid in an expression that uses operation `operator`. Error QName=err:XPTY0004.

SQL16023N The XQuery prolog cannot contain multiple declarations for the same namespace prefix `ns-prefix`. Error QName=err:XQST0033.

SQL16024N The prefix `prefix-name` cannot be redeclared or cannot be bound to the URI http://www.w3.org/XML/1998/namespace. Error QName=err:XQST0070.

SQL16026N The name `attribute-name` is used for more than one attribute in the constructor for the element named `element-name`. Error QName=err:XQST0040.

SQL16027N The value of the name expression `value` in a computed processing instruction constructor is not valid. Error QName=err:XQDY0041.

SQL16029N Two or more namespaces within the same XQuery element constructor use the same namespace prefix `prefix-name`. Error QName=err:XQST0071.

SQL16030N The value `value` returned by the name expression of a computed attribute constructor is in the namespace for the prefix xmlns, or is in no namespace and has the local name xmlns. Error QName=err:XQDY0044.

SQL16031N XQuery language feature using syntax `string` is not supported.

SQL16032N The string `string` is not a valid URI. Error QName=err:XQST0046.

SQL16033N The target data type `type-name` of a cast or castable expression is not an atomic data type defined for the in-scope XML schema types or is a data type that cannot be used in a cast or castable expression. Error QName=err:XPST0080.

SQL16034N The QName `qname` is used as an atomic type in a sequence type, but is not defined in the in-scope schema type definitions as an atomic type. Error QName=err:XPST0051.