SQL20250 - SQL20499
SQL Message ID | Message | Explanation | User Response |
---|---|---|---|
SQL20250N |
The number of data partitions exceeds the number of table spaces for the table. |
The partitioned table was defined with NO CYCLE and there are not enough table spaces defined for the number of specified table partitions. The statement cannot be processed. |
In the CREATE TABLE statement, either specify additional table spaces for the table or remove the NO CYCLE specification for the table. sqlcode: -20250 sqlstate: 428G1 |
SQL20251N |
The last data partition cannot be detached from the table table-name. |
The ALTER TABLE statement would have resulted in the last remaining data partition being detached from the table. This operation is not allowed. A partitioned table must have at least one data partition whose status is normal or attached. A partitioned table cannot have only data partitions whose status is detached. To determine the status of partitions, query the catalog view, SYSCAT.DATAPARTITIONS. The statement cannot be processed. |
Ensure that the ALTER TABLE statement leaves at least one data partition in the table. sqlcode: -20251 sqlstate: 428G2 |
SQL20253N |
The BEFORE trigger or generated column name cannot be created, altered, or executed because doing so would cause the table on which the BEFORE trigger or generated column is defined to be delete-connected to at least one ancestor table through multiple relationships with conflicting delete rules. The conflict is between the delete rules of constraints constraint-name1 and constraint-name2. Reason code = reason-code. |
The definition for the BEFORE trigger or generated column name in the CREATE TRIGGER, CREATE TABLE or ALTER TABLE statement is not valid for the reason specified by the reason-code as follows:
The statement cannot be processed. |
The action corresponding to the reason code is:
sqlcode: -20253 sqlstate: 42915 |
SQL20254N |
FOREIGN KEY name is not valid since it would cause table table-name to be delete-connected to itself through a cycle that contains a delete rule of either RESTRICT or SET NULL. Reason code = reason-code. |
A referential cycle must not contain a delete rule of RESTRICT or SET NULL. The delete rule specified for FOREIGN KEY name in the CREATE TABLE or ALTER TABLE statement is not valid for the reason specified by the reason-code as follows:
name is the constraint name, if specified, in the FOREIGN KEY clause. If a constraint name was not specified, name is the first column name specified in the column list of the FOREIGN KEY clause followed by three periods. The statement cannot be processed. |
The action corresponding to the reason code is:
sqlcode: -20254 sqlstate: 42915 |
SQL20255N |
FOREIGN KEY name is not valid because it would cause a descendent table descendent-table-name to be delete-connected to its ancestor table ancestor-table-name through multiple relationships with conflicting delete rules. The conflict is between the delete rules of constraints constraint-name1 and constraint-name2 on the descendent table. Reason code = reason-code. |
The referential constraint definition specified for FOREIGN KEY name in the CREATE TABLE or ALTER TABLE statement is not valid. The reason code indicates more specifcally what the problem is:
name is the constraint name, if specified, in the FOREIGN KEY clause. If a constraint name was not specified, name is the first column name specified in the column list of the FOREIGN KEY clause followed by three periods. The same convention applies to constraint-name1 and constraint-name2. |
Respond according to the reason code:
sqlcode: -20255 sqlstate: 42915 |
SQL20256N |
FOREIGN KEY name is not valid because it would cause two tables table-name1 and table-name2 to be delete-connected to each other while they are delete -connected to the same ancestor table ancestor-table-name through CASCADE relationships. Reason code = reason-code. |
When two tables are delete-connected to the same table through CASCADE relationships, the two tables must not be delete-connected to each other where the delete rule of the last relationship in each path is RESTRICT or SET NULL. The delete rule specified in a FOREIGN KEY clause of the CREATE TABLE or ALTER TABLE statement is not valid for the reason specified by the reason-code as follows:
|
The action corresponding to the reason code is:
sqlcode: -20256 sqlstate: 42915 |
SQL20257N |
FINAL TABLE is not valid when the target view viewname of the SQL data change statement in a fullselect has an INSTEAD OF trigger defined. |
The fullselect includes an INSERT or UPDATE statement that targets a view that has an INSTEAD OF trigger defined for the SQL data change operation. The FINAL TABLE results of an INSTEAD OF trigger cannot be returned. The statement cannot be processed. |
Change FINAL TABLE to NEW TABLE or drop the INSTEAD OF trigger. sqlcode: -20257 sqlstate: 428G3 |
SQL20258N |
Invalid use of INPUT SEQUENCE ordering. |
The ORDER BY clause specifies INPUT SEQUENCE and the FROM clause of the fullselect does not specify an INSERT statement. The statement cannot be processed. |
Use INPUT SEQUENCE when the FROM clause of the fullselect specifies an INSERT statement. sqlcode: -20258 sqlstate: 428G4 |
SQL20259N |
Column column-name cannot be selected from the target of the data change statement in the FROM clause of the fullselect. |
A column has been selected that cannot be specified in the select list of this query. This column is based on a column in a view or fullselect that is the target of an INSERT or UPDATE statement that is specified in a FROM clause using either NEW TABLE or FINAL TABLE. The column selected is based on:
The statement cannot be processed. |
Change the select list to remove the column. sqlcode: -20259 sqlstate: 428G6 |
SQL20260N |
The assignment clause of the UPDATE statement must specify at least one column that is not an INCLUDE column. |
The UPDATE statement has specified INCLUDE columns and the only assignments are made to INCLUDE columns. At least one of the assignments in an UPDATE statement must be to a column of the target of the UPDATE statement. The statement cannot be processed. |
Change the statement to specify an assignment to a column of the target of the UPDATE statement. sqlcode: -20260 sqlstate: 428G5 |
SQL20261N |
Invalid row movement to table table-name within the UNION ALL view view-name. |
A check-constraint on table table-name caused an updated row to be rejected. When attempting to insert the row into another underlying table of view-name, the table table-name accepted the row. The destination table of a moved row cannot be identical to the table from which it originated. The statement cannot be processed. |
Verify the interaction between before update and before insert triggers on the target table. When performing row movement, DB2 executes before update triggers first, which may modify the row. The rejected row may then be processed by before insert triggers which may again modify the row in a way that it is now accepted by the check constraints of the target table. Change the triggers so that this does not happen. sqlcode: -20261 sqlstate: 23524 |
SQL20262N |
Invalid usage of WITH ROW MOVEMENT in view view-name. Reason code = reason-code. |
The view view-name has been defined with the WITH ROW MOVEMENT clause. This clause is not applicable for the view because of one of the following:
The view cannot be created. |
Depending on the reason code, do the following:
sqlcode: -20262 sqlstate: 429BJ |
SQL20263N |
Invalid attempt to update view view-name1 because view view-name2 is defined WITH ROW MOVEMENT. |
The attempt to update view-name1 failed because it directly or indirectly contains a UNION ALL operation involving view view-name2 which is defined with the WITH ROW MOVEMENT clause. The statement cannot be executed. |
Drop the view view-name2 and recreate it without the WITH ROW MOVEMENT clause. sqlcode: -20263 sqlstate: 429BK |
SQL20264N |
For table table-name, authorization ID auth-id does not have access-type access to the column column-name. |
While accessing the table named table-name, the authorization ID auth-id is attempting access-type access on column column-name. The authorization ID does not have the LBAC credentials necessary to access the column in that way. If a generated column is being created, LBAC credentials for reading the column are required to include the column in a generation-expression. |
Contact a user who has SECADM authority and ask the user to grant the authorization ID authid LBAC credentials that allow access-type access to the column column-name. sqlcode: -20264 sqlstate: 42512 |
SQL20267N |
The function function-name (specific specific-name) modifies SQL data and is invoked in an illegal context. Reason code = reason-code. |
The function function-name with specific name specific-name is defined with the MODIFIES SQL DATA property. Functions with this property are only allowed as the last table reference in a select-statement, common-table-expression, RETURN statement that is a subselect, SELECT INTO statement, or row-fullselect in a SET statement. As well, each argument to the table function must be correlated to a table reference in the same FROM clause as the table function, and every table reference must be correlated to by some argument in the table function. An argument is correlated to a table reference when it is a column of that table reference. Reason-code:
The statement cannot be processed. |
For reason codes 1, 2, and 3, the query can be rewritten using a common table expression to isolate the table function invocation. For example: Can be rewritten as: sqlcode: -20267 sqlstate: 429BL |
SQL20268N |
Collation cannot be applied. Reason code = reason-code. |
The collation cannot be applied for reason code reason-code. The reason codes and their meanings are:
|
For each reason code:
sqlcode: -20268 sqlstate: 429BM |
SQL20269N |
The nickname nickname cannot be referenced in an enforced referential constraint. |
A referential constraint in the CREATE TABLE statement or the ALTER TABLE statement is invalid. The constraint definition specifies ENFORCED but refers to a nickname. The statement cannot be processed. |
Change the referential constraint to specify NOT ENFORCED or remove the reference to the nickname. sqlcode: -20269 sqlstate: 428G7 |
SQL20271W |
The name at ordinal position number in the statement, with name name, was truncated. |
At least one name in the described statement was truncated. The first name that was truncated is identified by the name name and ordinal position number. If performing a describe output of a prepared query, the ordinal position is relative to the select list column of the query. If performing a describe output of a CALL statement, the ordinal position is relative to the OUT or INOUT parameters of the procedure to which the CALL resolved. If performing a describe input of a CALL statement, the ordinal position is relative to the IN or INOUT parameters of the procedure to which the CALL resolved. The column name, parameter name, user defined type name or user defined type schema name was either too long, or became too long after code page conversion. Note that the length of the column name, parameter name, user defined type name, and user defined type schema name are limited when using the SQLDA structure. |
If the exact name or schema is significant, do one of the following:
sqlcode: +20271 sqlstate: 01665 |
SQL20273N |
The nickname statistics cannot be updated because the database is not enabled for federation. |
An error has been detected at the instance level. The requested operation cannot be completed because federation was not enabled for the instance. |
Set the DBM variable FEDERATED to YES and then restart the database manager. sqlcode: -20273 sqlstate: 55056 |
SQL20274W |
Some of the nickname statistics cannot be updated. |
Either the database manager cannot execute a query against a nickname to gather the statistics, or the database manager cannot write the results of the updates to the federated database system catalog. |
The nickname statistics update errors are listed in the log file, if a log file path was specified. sqlcode: +20274 sqlstate: 550C8 |
SQL20275N |
The XML name xml-name is not valid. Reason code = reason-code. |
The statement cannot be processed because it violates a constraint as indicated by the following reason code:
|
Correct the XML name and resubmit the statement. sqlcode: -20275 sqlstate: 42634 |
SQL20276N |
The XML namespace prefix xml-namespace-prefix is not valid. Reason code = reason-code. |
The statement cannot be processed because it violates a constraint as indicated by the following reason code:
|
Correct the XML namespace prefix and resubmit the statement. sqlcode: -20276 sqlstate: 42635 |
SQL20277W |
Characters were truncated while performing conversion from code page source-code-page to code page target-code-page. The maximum size of the target area was max-len. The source string length was source-len and its hexadecimal representation was string. |
During the execution of the SQL statement, a code page conversion operation has resulted in a string that is longer than the maximum size of the target object. Characters were truncated so the result would fit in the target area. |
If the truncation has caused an unexpected consequence, then expand the length of the target column and issue the statement again. sqlcode: +20277 sqlstate: 01004 |
SQL20278W |
The view viewname may not be used to optimize the processing of queries. |
The fullselect of the view includes elements that prohibit the use of the statistics on the view for optimization when the view is not referenced directly in a query. These elements of the fullselect may include:
The view is successfully altered to enable query optimization. |
No action is required. If the intent of the view is to optimize queries that do not directly reference the view, then the view could be dropped or have query optimization disabled. You could also consider defining the fullselect of the view to remove the elements that prevent optimization. sqlcode: +20278 sqlstate: 01667 |
SQL20279N |
The view view-name cannot be enabled for query optimization. Reason code = reason-code. |
The view cannot allow the ENABLE QUERY OPTIMIZATION option because the fullselect does not conform to the set of queries that can take advantage of this capability. The statement failed for one of the following reasons:
The statement cannot be processed. |
The action is based on the reason code as follows:
sqlcode: -20279 sqlstate: 428G8 |
SQL20280W |
Insufficient permission to create or write to the log-file-path file. |
The statement completed successfully, but the user does not have permission to create or write to the specified log file, log-file-path. |
To write the details to the log file, make sure that you have write access to the log file path specified. Alternatively, omit the optional log file path. sqlcode: -20280 sqlcode: 42501 |
SQL20282N |
.NET procedure or user-defined function name, specific name specific-name could not load .NET class class. Reason code reason-code. |
The .NET class given by the EXTERNAL NAME clause of a CREATE PROCEDURE or CREATE FUNCTION statement could not be loaded. The reason codes are:
|
sqlcode: -20282 sqlstate: 42724 |
SQL20284N |
No plan was possible to create for federated data source server-name. Reason = reason-code. |
While building a federated query access plan, the query fragment for one or more data sources cannot be processed because of a missing predicate or a problem with the query syntax as indicated by the following reason code:
|
See the federation documentation for this data source. Correct the query syntax as needed and resubmit the statement. The action corresponding to the reason code is:
sqlcode: -20284 sqlcode: 429BO |
SQL20285N |
The statement or command was not processed either because the table named table-name has detached dependent tables or because an asynchronous partition detach operation on the table is not complete. Reason code = reason-code. |
You can manage ranges of data by using data partitioning. The process of detaching a data partition occurs in two phases:
Tables that need to be incrementally maintained with respect to the detached data partition are referred to as detached dependent tables. The specific reason this message was returned is indicated by the value of the runtime token reason-code:
|
Respond to this message according to the reason code:
sqlcode: -20285 sqlstate: 55057 |
SQL20287W |
The environment of the specified cached statement is different than the current environment. The current environment will be used to reoptimize the specified SQL statement. |
The Explain facility has been invoked to explain a statement that has been previously reoptimized with REOPT ONCE, but the current environment is different than the environment in which the cached statement was originally compiled. The current environment will be used to reoptimize the specified statement. The statement will be processed. |
In order to ensure that the plan matches the plan in the cache, reissue the EXPLAIN in an environment that matches the one in which the original statement was reoptimized and cached. sqlcode: -20287 sqlstate: 01671 |
SQL20288N |
Statistics could not be updated for the object. Object name: object-name. Object type: object-type. Reason code: reason-code. |
You can collect and update statistics on tables, indexes, and statistical views to provide the optimizer with accurate information for access plan selection by using the RUNSTATS utility. This message is returned when statistics could not be collected. The reason code indicates the cause of the failure:
|
Respond to this error according to the reason code:
sqlcode: -20288 sqlstate: 428DY |
SQL20289N |
Invalid string unit unit in effect for function function-name. |
The statement invoked a built-in function using a string unit that is not valid with the type of data that is provided to the function. This can occur for the following reasons:
The statement cannot be executed. |
Change the invocation of the function to remove the invalid string length unit or change it to a unit valid for the data type and values being processed. sqlcode: -20289 sqlstate: 428GC |
SQL20290N |
The SQL statement references routine routine-name (specific name specific-name) which cannot be run on partition partition-number. |
The routine routine-name (specific name specific-name) was called with an invalid partition number partition-number. |
Specify -1 for the partition number parameter to run the routine on the current partition. sqlcode: -20290 sqlstate: 560CA |
SQL20296N |
The ALTER TABLE statement is not allowed as it modifies some physical attribute of the table table-name that has detached partitions and there are dependant tables that need to be incrementally maintained with respect to these detached partitions. |
The table has detached partitions and there are dependent tables that need to be incrementally maintained with respect to these detached partitions. Modifying any physical attribute of the table is not allowed as doing so would invalidate the incremental maintenance of the dependent tables. The restricted physical attribute modification may include: adding a column, altering a column; or altering one of the following values: data capture, value compression, append, compact, logged, activate not logged initially. |
Identify the dependent tables that require incremental maintenance and issue the SET INTEGRITY statement with the IMMEDIATE CHECKED option on these dependent tables before re-issuing the failing ALTER TABLE statement. The following query can be used to identify the dependent tables that require incremental maintenance, where <schema name> is the qualifier of table-name and <table name> is the table name portion of table-name.
sqlcode: -20296 sqlstate: 55057 |
SQL20302W |
More table spaces than required were specified in the IN or LONG IN clause. The extra table spaces are ignored. |
If the table being created is a non-partitioned table, then more than one table space is specified in the IN or LONG IN clause. The first table space specified is used to store the table data or long data. Only one table space should be specified in the IN or LONG IN clause for a non-partitioned table. If the table being created is a partitioned table, then the number of table spaces specified in the IN or LONG IN clause was more than the number of partitions defined for the table. When adding partitions to a partitioned table that was created with the long data in the same table space as regular data, the LONG IN clause provided in the ADD PARTITION clause is ignored. The statement was processed successfully, but the extra table spaces were ignored. |
None. sqlcode: +20302 sqlstate: 01675 |
SQL20303N |
The partitioned unique index was not created because either the index definition did not include all of the partitioning columns, or the index was being created over XML data. |
You can create a partitioned index for a partitioned table by specifying the PARTITIONED clause in the CREATE INDEX statement. When you create a partitioned index for a partitioned table, each data partition is indexed in its own index partition. When you are defining a partitioned unique index, you must include all columns from the table-partitioning key in the index key. Note that any column that is included in an expression-based index key must also be specified plainly, without being included as part of an expression. This message can be returned for different reasons:
|
Submit the CREATE INDEX statement again, specifying all the partitioning columns in the index key. sqlcode: -20303 sqlstate: 42990 |
SQL20304N |
The index was not created because of a problem with an XMLPATTERN clause or a column of data type XML. Reason code: reason-code. |
This message can be returned when a column defined with a data type of XML is included (or missing) in the columns for the index. The reason code indicates what is invalid about the index definition:
|
Respond to this error according to the reason code:
sqlcode: -20304 sqlstate: 429BS |
SQL20305N |
An XML value cannot be inserted or updated because of an error detected when inserting or updating the index identified by index-id on table table-name. Reason code = reason-code. For reason codes related to an XML schema the XML schema identifier = xml-schema-id and XML schema data type = xml-schema-data-type. |
The statement cannot proceed and the table and index remain unchanged because of one of the following reason codes. The schema data type and schema identifier are not applicable for all reason codes. See specific reason codes for details.
|
Determine the index name and the XML pattern clause. The index name (<index-name>,<index-schema>) can be obtained from SYSCAT.INDEXES by issuing the following query using index-id: After the index name (<index-name>,<index-schema>) is found, it can be used to obtain the index data type and XML pattern from SYSCAT.INDEXES by issuing the following query: If the <xml-schema-id> is not "*N", obtain the name of the XML schema containing the identified schema data type by issuing the following query using <xml-schema-id>:
sqlcode: -20305 sqlstate: 23525 |
SQL20306N |
An index on an XML column cannot be created because of an error detected when inserting the XML values into the index. Reason code = reason-code. For reason codes related to an XML schema the XML schema identifier = xml-schema-id and XML schema data type = xml-schema-data-type. |
The statement cannot proceed and the table remains unchanged because of one of the following reason codes. The schema data type and schema identifier are not applicable for all reason codes.
|
Determine the XML pattern clause from the index definition. If the <xml-schema-id> is not "*N", obtain the name of the XML schema containing the identified schema data type by issuing the following query using <xml-schema-id>:
sqlcode: -20306 sqlstate: 23526 |
SQL20307N |
Table source-tablename cannot be attached to table target-tablename. Reason code = reason-code. |
The characteristics of the target table do not sufficiently match the characteristics of the source table in the ALTER TABLE...ATTACH statement. The reason-code indicates the type of mismatch.
|
Correct the mismatch between the tables by modifying the source table to match the characteristics of the target table, or by modifying the target table to match the characteristics of the source table. For reason codes 4, 5, 6 and 11 the characteristics of neither the source or target table can be easily modified for compatibility. (For reason code 5, source-tablename is partitioned, so it must have exactly one visible (neither attached or detached) data partition.) In cases where it is difficult to modify the characteristics of either the source or target table for compatibility, create a new table that is compatible with the target table, and copy the data from source-tablename to this new table.
sqlcode: -20307 sqlstate: 428GE |
SQL20308N |
Parsing with the STRIP WHITESPACE option is not allowed when the input includes a text node string value with only whitespace characters that is more than 1000 bytes long. |
The option to STRIP WHITESPACE during XML parsing will fail if a text node string value is encountered that consists only of whitespace characters and has a length of more than 1000 bytes. The statement cannot be processed. |
Use the PRESERVE WHITESPACE option or modify the input to remove whitespace in excess of 1000 bytes from any text nodes with a string value consisting of only whitespace characters. sqlcode: -20308 sqlstate: 54059 |
SQL20309N |
Invalid use of an error tolerant nested-table-expression. |
An error tolerant nested-table-expression (a nested-table-expression that specifies the RETURN DATA UNTIL clause) cannot be referenced in the following places:
The statement cannot be processed. |
Remove the RETURN DATA UNTIL clause of the nested-table-expression and resubmit the statement. sqlcode: -20309 sqlstate: 428GG |
SQL20316N |
Invalid compilation environment. Reason code = reason-code. |
The compilation environment provided is invalid for the reason specified in the accompanying reason code.
The statement cannot be executed. |
The action is based on the reason codes as follows:
sqlcode: -20316 sqlstate: 51040 |
SQL20317N |
The command or statement failed because the operation is only supported when there is at least one storage group defined for the database against which the command or statement was executed. |
Automatic storage simplifies storage management for table spaces. When you create a storage group, you specify the storage paths where the database manager will place your data. After a storage group is created in a database, there is always a default storage group for the database. As you create and populate automatic storage table spaces, the database manager will manage the container and space allocation for those automatic storage table spaces to use the default or specified storage group. This message is returned when an attempt is made to perform an action that require a storage group against a database that has no storage groups defined, such as the following examples:
|
To use automatic storage functionality with this database, create at least one storage group. sqlcode: -20317 sqlstate: 55060 |
SQL20318N |
The ALTER TABLESPACE statement failed because the change is not allowed for the type of table space. Table space name: tablespace-name. Table space type: tablespace-type. Incompatible clause: clause. |
The following are operations that are incompatible with a corresponding table space type, as indicated.
|
Rewrite the ALTER TABLESPACE statement to ensure that the operations are compatible with the table space type. sqlcode: -20318 sqlstate: 42858 |
SQL20319N |
The SET TABLESPACE CONTAINERS command is not allowed on an automatic storage table space. |
Containers associated with automatic storage table spaces are under the control of the database and cannot be redefined via the SET TABLESPACE CONTAINERS command. |
To specify a new set of paths for all automatic storage table spaces in the database, use the ON option of the RESTORE DATABASE command and specify one or more paths. sqlcode: -20319 sqlstate: 55061 |
SQL20320N |
The maximum size specified for the table space is not valid. |
The maximum size specified in the CREATE TABLESPACE or ALTER TABLESPACE statement is not valid. If creating the table space, the maximum size must be greater than or equal to the initial size specified. If altering an existing table space, the maximum size must be greater than or equal to the current size of the table space. |
Specify a larger value for the maximum size as described in this message's Explanation. sqlcode: -20320 sqlstate: 560B0 |
SQL20321N |
The command failed because storage paths cannot be provided when there are no storage groups in the database. |
The database in the backup image does not define a storage group but storage paths are being provided in one of the following ways:
Prior to Version 10, a database in the backup image had to be defined to use automatic storage in order to specify storage paths. This message is returned by database servers prior to Version 10 when an attempt is made to perform an action that requires automatic storage in a database backup image that has not been enabled for automatic storage. |
Resolve the problem using the appropriate action:
sqlcode: -20321 sqlstate: 55062 |
SQL20322N |
The database name provided does not match server-name, the name of the database that the application is connected to. |
The database name does not match server-name, the name of the database that the application is currently connected to. The database name was either explicitly specified or determined by the specified database alias name. |
If the intention is to alter the database that you are currently connected to, either remove the database name from the statement or specify the correct name. If the intention is to alter the database with the given name, and not the database you are currently connected to, disconnect from the current database and connect to the specified database before resubmitting the statement. If you are backing up or restoring a database, connect to that database and provide the correct database name or database alias name. sqlcode: -20322 sqlstate: 42961 |
SQL20323N |
The storage path storage-path already exists for the storage group or is specified more than once. |
Either a storage path being added already exists for the storage group, or there are duplicates within the list being provided. |
Remove the path from the command or statement and resubmit the command or statement. sqlcode: -20323 sqlstate: 42748 |
SQL20324N |
The operation operation is already in progress. |
The operation operation has already been issued in this transaction or it has been issued as part of a separate uncommitted transaction. |
Commit the transaction with the outstanding operation and reissue the statement. sqlcode: -20324 sqlstate: 25502 |
SQL20325N |
Adding, extending, or setting containers for table space tablespace-name would exceed the maximum size max-size. |
Table space tablespace-name has AUTORESIZE set to YES with a defined maximum size. However, the amount of space being added to the table space by the ALTER TABLESPACE statement or set by the SET TABLESPACE CONTAINERS command is resulting in the size of the table space being greater than this maximum size. |
If executing an ALTER TABLESPACE statement then before resubmitting the statement, increase MAXSIZE for the table space such that it is greater than or equal to the current size of the table space plus the amount of space being added. Alternately, set AUTORESIZE to NO for the table space. Note that disabling auto-resize will result in the current values of MAXSIZE and INCREASESIZE being lost. If executing the SET TABLESPACE CONTAINERS command then specify a set of containers that has a total size less than or equal to the maximum size of the table space. sqlcode: -20325 sqlstate: 54047 |
SQL20326N |
An XML element name, attribute name, namespace prefix or URI ending with string exceeds the limit of 1000 bytes. |
The system is processing an element name, attribute name, namespace prefix or a URI to generate an internal identifier for the string. The length of the string exceeds the limit of 1000 bytes for the string when represented in UTF8. The value of string gives the ending characters of the string that exceeded the limit. The statement cannot be processed. |
Try to use shorter element names, attribute names, namespace prefixes or URIs and then try the operation again. sqlcode: -20326 sqlstate: 54057 |
SQL20327N |
The internal representation of an XML path exceeds the limit of 125 levels. |
The system is generating an internal representation of an XML path. The path may exist in an XML document that is being parsed or validated or in an XML value that is being constructed. The limit is reached because the document is nested too deep. The statement cannot be processed. |
For a document or constructed XML value, reduce the number of levels of elements and attributes that are used. sqlcode: -20327 sqlstate: 54058 |
SQL20328N |
The document with target namespace namespace and schema location location already has been added for the XML schema identified by schema-name. |
This error can occur while invoking the XSR_ADDSCHEMADOC stored procedure. Within an XML schema, there cannot be two documents with the same targetnamespace and schemalocation. The statement cannot be processed. |
Change either the namespace or schemalocation of the document that is being added. sqlcode: -20328 sqlstate: 42749 |
SQL20329N |
The completion check for the XML schema failed because one or more XML schema documents is missing. One missing XML schema document is identified by uri-type as uri. |
The XML schema registration completion processing determined that more than one XML schema document is required for a complete XML schema and at least one XML schema document is missing from the XML schema repository. The missing XML schema document is identified by the either targetnamespace or schemalocation uri-type and the value for the namespace or XML schema location uri. The reference to the missing XML schema document may be included in one of the XML schema documents that is defined for the XML schema. The statement cannot be processed. |
Add any missing XML schema documents for the XML schema to the XML schema repository. The document identified by uri-type as uri must be added. sqlcode: -20329 sqlstate: 428GI |
SQL20330N |
The xsrobject-type identified by the XML uri-type1 uri1 and XML uri-type2 uri2 is not found in the XML schema repository. |
Processing of the statement or command required the use of an XSROBJECT from the XML schema respository that could not be found. If the xsrobject-type is XMLSCHEMA, then an XML schema is required for validation of an XML value. The uri-type1 is NAMESPACE and the XML schema target namespace uri1 may have been identified explicitly in the statement using the ACCORDING TO XMLSCHEMA URI clause or may be identified in the XML value. If the optional LOCATION clause is also specified, then uri-type2 is LOCATION and uri2 indicates this value, otherwise it is an empty string. If the xsrobject-type is EXTERNAL ENTITY, then an XML external entity is required for parsing or validation of an XML value. The identification of the external entity is based on uri-type1 of SYSTEM ID with the system identifier as uri1 and uri-type2 of PUBLIC ID with the public identifier as uri2. If uri2 is empty, then no public identifier was available. The statement or command cannot be processed. |
Register the XML schema or XML external entity identified by uri1 and uri2 before processing the XML value. sqlcode: -20330 sqlstate: 22532, 4274A |
SQL20331N |
The XML comment value string is not valid. |
The XML comment cannot contain two adjacent hyphens and cannot end in a hyphen. |
Ensure the value for the XML comment is valid. sqlcode: -20331 sqlstate: 2200S |
SQL20332N |
The XML processing instruction value string is not valid. |
The XML processing instruction must not contain the substring '?>'. |
Ensure the value for the XML processing instruction is valid. sqlcode: -20332 sqlstate: 2200T |
SQL20333N |
The operation could not be performed because it violated an integrity constraint at data source data-source. Associated text and tokens are tokens. |
The insert, update, or delete operation violated an integrity constraint defined at a federated data source. The violation could be due to the interaction of a trigger at the data source. The statement could not be executed. The contents of the object table are unchanged. Some data sources do not provide specific information about the constraint that was violated. Other data sources provide more information in the db2diag log file. |
Examine the constraints on the object referenced by the operation to determine the cause of the violation. Look in the db2diag log file for more information about the constraint that was violated. sqlcode: -20333 sqlstate: 23527 |
SQL20334N |
A SOAP Fault was received from the web services data source tokens. Associated text and tokens are text-and-tokens. |
The web services data sourcedata-source-name that is using the Simple Object Access Protocol (SOAP) sent a SOAP Fault to the federated server. Further information about this error situation is in tokens. |
Use the information provided intokens to identify and correct the root cause of the SOAP Fault at the data source, data-source-name. sqlcode: -20334 sqlstate: 560CB |
SQL20335N |
More than one xsrobject-type exists identified by XML uri-type1 uri1 and uri-type2 uri2 exists in the XML schema repository. |
There is more than one registered XSROBJECT that matches the URI used to identify an XML schema or external entity. If xsrobject-type is XMLSCHEMA, then identification for the XML schema is based on uri-type1 of NAMESPACE with the XML schema target namespace as uri1 and uri-type2 of LOCATION with XML schema location as uri2. If ui2 is empty, then no schema location was specified. If xsrobject-type is EXTERNAL ENTITY, then identification for the external entity is based on uri-type1 of SYSTEM ID with the system identifier as uri1 and uri-type2 of PUBLIC ID with the public identifier as uri2. If uri2 is empty, then no public identifier was specified. The statement cannot be processed. |
If both uri1 and uri2 are indicated, then either drop duplicate XSROBJECTs of type xsrobject-type from the XML schema repository or, for XML schemas, explicitly specify the XMLSCHEMA ID for one of these XML schemas. If the schema location (uri2) is empty, it may also be possible to explictly specify XMLSCHEMA URI and LOCATION to uniquely identify an XML schema. sqlcode: -20335 sqlstate: 22533, 4274B |
SQL20336N |
A value with data type source-data-type cannot be XMLCAST to type target-data-type. |
The statement contains a CAST with the first operand having a data type of source-data-type to be cast to the data type target-data-type. This cast is not supported. |
Change the data type of either the source or target so that the cast is supported. For predefined data types these are documented in the SQL Reference. For a cast involving a user-defined distinct type, the cast can be between the base data type and the user-defined distinct type or from a data type that is promotable to the base data type to the user-defined distinct type. sqlcode: -20336 sqlstate: 42846 |
SQL20337N |
The BY REF clause is missing or used incorrectly. Reason code=reason-code. |
The following explain the error based on possible values for reason-code.
|
Take the following action based on the reason-code.
sqlcode: -20337 sqlstate: 42636 |
SQL20338N |
The data type of either the source or target operand of an XMLCAST specification must be XML. |
The XMLCAST specification must have one operand that has the data type XML. The XMLCAST operation can be from an XML type value to an SQL type value or from an SQL type value to and XML type value. The XMLCAST specification also accepts having both the source and target operands as XML but no actual casting operation is performed in this case. |
If both operands are SQL data types other than XML, use the CAST specification. Otherwise, change the XMLCAST specification so that at least one operand is the XML data type. sqlcode: -20338 sqlstate: 42815 |
SQL20339N |
The XML schema xmlschema-name is not in the correct state to perform operation operation. |
The operation specified by operation cannot be performed on the XML schema identified by the XML schema identifier xmlschema-name because it is not in the correct state. For example, the XML schema has already been completed and the operation is attempting to add additional XML schema documents. The statement cannot be processed. |
Check the current state of the XML schema to determine the operations that are valid for the XML schema. If the XML schema is completed, no further XML schema documents can be added. sqlcode: -20339 sqlstate: 55063 |
SQL20340N |
The XML schema xmlschema-name includes at least one XML schema document in namespace namespace with component ID component-id that is not connected to the other XML schema documents in the same namespace using an include or redefine. |
The XML schema identified by identifier xmlschema-name includes multiple XML schema documents in the namespace namespace. At least one of these XML schema documents is not connected to the other XML schema documents in the same namespace using an include or redefine. One such XML schema document is identified in the XML schema repository with component identifier component-id. The statement cannot be processed. |
Correct the XML schema documents so that all XML schema documents within a namespace are connected using an include or a redefine. The component-id can be used to query SYSCAT.XSROBJECTCOMPONENTS for further information about the specifically reference XML schema document that is not connected within the namespace. sqlcode: -20340 sqlstate: 22534 |
SQL20341W |
Transfer operation ignored since auth-ID is already the owner of the database object. |
The TRANSFER statement specified to transfer the database object to authorization ID auth-ID. The authorization ID is already the owner of the database object. There is no need to transfer the database object. |
No action is required. sqlcode: +20341 sqlstate: 01676 |
SQL20342N |
auth-ID does not have one or more required privileges privilege-list on object object-name of type object-type necessary for ownership of the object. |
The TRANSFER statement attempted to transfer ownership of the object to authorization ID auth-ID which does not have the necessary privileges to be the owner of the object. The privileges privilege-list on the object object-name are the privileges that are missing. The statement cannot be processed. |
Grant the authorization ID auth-ID all the privileges necessary, as indicated by privilege-list, on object object-name, for the authorization ID to be the owner of the object being transferred. sqlcode: -20342 sqlstate: 42514 |
SQL20344N |
Transferring ownership of object-name1 failed because of a dependency involving object-name2. Reason code: reason-code. |
When an object is created, one authorization ID is assigned ownership of the object. Ownership means the user is authorized to reference the object in any applicable SQL or XQuery statement. You can transfer ownership of a database object by using the TRANSFER OWNERSHIP statement. This message is returned when an attempt to transfer the ownership of an object fails. The reason code indicates the specifics of the failure:
|
Respond to this message according to the reason code:
sqlcode: -20344 sqlstate: 429BT |
SQL20345N |
The XML value is not a well-formed document with a single root element. |
The XML value is not a well-formed document. An XML value that is being stored in a table or validated must be a well-formed XML document with a single root element. The document node of the XML value must not have any text node children, although it can have comment node or processing instruction node children. The statement cannot be processed. |
Storing or validating the XML value requires that the XML value be modified so that it is a well-formed document with a single root element. If the document is well-formed, ensure that the document node of the XML value has only a single element node as a child and no text node child. Otherwise, do not attempt store or validate the XML value. sqlcode: -20345 sqlstate: 2200L |
SQL20346N |
The XML schema xmlschema-id does not contain a global element named element-local-name in namespace namespace-uri. |
A validation operation specified that an explicit element local name element-local-name in namespace namespace-uri should be the root element of the XML document to be validated. However, the XML schema with SQL identifier xmlschema-id does not have element-local-name declared as a global element in namespace namespace-uri. The statement cannot be processed. |
Check that the element local name element-local-name in namespace namespace-uri is correct for the XML schema and the XML document that is being validated. Change the element local name, namespace or the XML schema and try the validation again. sqlcode: -20346 sqlstate: 22535 |
SQL20347N |
The XML value does not contain a root element named element-local-name in namespace namespace-uri. |
The root element of the XML document does not match the required element local name element-local-name in namespace namespace-uri specified for validation. The statement cannot be processed. |
Provide an XML value where the root element matches with the specified element local name and namespace. If the XML value is correct, change the specified element local name or namespace. sqlcode: -20347 sqlstate: 22536 |
SQL20349N |
The user mappings from the user mapping repository for plugin plugin-name cannot be accessed. Reason code reason-code. |
The user mapping from the user mapping repository for plugin plugin-name cannot be accessed. The cause of the error is indicated by the reason-code:
|
See the federation documentation for details on user mapping plugins. The action is based on the reason-code as follows:
sqlcode: -20349 sqlstate: 429BU |
SQL20350N |
Authentication at the user mapping repository for plugin plugin-name failed. |
The user mapping from the user mapping repository for plugin plugin-name cannot be accessed because authentication at the user mapping repository failed. |
See the federation documentation for details on user mapping plugins. Correct the repository connection credential parameters of the plugin. sqlcode: -20350 sqlstate: 42516 |
SQL20351W |
Wrapper options were ignored for servers of wrapper wrapper-name that already have the plugin defined. |
The existing DB2_UM_PLUGIN related options specified for a server are not overwritten when DB2_UM_PLUGIN related options of the corresponding wrapper are created or altered. |
To change the DB2_UM_PLUGIN related options that are already specified for a server, alter the server options directly. sqlcode: +20351 sqlstate: 01677 |
SQL20352W |
Changes to the user mapping apply only to the federated catalog table and not to the external user mapping repository. |
The DB2_UM_PLUGIN option has been set for the server. User mappings for this server are read from the external user mapping repository, however CREATE USER MAPPING, ALTER USER MAPPING, and DROP (USER MAPPING) statements only affect user mappings in the federated catalog table. |
Use another interface to the external user mapping repository to create, alter, or drop the user mappings. sqlcode: +20352 sqlstate: 01678 |
SQL20353N |
An operation involving comparison cannot use operand name defined as data type type-name. |
The use of the value identified by name defined as data type type-name is not permitted in operations involving comparisons. An expression resulting in a type-name data type is not permitted in:
The statement cannot be processed. |
The requested operation on the data type type-name is not supported. You may be able to change the data type of the value to a data type that is supported using a cast or some other function. sqlcode: -20353 sqlstate: 42818 |
SQL20354N |
Invalid specification of a row change timestamp column for table table-name. |
The specification of a row change timestamp column is invalid for one of the following reasons. A row change timestamp column cannot:
The statement cannot be executed. |
Correct the syntax and resubmit the statement. sqlcode: -20354 sqlstate: 429BV |
SQL20356N |
The table table-name cannot be truncated because DELETE triggers exist for the table, or the table is the parent in a referential constraint. |
The TRUNCATE statement could not be processed for one of the following reasons:
The statement cannot be processed. |
If the statement failed because of the existence of DELETE triggers, specify the IGNORE DELETE TRIGGERS clause on the TRUNCATE statement. If the statement failed because of referential constraints, use the ALTER TABLE statement to drop the referential constraints, and then re-issue the TRUNCATE statement. sqlcode: -20356 sqlstate: 428GJ |
SQL20357N |
One or more federated one-phase commit data source sites have failed commit or rollback processing. As a result, the transaction outcome might not be consistent across all sites. Subsequent SQL statements can be processed. Reason code reason-code. |
A federated server has sent a transaction commit or rollback request and one or more of the federated one-phase commit data source sites cannot complete the request. This may be caused by a server failure, communication link failure, or other failure. The transaction is not completely committed or rolled back. The reason code indicates the specific situation.
|
Check the administration notification log for details. Compensating actions may need to be applied manually at the federated one-phase commit data source sites. It may be necessary to contact the system administrator for assistance. For reason 5, disconnect the application from the federated server, e.g. issue a 'connect reset' clp command and reconnect. sqlcode: -20357 sqlstate: 40003 |
SQL20358N |
Commit or rollback processing encountered an error. The transaction at some federated two-phase commit data source sites could be indoubt. Subsequent SQL statements can be processed. Reason code reason-code. |
A federated server has sent a transaction commit or rollback request and one or more of the federated two-phase commit data source sites cannot complete the request. This may be caused by a server failure, communication link failure, or other failure. The transaction might be indoubt at the federated two-phase commit data source site. The reason code indicates the specific situation.
|
Determine the cause of the error. It may be necessary to contact the system administrator for assistance since the most common cause of the error is a federated server failure, federated data source site failure, or connection failure. For a federated server failure, the RESTART DATABASE command will complete the commit or rollback processing for this transaction. For a federated data source site failure, restart the failed data source. For a connection failure, consult with your network administrator and/or communication expert to determine the cause of the problem. For reason 3, check possible indoubt transactions on the federated data source site, and manually resolve them if existing. For reason 4, disconnect the application from the federated server, e.g. issue a 'connect reset' clp command and reconnect. sqlcode: -20358 sqlstate: 08007 |
SQL20360W |
A trusted connection cannot be established for the specified authorization ID. |
A trusted connection cannot be established for the specified authorization ID. A matching trusted context is not currently defined or the server does not support trusted context. The attempt to create a trusted connection was not successful and a normal connection was created. Federated system users: If this message is returned during a federated request, then the attempt to create a trusted connection between the federated database and the remote server was not successful, and a normal connection was created instead. |
Ensure that the server supports trusted contexts and that the trusted context has been correctly defined, and try to re-establish a trusted connection. Federated system users: Ensure that the remote server supports trusted contexts and that the trusted context has been correctly defined on the remote server. sqlcode: +20360 sqlstate: 01679 |
SQL20361N |
The switch user request using authorization ID authorization-name within trusted context context-name failed with reason code reason-code. |
The switch user request within the trusted context context-name failed. The trusted connection is in an unconnected state. |
Use the authorization ID authorization-name and the following explanations for reason code reason-code to determine what action to take.
sqlcode: -20361 sqlstate: 42517 |
SQL20362N |
Attribute attribute-name with value value cannot be dropped or altered because it is not part of the definition of trusted context context-name. |
Attribute attribute-name was specified for a trusted context, but the trusted context is not defined with an attribute with this name. The statement could not be processed. |
Remove the name of the unsupported attribute and re-issue the statement. sqlcode: -20362 sqlstate: 4274C |
SQL20363N |
Attribute attribute-name with value value is not unique for trusted context context-name. |
During the create or alter of trusted context context-name, a duplicate value value was specified for the attribute-name attribute. Each pair of attribute name and value must be unique for a trusted context. The statement cannot be processed. |
Remove the non-unique specification of attribute-name and and re-issue the statement. sqlcode: -20363 sqlstate: 4274D |
SQL20364N |
The identifier with the name name at ordinal position number in the statement is too long. |
At least one identifier in the described statement is too long to fit in the destination buffer. The first name that is too long is identified by the name name and ordinal position number. If performing a describe output of a prepared query, the ordinal position is relative to the select list column of the query. If performing a describe output of a CALL statement, the ordinal position is relative to the OUT or INOUT parameters of the procedure to which the CALL resolved. If performing a describe input of a CALL statement, the ordinal position is relative to the IN or INOUT parameters of the procedure to which the CALL resolved. The column name, parameter name, user defined type name or user defined type schema name was either too long, or became too long after code page conversion. Note that the lengths of the column name, parameter name, user defined type name, and user defined type schema name are limited when using the SQLDA structure. |
Do one of the following:
sqlcode: -20364 sqlstate: 42622 |
SQL20365W |
A signaling NaN was encountered in an arithmetic operation or function involving DECFLOAT |
A signaling NaN (sNaN) was encountered in an expression, arithmetic operation, or function involving a DECFLOAT column or value. The result is NaN |
To stop the warning from being returned, find the tuple or tuples containing a signaling NaN and exclude them from the query. sqlcode: +20365 sqlstate: 01565 |
SQL20371W |
The ability to use trusted context context-name was removed from some, but not all authorization IDs specified in the statement. |
An ALTER TRUSTED CONTEXT statement for context-name contained a DROP USE FOR clause with multiple authorization IDs or PUBLIC, but one or more authorization IDs were not defined to use the trusted context. One or more users were removed from the definition of the trusted context, but one or more other users were not previously allowed to use the trusted context. The statement was processed. |
Verify that the ability to use the trusted context was removed from all of the authorization IDs that was intended. sqlcode: +20371 sqlstate: 01682 |
SQL20372N |
The trusted context context-name specified authorization ID authorization-name which is already specified for another trusted context. |
A CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT statement for context-name specified SYSTEM AUTHID authorization-name, but this authorization ID is already defined to use a different trusted context. A system authorization ID that is defined as the SYSTEM AUTHID for a trusted context cannot be associated with any other trusted context as the SYSTEM AUTHID. Use the following query to determine which trusted context is already using the authorization ID: The statement could not be processed. |
Change the authorization ID to be the system authorization ID for the trusted context and reissue the CREATE or ALTER statement. sqlcode: -20372 sqlstate: 428GL |
SQL20373N |
A CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT statement specified authorization-name more than once or the trusted context is already defined to be used by this authorization ID or PUBLIC. |
The statement specified that authorization-name be allowed to use the trusted context, but the specified authorization ID or PUBLIC is already defined to use the trusted context, or the authorization ID was specified more than once in the statement. The authorization ID or PUBLIC must not already be allowed to use the trusted context, and it can only be specified once within a statement for a trusted context. The statement could not be processed. |
If the authorization ID or PUBLIC was specified more than once, remove the extra specifications of authorization-name, and re-issue the statement. If an ALTER TRUSTED CONTEXT statement contained an ADD USE FOR clause, and the trusted context already was defined for use by that authorization ID or PUBLIC, use the REPLACE USE FOR clause instead to redefine the usage characteristics for the specified users to use the trusted context. sqlcode: -20373 sqlstate: 428GM |
SQL20374N |
An ALTER TRUSTED CONTEXT statement for context-name specified authorization-name but the trusted context is not currently defined to be used by this authorization ID or PUBLIC. |
An ALTER TRUSTED CONTEXT statement for context-name attempted to replace or remove the ability for authorization-name to use the trusted context, but the specified authorization ID or PUBLIC is not currently defined to use the trusted context. The statement could not be processed. |
If an ALTER TRUSTED CONTEXT statement contained a REPLACE USE FOR clause, and the trusted context was not already defined for use by that authorization ID or PUBLIC, use the ADD USE FOR clause instead to define the trusted context to be used by the specified users. If the ALTER TRUSTED CONTEXT statement contained the DROP USE FOR clause, none of the specified authorization IDs or PUBLIC were currently defined to use the trusted context. sqlcode: -20374 sqlstate: 428GN |
SQL20377N |
An illegal XML character hex-char was found in an SQL/XML expression or function argument that begins with string start-string. |
An SQL/XML expression or function attempted to convert an SQL string value from one of the arguments to an XML string, but the string included a character at Unicode code point hex-char that is not a legal XML 1.0 character. The character is included in a string that begins with the string start-string. The value for hex-char represents the illegal character as a Unicode code point in the form "#xH", where H is one or more hexadecimal characters. The following set of Unicode characters (defined using a regular expression) are allowed: #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]. Examples of the SQL/XML expression or function that may encounter this error are XMLCAST, XMLELEMENT, XMLFOREST, XMLAGG, XMLDOCUMENT, XMLTEXT, XMLATTRIBUTES, XMLQUERY, or XMLTABLE. The statement cannot be processed. |
Remove the illegal character hex-char or replace it with a character that is allowed. sqlcode: -20377 sqlstate: 0N002 |
SQL20379N |
An authorization ID cannot use its SECADM authority to transfer the ownership of an object to itself. |
An authorization ID that has the SECADM authority cannot transfer the ownership of an object it does not already own to itself. It can, however, transfer the ownership of the object to another authorization ID. The statement cannot be processed. |
Choose a different authorization ID as the new owner of the object. sqlcode: -20379 sqlstate: 42502 |
SQL20383W |
Errors were encountered and tolerated as specified by the RETURN DATA UNTIL clause. |
At least one error as specified by the RETURN DATA UNTIL clause was encountered and tolerated, with execution continuing for the query. The results of the query might not be the same as they would be if the error had not occurred. |
Be aware that the query results might not be complete. If appropriate, check the source of the tolerated error and correct the situation. sqlcode: +20383 sqlstate: 02506 |
SQL20384W |
The specified locale is not supported. The message was returned in the English locale. |
The specified locale is not supported by the database manager. |
Refer to the Administration Guide: Planning for the "Supported code pages and territories" or refer to the DB2 infocenter for the supported server languages and the corresponding locale values. sqlcode: +20384 sqlstate: 01684 |
SQL20386N |
An XQuery expression cannot be specified in a DECLARE CURSOR statement. |
The DECLARE CURSOR statement does not allow an XQuery expression to be specified directly following the FOR keyword. An XQuery expression can only be associated with a cursor using a prepared statement name. |
Remove the XQuery expression from the DECLARE CURSOR statement and replace it with a statement name. Prepare the XQuery expression by issuing a PREPARE statement using the same statement name. sqlcode: -20386 sqlstate: 42637 |
SQL20387N |
Two or more elements are specified for the security label component component-name. |
A security label cannot have multiple elements for a component of type ARRAY. |
Specify only one element for the security label component component-name. sqlcode: -20387 sqlstate: 428GP |
SQL20388N |
Too many elements are specified for the security label component component-name. |
A security label component of type SET or TREE can have no more than 64 elements. More than this number are specified for security label component component-name. For a security label component of type ARRAY, the maximum number of elements is 65 535. If elements are added via the ALTER SECURITY LABEL COMPONENT statement, the actual limit may be lower than this maximum due to the way DB2 assigns an encoded value to each new element. |
For TREE and SET security label components, remove elements so that there are no more than 64. For ARRAY security components, if the maximum has not been reached, drop and create the component again with all the desired elements specified. sqlcode: -20388 sqlstate: 54061 |
SQL20389N |
The component element element is not defined in the security label component component-name. |
The component element element does not exist in the definition of security label component component-name. |
Provide a valid element for the component. You can submit the following query to list the valid elements for the security label components: If you get this error when executing the scalar function SECLABEL, then also check the security label string to make sure that the values are listed in the same order that their components are listed in the security policy. sqlcode: -20389 sqlstate: 4274F |
SQL20390N |
The security label component component-name is not defined in the security policy security-policy so that component cannot be used in the security label security-label. |
Security labels can only contain values for those components that are defined in the security policy that the label is part of. The security label component component-name is not part of the security policy security-policy. The security label security-label is part of that security policy so the component component-name cannot be used in that security label. |
Provide a security label component that is part of the security policy security-policy. You can execute the following query to list the security label components that are part of the security policy: sqlcode: -20390 sqlstate: 4274G |
SQL20391N |
Label-based access control cannot be applied to the column column-name because there is no security policy associated with the table. |
In order to use the SECURED WITH clause with column column-name or to define it with a data type of DB2SECURITYLABEL, a security policy must be associated with the table. |
Add a security policy to the table using the SECURITY POLICY clause of the CREATE TABLE statement or the ADD SECURITY POLICY clause of the ALTER TABLE statement. sqlcode: -20391 sqlstate: 55064 |
SQL20392N |
The table table already has a security policy. |
A table can have at most one security policy. Once associated, a security policy cannot be changed for a table. |
Do not try to assign another security policy to the table. sqlcode: -20392 sqlstate: 55065 |
SQL20393N |
The maximum number of components in security policy security-policy has been exceeded. |
A security policy can have maximum of 16 components. |
Reduce the number of components specified for the security policy security-policy. sqlcode: -20393 sqlstate: 54062 |
SQL20394N |
The access rule access-rule does not exist in the rule set used by the security policy policy-name. |
The access rule access-rule specified in the GRANT EXEMPTION or REVOKE EXEMPTION statement is not part of the LBAC rule set that is used by the security policy policy-name. |
The specified access rule does not exists for in the rule set used by the specified security policy. sqlcode: -20394 sqlstate: 4274H |
SQL20395N |
The GRANT of security label security-label1 conflicts with security label security-label2 that is also granted to authorization ID authorization-name. |
If the user, group, or role is granted two distinct labels, one for WRITE access and another for READ access, they must satisfy the following rules:
|
Grant a different security label or make one of these modifications to the security label that is being granted:
sqlcode: -20395 sqlstate: 428GQ |
SQL20396N |
The security label named security-label-name cannot be found for the security policy policy-name. |
The security label named security-label-name cannot be found for the security policy policy-name. This caused execution of the built-in function SECLABEL_BY_NAME to fail. |
Check the spelling of security-label-name. Make sure you are using the correct security policy name. sqlcode: -20396 sqlstate: 4274I |
SQL20397W |
Routine routine-name execution has completed, but at least one error, error-code, was encountered during the execution. More information is available. |
Routine routine-name execution has completed. At least one error was encountered during the internal execution of the requested function. The last error encountered was error-code. More detailed information on the errors encountered is available. For the ADMIN_CMD routine, its output parameter and result set, if any, have been populated. |
Retrieve the output parameter and result set, if any, for more information on the errors encountered. If message files were generated during the execution, examine their content and resolve the error situations. If appropriate, reinvoke the routine again. sqlcode: +20397 sqlstate: 01H52 |
SQL20401N |
The table cannot be protected by a security policy because an MQT or staging table named object-name depends on the table. |
The table cannot be protected with LBAC because, a materialized query table (MQT) or staging table depends on the table. |
If appropriate, drop the MQT or staging table object-name and resubmit the statement. sqlcode: -20401 sqlstate: 55067 |
SQL20402N |
Authorization ID auth-id does not have the LBAC credentials to perform the operation-name operation on table table-name. |
The authorization ID auth-id is not allowed to perform operation operation-name on the table table-name. A user is not allowed to insert, update or delete a row in a protected table or alter the table to become a protected table if they do not have appropriate security label and/or exemption credentials. |
Ask your database security administrator to grant the authorization ID auth-id the proper security label or exemptions required to perform the insert, update or delete operation. To alter the table to become a protected table, a grant of a security label for WRITE access is required. sqlcode: -20402 sqlstate: 42519 |
SQL20403N |
The authorization ID auth-id already has a security label (security-label) for access-type access. |
Each authorization ID can have at most one security label for WRITE access and at most one for READ access. The security label security-label has already been granted to the authorization ID auth-id for access-type access. |
If you want to change the security label used for access-type access you must first use the REVOKE SECURITY LABEL statement to revoke the security label security-label from authorization ID auth-id. sqlcode: -20403 sqlstate: 428GR |
SQL20404N |
The security label object policy-name.object-name cannot be dropped because it is currently in use. Reason code reason-code. |
The security label object object-name could not be dropped. The reason it could not be dropped is specified by the reason code reason-code:
|
The user response corresponding to the reason code is:
sqlcode: -20404 sqlstate: 42893 |
SQL20405N |
The security policy object object-name cannot be dropped because it is currently in use. Reason code reason-code. |
The security object object-name could not be dropped. The reason it could not be dropped is specified by the reason code reason-code:
|
The user response corresponding to the reason code is:
sqlcode: -20405 sqlstate: 42893 |
SQL20406N |
The security label component object object-name cannot be dropped because it is part of a security policy. |
The security label component object object-name cannot be dropped because one or more security policies refer to it. |
Drop all the security policies that refer to this security component. The following query can be used find all the security policies that refer to this security component:
sqlcode: -20406 sqlstate: 42893 |
SQL20408N |
Table source-tablename cannot be attached to table target-tablename because column source-columnname of the source table and its associated column target-columnname of the target table do not match. Reason code = reason-code. |
An attribute of the target table column does not match the attribute of the corresponding column (aligned by ordinal position) in the source table in the ALTER TABLE ... ATTACH PARTITION statement. The reason-code indicates the type of mismatch and in which column of the SYSCAT.COLUMNS view to find the table attribute. In cases where it is difficult or impossible to modify the characteristics of either the source or target table for compatibility, you can create a new table that is compatible with the target table, and copy the data from source-tablename to this new table.
|
Correct the mismatch in the tables.
sqlcode: -20408 sqlstate: 428GE |
SQL20409N |
An XML document or constructed XML value contains a combination of XML nodes that causes an internal identifier limit to be exceeded. |
An internal identifier that must be associated with each XML node of an XML value cannot be generated because the combination of the number of levels of XML nodes and the number of children nodes within these levels causes the identifier to overflow. |
For a document or constructed XML value, reduce the number of levels of XML nodes or the number of children nodes especially at the deeper levels of XML nodes. sqlcode: -20409 sqlstate: 560CG |
SQL20410N |
The number of children nodes of an XML node in an XML value has exceeded the limit of limit-number children nodes. |
An expression generated an XML value with an XML node that has a number of children nodes which exceeds the limit of limit-number children nodes. |
Rewrite the expression generating the XML value such that the number of children nodes does not exceed the limit. sqlcode: -20410 sqlstate: 560CH |
SQL20412N |
Serialization of an XML value resulted in characters that could not be represented in the target encoding. |
Serialization of XML data may require conversion to an encoding different from the source UTF-8 encoding. If characters exist in the source encoding that cannot be represented in the target encoding, code page conversion produces substitution characters which are not allowed in the result of XML serialization. |
Choose a target encoding that can represent all characters in the XML value. Unicode encodings are recommended as they can represent all characters. sqlcode: -20412 sqlstate: 2200W |
SQL20413N |
The built-in function SECLABEL_TO_CHAR could not be executed because authorization ID auth-id has had its security label for READ access revoked. |
To execute the built-in function SECLABEL_TO_CHAR, the authorization ID must have a security label for READ access. The security label for READ access has been revoked from authorization ID auth-id. |
Contact the database security administrator or a user with SECADM authority and ask that the security label be granted again. sqlcode: -20413 sqlstate: 42520 |
SQL20414N |
The authority-or-privilege authority or privilege cannot be granted to authorization ID authorization-ID. |
The GRANT statement attempted to grant an authority or privilege to an authorization name that is not allowed to receive that authority or privilege. The statement cannot be processed |
Grant a different authority or privilege or grant it to an authorization ID that can receive the authority or privilege. sqlcode: -20414 sqlstate: 42521 |
SQL20415N |
Update, delete, or Insert into a UNION ALL view failed because one of the underlying tables is protected. |
Updates, deletes, and Inserts are not allowed into a UNION ALL view if that view is created on one or more protected tables. The statement cannot be processed |
Do not update, delete, or insert into the UNION ALL view. sqlcode: -20415 sqlstate: 429BZ |
SQL20416N |
The value provided (seclabel) could not be converted to a security label. Labels for the security policy with a policy ID of policy-id should be correct-length characters long. The value is value-length characters long. |
An INSERT or UPDATE statement specified a value for a column of type DB2SECURITYLABEL. The value cannot be converted to a valid security label because it is not the correct length for security labels that are part of the security policy that is protecting the table. If the seclabel value is *N, then the actual value has been written in the db2diag log file. |
Check the INSERT or UPDATE statement and make sure that the value being set in the security label column is valid for the security policy protecting the table. Sometimes an invalid value can be generated as a result of a SELECT done from a table that is not protected with the same security policy as the target table. You should only copy security labels between tables protected by the same security policy. To get the security policy name for the given policy ID use this SQL query. Replace policy-id with the policy ID number given in the error message. sqlcode: -20416 sqlstate: 23523 |
SQL20417W |
The SQL compilation completed without connecting to the data source data-source-name. Connection error error-text was encountered. |
The federated server could not connect to the data source data-source-name during SQL compilation to determine which features the data source supports. The SQL query has been compiled using default settings. At run time an error may be received because the remote server's capabilities were not correctly determined at compilation time. The error-text contains information about what connection error was encountered. |
Recompile the statement or bind the package again when the data source is available, or if an error tolerant nested table expression is used in the SQL statement, execute the package immediately after the compilation to reduce the chance of the connection state changing between compilation and run time. Use the information in error-text to resolve the error connecting to the data source, if necessary. sqlcode: +20417 sqlstate: 01689 |
SQL20418N |
The database partition group is already assigned to the buffer pool. |
The database partition group that you are attempting to add has already been assigned to the buffer pool. |
Choose another database partition group and try again. sqlcode: -20418 sqlstate: 4274J |
SQL20419N |
For table table-name, authorization ID auth-id does not have LBAC credentials that allow using the security label security-label-name to protect column column-name. |
A user cannot use a security label to protect a column unless that user has LBAC credentials that allow writing to a column protected by the security label. Authorization ID auth-id does not have LBAC credentials that allow write access to data protected by the security label security-label-name and therefore cannot use it to protect column column-name in table table-name. |
Ask a database security adminstrator to grant the authorization ID authid LBAC credentials that allow write access to a column protected by security label security-label-name. sqlcode: -20419 sqlstate: 42522 |
SQL20420N |
For table table-name, authorization ID auth-id does not have LBAC credentials that allow removing the security label security-label-name from column column-name. |
To be able to drop or replace a security label that is protecting a column, an authorization ID must have LBAC credentials that allow both reading from and writing to a column. The authorization ID auth-id does not have LBAC credentials that allow both reading from and writing to a column protected by the security label security-label-name and therefore cannot drop or replace that security label. |
Ask a database security adminstrator to grant the authorization ID authid LBAC credentials that allow both read and write access to a column protected by security label security-label-name. sqlcode: -20420 sqlstate: 42522 |
SQL20421N |
The table table-name is not protected with a security policy. |
A security policy cannot be dropped from a table that is not protected with a security policy. |
Specify a table that is protected with a security policy. sqlcode: -20421 sqlstate: 428GT |
SQL20422N |
The statement failed because the table table-name would only contain hidden columns. |
A CREATE TABLE or ALTER TABLE statement attempted to create or alter table table-name in which all the columns are considered implicitly hidden. This can occur when:
Change the column definition ensuring it includes at least one column that is defined as not hidden. |
Ensure that the table definition includes at least one column that is not defined as implicitly hidden. sqlcode: -20422 sqlstate: 428GU |
SQL20423N |
Error occurred during text search processing on server server-name using index index-name. The error message is text-search-error-msg. |
An error described by text-search-error-msg occurred during the processing of a text search function that used the text search index index-name. |
Use text-search-error-msg to determine the cause of the error. If the error message is truncated, you can see the complete message in the db2diag log file. The first word in text-search-error-msg is an error identifier. If the error identifier starts with 'CIE', use the db2ts command to obtain more details, for example, db2ts help error-identifier. If the error identifier does not start with 'CIE', use the DB2 Text Search documentation to obtain more details about text-search-error-msg. sqlcode: -20423 sqlstate: 38H10 |
SQL20424N |
Text search support is not available. Reason code = reason-code. |
An error occurred while attempting to use text search. The reason code provides more information about the error:
|
Restart the text search instance service and try the operation again. If the error reoccurs, contact your system administrator to ensure that support for text searching has been installed, properly configured, and has been started on your system. sqlcode: -20424 sqlstate: 38H11 |
SQL20425N |
The statement failed because the column named column-name in the table named table-name was specified as an argument to a text search function, but an active text search index does not exist for the specified column. |
Text search processing cannot be performed for the specified column. |
sqlcode: -20425 sqlstate: 38H12 |
SQL20426N |
Conflicting text search administration procedures or commands running on the same index. |
Two or more conflicting administration procedures or commands are running on the same index. |
Invoke the administration procedure or command after the currently running procedure or command completes. If the operation attempted is DISABLE, retry this operation later or use the FORCE option of the command. sqlcode: -20426 sqlstate: 38H13 |
SQL20427N |
An error occurred during a text search administration procedure or command. The error message is text-search-error-msg. |
A text search administration operation failed with an error message text-search-error-msg. |
Use the error message text-search-error-msg to determine the cause of the error. If the message is truncated, you can see the db2diag log file. The first word in text-search-error-msg is an error identifier. If the error identifier starts with 'CIE', use the db2ts command to obtain more details, for example, db2ts help error-identifier. If the error identifier does not start with 'CIE', use the DB2 Text Search documentation to obtain more details about text-search-error-msg. sqlcode: -20427 sqlstate: 38H14 |
SQL20428N |
URI specified in the ACCORDING TO XMLSCHEMA clause is an empty string. |
The target namespace URI specified following the URI keyword or the schema location URI specified following the LOCATION keyword is an empty string. |
Ensure that every target namespace URIs and every schema location URI in the ACCORDING TO XMLSCHEMA clause is a valid URI that is not an empty string. sqlcode: -20428 sqlstate: 428GV |
SQL20429N |
The XML operation operation-name is not allowed on strings that are not FOR BIT DATA on this database. |
The specified operation could not be performed on the string because it is not FOR BIT DATA. operation-name is either XMLPARSE or another prohibited operation. |
The database configuration parameter ENABLE_XMLCHAR is set to NO. To allow XMLPARSE on strings that are not FOR BIT DATA, set ENABLE_XMLCHAR to YES. Note that character substitution may occur if the database is not Unicode and the XML value being parsed contains characters that are not present in the database code page. Alternatively, rework the statement to use a host variable, expression or parameter marker of type XML. sqlcode: -20429 sqlstate: 428GW |
SQL20430N |
Global variable variable-name cannot be set or referenced in this context. |
In some contexts a global variable cannot be set and in other contexts it cannot be referenced. This message can be returned in the following situations:
The statement cannot be processed. |
Remove the unsupported setting or reference of the global variable. sqlcode: -20430 sqlstate: 428GX |
SQL20431N |
ROW CHANGE TIMESTAMP FOR table-designator cannot be returned for the table designator. |
A ROW CHANGE TIMESTAMP FOR table-designator expression is not valid for a table which does not have a column defined as a row change timestamp column. The statement cannot be processed. |
Remove the ROW CHANGE TIMESTAMP FOR expression from the statement or alter the table and add the row change timestamp column. sqlcode: -20431 sqlstate: 55068 |
SQL20432N |
The original XML schema contains schema-component that is enclosed within or referenced by enclosing-schema-component which is not compatible with the updated XML schema. The reason for the incompatibility is: reason-code (reason-string). |
The XML schema specified to update another existing XML schema does not meet the criteria for a compatible XML schema update. The original XML schema contains an element, attribute, or type schema-component that is enclosed within or referenced by the element or attribute enclosing-schema-component which is not compatible with the updated XML schema. The specific reason for the incompatibility is given by reason-code (reason-string).
|
Compare the explanations provided with reason-code (reason-string) and identify the cause of the incompatibility. Next, correct the problem and then resubmit the command to update the XML schema. sqlcode: -20432 sqlstate: 22538 |
SQL20435N |
The SELECT clause includes an ARRAY_AGG function and all invocations of ARRAY_AGG, LISTAGG, XMLAGG, and XMLGROUP functions in the same SELECT clause do not have the same order. |
The SELECT clause includes an ARRAY_AGG and one of the following conditions exists:
|
Change the sort-keys to make them identical, or remove the specification of sort-key in all but one of the function invocations. sqlcode: -20435 sqlstate: 428GZ |
SQL20436N |
The data type specified for an array is not valid. |
The data type specified for an array in the CREATE TYPE statement, CREATE HADOOP TABLE statement with columns of type array, array constructor, argument to UNNEST, argument to ARRAY_AGG, or target of ARRAY_AGG is not valid. The following restrictions apply when specifying a data type.
|
Ensure that the data type specified in a CREATE TYPE (array) statement, a CREATE HADOOP TABLE statement with columns of type array, an array constructor, the argument to UNNEST, the argument to ARRAY_AGG, or as the target of ARRAY_AGG is supported. sqlcode: -20436 sqlstate: 429C2 |
SQL20437N |
The array index operation cannot be applied to an object of a data type that is not ARRAY. |
The array index operation of the form object[array index] cannot be applied to an object whose type is not ARRAY. |
Change the variable or parameter to be of type ARRAY. sqlcode: -20437 sqlstate: 428H0 |
SQL20438N |
The data type of an array index expression is not assignable to the array index type. |
The type of an array index expression in an expression of the form object[array_index] must be assignable to INTEGER if the object is an ordinary array. If the object is an associative array, then the type of the array index expression must be assignable to the data type of the array index (INTEGER or VARCHAR). |
Change the data type of the array index expression to be one that is supported. sqlcode: -20438 sqlstate: 428H1 |
SQL20439N |
Array index with value value is out of range or does not exist. |
The value of an array index for an array element specification or the second argument to TRIM_ARRAY is out of range or the null value. If the array index is specified in an array element specification for an associative array and is valid for the array index data type, the element with array index value value does not exist in the array. |
For an associative array:
For an ordinary array:
sqlcode: -20439 sqlstate: 2202E |
SQL20440N |
Array value with cardinality cardinality is too long. The maximum cardinality allowed is max-cardinality. |
The array value required truncation from its cardinality of cardinality to a maximum cardinality of max-cardinality. A system (built-in) cast or adjustment function was called to transform the value in some way. The truncation is not allowed where the value is used. The array value being transformed is one of the following:
|
Examine the SQL statement to determine where the transformation is taking place. Either the input to the transformation is too long, or the target is too short. Explicitly reduce the cardinality of the input, or increase the cardinality that the target can support. sqlcode: -20440 sqlstate: 2202F |
SQL20441N |
A type-name data type is not supported in the context where it is being used. |
The data type can be specified in multiple contexts, including the following.
The following is a list of some invalid contexts:
|
Refer to the documentation for the most up to date list of supported contexts and for restrictions on the use of this data type. Remove any data types used in unsupported contexts. If referencing the data type in a routine reference from a command interface, invoke the routine from within an SQL PL context or provide a global variable of the specified data type as the routine argument. sqlcode: -20441 sqlstate: 428H2 |
SQL20442N |
There is not enough storage to represent the array value. |
The amount of memory required to represent an array value is larger than the maximum allowed for the system. |
Possible solutions may include:
sqlcode: -20442 sqlstate: 57011 |
SQL20443N |
The value for attribute attribute-name cannot exceed length. |
An attribute specified for a trusted context or workload definition is too long. Attribute attribute-name was specified, but the value exceeds the maximum length of length. |
Specify a valid value with a length no longer than length. sqlcode: -20443 sqlstate: 42907 |
SQL20445N |
The security label name name is not valid as specified. |
In the context where it is specified, the security label name must be explicitly qualified with an existing security policy name. |
Provide a security label name that is explicitly qualified with an existing security policy name. sqlcode: -20445 sqlstate: 42704 |
SQL20447N |
Format string format-string is not valid for the function-name function. |
The given format string format-string is invalid for the function named function-name. The function identified as function-name could be VARCHAR_FORMAT or TIMESTAMP_FORMAT, even if the name used to invoke the function was TO_CHAR, TO_DATE, or TO_TIMESTAMP. This message is returned when there is one of the following problems with the format-string argument:
The statement cannot be processed. |
Change the format string argument and call the function-name function again. sqlcode: -20447 sqlstate: 22007 |
SQL20448N |
string-expression cannot be interpreted using format string format-string for the TIMESTAMP_FORMAT function. |
The TIMESTAMP_FORMAT function was invoked with string-expression and format-string. The name used to invoke the function could also be TO_DATE or TO_TIMESTAMP. The value string-expression cannot be interpreted with the format string format-string to produce a timestamp value. This error can occur for any of the following reasons:
The statement cannot be processed. |
Change the format string argument of the TIMESTAMP_FORMAT function. For more information, see the TIMESTAMP_FORMAT function in the SQL Reference. sqlcode: -20448 sqlstate: 22007 |
SQL20449N |
Tree element element-value is not valid where specified. |
The tree element element-value is an existing element in the tree, but is not valid where it is specified in the statement. The tree structure of the tree component must be maintained. For example, in an ALTER SECURITY LABEL COMPONENT statement, the element-name specified in the OVER clause of the ADD ELEMENT clause is not an immediate child element of the tree element specified immediately after the UNDER keyword. |
Specify a valid tree element that would maintain the tree structure. For example, only specify existing tree elements that are immediate children elements of the tree element specified immediately after the UNDER keyword. sqlcode: -20449 sqlstate: 428H3 |
SQL20450N |
Recursion limit exceeded within a hierarchical query. |
Hierarchical queries using the CONNECT BY clause are limited to a recursive depth of 64 levels. The query has exceeded this level. |
Validate the correctness of the START WITH and CONNECT BY clauses. If recursions deeper than 64 levels are expected, rewrite the query using a recursive common table expression. Recursive common table expressions support arbitrary recursive depth. sqlcode: -20450 sqlstate: 54066 |
SQL20451N |
Cycle detected in a hierarchical query. |
The hierarchical query using the CONNECT BY clause has found a row which is a direct or indirect parent to itself, given the CONNECT BY search condition. The statement cannot be processed. |
Validate the correctness of the CONNECT BY clause, paying particular attention to the PRIOR operator.
sqlcode: -20451 sqlstate: 560CO |
SQL20452N |
Hierarchical query construct name is used out of context. |
One of the following constructs has been found outside of the context of a hierarchical query:
The reason can be one of the following:
The statement cannot be processed. |
sqlcode: -20452 sqlstate: 428H4 |
SQL20453N |
The task task-name cannot be removed because it is currently executing. |
An attempt to remove task task-name failed because it is currently executing. |
Wait until the task completes and then use the SYSPROC.ADMIN_TASK_REMOVE procedure to remove the task. The SYSTOOLS.ADMIN_TASK_STATUS view can be used to check the execution status of the task. sqlcode: -20453 sqlstate: 5UA01 |
SQL20454N |
Invalid use of an outer join operator. Reason code = reason-code. |
The outer join operator (specified as "(+)") was used incorrectly in an SQL statement. The meaning of the invalid use is given by the reason code reason-code.
The statement cannot be processed. |
Replace the use of the outer join operator with explicit OUTER JOIN syntax in the FROM clause. Alternatively, correct or remove the invalid use of the outer join operator based on the reason code. sqlcode: -20454 sqlstate: 428H5 |
SQL20456N |
An insert or update operation of multiple rows failed because both DEFAULT and explicit values cannot be specified for a column defined as ROW CHANGE TIMESTAMP and GENERATED BY DEFAULT. |
An insert or update operation on multiple rows of data attempted to insert or update rows specifying DEFAULT for some rows and explicit values for some rows for a column that is defined with both the ROW CHANGE TIMESTAMP attribute and GENERATED BY DEFAULT attribute. |
Modify the statement so that only DEFAULT is specified for the column for all of the rows, or explicit values are provided for the column for all of the rows. Alternatively, use two statements for this operation, one to set the column values to DEFAULT, and the other to set the column values to the explicitly provided values. sqlcode: -20456 sqlstate: 560CP |
SQL20457N |
The procedure procedure-name has encountered an unsupported version, version, for parameter number. |
The version, version, specified for the parameter in ordinal position number is not supported by the procedure procedure-name. |
Call the procedure and specify a supported version number for the parameter. The highest supported version number for the parameter can be obtained by calling the procedure and specifying NULL for the value of this parameter. sqlcode: -20457 sqlstate: 38554 |
SQL20458W |
The procedure procedure-name has encountered an internal parameter processing error in parameter number1. The value for parameter number2 contains further information about the error. |
The format or content of the parameter in ordinal position number1 in the call to the procedure procedure-name is invalid. The output parameter specified in ordinal position number2 contains information on how to respond to the error. |
Use the information in the output parameter specified in ordinal position number2 to correct the format or content of the parameter value and call the procedure again. sqlcode: +20458 sqlstate: 01H54 |
SQL20459W |
The procedure procedure-name has encountered an internal processing error. The value for parameter number contains further information about the error. |
An error occurred when the procedure procedure-name was processing a request. The output parameter specified in ordinal position number contains information on how to respond to the error. |
Use the information in the output parameter specified in ordinal position number to correct the error and call the procedure again. sqlcode: +20459 sqlstate: 01H55 |
SQL20460W |
The procedure procedure-name supports a higher version, version1, than the specified version, version2, for parameter number. |
A higher version, version1, for the parameter in ordinal position number is supported by the procedure procedure-name. The specified version, version2, is supported for the parameter. |
Check the documentation for the procedure to understand the additional features supported by the newer version of the parameter. Upgrade to the current version to take advantage of these additional features. sqlcode: +20460 sqlstate: 01H56 |
SQL20461W |
The procedure procedure-name returned output in the alternate locale, locale1, instead of the locale, locale2, specified in parameter number. |
The locale, locale2, specified in the parameter in ordinal position number was not available for the output of the procedure procedure-name. The output is returned using locale locale1. |
Install the message file support on the server for the specified locale, locale2, or specify a supported locale. sqlcode: +20461 sqlstate: 01H57 |
SQL20462W |
Unable to return distinct row change columns. Reason code = reason-code. |
WITH ROW CHANGE COLUMNS ALWAYS DISTINCT was specified as a prepare attribute, but the database manager is unable to return distinct row change columns. The statement was prepared successfully. |
If distinct row change columns are desired, use the following reason-code values to determine what to do.
sqlcode: +20462 sqlstate: 0168T |
SQL20464N |
An attempt to revoke the SECADM authority from authorization-ID was denied because it is the only external authorization ID of type user with SECADM authority. |
The SECADM authority must be held by at least one external authorization ID of type user, and the REVOKE statement is attempting to revoke the authority from the last authorization ID of type user that holds this authority. The statement cannot be executed. The SECADM authority is not revoked. |
Grant the SECADM authority to another external authorization ID of type user to allow the SECADM authority to be revoked from authorization-ID. sqlcode: -20464 sqlstate: 42523 |
SQL20465N |
The binary XML value is incomplete or contains unrecognized data at location position starting with the hex data text. Reason code = reason-code. |
An error occurred when processing a binary XML value. The first eight bytes of XML data in hexadecimal at position bytes is text. If the unrecognized data is located within the last eight bytes of the binary XML data, only the data starting at location position up to the end of the binary XML data is displayed. The reason code indicates the specific problem:
The statement cannot be processed. |
Fix the problem in your XML data or change your application to use textual XML format for data transfer. sqlcode: -20465 sqlstate: 22541 |
SQL20467N |
The statement was not executed because an expression cannot be computed as a single value for the query. The invalid expression is in the statement near the syntax element text. |
The expression in the statement near the syntax element text must result in a single value and must consist of one of the following elements:
The expression cannot include any of the following elements:
|
Run the statement again, after changing the expression to remove any elements that cannot be included. sqlcode: -20467 sqlstate: 428H7 |
SQL20469N |
Row or column access control activation for table table-name has failed due to reason code reason-code. |
Row access control cannot be activated explicitly or implicitly, or column access control cannot be activated explicitly for table table-name. The reason code indicates more specifically why the activation failed:
|
Correct the error and retry the activation of the row or column access control for the table. sqlcode: -20469 sqlstate: 55019 |
SQL20470N |
The CREATE or ALTER statement failed because object-type1 object-name1 was not defined as secure and object-type2 object-name2 is dependent on it. |
object-type1 object-name1 must be defined as secure because object-type2 objectname2 depends on it for row or column access control. The statement cannot be processed. |
The object needs to remain secure as long as a row permission or a mask depends on it, or a materialized query table that references tables with row or column access control activated depends on it. To complete the CREATE or ALTER statement, drop the dependent object after ensuring that it is not needed. sqlcode: -20470 sqlstate: 428H8 |
SQL20471N |
The INSERT or UPDATE statement failed because a resulting row did not satisfy row permissions. |
Row access control is enforced for the object of the INSERT or UPDATE operation. All attempts to INSERT or UPDATE rows in the table are checked to ensure that the resulting rows conform to the row permissions defined for that table. The statement cannot be processed. No INSERT or UPDATE operation was performed, and the contents of the table remain unchanged. |
Examine the definitions of the row permissions to determine why the requested INSERT or UPDATE operation failed. This may be a data-dependent condition. sqlcode: -20471 sqlstate: 22542 |
SQL20472N |
The ALTER statement on the permission or mask object-name failed due to reason code reason-code. |
The ALTER MASK or ALTER PERMISSION statement cannot be processed for one of the following reasons:
The statement cannot be processed. |
sqlcode: -20472 sqlstate: 428H9 |
SQL20473N |
The function function-name, created with the NOT SECURE option failed. The function referenced column column-name which has a column mask with column access control activated for the table. |
The input argument of an insecure function must not reference a column which has a column mask defined with column access control activated for the table. The statement cannot be processed. |
sqlcode: -20473 sqlstate: 428HA |
SQL20474N |
The CREATE PERMISSION or CREATE MASK statement failed on the database object object-name of object type object-type due to reason code reason-code. |
The CREATE PERMISSION or CREATE MASK statement could not be processed because the definition in the CREATE PERMISSION or CREATE MASK statement references an unsupported object. The reason code indicates what is unsupported:
The statement cannot be processed. |
Correct the error and run the CREATE statement again. sqlcode: -20474 sqlstate: 428HB |
SQL20475N |
The CREATE MASK statement failed because a column mask is already defined for the specified column. Column name: column-name. Table name: table-name. Existing mask name: mask-name. |
Only a single mask can be defined for a column. The statement cannot be processed. |
sqlcode: -20475 sqlstate: 428HC |
SQL20476N |
The function-name function was invoked with an invalid format string format-string. |
An invalid format string was specified for the function-name function. The value for function-name could be VARCHAR_FORMAT or DECFLOAT_FORMAT, even if the name used to invoke the function was TO_CHAR or TO_NUMBER. A valid format string for the VARCHAR_FORMAT function must:
A valid format string for the DECFLOAT_FORMAT function must:
The statement cannot be processed. |
Change the format string argument of the function-name function. For more information, see the corresponding description of the function in the SQL Reference. sqlcode: -20476 sqlstate: 22018 |
SQL20477N |
The function-name function is not able to use format string format-string to interpret the argument string-expression. |
The function-name function was invoked with format-string and string-expression. The value for function-name would be DECFLOAT_FORMAT, even if the name used to invoke the function was TO_NUMBER. The value of the argument string-expression cannot be interpreted with the format string format-string to produce a DECFLOAT(34) value. This error can occur for any of the following reasons:
The statement cannot be processed. |
Change the arguments of the function-name function to valid values. For more information, see the corresponding description of the function in the SQL Reference. sqlcode: -20477 sqlstate: 22018 |
SQL20478N |
The statement failed because the column mask mask-name defined for column column-name exists and the column mask cannot be applied or the column mask conflicts with the failed statement. Reason code reason-code |
A reference to a column mask is not supported. The cause of the error is described by the following reason codes:
The statement cannot be processed. |
sqlcode: -20478 sqlstate: 428HD |
SQL20479N |
The ALTER or RENAME statement failed on the table table-name because the table is part of row or column access control definitions. Reason code reason-code. |
The table table-name in an ALTER or RENAME statement cannot be altered as specified for one of the following reasons:
The statement cannot be processed. |
sqlcode: -20479 sqlstate: 42917 |
SQL20480W |
The newly defined object object-name is marked as invalid because it references an object object-name2 which is not defined or is invalid, or the definer does not have privilege to access it. |
The object object-name was successfully defined, but has been marked as invalid. Objects such as views, triggers, SQL procedures, and SQL functions, can be defined successfully even though they reference an object, such as object-name2, that is either not defined at the application server, or is in the invalid state, or the definer does not have privilege to access it. Invalid objects can be automatically revalidated implicitly the next time they are accessed or explicitly by using the procedure SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS. |
If object-name2 was expected to be defined or valid, then create or revalidate the object and then redefine object-name. Ensure that all objects referenced by object-name are valid and the definer has the privilege to access them before the first access to the object, so it will be revalidated successfully. sqlcode: +20480 sqlstate: 0168Y |
SQL20481N |
The creation or revalidation of object object-name would result in an invalid direct or indirect self-reference. |
The definition of the object being created or replaced contains a direct or indirect reference to itself. This self-reference can either be explicit in the definition, or implicit by a reference to another object that explicitly or implicitly references the object. An object definition can only contain a valid reference to itself when it is created using the CREATE SCHEMA statement. Such an object can only be replaced or revalidated if the new definition does not contain the self-reference. |
Remove the self-reference or use the CREATE SCHEMA statement to create the object that has a valid reference to itself. sqlcode: -20481 sqlstate: 429C3 |
SQL20482N |
Revalidation failed for all objects that were specified to be revalidated. One object, object-name1, could not be revalidated because it references object object-name2. |
All of the objects specified to be revalidated by the SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS procedure were not able to be revalidated successfully because at least one object that they reference does not exist or continues to be invalid. One of the objects, object-name1, could not be revalidated because it references object object-name2 which either does not exist or continues to be invalid. |
Create any objects that should exist and correct any objects that continue to be invalid that are referenced by the objects to be revalidated. The SYSCAT.INVALIDOBJECTS catalog view contains information on invalid objects. sqlcode: -20482 sqlstate: 429C4 |
SQL20483N |
Invalid use of named argument parameter-name when invoking routine routine-name. Reason code: reason_code. |
This error can occur for the following reasons:
The statement cannot be processed. |
Correct the routine invocation in the SQL statement. sqlcode: -20483 sqlstate: 4274K |
SQL20484N |
The invocation of routine routine-name omits a parameter parameter-name which is not defined with a DEFAULT. |
A parameter value is omitted from a procedure invocation. This is invalid unless the parameter is defined to have a DEFAULT value. The statement cannot be processed. |
Correct the procedure invocation to provide a parameter value for the omitted parameter. sqlcode: -20484 sqlstate: 428HF |
SQL20485N |
The CREATE statement for routine routine-name defines a parameter without a DEFAULT after a parameter that has been defined with a DEFAULT. |
During the creation of procedure routine-name, a parameter is specified without a defined DEFAULT value after the specification of a parameter with a defined DEFAULT value. All parameters without a defined DEFAULT must be specified before those which have a defined DEFAULT value. The statement cannot be processed. |
Provide a DEFAULT value for all parameters that follow the first parameter that is defined with a DEFAULT value or re-order the parameter list such that all parameters defined with a DEFAULT value are after all parameters defined without a DEFAULT value. sqlcode: -20485 sqlstate: 428HG |
SQL20490N |
The statement failed because a VERSIONING clause was specified for table table-name, but the table cannot be used as a system-period temporal table. Reason code reason-code. |
The CREATE or ALTER TABLE statement attempted to make the table into a system-period temporal table, but the table definition is invalid for reason code indicated:
The statement cannot be processed. |
Correct the syntax and resubmit the statement. sqlcode: -20490 sqlstate: 428HM |
SQL20491N |
The statement failed because the specification of a period period-name is not valid. Reason code reason-code. |
The specification of a period attribute in a CREATE or ALTER statement is invalid for the reason code indicated:
The statement cannot be processed. |
Correct the syntax and resubmit the statement. sqlcode: -20491 sqlstate: 428HN |
SQL20494N |
A public alias name, name, can be qualified only with SYSPUBLIC and not the schema name schema-name. |
A qualified name was specified for a public alias but the qualifier was not SYSPUBLIC. |
Change the two-part name to a one-part name or specify the qualifier SYSPUBLIC. If a public alias was not intended and PUBLIC was specified in the statement, remove the keyword PUBLIC. sqlcode: -20494 sqlstate: 428EK |
SQL20495N |
The definition of the module initialization procedure SYS_INIT is not valid. Reason code rc. |
Initialization procedure definitions can be invalid for the following reasons:
|
Modify the initialization procedure definition so that it conforms to the valid syntax. sqlcode: -20495 sqlstate: 428HP |
SQL20496N |
The routine name cannot be invoked because it is only a routine prototype. |
Routine name is defined as a prototype in a module, but is not fully implemented. A routine prototype with the specified routine name was found in the module, but without a routine body. The routine definition is incomplete and therefore cannot be invoked. |
Alter the module and add a full routine definition. Try again. sqlcode: -20496 sqlstate: 55019 |
SQL20498N |
The data type that was specified for the following field is not supported: field-name Specified data type type-name. |
The data type specified for a row in the CREATE TYPE statement or CREATE HADOOP TABLE statement with columns of type array is not valid. The following restrictions apply when specifying a data type.
|
Ensure that the data types specified for fields in the CREATE TYPE (row) statement, CREATE HADOOP TABLE statement with columns of type array, fields defined by the columns of the anchor table, or anchor view are supported sqlcode: -20498 sqlstate: 429C5 |
SQL20499N |
The data type typename is not valid for the operand of the keywords predicate. |
The predicate indicated by keywords does not support the data type typename as the operand of the predicate. |
Change the operand to have a data type that is supported by the predicate or remove the predicate with the invalid operand data type. sqlcode: -20499 sqlstate: 428HQ |