SQL20000-20999

SQL20005N

The statement failed because the maximum number of internal identifiers has been exceeded for the object type. Internal identifier limit: of limit. Object type: object-type.

When one of several types of database object is created, declared, or altered, an internal identifier is created to uniquely identify that object. There is an upper limit on the number of unique identifier that can be created.

This message is returned when the limit for internal identifiers for this type of object has been exceeded.

Respond to this error by performing the following troubleshooting steps:

• Drop objects of type object-type that are no longer being used.
• If object-type is DECLARE TYPE, remove the type declarations within the current compound SQL (compiled) statement for any types that are not being used.
• If object-type is a workload management object, you can reset the numbering of the internal identifiers by performing the following steps:
  1. Extract the DDL statements that would reproduce your workload management objects by using the db2look utility, specifying the -wlm option.
  2. Drop all of the workload management objects of the specified type from the database.
  3. Recreate the workload management objects of the specified type using the information from the db2look utility generated file.

sqlcode: -20005

sqlstate: 54035

SQL20010N

Mutation method method-ID is not allowed when the instance of the structured type is NULL.

The method method-ID is a mutator method that is specified with an instance of a structured type that is null. Mutator methods cannot be processed on a null instance. In some cases, the method name is not available.

The statement cannot be processed.

Determine the null instance that is used with a mutator method. Use a constructor function to create a non-null instance of the structured type before using any mutator methods on the instance.

SELECT FUNCSHEMA, FUNCNAME,
       SPECIFICNAME
 FROM SYSCAT.FUNCTIONS
 WHERE
   FUNCID = INTEGER(
            method-ID
            )

sqlcode: -20010

sqlstate: 2202D

SQL20011N

Transform group group-name is already defined for a subtype or supertype of data type type-name.

A transform group called group-name already exists for a type in the same hierarchy as type-name. It may be defined for a supertype or subtype of type-name. A transform group name can only be used once within a structured type hierarchy.

The statement cannot be processed.

Change the name of the transform group.

sqlcode: -20011

sqlstate: 42739

SQL20012N

Type type-name does not have any associated transform groups to drop.

There are no transforms defined for type-name. There is nothing to drop.

The statement did not drop any transform groups.

Ensure the name of the type (including any required qualifiers) is correctly specified in the SQL statement and that the type exists.

sqlcode: -20012

sqlstate: 42740

SQL20013N

The object super-object-name is not valid as a supertype, supertable, or superview of object sub-object-name.

If the statement resulting in the error is creating a type, then super-object-name is a type that cannot be a supertype of sub-object-name because it is not a user-defined structured type.

If the statement resulting in the error is creating a table, then super-object-name is a table that cannot be a supertable of table sub-object-name because it is not defined as a typed table or the type of table super-object-name is not the direct supertype of the type used in defining table sub-object-name.

If the statement resulting in the error is creating a view, then super-object-name is a view that cannot be a superview of view sub-object-name because it is not defined as a typed view or the type of view super-object-name is not the direct supertype of the type used in defining view sub-object-name.

The statement cannot be processed.

Specify a valid type, table, or view in the UNDER clause of the CREATE statement.

sqlcode: -20013

sqlstate: 428DB

SQL20014N

The transform group group-name transform-type transform function for type type-name is not valid. Reason code = reason-code.

The statement cannot be processed.

sqlcode: -20014

sqlstate: 428DC

SQL20015N

A transform group group-name is not defined for data type type-name.

A specified transform group group-name is not defined for the data type type-name. The data type type-name may have been explicitly specified in the statement or may be implicit based on the use of a structured type that requires the existence of the transform group for the data type.

If group-name is empty, either the TRANSFORM GROUP bind option or the CURRENT DEFAULT TRANSFORM GROUP special register was not specified and therefore there was no transform for type-name.

The statement cannot be processed.

Define transform group transform-type for data type type-name using the CREATE TRANSFORM statement. If the error occurred when dropping the transform, no action is required because the transform group did not exist for the data type.

If group-name is empty, specify the TRANSFORM GROUP bind option on the CURRENT DEFAULT TRANSFORM GROUP special register.

sqlcode: -20015

sqlstate: 42741

SQL20016N

The value of the inline length associated with type or column type-or-column-name is too small.

For the definition of structured type type-or-column-name, it has an INLINE LENGTH value specified that is smaller than the size returned by the constructor function (32 + 10 * number_of_attributes) for the type and is less than 292. For the altering of column type-or-column-name, the INLINE LENGTH specified is smaller than the current inline length.

The statement cannot be processed.

Specify an INLINE LENGTH value that is large enough. For a structured type, that is at least the size returned by the constructor function for the type or is at least 292. For a column, it must be larger than the current inline length. If this error occurs when altering the type (or some supertype of this type) to add an attribute, either the attribute cannot be added or the type must be dropped and re-created with a larger INLINE LENGTH value.

sqlcode: -20016

sqlstate: 429B2

SQL20017N

Addition of this subtype exceeds the maximum number of levels of a type hierarchy.

The maximum number of levels in a type hierarchy is 99. Adding this type would exceed the maximum.

The statement cannot be processed.

Do not add any more subtypes to this type hierarchy.

sqlcode: -20017

sqlstate: 54045

SQL20018N

Row function function-name must return at most one row.

The function is a defined to return a single row. The result of the processing the function is more than one row.

Ensure that the function is defined in such a way that at most one row is returned.

sqlcode: -20018

sqlstate: 21505

SQL20019N

The result type returned from the function body cannot be assigned to the data type defined in the RETURNS clause.

The data type of each column returned by the function body must be assignable to the corresponding column specified in the RETURNS clause.

If the function is a scalar function, there is only one column.

Change the RETURNS type or the type returned from the function body so that the data types of corresponding columns are assignable.

sqlcode: -20019

sqlstate: 42866

SQL20020N

Operation operation-type is not valid for typed tables.

The operation identified by operation-type cannot be performed on a typed table.

The statement cannot be processed.

If it is an ALTER statement, remove the ADD COLUMN clause, ADD PERIOD clause, or SET DATATYPE clause. Columns can only be added by re-defining the table with a structured type that includes the new column as an attribute. Similarly, the data type of a column can only be changed by re-defining the table with a type that includes the column with a different data type.

If it is a CREATE TABLE statement, remove the DISTRIBUTE BY RANDOM clause. Typed tables are not allowed to be created as random distribution tables.

sqlcode: -20020

sqlstate: 428DH

SQL20021N

Inherited column or attribute name cannot be changed or dropped.

The statement cannot be processed.

The options for a column may only be set or altered for the table or view in the typed table hierarchy or typed view hierarchy where the column is introduced. An attribute can only be dropped from the data type in the type hierarchy where the attribute was introduced.

sqlcode: -20021

sqlstate: 428DJ

SQL20022N

The scope for the reference column column-name is already defined.

The scope for the reference column column-name cannot be added because it is already defined.

The statement cannot be processed.

Remove the ADD SCOPE clause from the ALTER TABLE statement.

sqlcode: -20022

sqlstate: 428DK

SQL20023N

Parameter parm-number of the external or sourced function has a scope defined.

A reference type parameter should not have a scope defined when used with external or sourced user defined functions.

The statement cannot be processed.

Remove the SCOPE specification from the definition of the parameter.

sqlcode: -20023

sqlstate: 428DL

SQL20024N

The scope table or view target-name is not defined with structured type type-name.

The statement cannot be processed.

Specify the scope of the reference using a typed table or typed view with the same type as the target type of the REF type.

sqlcode: -20024

sqlstate: 428DM

SQL20025N

SCOPE is not specified in the RETURNS clause of an external function or is specified in the RETURNS clause of a sourced function.

The statement cannot be processed.

When defining an external function with a reference type as a returns type, ensure that the SCOPE clause is specified. When defining SOURCED function with a reference type as a returns type, ensure that the SCOPE clause is not specified.

sqlcode: -20025

sqlstate: 428DN

SQL20026N

The type type-name is not a structured type or is not an instantiable structured type.

The statement cannot be processed.

Verify that the correct type name is used in the statement.

sqlcode: -20026

sqlstate: 428DP

SQL20027N

The subtable or subview sub-object-name was not created because subtable or subview object-name with type type-name already exists.

Within a typed table or view hierarchy, only one subtable or subview may exist of a particular subtype. The table or view sub-object-name cannot be created since there is already a table or view of type type-name defined. The table or view that already exists is object-name.

The statement cannot be processed.

Verify that the subtable or subview is being created with the correct type and that the subtable is being created under the correct supertable or the subview is being created under the correct superview.

sqlcode: -20027

sqlstate: 42742

SQL20028N

The table or view table-name cannot have a different schema name from the other tables or views in the same hierarchy.

All tables in a typed table hierarchy must have the same schema name and all views in a typed view hierarchy must have the same schema name.

The statement cannot be processed.

Verify that the schema name of the table or view is correct. If a hierarchy name is specified, verify that its schema name matches the schema name of the root table or view. If a subtable is being created, verify that it is being created under the correct supertable. If a subview is being created, verify that it is being created under the correct superview.

sqlcode: -20028

sqlstate: 428DQ

SQL20029N

operation cannot be applied to a subtable or subview.

The operation operation was applied to a table or view that is not the root of a table hierarchy or view hierarchy.

The subtable or subview cannot be a random distribution table.

The statement cannot be processed.

Specify the root table of the table hierarchy or root view of the view hierarchy in the operation.

If the operation was DISTRIBUTE BY RANDOM, execute the CREATE TABLE statement again without the DISTRIBUTE BY RANDOM clause.

sqlcode: -20029

sqlstate: 428DR

SQL20030N

Attributes of a structured type type-name cannot be added or dropped when a typed table, typed view, or index extension object-name is dependent on the type.

The attributes of a structured type cannot be added or dropped if a typed table or typed view of the structured type or any of its subtypes currently exists. Attributes of a structured type also cannot be added or dropped when a column exists in the table that directly or indirectly uses type-name. Also, attributes of a structured type cannot be added or dropped when the type type-name or one of its subtypes is used in an index extension. The table, view, or index extension object-name is one table, view, or index extension that is dependent on the structured type type-name. There may be other tables, views, or index extensions that are dependent on the type or one of its proper subtypes.

The statement cannot be processed.

Verify that the right type is being altered or drop any tables, views, and index extensions that are dependent on the structured type type-name.

sqlcode: -20030

sqlstate: 55043

SQL20031N

Object may not be defined on a subtable.

Primary key and unique constraints can only be defined on the root table of a typed table hierarchy. Similarly, unique indexes can only be defined on the root table of a typed table hierarchy.

The statement cannot be processed.

Unique indexes, Primary key or unique constraints can only be defined on the root table of a table hierarchy.

sqlcode: -20031

sqlstate: 429B3

SQL20032N

Index on the specified columns cannot be defined on subtable table-name.

The columns specified for the index were all introduced at a higher level in the typed table hierarchy than subtable table-name. Therefore, the index cannot be created on this subtable.

The statement cannot be processed.

Determine the table in the table hierarchy where all of the columns are included for the first time. Use this as the table name when creating the index.

sqlcode: -20032

sqlstate: 428DS

SQL20033N

An expression including partial-expression does not include a valid scoped reference.

The expression that includes partial-expression requires an operand that is reference type with a scope defined. If the expression includes the DEREF function, the argument of the function must be a reference type with a scope defined.

For the dereference operator (->), the left operand needs to be a reference type with a scope defined.

The statement cannot be processed.

Correct the SQL statement syntax so the operand or argument is a reference type with a scope defined.

sqlcode: -20033

sqlstate: 428DT

SQL20034N

The data type list-type-name is not included in a structured data type hierarchy that includes the data type left-type-name of the left operand of the TYPE predicate.

All the data types listed in the TYPE predicate must be included in a data type hierarchy that includes the data type of the left operand of the TYPE predicate. The data type left-type-name is not a structured data type (not part of any type hierarchy) or the data type list-type-name is not included in the data type hierarchy that includes left-type-name.

The statement cannot be processed.

Ensure that the data type of the expression and all listed data types in the TYPE predicate are structured data types within the same data type hierarchy. If left-type-name is SYSIBM.REFERENCE, use DEREF to make the result data type of the expression a structured data type.

sqlcode: -20034

sqlstate: 428DU

SQL20035N

Invalid left operand of a dereference operator. Path expression starts with expression-string.

Correct the left operand of the dereference operator for the path expression that starts with expression-string.

sqlcode: -20035

sqlstate: 428DV

SQL20036N

The object identifier column column-name cannot be referenced using the dereference operator.

The dereference operator is used with column-name as the right operand. This column is the object identifier column of the target table of the dereference and is not valid for this operator.

The statement cannot be processed.

Correct the name of the column in the dereference operation.

sqlcode: -20036

sqlstate: 428DW

SQL20037N

Object identifier column is required to create the root table or root view object-name of a typed table or view hierarchy.

When creating the root table of a typed table hierarchy, an object identifier (OID) column must be defined (using the REF IS clause) on the CREATE TABLE statement.

When creating the root view of a typed view hierarchy, an object identifier (OID) column must be defined (using the REF IS clause) on the CREATE VIEW statement.

The statement cannot be processed.

Add the required OID column (REF IS clause) to the CREATE TABLE or CREATE VIEW statement.

sqlcode: -20037

sqlstate: 428DX

SQL20038N

The statement could not be processed because the statement contains the following incompatible clauses or elements: keywords1 and keywords2.

The keywords2 clause in the statement cannot be specified with the keywords1 clause. If CODEUNITS32 is one of the incompatible elements, note that the string unit might be set implicitly with the string_units configuration parameter.

1. Remove either the keywords1 or the keywords2 clause from the statement.
2. If CODEUNITS32 is one of the incompatible elements, explicitly specify OCTETS as the string unit for the data type.

sqlcode: -20038

sqlstate: 42613

SQL20039N

The definition of index index-name does not match the definition of index extension index-ext-name.

The statement cannot be processed.

Change the index definition so that the index extension matches.

sqlcode: -20039

sqlstate: 428E0

SQL20040N

Number or type of the result of the range-producing table function range-function-name, is inconsistent with that of key transformation table function transform-function-name for index extension index-ext-name.

More precisely, let a ₁:t ₁,... a _n:t _n be the function result columns and data types of the key transformation function. The function result columns of the range-producing function must be b ₁:t ₁,...,b _m:t _m,c ₁:t ₁,...,c _m:t _m, where m <= n and the "b" columns are the start key columns and the "c" columns are the stop key columns.

The statement cannot be processed.

Specify a range-producing table function that is consistent with the key transformation table function.

sqlcode: -20040

sqlstate: 428E1

SQL20041N

Number or the type of target key parameters does not match with the number or type of key transform function function-name for index extension index-ext-name.

The number of target key parameters has to match with the number of results returned by the key transform function. In addition, the type of the target key parameters must exactly match the corresponding function result types.

The statement cannot be processed.

Specify the correct number and type of parameters as the target key parameters.

sqlcode: -20041

sqlstate: 428E2

SQL20042N

The maximum allowable parm-type parameters is exceeded in index extension index-ext-name. The maximum is max-value.

Too many parameters were specified. If parm-typeis INDEX EXTENSION, then up to max-value instance parameters may be specified. If parm-typeis INDEX KEYS, then up to max-value key source parameters may be specified.

The statement cannot be processed.

Specify no more than the maximum number of parameters.

sqlcode: -20042

sqlstate: 54046

SQL20043N

Argument for routine routine-name is not valid. Reason code = reason-code.

The statement cannot be processed.

Specify a valid argument for the function.

sqlcode: -20043

sqlstate: 428E3

SQL20044N

The routine routine-name or the CASE expression is not valid in a CREATE INDEX EXTENSION or CREATE FUNCTION statement. Reason code = reason-code.

The statement cannot be processed.

If routine-name is not empty, specify a routine that conforms to the rules for a function or method specified in the specific clause of the CREATE INDEX EXTENSION or CREATE FUNCTION statement. Otherwise, specify a CASE expression that conforms to the rules for a CASE expression in the FILTER USING clause.

sqlcode: -20044

sqlstate: 428E4

SQL20045N

The data type of instance parameter parameter-name is invalid in index extension index-ext-name.

An instance parameter must be one of the following data types: VARCHAR, VARGRAPHIC, INTEGER, DECIMAL, or DOUBLE.

The statement cannot be processed.

Specify a valid data type for the instance parameter parameter-name.

sqlcode: -20045

sqlstate: 429B5

SQL20046N

SELECTIVITY clause following predicate-string can only be specified for a valid user-defined predicate.

The SELECTIVITY clause is specified with a predicate that does not include a valid user-defined function. A valid user-defined function includes a PREDICATES clause with a WHEN clause that matches the predicate. The SELECTIVITY clause cannot be specified except with a user-defined predicate.

The statement cannot be processed.

Remove the SELECTIVITY clause following the predicate.

sqlcode: -20046

sqlstate: 428E5

SQL20047N

The search method method-name is not found in the index extension index-ext-name.

The method method-name referenced in an exploitation rule of the user-defined predicate has to match one of the search methods specified in the index extension index-ext-name.

The statement cannot be processed.

Specify a method defined in the index extension.

sqlcode: -20047

sqlstate: 42743

SQL20048N

The search argument of method method-name does not match the one in the corresponding search method in the index extension index-ext-name.

The search argument provided for method method-name does not match the argument of the corresponding search method in the index extension index-ext-name. Either the number of arguments or the type of the arguments do not match the defined number or type of the parameters.

The statement cannot be processed.

Specify a search argument that matches the parameters defined in the index extension.

sqlcode: -20048

sqlstate: 428E6

SQL20049N

Type of an operand following the comparison operator in the AS PREDICATE WHEN clause does not exactly match the RETURNS type.

The definition of the user-defined predicate is not valid. In the AS PREDICATE WHEN clause, the type of the operand following the the comparison operator is not an exact match with the RETURNS type of the function.

The statement cannot be processed.

Specify an the operand with the correct data type.

sqlcode: -20049

sqlstate: 428E7

SQL20050N

The search target or search argument parameter-name does not match a name in the function being created.

Each search target in an index exploitation rule has to match some parameter name of the function that is being created. Each search argument in an index exploitation rule must match either an expression name in the EXPRESSION AS clause or a parameter name of the function being created. Parameter names must be specified in the parameter list for the function.

The statement cannot be processed.

Specify only valid names of the function in the search target or search argument.

sqlcode: -20050

sqlstate: 428E8

SQL20051N

The argument parameter-name cannot appear as both a search target and a search argument in the same exploitation rule.

In the exploitation clause, a function parameter cannot be specified as an argument following KEY and as an argument of the method specified following the USE keyword.

The statement cannot be processed.

Specify a parameter name of the function in no more than on of the search target or the search argument.

sqlcode: -20051

sqlstate: 428E9

SQL20052N

Column column-name is an object identifier column which cannot be updated.

The UPDATE statement includes setting a column that is an object identifier (OID) column. An OID column cannot be updated.

The statement cannot be processed.

Remove the SET of column-name from the UPDATE statement.

sqlcode: -20052

sqlstate: 428DZ

SQL20053N

Fullselect in typed view view-name is not valid. Reason code = reason-code.

sqlcode: -20053

sqlstate: 428EA

SQL20054N

The operation was not performed because the table is in an invalid state for the operation. Table name: table-name. Reason code: reason-code.

The table is in a state that does not allow the operation. The reason code indicates the state of the table that prevents the operation.

21

The table is in Datalink Reconcile Pending (DRP) state or Datalink Reconcile Not Possible (DRNP) state.

22

The generated column expression cannot be added or altered because the table is not in check pending mode.

23

The maximum number of REORG-recommended ALTER operations have been run. Up to 31 REORG-recommended operations are allowed on a table before a classic reorg must be done to update the table rows to match the current schema.

24

Executing an ALTER TABLE statement with the ADD COLUMN clause on a LOB or LONG column is not allowed in the same unit of work as an ALTER TABLE statement with the DROP COLUMN clause on the last LOB or LONG column in the table.

In addition, on database servers Version 9.7 and later, executing an ALTER TABLE statement with the ADD COLUMN clause on an XML column is not allowed in the same unit of work as an ALTER TABLE statement with the DROP COLUMN clause on the last XML column in the table.

25

The table is in set integrity pending state.

26

Executing the ALTER TABLE ... ATTACH PARTITION or the ALTER TABLE ... DETACH PARTITION statement on a table whose database partition group is currently being redistributed is not allowed.

27

The alter table or copy schema operation called an internal procedure to manage database objects. The SYSTOOLS.DB2LOOK_INFO table used by the procedure is not in a valid state for the alter or copy operation. The SYSTOOLS.DB2LOOK_INFO table could be an older version, or totally different from what the procedure expects.

29

The operation that empties or truncates a table is not allowed because the table has a partition in one of the following three states:

1. Attached that has not yet been checked for integrity (SYSCAT.DATAPARTITIONS.STATUS = 'A').
2. Detached partitions and there are dependent tables that need to be incrementally maintained with respect to these detached partitions (SYSCAT.DATAPARTITIONS.STATUS = 'D').
3. Detached partitions pending index cleanup (SYSCAT.DATAPARTITIONS.STATUS = 'I').

30

A LOAD operation cannot be restarted when the following three things are true:

1. The LOAD operation failed in the BUILD, DELETE or INDEX COPY PHASE
2. The target table contains an XML column
3. Either one of the following is also true:
   • The table contains a unique index defined on an XML column
   • ALLOW READ ACCESS was specified with the original LOAD command
   • COPY YES was specified

43

The partitioned table has detached dependent tables and cannot support the creation of partitioned indexes.

44

The table is a source table for an attach partition operation of an ALTER TABLE statement and the table has a deferred index cleanup operation in progress as the result of an MDC rollout. Since MDC rollout using the deferred index cleanup mechanism is not supported for partitioned indexes, the attach operation will not be allowed if there are any RID indexes on the source table that will be kept during the attach operation, not rebuilt, and are pending asynchronous index cleanup of the rolled-out blocks.

49

The ALTER TABLE statement specifies SET DATA TYPE for a column that has already been changed and a REORG is pending on the table.

50

The operation could not be performed on the table because a dictionary for the table is currently being created in a background process.

60

The operation did not complete successfully because the indexes on the table are not rebuilt. The asynchronous rebuild application, db2recindex, might be running slowly.

61

The operation did not complete successfully because the asynchronous rebuild of the indexes on the table failed.

Respond to this error according to the reason code:

21

Refer to the Administration Guide for information on Datalink Reconcile Pending (DRP) and Datalink Reconcile Not Possible (DRNP) states to take appropriate action.

22

Use SET INTEGRITY FOR table-name OFF before altering the table. Then alter the table and use SET INTEGRITY FOR table-name IMMEDIATE CHECKED FORCE GENERATED to generate the values for the new or altered column.

23

Reorg the table using the reorg table command.

24

Complete the unit of work that dropped the last LOB, LONG, or XML column, and re-issue the command.

25

Move the table out of set integrity pending state by using the SET INTEGRITY statement with IMMEDIATE CHECKED option, and then perform the operation again.

26

Wait for the REDISTRIBUTE DATABASE PARTITION GROUP command to complete and then reissue the ALTER TABLE statement.

27

Either rename or drop the SYSTOOLS.DB2LOOK_INFO table. The internal procedure will create the correct version of the SYSTOOLS.DB2LOOK_INFO table. Resubmit the alter table or copy schema operation.

29

Depending on the state of the table partition which is blocking the operation, take the appropriate action and then issue the command again:

1. SYSCAT.DATAPARTITIONS.STATUS = 'A': Execute the SET INTEGRITY statement with the IMMEDIATE CHECKED or IMMEDIATE UNCHECKED option on the table with attached partitions
2. SYSCAT.DATAPARTITIONS.STATUS = 'D': Execute the SET INTEGRITY statement with the IMMEDIATE CHECKED option on the dependent immediate materialized query and staging tables of the tables that still need to be incrementally maintained with respect to the detached partitions. Query the SYSCAT.TABDETACHEDDEP catalog view to locate these detached dependent tables.
3. SYSCAT.DATAPARTITIONS.STATUS = 'I': Wait until index cleanup for the detached partition is completed. Query the SYSIBM.SYSTASKS to determine progress.

30

Respond to reason code 30 by following these steps:

1. Change the state of the table from "Load in Progress" to "Normal" using the LOAD TERMINATE command.
2. Rerun the original LOAD command.

43

Use the SET INTEGRITY statement with the IMMEDIATE CHECKED option to maintain the dependent tables, then create the partitioned index.

44

Wait for the deferred index cleanup operation to complete on the source table, then reissue the ALTER TABLE statement to attach the partition. To monitor the progress of the rollout cleanup, use the LIST UTILITIES command.

49

If the attempted data type change is in the same unit of work as the pending data type change, roll back the pending change and then reissue the ALTER TABLE statement. Otherwise, reorganize the table using the REORG TABLE command and then try the data type change again.

50

Wait for the background process that is creating the dictionary for the table to complete, and then reissue the command.

60

Reissue the command. If the problem persists, contact your system administrator. The system might be overloaded. See reason code 61 for more information.

61

Reissue the command. If the problem persists, contact your system administrator. Administration log message ADM5543E reports the reason the rebuild failed. The index rebuild is attempted automatically on the next successful access. Message ADM5540W is written when the rebuild of the index object starts. ADM6651W is written when starting the rebuild of each index. ADM5542W is written when the index object has been successfully rebuilt. Run a query of sysproc.admin_get_index_info to determine which indexes still have REQUIRES_REBUILD set to Y. Run LIST APPLICATIONS to list any db2recindex applications that are rebuilding indexes asynchronously.

sqlcode: -20054

sqlstate: 55019

SQL20055N

A result column data type in the select list is not compatible with the defined data type for column column-name.

The data type of the select list expression corresponding to column-name is not assignable to the data type for the attribute of the structured type.

Examine the current definition for the table and the associated structured type. Ensure the select list expression data type for the specified column is data type that is assignable to the attribute of the structure type.

sqlcode: -20055

sqlstate: 42854

SQL20056N

Processing on DB2 Data Links Manager name encountered an error. Reason code = reason-code.

The statement cannot be processed.

sqlcode: -20056

sqlstate: 58004

SQL20057N

Column column-name in subview view-name cannot be defined as read only when the corresponding column is updatable in the superview.

The column identified by column-name in the subview view-name is defined (implicitly) as read only. The superview of view-name includes the corresponding column that is updatable. A column cannot be changed from updatable to read only in a typed view hierarchy.

The statement cannot be processed.

Change the CREATE VIEW statement so that the column of the subview view-name is updatable or drop the superview(s) and recreate them using the READ ONLY clause to force the column to be read only.

sqlcode: -20057

sqlstate: 428EB

SQL20058N

The statement failed because the fullselect specified for the materialized query table table-name violates a restriction. Reason code = reason-code.

Restrictions apply to the contents of a fullselect used in the definition of a materialized query table. Some restrictions are based on the materialized query table options, such as REFRESH DEFERRED or REFRESH IMMEDIATE. Other restrictions are based on whether or not the table is replicated. The fullselect in the statement that returned this condition violates at least one of these restrictions.

If this message is returned during the creation of a staging table, the error applies to the query used in the definition of the materialized query table with which the staging table is associated.

The reason code indicate which restriction was violated:

1

One or more of the select list elements have no name.

2

The fullselect referenced an unsupported object type.

3

The fullselect contained column references or expressions of an unsupported data type.

4

The fullselect contained column references or expressions or functions that violate one or more restrictions.

5

The REPLICATED option violated a restriction.

6

A fullselect violated a restriction when REFRESH IMMEDIATE was specified

7

The REFRESH IMMEDIATE option violated a restriction.

8

The REFRESH IMMEDIATE option was specified when a fullselect contained a GROUP BY clause and a restriction was violated.

9

The REFRESH IMMEDIATE option was specified and a fullselect was not a subselect.

10

The FROM clause referenced more than one table, and either the REFRESH IMMEDIATE option or the MAINTAINED BY REPLICATION option was specified.

11

The REFRESH IMMEDIATE option was specified and the input table expressions of a UNION ALL or a JOIN contained one or more aggregate functions.

12

The incremental maintenance of the materialized query table required space which exceeded the largest system temporary table space currently available in the database.

13

The fullselect included a CONNECT BY clause.

14

MAINTAINED BY FEDERATED_TOOL was specified in the CREATE TABLE statement and the select clause contained a reference to a base table.

15

An attempt was made to create an MQT in one of the following ways:

• A column-organized MQT is not defined as MAINTAINED BY REPLICATION but references a row-organized table
• A column-organized MQT does not specify the ORGANIZE BY COLUMN clause
• A row-organized MQT references a column-organized table

16

An attempt was made to create a column-organized materialized query table (MQT) in one of the following ways:

• Without specifying the MAINTAINED BY USER clause
• Without specifying the MAINTAINED BY REPLICATION clause
• By specifying the MAINTAINED BY SYSTEM clause without specifying the REFRESH DEFERRED and DISTRIBUTE BY REPLICATION clauses
• By specifying the REFRESH IMMEDIATE clause

17

The MAINTAINED BY REPLICATION clause was specified to create a shadow table, but the fullselect references a table that either violates a restriction or is missing a requirement of shadow tables.

18

The MAINTAINED BY REPLICATION clause was specified to create a shadow table, but the fullselect references columns that violate a restriction or that are missing a requirement for shadow tables.

19

The MAINTAINED BY REPLICATION clause was specified to create a shadow table, but the fullselect includes an expression or clause that is not supported with creating shadow tables.

20

The MAINTAINED BY REPLICATION clause was specified to create a shadow table, but the names of the columns of the shadow table do not exactly match the names of the selected columns of the base table.

Respond according to the reason code:

1

Ensure all elements have a name. You can use the AS clause to name expressions, or explicitly name all the columns in the column list of the materialized query table definition.

2

Do not reference unsupported objects.

3

Do not reference unsupported column or expression types.

4

Do not reference unsupported columns, expressions or functions.

5

Create the materialized query table as not replicated. Or correct the statement so the query refers to a single table and does not contain subqueries, aggregation, or the PARTITIONING clause.

6

Create the materialized query table as REFRESH DEFERRED, or:

• remove nickname references.
• remove DISTINCT.
• remove special registers and built-in functions that depend on the value of a special register.
• remove the not deterministic function or replace it with a deterministic function.
• remove all OLAP, sampling, and text functions.
• remove the aggregate function from the expression or change the expression to be a simple reference to the aggregate function.
• remove the aggregate functions or add a GROUP BY clause.
• correct the CREATE TABLE statement to ensure that no recursive common table expression is referenced.
• remove the subquery.

7

Create the materialized query table as REFRESH DEFERRED, or:

• correct the CREATE TABLE statement to ensure all GROUP BY items are in the select list.
• correct the GROUP BY clause to ensure there are no duplicate grouping sets.
• remove the nullable column, C, or add GROUPING(C) in the select list.
• correct the CREATE TABLE statement to ensure at least one unique key from each table referenced in the query appears in the select list.

8

Create the materialized query table as REFRESH DEFERRED, or:

• add COUNT(*) or COUNT_BIG(*) to the select list or remove the GROUP BY clause.
• add COUNT(*) to the select list or remove SUM(C), or alter the column C to be not nullable.
• remove unsupported aggregate functions or replace them with supported functions.
• remove the HAVING clause.
• correct the CREATE TABLE statement to ensure that the GROUP BY clause contains all of the partitioning key columns.

9

Create the materialized query table as REFRESH DEFERRED, or change the table definition to a subselect or to a UNION ALL in the input table expression of a GROUP BY.

10

Respond to reason code 10 in one of the following ways:

• If REFRESH IMMEDIATE is specified and the FROM clause used the explicit INNER JOIN syntax, change the FROM clause to reference a single table or replace the explicit INNER JOIN syntax with the implicit inner join syntax.
• If REFRESH IMMEDIATE was specified, replace it with REFRESH DEFERRED.
• If MAINTAINED BY REPLICATION was specified, change the FROM clause to reference a single table.

11

Create the materialized query table as REFRESH DEFERRED, or remove the aggregate functions from the input table of the UNION ALL or JOIN.

12

Create the materialized query table as REFRESH DEFERRED, or reduce the total row width, or number of columns of the MQT. Create a system temporary table space with suitable page size.

13

Ensure that the fullselect does not include a CONNECT BY clause. A hierarchical query cannot be used to create a materialized query table.

14

Rewrite the CREATE TABLE statement so that the select clause does not contain a reference to a base table.

15

Ensure that the column-organized MQT is referencing only column-organized tables or specifies MAINTAINED BY REPLICATION, or specifies ORGANIZE BY COLUMN. Also ensure that a row-organized MQT is referencing only row-organized tables. Then re-issue the statement.

16

Ensure that the statement contains one of the following clauses, then re-issue the statement.

• MAINTAINED BY USER
• MAINTAINED BY REPLICATION
• MAINTAINED BY SYSTEM, with the REFRESH DEFERRED and DISTRIBUTE BY REPLICATION clauses
• REFRESH DEFERRED, instead of REFRESH IMMEDIATE

17

To create a shadow table on the specified base table, alter the specified base table so that the table is supported as a base table for shadow tables.

18

To create a shadow table on the specified base table, include different columns in the fullselect or ensure that the specified columns satisfy all requirements.

19

Modify the fullselect to satisfy requirements for creating shadow tables.

20

Define the shadow table so that the names of the columns of the shadow table exactly match the names of the selected columns of the base table.

sqlcode: -20058

sqlstate: 428EC

SQL20059W

The materialized query table table-name may not be used to optimize the processing of queries.

The materialized query table is defined with REFRESH DEFERRED and a fullselect that is currently not supported by the database manager when optimizing the processing of queries. The rules are based on the materialized query table options (REFRESH DEFERRED or REFRESH IMMEDIATE). The fullselect in the CREATE TABLE statement that returned this condition violates at least one of the rules as described in the SQL Reference.

The materialized query table is successfully created but will only be routed to for queries that reference the materialized query table directly.

No action is required. However, if the materialized query was intended to optimize the processing of queries that do not reference the materialized query table directly, then this can be achieved as follows. Create a view using the fullselect specified for table-name and then re-create the materialized query table table-name using a fullselect that simply does a "SELECT *" from the view. This way, the materialized query table can be routed to by queries that reference the view.

sqlcode: +20059

sqlstate: 01633

SQL20060N

The key transform table function used by the index extension of index index-id of table table-id in tbspace-id generated duplicate rows.

The key transform table function specified by the GENERATE USING clause of the index extension used by index index-id generated duplicate rows. For a given invocation of the key transform table function, no duplicate rows should be produced. This error is occurred when inserting or updating the key value for the index index-id of table table-id in table space tbspace-id.

The statement cannot be processed.

The code for the key transform table function used by the index extension of index index-id must be modified to avoid the creation of duplicate rows.

SELECT IID, INDSCHEMA, INDNAME
  FROM SYSCAT.INDEXES AS I,
       SYSCAT.TABLES AS T
  WHERE IID = <index-id>
      AND TABLEID = <table-id>
      AND TBSPACEID = <tbspace-id>
      AND T.TBASCHEMA = I.TABSCHEMA
      AND T.TABNAME = I.TABNAME

sqlcode: -20060

sqlstate: 22526

SQL20062N

Transform function transform-type in transform group group-name for type type-name cannot be used for a function or method.

The transform function defined in the transform group group-name for type type-name cannot be used for a function or method because the transform function is not written in SQL (defined with LANGUAGE SQL). The transform group cannot be used for this function or method.

The statement cannot be processed.

Specify a transform group for type type-name that has the transform functions defined with LANGUAGE SQL.

sqlcode: -20062

sqlstate: 428EL

SQL20063N

TRANSFORM GROUP clause must be specified for type type-name.

The function or method includes a parameter or returns data type of type-name that does not have a transform group specified.

The statement cannot be processed.

Specify a TRANSFORM GROUP clause with a transform group name that is defined for type-name.

sqlcode: -20063

sqlstate: 428EM

SQL20064N

Transform group group-name does not support any data type specified as a parameter or returned data type.

The transform group group-name specified in the TRANSFORM GROUP clause is not defined for any data type that is included in the parameter list or the RETURNS clause of a function or method.

The statement cannot be processed.

Remove the transform group from the function or method definition.

sqlcode: -20064

sqlstate: 428EN

SQL20065N

Transform group group-name for data type type-name cannot be used to transform a structured type for use with a client application.

The statement cannot be processed.

For static embedded SQL, specify a different transform group using the TRANSFORM GROUP bind option. For dynamic SQL, specify a different transform group using the SET DEFAULT TRANSFORM GROUP statement.

sqlcode: -20065

SQL20066N

The transform-type transform function is not defined in the transform group group-name for data type type-name.

The transform-type transform function of transform group group-name for data type type-name is required for a transform group used in a function or method definition.

The statement cannot be processed.

If creating a function or method, specify a different transform group in the function or method definition. If referencing a structured type in a dynamic SQL statement, specify a different transform group for the CURRENT DEFAULT TRANSFORM GROUP special register. Alternatively, add a transform-type transform function to the transform group group-name for data type type-name.

sqlcode: -20066

sqlstate: 42744

SQL20067N

The transform-type transform function is defined more than once in the transform group group-name for data type type-name.

A TO SQL or FROM SQL transform function can only be specified once in a transform group. The transform group group-name for data type type-name has at least two FROM SQL or TO SQL (or both) transform functions defined.

The statement cannot be processed.

Delete the TO SQL or FROM SQL definitions from group-name in the transform definition so that there is only one of each.

sqlcode: -20067

sqlstate: 42628

SQL20068N

The structured type type-name may not be defined so that one of its attribute types directly or indirectly uses itself. The attribute attribute-name causes the direct or indirect use.

You cannot define a type so that one of its attribute types directly or indirectly uses itself. The type for attribute attribute-name is the cause of the direct or indirect use.

Evaluate the type and remove the attribute type that causes the direct or indirect use.

sqlcode: -20068

sqlstate: 428EP

SQL20069N

The RETURNS type of the routine-type routine-name is not the same as the subject type.

The method method-name specifies SELF AS RESULT. The RETURNS data type of the method must be the same as the subject data type of the method.

Change the RETURNS type of the method method-name to match the subject type.

sqlcode: -20069

sqlstate: 428EQ

SQL20075N

The index or index extension index-name cannot be created or altered because the length of column-name is more than 255 bytes.

The index could not be created or altered because the key column length is greater than 255.

• index-name is the index name.
• column-name is the name of the key column. If this error was returned from an ALTER TABLE or ALTER NICKNAME operation, then the value of column-name is the column number.

The index extension could not be created because a column returned by the GENERATE KEY function is greater than 255 bytes.

• index-name is the index extension name.
• column-name is the name of a column returned by the GENERATE KEY function.

The statement could not be processed. The specified index or index extension was not created, or the table or nickname could not be altered.

If creating an index, eliminate the column from the index definition. If altering a table, reduce the new column length to the permitted maximum. If creating an index extension, specify a different GENERATE KEY function, or redefine the function to eliminate the column.

sqlcode: -20075

sqlstate: 54008

SQL20076N

The instance for the database is not enabled for the specified action or operation. Reason code = reason-code.

An error has been detected at the instance level. The requested operation cannot be completed because a specified functional area was not installed or because a specified functional area was not enabled to the instance.

The following is the list of reason codes and associated functional areas you can enable at the instance level:

1. The ability to execute distributed request operations against multiple data sources in a single statement.

Enable the instance for the requested action or operation. First, install the specified functional area if it is missing. Then, enable the specified functional area. Enablement steps vary by reason-code:

1. For a federated server, set the DBM variable <FEDERATED> to YES and then restart the database manager.

sqlcode: -20076

sqlstate: 0A502

SQL20077N

Cannot construct structured type objects that have Datalink type attributes.

An attempt was made to invoke the constructor of a structured type which has a Datalink and/or a Reference type attribute. This functionality is currently not supported. In Version 6.1 or earlier, this error may also be issued for a structured type object with a Reference type attribute.

The statement cannot be processed.

The error can be corrected by doing one of the following:

1. Removing the invocation of the constructor of the type from the program.
2. Removing any Datalink (or Reference) type attributes from the definition of the structured type (this may not be possible if there are any tables that depend on this type).

sqlcode: -20077

sqlstate: 428ED

SQL20078N

Hierarchy object object-name of type object-type can not be processed using operation operation-type.

The operation operation-type was attempted using a hierarchy object named object-name of type object-type. This operation does not support processing of a hierarchy object.

The statement could not be processed.

Verify that the correct object name was used. For objects types TABLE or VIEW, the object must be the name of a subtable in the table or view hierarchy. In some cases, the object must specifically name the root table. For objects of type index, the name must be a name of an index created on a subtable.

sqlcode: -20078

sqlstate: 42858

SQL20080N

Method specification for method-name cannot be dropped because a method body exists.

The method specification method-name still has an existing method body that must be dropped before the method specification can be dropped.

The statement cannot be processed.

Use the DROP METHOD statement with the same method specification to drop the method body and then issue the ALTER TYPE statement again to drop the method specification.

sqlcode: -20080

sqlstate: 428ER

SQL20081N

The method body cannot be defined for a LANGUAGE language-type method specification method-name.

The method specificationmethod-name is defined with LANGUAGE language-type. If the LANGUAGE is SQL, the method body must be an SQL control statement. For other languages, the EXTERNAL clause must be specified.

The statement cannot be processed.

Change the method body to match the LANGUAGE specified in the method specification.

sqlcode: -20081

sqlstate: 428ES

SQL20082N

The dynamic type expression-type-id of the expression is not a subtype of the target data type target-type-id in a TREAT specification.

The dynamic data type of the result of the expression specified in the TREAT specification is expression-type-id. The specified target data type target-type-id is a proper subtype of expression-type-id which is not allowed.

The statement cannot be processed.

Change the target-type-id of the TREAT specification to a supertype of expression-type-id or change the expression so that the dynamic data type of the result is a subtype of target-type-id.

SELECT TYPEID, TYPESCHEMA, TYPENAME
FROM SYSCAT.DATATYPES
WHERE TYPEID IN INTEGER(
  expression-type-id),
  INTEGER(
    target-type-id
  )
)

sqlcode: -20082

sqlstate: 0D000

SQL20083N

The data type of the value returned by routine-type routine-id does not match the data type specified as RESULT.

The method routine-id specifies SELF AS RESULT and therefore requires that the data type of the value returned must be the same as the subject data type used to invoke the method. The RETURN statement in either the SQL method body or in the TO SQL transform function for the type of an external method resulted in the incorrect data type.

The statement cannot be processed.

Change the RETURN statement of the method or transform function to ensure that the data type of the returned value is always the subject type used to invoke the method.

SELECT FUNCSCHEMA, FUNCNAME,
       SPECIFICNAME
FROM   SYSCAT.FUNCTIONS
WHERE  FUNCID = INTEGER(
         routine-id
       )

sqlcode: -20083

sqlstate: 2200G

SQL20084N

The routine-type routine-name would define an overriding relationship with an existing method.

A function and a method may not be in an overriding relationship. This means that if the function were a method with its first parameter as subject S, it must not override another method of any supertype of S and it must not be overridden by another method of any subtype of S.

The statement cannot be processed.

Change the routine that is being defined to use a different routine name than routine-name or change the parameters of the routine.

sqlcode: -20084

sqlstate: 42745

SQL20085N

A routine defined with PARAMETER STYLE JAVA cannot have structured type type-name as a parameter type or as the returns type.

A routine is defined with PARAMETER STYLE JAVA and one of the parameter types or a returns type is defined using the structured type type-name. This is not supported by this version of DB2.

The statement cannot be processed.

Change to a different parameter style for the routine or remove the structured type from the routine definition.

sqlcode: -20085

sqlstate: 429B8

SQL20086N

Length of the structured type value for a column exceeds the system limit.

The value for a structured type column exceeds 1 gigabyte in overall size, including descriptor data for the instance. The column could be one that is being inserted or updated directly or it may be a column that is generated.

The statement cannot be processed.

Reduce the size of the structured type value that is being assigned to the column.

sqlcode: -20086

sqlstate: 54049

SQL20087N

DEFAULT or NULL cannot be used in an attribute assignment.

The UPDATE statement is using an attribute assignment to set the value of an attribute in a structured type column. This form of assignment statement does not allow the use of the keyword DEFAULT or the keyword NULL as the right hand side of the assignment.

The statement cannot be processed.

Specify an expression for the right hand side of the attribute assignment or change the assignment so it is not using the attribute assignment syntax.

sqlcode: -20087

sqlstate: 428B9

SQL20089N

A method name cannot be the same as a structured type name within the same type hierarchy.

A specified method name is the same as the structured type which is defined for one of the supertypes or subtypes of the structured type.

The statement cannot be processed.

Specify a different name for the method.

sqlcode: -20089

sqlstate: 42746

SQL20090W

The use of the structured type having attribute attribute-name of type DATALINK is effectively limited to the type of a typed table or type view.

The attribute attribute-name is defined with a type of DATALINK or a distinct type based on a DATALINK. A structured type that includes such an attribute can only be used as the type of a table or view. If used as the type of a column of a table or view it can only be assigned the null value.

The statement continued processing.

Consider the intended use of the structured type. If the type will be used as a column data type, then remove the attribute attribute-name from the structured type or use a data type other than DATALINK for the attribute.

sqlcode: +20090

sqlstate: 01641

SQL20092N

The statement failed because a table or view was specified in the LIKE clause and the object cannot be used in this context.

The LIKE clause for a CREATE GLOBAL TEMPORARY TABLE statement or DECLARE GLOBAL TEMPORARY TABLE statement specified the name of a table that has a column defined as IMPLICITLY HIDDEN. Since the implicitly hidden attribute is not supported for created temporary tables and declared temporary tables, the table cannot be specified in the LIKE clause.

Specify the name of a table that is not defined with an implicitly hidden column.

In order to specify a created temporary table or declared temporary table that includes columns that are defined as IMPLICITLY HIDDEN, use the AS (fullselect) option to explicitly specify those columns in the table. As a result, the IMPLICITLY HIDDEN attribute is not copied to the column being defined.

sqlcode: -20092

sqlstate: 560AE

SQL20093N

The table table-name cannot be converted to or from a materialized query table. Reason code = reason-code.

The ALTER TABLE statement is being used to change a table from a materialized query table to DEFINITION ONLY or to convert a regular table to a materialized query table. The ALTER TABLE statement failed as indicated by the following reason codes.

1

The table is a typed table or hierarchy table.

2

The table is not a materialized query table and DEFINITION ONLY was specified.

3

The table is a replicated materialized query table and DEFINITION ONLY was specified.

4

The table has at least one trigger defined.

5

The table has at least one check constraint defined.

6

The table has at least one unique constraint or unique index defined.

7

The table has at least one referential constraint defined.

8

The table is referenced in the definition of an existing materialized query table.

9

The table is referenced directly or indirectly (through a view, for example) in the fullselect.

10

The table is already a materialized query table.

11

The number of columns of the existing table does not match the number of columns defined in the select list of the fullselect.

12

The data types of the columns of the existing table do not exactly match the corresponding columns in the select list of the fullselect.

13

The column names of the columns of the existing table do not exactly match the corresponding column names in the select list of the fullselect.

14

The nullability characteristics of the columns of the existing table do not exactly match the nullability characteristics of the corresponding columns in the select list of the fullselect.

15

The conversion cannot be performed if there are any other table alterations in the same ALTER TABLE statement.

16

The table is referenced in the definition of an existing view enabled for query optimization.

17

The table is a protected table.

18

The fullselect refers to a nickname on which caching is not allowed.

19

The table is a system-period temporal table or a history table.

20

The table has a permission or mask defined by a security administrator.

21

An attempt was made to convert the table into a shadow table by specifying the MAINTAINED BY REPLICATION clause, but the table cannot be converted to a shadow table because the table is organized by row.

22

An attempt was made to convert the table into a shadow table by specifying the MAINTAINED BY REPLICATION clause, but the table cannot be converted to a shadow table because the table has a unique constraint or index other than a primary key, or the primary key was defined as NOT ENFORCED.

Respond according to the reason code:

1

The table cannot be converted to a materialized query table. Create a new materialized query table instead.

2

There is no need to convert this table. No action required.

3

A replicated table can only be a materialized query table. Create a new table instead.

4

Drop any triggers and try the ALTER TABLE statement again.

5

Drop any check constraints and try the ALTER TABLE statement again.

6

Drop any unique constraints and unique indexes. Try the ALTER TABLE statement again.

7

Drop any referential constraints and try the ALTER TABLE statement again.

8

Drop the materialized query table that references the table and try the ALTER TABLE statement again.

9

A materialized query table cannot reference itself. Modify the fullselect to remove the direct or indirect reference to the table being altered.

10

The operation is not allowed since the table is already a materialized query table.

11

Modify the fullselect to include the correct number of columns in the select list.

12

Modify the fullselect so that the result column data types exactly match the data types of the corresponding existing columns.

13

Modify the fullselect so that the result column names exactly match the column names of the corresponding existing columns.

14

The table cannot be converted to a materialized query table unless the nullability characteristics can be matched. Create a new materialized table instead.

15

Perform the other table alterations in an ALTER TABLE statement that does not include the SET MATERIALIZED QUERY AS clause.

16

Disable the view enabled for query optimization that references the table and try the ALTER TABLE statement again.

17

Either remove the protection from the table or do not convert it to a materialized query table.

18

Correct the fullselect specified in the ALTER TABLE statement so that it does not reference a nickname on which caching is not allowed.

19

Either correct the table name to specify a table that is not a system-period temporal table or history table, or alter the system-period temporal table with an ALTER TABLE statement that specifies a DROP VERSIONING clause.

20

Either remove the permissions and masks or do not convert it to a materialized query table.

21

To convert the table into a shadow table, first convert the table to be organized by column.

22

To convert the table into a shadow table, remove all unique constraints and indexes other than a primary key from the table, or define the primary key as ENFORCED.

sqlcode: -20093

sqlstate: 428EW

SQL20094N

The statement failed because the column column-name is a generated column or is defined with the data type DB2SECURITYLABEL and cannot be used in the BEFORE trigger trigger-name.

The indicated column cannot be named in the column name list of a BEFORE UPDATE trigger or set in a BEFORE trigger because it is one of the following:

• A row-begin column
• A row-end column
• A transaction-start-ID column
• A generated expression column
• A column defined with the data type DB2SECURITYLABEL

The statement cannot be processed.

Remove the column from either the column name list or the SET assignment statement that sets the new transition variable of a generated column and resubmit the statement.

sqlcode: -20094

sqlstate: 42989

SQL20102N

The CREATE or ALTER statement for the routine routine-name specified the option-name option which is not allowed for the routine.

The option option-name was specified when creating or altering the routine routine-name. The option does not apply to the routine because of other characteristics of the routine. For sourced procedures, only ALTER PARAMETER can be specified, and ALTER PARAMETER can only be specified for sourced procedures.

For an ALTER statement, ensure that the correct routine is being specified. Otherwise, remove the failing option and reissue the statement.

sqlcode: -20102

sqlstate: 42849

SQL20108N

A result set contains an unsupported data type in position position-number for the cursor cursor-name opened by the stored procedure procedure-name.

The stored procedure named by procedure-name cannot return at least one of its query result sets named by cursor-name because at least one of the columns, column position-number contains a data type which is not supported by either the DRDA Application Requestor (client) or the DRDA Application Server (server). As such the call to the stored procedure fails.

Modify the OPEN statement (and subsequent FETCH statements) for cursor cursor-name in the stored procedure procedure-name on the server to not select the unsupported data type in column position-number. The client application which invoked the stored procedure may need to be modified to reflect the change in the stored procedure.

sqlcode: -20108

sqlstate: 56084

SQL20109W

Error in DB2 debugger support. Reason code: reason-code.

The debugger support had an error situation which will disable debugging, but not affect normal execution. The following is a list of reason codes:

1. The debugger support is not installed.
2. There has been a syntax error in IP address of debugger client in the debugger table.
3. A timeout in the communication between the debugger backend and the debugger client occurred.
4. A problem occurred accessing the debugger table DB2DBG.ROUTINE_DEBUG.

1. Verify that you installed the debugger option on the database server machine.
2. Make sure that the IP address in the debugger table has the correct syntax.
3. Check that the debugger daemon on the client is started and that the ports on the client and server match.
4. Verify that you have created the debugger tables with the correct layout.

sqlcode: +20109

sqlstate: 01637

SQL20111N

A SAVEPOINT, RELEASE SAVEPOINT, or ROLLBACK TO SAVEPOINT statement cannot be issued in this context. Reason code = reason-code.

The statement cannot be processed because it violates a restriction as indicated by the following reason code:

1. Savepoint cannot be issued inside a trigger.
2. Savepoint cannot be issued inside a global transaction.

The statement cannot be processed.

Remove the SAVEPOINT, RELEASE SAVEPOINT, or ROLLBACK TO SAVEPOINT statement in the trigger or global transaction.

sqlcode: -20111

sqlstate: 3B503

SQL20112N

A savepoint cannot be set because a savepoint already exists and nested savepoints are not supported.

A savepoint is a named entity that represents the state of data and schemas at a particular point in time within a unit of work. You can use savepoints in several ways. For example, you can roll a database back to a savepoint. You can set a savepoint within a transaction using the SAVEPOINT statement. In some environments, you can also set multiple, or nested, savepoints within the same transaction.

This message can be returned when an error occurred in a SAVEPOINT statement or atomic compound SQL statement for the following reasons:

• An attempt has been made to set a nested savepoint, but a savepoint already exists and nested savepoints are not supported in this environment.
• An attempt has been made to set a nested savepoint for a federated data source that does not support nested savepoints.

Respond to this error in one of the following ways:

• Release existing savepoints before attempting to set new savepoints.
• To re-establish an existing savepoint perform the following steps:
  1. Free the existing savepoints using the RELEASE SAVEPOINT statement.
  2. Recreate the savepoint using the SAVEPOINT statement.
• For atomic compound SQL: set the savepoint after the end of the compound statement.

sqlcode: -20112

sqlstate: 3B002

SQL20113N

Null cannot be returned from method method-id defined with SELF AS RESULT.

The method with method identifier method-id is defined with SELF AS RESULT. The invocation of the method used a non-null instance of a structured type so the method cannot return a null instance.

SELECT FUNCSCHEMA, FUNCNAME,
       SPECIFICNAME
  FROM SYSCAT.FUNCTIONS
  WHERE FUNCID = method-id

sqlcode: -20113

sqlstate: 22004

SQL20114W

Column column-name in table table-name is not long enough for the defined length of the USER default value.

The column column-name is defined with a length that is less than 128 bytes. The clause DEFAULT USER has been specified for this column. Since the USER special register is defined as VARCHAR(128), any attempt to assign the default value for table-name by a user with a user ID longer than the column length results in an error. A user with a user ID longer than the column length would never be able to insert or update this column to the default value.

If your system standards would not allow a user ID to exceed the length of the column, then this warning may be ignored. To prevent this warning from occurring, the length of the column must be at least 128 bytes. You can change the column length by dropping and creating the table again, or, if the data type is VARCHAR, by using ALTER TABLE to increase the length of the column.

sqlcode: +20114

sqlstate: 01642

SQL20115N

The routine-type routine-name cannot be used as a transform-type transform function in transform group group-name.

If routine-type is FUNCTION, then the function defined by routine-name cannot be used as a transform function because it is a built-in function. If routine-type is METHOD, then the method defined by routine-name cannot be used as a transform function because it is a method.

The statement cannot be processed.

Specify a different function for the transform-type transform function of transform group group-name.

sqlcode: -20115

sqlstate: 428EX

SQL20116N

The data type of the search target parameter-name does not match that of the source key specified in the index extension index-extension-name.

If the search target is of a built-in or distinct data type, its type must exactly match that of the source key specified in the index extension. If the data type of the search target is a structured type, it must be in the same structured type hierarchy as the data type of the source key in the index extension.

The statement cannot be processed.

Specify a search target with a data type that matches that of the source key in the index extension.

sqlcode: -20116

sqlstate: 428EY

SQL20117N

A window specification for an OLAP function is not valid. Reason code = reason-code.

The statement cannot be processed.

sqlcode: -20117

sqlstate: 428EZ

SQL20118N

Structured type type-name has more than the maximum number of allowable attributes. The maximum is max-value.

The maximum number of attributes, including inherited attributes, allowed for each structured type has been exceeded with the definition of structured type type-name. The maximum number of attributes, including inherited attributes, is max-value.

The statement cannot be processed.

Ensure that the number of attributes for the structured type does not exceed the limit.

sqlcode: -20118

sqlstate: 54050

SQL20119N

A ROW function must define at least two columns.

A function that specifies ROW in the RETURNS clause must include a column list with at least two columns.

Either remove the ROW keyword from the RETURNS clause to make it a scalar function or specify multiple columns in the column list of the RETURNS clause.

sqlcode: -20119

sqlstate: 428F0

SQL20120N

An SQL TABLE function must return a table result.

An SQL function that specifies TABLE in the RETURNS clause must return a result that is a table. With the exception of a scalar fullselect, a scalar expression cannot be returned as the result of an SQL TABLE function.

Either remove the TABLE keyword from the RETURNS clause to make it a scalar function or specify a fullselect in the RETURN statement of the TABLE function body.

sqlcode: -20120

sqlstate: 428F1

SQL20121N

Only one of WITH RETURN or SCROLL can be specified for cursor cursor-name.

Both WITH RETURN and SCROLL were specified for cursor cursor-name, but this is not allowed.

The statement cannot be processed.

Change the DECLARE CURSOR statement to either specify NO SCROLL (or remove the SCROLL keyword), or remove the WITH RETURN clause.

sqlcode: -20121

sqlstate: 428F3

SQL20123N

Call to stored procedure procedure failed because the result set returned for a scrollable cursor is not positioned before the first row.

A scrollable result set has been returned by a CALL to stored procedure procedure, and one or more of these cursors is not positioned before the first row.

The CALL to the stored procedure was not successful. All result set cursors defined in the stored procedure were closed before returning to the caller. The scrollable cursor cannot be used to FETCH from the result set. Actions done by the stored procedure are not rolled back, and any external actions initiated by the stored procedure have completed because the error was detected at the end of the execution of the stored procedure.

Modify the content of the stored procedure to make sure that the result set cursors are positioned before the first row before returning to the caller.

sqlcode: -20123

sqlstate: 560B1

SQL20128N

Cursor cursor-name is scrollable, but the result table cannot include output from a table function.

The cursor cursor-name is defined to be scrollable, but the result table includes output from a table function. This combination is not supported.

The statement cannot be processed.

Either modify the definition of the cursor so it is not scrollable, or ensure that the result table does not include output from a table function.

sqlcode: -20128

sqlstate: 428F6

SQL20131N

Object number object-number of type object-type was specified more than once in a list of objects.

In a list of object names of type object-type, the object numbered object-number was specified more than once. The operation of the statement cannot be performed on the object more than once.

Correct the duplicated object in the list removing duplicate occurrences. (In the MDC case, the object type will be “dimension”.)

sqlcode: -20131

sqlstate: 42713

SQL20133N

Operation operation-name cannot be performed on external routine routine-name. The operation can only be performed on SQL routines.

You attempted to perform operation operation-name on external routine routine-name. However, you can only perform that operation on SQL routines. The operation did not complete successfully.

Ensure the name you provide identifies an SQL routine.

sqlcode: -20133

sqlstate: 428F7

SQL20134N

The SQL Archive (SAR) file for routine routine-name could not be created on the server.

The creation of the SQL archive (SAR) for routine routine-name failed because the database manager could not find either the library or the bind file for the specified routine. Bind files are only available for SQL routines created with DB2 Version 7.1, FixPak 2 or later.

Recreate the procedure on a server with DB2 Version 7.1, FixPak 2 or later, and try the operation again.

sqlcode: -20134

sqlstate: 55045

SQL20135N

The specified SQL archive does not match the target environment. Reason code = reason-code.

Ensure that the environment on which the SQL archive was created matches the target environment and reissue the command. If the environments do not match, you must manually create the SQL routine using the target environment.

sqlcode: -20135

sqlstate: 55046

SQL20136N

Routine routine-name (specific name specific-name) attempted to access a federated object.

An SQL statement in an external function or method attempted to access one or more federated objects. This statement is executed from routine routine-name (specific name specific-name). It is currently not supported to access a federated object from an external function or method.

Remove the references to federated objects from the routine.

sqlcode: -20136

sqlstate: 55047

SQL20138N

The statement may not be explained because the routine routine-name (specific name specific-name) is not defined as MODIFIES SQL DATA.

The routine routine-name (specific name specific-name) is defined as either CONTAINS SQL or READS SQL DATA and attempted to explain an SQL statement. Explaining an SQL statement requires writing to the explain tables, which is only permitted in a MODIFIES SQL DATA routine.

Do not attempt to explain SQL statements from a routine defined as either CONTAINS SQL or READS SQL DATA.

sqlcode: -20138

sqlstate: 42985

SQL20139N

SQL statements may not be issued in routine routine-name (specific name specific-name) because of a previous statement failed or was interrupted.

During the execution of routine routine-name (specific name specific-name), or a nested routine, either a statement failed and requires a roll back or an interrupt occurred. It is necessary for all routines invoked from the outer-most statement to finish executing and for control to be passed back to the outer-most statement so that the database manager may perform the necessary recovery. Until this recovery has been completed, SQL statements may not be issued.

The routine continues to execute. The routine should not execute any further SQL statements and should return control to the invoking statement as quickly as possible.

The recovery for the initial failure of interrupt will be automatically performed by the database manager once all routines have completed.

sqlcode: -20139

sqlstate: 51038

SQL20140W

COMPRESS column attribute ignored because VALUE COMPRESSION is deactivated for the table.

To allow COMPRESS to be specified for the column, ALTER the table and activate VALUE COMPRESSION for the table.

sqlcode: +20140

sqlstate: 01648

SQL20142N

Sequence sequence-name cannot be used as specified.

sequence-name was referenced in a context in which it cannot be used. sequence-name is a sequence generated by the system. It was generated for one of the following purposes:

• An identity column.
• The distribution key for a random distribution table using the random by generation method.
• The system hidden SYSROWID column of a table enabled for row modification tracking.

These sequences cannot be referenced in a DROP SEQUENCE, GRANT or REVOKE statement, or in a NEXT VALUE or PREVIOUS VALUE expression.

Specify the name of a user-defined sequence object in this context.

sqlcode: -20142

sqlstate: 428FB

SQL20143N

The encryption or decryption function failed, because the ENCRYPTION PASSWORD value is not set.

The ENCRYPTION PASSWORD value is not set.

Issue the SET ENCRYPTION PASSWORD statement to set the ENCRYPTION PASSWORD value. The length of the password must be a minimum of 6 bytes and a maximum of 127 bytes.

sqlcode: -20143

sqlstate: 51039

SQL20144N

The encryption password is invalid because the length of the specified password was less than 6 bytes or greater than 127 bytes.

The data must be encrypted with a password length between 6 and 127.

Ensure that the password length is between 6 and 127.

sqlcode: -20144

sqlstate: 428FC

SQL20145N

The decryption function failed. The password used for decryption does not match the password used to encrypt the data.

The data must be decrypted using the same password that was used to encrypt the data.

Ensure that the same password is used to encrypt and decrypt the data.

sqlcode: -20145

sqlstate: 428FD

SQL20146N

The decryption function failed. The data is not encrypted.

The data must be a result of the ENCRYPT function.

Ensure that the data type is a result of the ENCRYPT function.

sqlcode: -20146

sqlstate: 428FE

SQL20147N

The ENCRYPT function failed. Multiple pass encryption is not supported.

Data that has already been encrypted cannot be encrypted again.

Ensure that the data has not already been encrypted.

sqlcode: -20147

sqlstate: 55048

SQL20148N

Routine routine-name with specific name specific-name must have the RETURN statement as the last SQL statement of the compound body.

The RETURN statement must be the last SQL statement of the compound body in an SQL ROW or TABLE function. No other RETURN statement is allowed within the routine body.

Ensure there is only one RETURN statement and it is the last SQL statement of the compound body.

sqlcode: -20148

sqlstate: 429BD

SQL20149W

The buffer pool operation has been completed but will not take effect until the next database restart.

The buffer pool has been successfully created or altered, but the changes will not take effect immediately. The changes will take effect when the database is restarted.

To have the changes take effect at next database restart time, no further action is required.

sqlcode: +20149

sqlstate: 01649

SQL20150N

The statement failed because the number of block pages for a buffer pool is too large for the size of the buffer pool.

You can optimize performance for sequential prefetching by using block-based buffer pools. When creating or altering a buffer pool, you can specify the number of pages that should exist in the block-based area by using the NUMBLOCKPAGES clause of the CREATE BUFFERPOOL statement or the ALTER BUFFERPOOL statement.

The number of pages that are specified to exist in the block-based area must not exceed 98 percent of the total number of pages in the buffer pool. This message is returned when an attempt is made to configure more than 98 percent of the pages in a block-based buffer pool to exist in the block-based area.

Respond to this message in one of the following ways:

• Disable block-based I/O for this buffer pool by setting NUMBLOCKPAGES to zero.
• Reduce the number of pages specified to exist in the block-based area:
  1. Determine the total number of pages for this buffer pool by examining the NPAGES column of the SYSCAT.BUFFERPOOLS catalog view.
  2. Specify a value for NUMBLOCKPAGES that is not greater than 98 percent of the total number of pages.

sqlcode: -20150

sqlstate: 54052

SQL20151N

The value specified for BLOCKSIZE is not in the valid range.

The valid range for the value of BLOCKSIZE is 2 to 256.

Change the value for BLOCKSIZE to be greater than or equal to 2 and less than or equal to 256. An optimal value would be the extent size.

sqlcode: -20151

sqlstate: 54053

SQL20152N

The specified buffer pool is not currently block-based.

The BLOCKSIZE option was used without specifying the number of pages to use in the block area of the buffer pool.

Specify a value for NUMBLOCKPAGES along with the BLOCKSIZE option.

sqlcode: -20152

sqlstate: 428FF

SQL20153N

The split image of the database is in the suspended state.

The database split image cannot be used while it is in the suspended state.

To resume I/O for this database split image, issue one of the following db2inidb commands:

• db2inidb <db-name> as mirror
• db2inidb <db-name> as snapshot
• db2inidb <db-name> as standby

In a DB2 pureScale environment, you can issue this command from any member and need to issue the command only once.

In a partitioned database environment, you must execute the db2inidb command on each database partition. You can run the command concurrently on each database partition.

sqlcode: -20153

sqlstate: 55040

SQL20154N

The requested insert or update operation into view view-name is not allowed because no target table can be determined for a row. Reason code = reason-code.

The specified view contains a UNION ALL query. The reason-code indicates that a given row either:

1. does not satisfy the check constraint of any underlying base table, or
2. satisfies all the check constraints for more than one underlying base table.

Federated system users: Some other data source specific limitation may be preventing the row from being inserted.

Ensure that the check constraints used by the underlying base tables to partition their rowsets cover the set of rows to be inserted. Also, ensure that for a view defined with UNION ALL for its fullselect that WITH ROW MOVEMENT is also specified if updates are to move rows from one underlying table to another. For example, given the check constraints (T1.c1 in (1,2)) on T1, and (T2.c1 in (2,3)) on T2, and view V1 as a union of T1 and T2,

1. the row c1 = 4 does not satisfy the check constraints of either underlying base table and
2. the row c1 = 2 satisfies the check constraints of both underlying base tables.

Federated system users: If the reason is unknown, isolate the problem to the data source failing the request and examine the object definition and the update restrictions for that data source.

sqlcode: -20154

sqlstate: 23513

SQL20155N

Creating or activating the event monitor failed because the specified event monitor target tables are invalid. Reason code: reason-code.

The reason code indicates more specifically what the problem is:

1

At least one column name does not match an event monitor data element identifier.

2

At least one column has a data type that is incompatible with the data type for an event monitor data element identifier.

3

At least one column name matches an event monitor data element identifier, but that element is not allowed in the target table.

4

The row size for the table is too large for the page size of the table space.

5

A mandatory column is missing.

6

The table must not be declared with CCSID UNICODE if the database is not a Unicode database.

7

The table is partitioned.

8

The name of the table specified for storing event monitor output is already in use by another event monitor.

9

An event monitor target table exists for a logical data group that is not supported in the current release.

10

The table is a column-organized table.

11

The table includes an expression-based index.

Check the administration notification log for detailed information and correct the table definition.

sqlcode: -20155

sqlstate: 55049

SQL20156W

The event monitor was activated successfully, however some monitoring information may be lost.

An event monitor activated successfully, however it was determined that the event monitor may lose some information because of one of the following:

• The data type for a column is smaller than the data type required to hold an event monitor element identifier. This data will be truncated.
• A target table was found in the SYSCAT.EVENTTABLES, but that table does not exist in the database. All monitor information for the corresponding table will not be recorded.
• A target table was found in the SYSCAT.EVENTTABLES, but that table does not reside on all database partitions. Monitor information on some partitions will not be recorded
• The buffer size of a statistics event monitor that writes to a file is too small to accommodate the largest record.

Check the administration notification log for detailed information.If this is a statistics event monitor, check the buffer size; if it is too small, recreate the event monitor with a buffer size of at least 4. For other types of event monitors, recreate the event monitor to create all target tables if necessary.

sqlcode: +20156

sqlstate: 01651

SQL20157N

User with authorization ID authorization-ID failed to attach to a quiesced instance, or connect to a quiesced database or a database in a quiesced instance which is in the following quiesce mode: quiesce-mode

The specified authorization ID does not have the authority to attach to a quiesced instance or connect to a database in a quiesced instance when the instance is in QUIESCE RESTRICTED ACCESS mode. To be able to attach to the instance or connect to the database, the authorization ID must satisfy one of the following listed criteria:

• Hold SYSADM, SYSCTRL, or SYSMAINT authority
• Be the user that was specified using the USER option of the QUIESCE INSTANCE or START DATABASE MANAGER commands (or db2InstanceQuiesce or db2InstanceStart APIs)
• Be a member of the group that was specified using the GROUP option of the QUIESCE INSTANCE or START DATABASE MANAGER commands (or db2InstanceQuiesce or db2InstanceStart APIs)

In the event the quiesced database is in QUIESCE DATABASE mode, then the authorization ID must satisfy one of the previously listed criteria or hold either the DBADM authority or QUIESCE_CONNECT privilege before the user can successfully connect to a quiesced database.

In the event the database in a quiesced instance is in QUIESCE INSTANCE mode, then the authorization ID must satisfy one of the above listed criteria or hold the DBADM authority before the user can successfully connect to a database in a quiesced instance.

In the event the instance is in QUIESCE INSTANCE mode, then the authorization ID must satisfy one of the above listed criteria before the user can successfully attach to the quiesced instance.

You can take one of the following actions to successfully connect to a quiesced database or a database of a quiesced instance, or attach to a quiesced instance:

• To connect to the database, wait for the database to be unquiesced.
• To attach to the instance or connect to a database in the instance, wait for the instance to be unquiesced.
• Retry connecting to the database or attaching to the instance using an authorization ID that has sufficient authority.

sqlcode: -20157

sqlstate: 08004

SQL20158N

DB2 Data Links Manager is not supported in this DB2 copy version.

The DB2 Data Links Manager is not supported in this DB2 copy version and an attempt was made to perform one of the following actions:

• Restore a database backup image for a database enabled for Data Links.
• Upgrade a database which uses the DATALINK data type.
• Create a database object which uses the DATALINK data type. Database objects that use a DATALINK data type include tables, views, functions, methods, distinct types and structured data types.

Perform one of the following actions:

• RESTORE the database backup image in a DB2 copy of a previous release that supports Data Links, disable the use of Data Links, back up the database, and then re-issue the RESTORE DATABASE command using the DB2 copy version to which you want to upgrade the database.
• Using a DB2 copy of a previous release that supports Data Links, disable the use of Data Links and then re-issue the UPGRADE DATABASE command.
• Remove all references to the DATALINK data type and then re-issue the statement to create the database object.

sqlcode: -20158

sqlstate: 42997

SQL20159W

The isolation clause or concurrent-access-resolution clause is ignored because of the statement context.

The isolation clause or concurrent-access-resolution clause is specified on a statement that is included in a compound statement that is processed as inline SQL. The clause is ignored. The default isolation level is used for all statements in the compound statement.

No response required. Remove the isolation clause or concurrent-access-resolution to prevent this warning.

sqlcode: +20159

sqlstate: 01652

SQL20160W

The authorizations were granted to USER userid. Groups were not considered because the authorization name is more than 8 bytes.

The authorization name has a length of more than 8 bytes. The privilege is granted to the user with authorization name userid without considering groups defined in the system that might have a matching name. Processing continues.

If the grant was intended for a user, no action is required. If the grant was intended for a group, consider choosing an alternate group because group names greater than 8 bytes are not supported. To avoid this warning message, specify the USER keyword before the authorization name.

sqlcode: +20160

sqlstate: 01653

SQL20161W

The column name column-name is not a valid column for an event monitor table.

The column name specified in the INCLUDES or EXCLUDES clause does not match any valid column for the event monitor table(s) being created.

Examine and correct the specified column name.

sqlcode: -20161

sqlstate: 428AA

SQL20165N

An SQL data change statement within a FROM clause is not allowed in the context in which it was specified.

If any input variables are used in other parts of the query, a multiple row INSERT in the FROM clause must not include the USING DESCRIPTOR clause. A multiple row INSERT statement in the FROM clause cannot specify NOT ATOMIC. A SQL fullselect within an XQuery statement cannot include an SQL data change statement in the FROM clause. An SQL fullselect in the default clause of a global variable definition cannot include an SQL data change statement in the FROM clause.

The statement cannot be processed.

Change the statement so that the SQL data change statement within a FROM clause is used in a supported context and is the only table-reference in the FROM clause.

sqlcode: -20165

sqlstate: 428FL

SQL20166N

An SQL data change statement within a SELECT specified a view view-name which is not a symmetric view or could not have been defined as a symmetric view.

The target view of the SQL data change statement within a SELECT statement must be defined WITH CASCADED CHECK OPTION or the fullselect in the view definition (or the fullselect of a view definition of a referenced view) must be able to be defined using WITH CASCADED CHECK OPTION.

A symmetric view is a view defined implicitly or explicitly with the WITH CASCADED CHECK OPTION.

The statement cannot be processed.

Do not use the SQL data change statement within a SELECT with the specified view.

sqlcode: -20166

sqlstate: 428FM

SQL20167N

The shared memory set is not large enough to process the request.

Try the request again. If the error persists, stop and restart the instance to allow the larger shared memory set size (automatically updated by DB2) to take effect and try the request again.

sqlcode: -20167

sqlstate: 57011

SQL20168N

The ALTER BUFFERPOOL statement is currently in progress.

A buffer pool cannot be dropped or altered if an ALTER operation is already in progress.

Wait until the ALTER operation has completed. Use the snapshot monitor to check the progress of the ongoing ALTER operation.

sqlcode: -20168

sqlstate: 55051

SQL20169W

The buffer pool is not started.

The statement was successful, but it will only take effect when the buffer pool is started.

The statement has completed successfully, and will take effect when the database is activated. This happens after all applications disconnect. For the statement to take effect immediately, re-submit it when the buffer pool is started. To start the buffer pool, it is possible in some cases to drop and re-create the buffer pool using the IMMEDIATE option.

sqlcode: +20169

sqlstate: 01654

SQL20170N

There is not enough space in the table space tablespace-name for the specified action. Reason code = reason-code.

1

Use the snapshot monitor to find the number of useable pages in the tablespace and the tablespace high-water mark. The difference between these values is the maximum number of pages that can be removed.

2

Use the snapshot monitor to find the number of useable pages in the tablespace and the tablespace extentsize. The number of useable extents in the tablespace is equal to the useable pages divided by the extentsize. There must be at least 5 extents worth of useable pages in the tablespace.

sqlcode: -20170

sqlstate: 57059

SQL20173W

The event monitor was created successfully but at least one event monitor target table already exists.

While an event monitor was being created, the database manager tried to create one or more target tables but determined that tables with those names already exist. The event monitor was successfully created and target tables were not created to replace tables of the same name that already exist. When the event monitor is activated, it will attempt to use these tables. Event monitor activation may fail if activation processing determines these tables are not suitable.

Check the administration notification log for detailed information. If necessary, drop all target tables and recreate the event monitor to create all target tables.

sqlcode: +20173

sqlstate: 01655

SQL20178N

View view-name already has an INSTEAD OF trigger trigger defined.

The view view-name already has an INSTEAD OF trigger defined for the indicated operation (UPDATE, DELETE, INSERT). Only one INSTEAD OF trigger can be defined for each operation on the view.

The statement cannot be processed. The INSTEAD OF trigger was not created.

If a new INSTEAD OF trigger is required, drop the existing trigger and then create the new trigger.

sqlcode: -20178

sqlstate: 428FP

SQL20179N

An INSTEAD OF trigger cannot be created because of how the view view-name is defined.

An INSTEAD OF trigger cannot be defined on:

• a view defined using WITH CHECK OPTION
• a view on which such a view has been defined either directly or indirectly
• a view on which such a view has been defined either directly or indirectly
• a view that references an unfenced nickname and the Database Partitioning Feature is enabled

An INSTEAD OF UPDATE trigger cannot be defined on:

• A view nested in a view defined with the WITH ROW MOVEMENT clause
• The view may be the target view of the INSTEAD OF trigger or it may be a view that depends directly or indirectly on the target view of the trigger.
• The statement cannot be processed. The INSTEAD OF trigger was not created.

• If the view is defined using WITH CHECK OPTION, remove the WITH CHECK OPTION clause.
• If the view is nested in a view defined with the WITH ROW MOVEMENT clause, remove the WITH ROW MOVEMENT clause.
• If the view references an unfenced nickname, specify a different view.

sqlcode: -20179

sqlstate: 428FQ

SQL20180N

column column-name in table table-name cannot be altered as specified

Column column-name cannot be altered for one of the following reasons:

• ADD COLUMN cannot be specified on ALTER TABLE if the table is defined as a history table.
• ALTER COLUMN cannot be specified on ALTER TABLE if the table is defined as a history table.
• ALTER COLUMN with SET GENERATED cannot be specified on ALTER TABLE for a column of a history table.
• ALTER COLUMN with SET GENERATED AS cannot be specified on ALTER TABLE for a column that already is a generated column or has a defined default.
• DROP COLUMN cannot be specified on ALTER TABLE if the table is defined as a history table.
• DROP COLUMN with DROP NOT NULL cannot be specified on ALTER TABLE for a column defined as part of a BUSINESS_TIME period.
• DROP COLUMN with DROP GENERATED cannot be specified on ALTER TABLE for a column defined as row-begin or row-end on a system-period temporal table.
• ALTER COLUMN with DROP GENERATED, SET NOT HIDDEN or SET IMPLICITLY HIDDEN cannot be specified on ALTER TABLE for a random distribution key column of a random distribution table using random by generation method

The statement cannot be processed.

Change the name of the column to a column that can be altered or dropped, and recreate the table with the necessary attributes.

sqlcode: -20180

sqlstate: 428FR

SQL20183N

The table table-name is not compatible with the specified table partitioning operation.

The partitioning clause for table table-name is not valid because:

ADD PARTITION BY was specified on an ALTER TABLE statement CREATE INDEX statement or CREATE TABLE statement, but the table is already a partitioned table.

ADD PARTITION, ALTER PARTITION, DROP PARTITION, or DROP DISTRIBUTION was specified on an ALTER TABLE statement, but the table is not a partitioned table, the table is a materialized query table, or a materialized query table is defined on this table.

ADD PARTITION for HASH partitions was specified on an ALTER TABLE statement, but the table is not partitioned using hashing.

DROP PARTITION of a data partition was specified on the ALTER TABLE statement, but the PRESERVE ROWS clause was used. The PRESERVE ROWS clause is only valid for partitioned tables that have hash partitioning.

Change the statement to one that is valid or specify a different table and reissue the statement.

sqlcode: -20183

sqlstate: 428FT

SQL20188N

The primary key or a unique key identified by name is a subset of the columns in the ORGANIZE BY clause.

All the columns in a primary or unique key are included in the table's ORGANIZE BY clause. This is not allowed, since each block of pages in the table would contain just one row, wasting all the rest of the space in the block.

name is the constraint name, if specified, of the primary key or unique constraint. If a constraint name was not specified, name is the first column name specified in the primary key or unique constraint clause followed by three periods. If a unique index is being created, name is the name of the unique index.

The statement cannot be processed.

Modify the primary or unique key definition, the unique index definition or the ORGANIZE BY clause, if possible, so that the key is not a subset of the dimensions.

sqlcode: -20188

sqlstate: 429BE

SQL20189W

The buffer pool operation (CREATE/ALTER) will not take effect until the next database startup due to insufficient memory.

The CREATE or ALTER BUFFERPOOL statement was issued and completed successfully, however due to insufficient memory the create/alter was done DEFERRED. The changes will take effect on the next database startup.

If you do not want to wait until the next startup to activate or resize the buffer pool, you can free memory resources and try again (with the same or different size). Memory resources that can be reduced include other buffer pools, the database heap, the catalog cache, the package cache, and the utility heap. These can be reduced using the ALTER/DROP BUFFERPOOL or UPDATE DATABASE CONFIGURATION command depending on the resource. In the future, to reserve extra memory for the dynamic allocation of buffer pool memory, you can increase the DATABASE_MEMORY database configuration parameter.

sqlcode: +20189

sqlstate: 01657

SQL20190N

Federated insert, update, or delete operation cannot be compiled because of potential data inconsistency.

When the data source does not provide application savepoint support and the server option 'iud_app_svpt_enforce' is set to 'Y', the federated insert, update, or delete operation is blocked during precompile. This will prevent potential data inconsistency, which may occur at runtime execution if an error is encountered in the middle of federated insert, update, or delete processing.

sqlcode: -20190

sqlstate: 0A503

SQL20191N

For an INOUT parameter in a dynamically prepared CALL statement, the same host variable must be used in both the USING and INTO clauses.

In a CALL statement, an INOUT parameter must correspond to a single host variable. When executing a dynamically prepared CALL statement, it is necessary to specify the same host variable in both the USING and INTO clauses of the EXECUTE statement.

When specifying a host variable that corresponds to a parameter marker for an INOUT parameter, use the same host variable in both the USING and INTO clauses of the EXECUTE statement. When using SQLDAs to specify a host variable that corresponds to a parameter marker for an INOUT parameter, then the SQLDATA pointers of the corresponding SQLVARs must point to the same host variable.

sqlcode: -20191

sqlstate: 560BB

SQL20192N

The specified modes are only supported in a partitioned database environment.

Either RECOMMEND PARTITIONINGS or EVALUATE PARTITIONINGS was not invoked in a partitioned database environment. These two modes are only supported in a partitioned database environment.

Invoke RECOMMEND PARTITIONINGS or EVALUATE PARTITIONINGS in a partitioned database environment.

sqlcode: -20192

sqlstate: 56038

SQL20193N

An error has occurred when accessing the file file-name. Reason code: reason-code.

Use the reason code information to determine how to make the file accessible and resubmit the statement.

sqlcode: -20193

sqlstate: 560BC

SQL20194N

Buffer pool bufferpool-name does not exist on database partition dbpartitionnum.

The ALTER BUFFERPOOL statement is specifying a buffer pool, bufferpool-name, that does not exist on the database partition dbpartitionnum.

Using the ALTER DATABASE PARTITION GROUP statement, add the database partition dbpartitionnum to a database partition group that has the buffer pool bufferpool-name already defined for it. If the buffer pool is not associated with any specific database partition group, then add the database partition to any database partition group or create a new database partition group for this database partition. Issue the ALTER BUFFERPOOL statement again.

sqlcode: -20194

sqlstate: 53040

SQL20195N

An error was encountered while processing line number line-number in the path rename configuration file config-file. Reason code = reason-code.

The path rename configuration file config-file is being used to rename containers during the current crash or rollforward recovery process. However, while processing the statements in this file, an error was encountered at line line-number that is preventing the recovery process from proceeding. An explanation of the error is indicated by the following reason code:

1. Invalid syntax.
2. The length of the container path exceeds the maximum allowed length for a container path.
3. The container path specified has already been listed on a previous line.
4. The length of the database path exceeds the maximum allowed length for a database path.
5. The database path specified has already been listed on a previous line.
6. The database path must be an absolute path.
7. The database path is specified incorrectly.
8. The wildcard character ("*") is being used incorrectly.

Make the corresponding change to the configuration file as described in the following instructions, and reissue the command:

1. Correct the syntax error.
2. Specify a shorter container path.
3. Remove the duplicate container path from the file.
4. Specify a shorter database path.
5. Remove the duplicate database path from the file.
6. Use an absolute database path instead of a relative one.
7. Specify the database path in the form of a drive letter followed by a colon (for example C:).
8. If using the wildcard character, it must be the last character in both the old and new paths.

sqlcode: -20195

sqlstate: 08504

SQL20196N

The one or more built-in types which are returned from the FROM SQL function or method does not match the corresponding built-in types which are parameters of the TO SQL function or method.

The built-in types which are returned by a FROM SQL transform function or method have to match the types in the parameter list of the corresponding TO SQL transform function or method.

Choose a different FROM SQL transform function or method or TO SQL transform function or method or alter either the FROM SQL transform function or method or TO SQL transform function or method to make sure that each built-in type returned from the FROM SQL function or method matches the corresponding built-in type that is a parameter of the TO SQL transform function or method.

sqlcode: -20196

sqlstate: 428FU

SQL20197N

Cannot define method-name as an overriding method. Reason code reason-code.

sqlcode: -20197

sqlstate: 428FV

SQL20198N

Method method-name calls itself recursively.

A method attempted to call itself recursively. The recursion might be direct or indirect in nature.

Modify the method definition.

sqlcode: -20198

sqlstate: 55054

SQL20199N

The key transform table function used by the index extension of index index-id of table table-id in tbspace-id generated duplicate rows.

The key transform table function specified by the GENERATE USING clause of the index extension used by index index-id generated duplicate rows. For a given invocation of the key transform table function, no duplicate rows should be produced. This error is occurred when inserting or updating the key value for the index index-id of table table-id in table space tbspace-id.

The statement cannot be processed.

The code for the key transform table function used by the index extension of index index-id must be modified to avoid the creation of duplicate rows.

SELECT IID, INDSCHEMA, INDNAME
  FROM SYSCAT.INDEXES AS I,
       SYSCAT.TABLES AS T
  WHERE IID = <index-id>
      AND TABLEID = <table-id>
      AND TBSPACEID = <tbspace-id>
      AND T.TBASCHEMA = I.TABSCHEMA
      AND T.TABNAME = I.TABNAME

sqlcode: -20199

sqlstate: 22526

SQL20200N

The install or replace of jar-id failed as url could not be located.

The URL specified on the install or replace jar procedure did not identify a valid jar file.

Reissue the install or replace jar procedure with a URL that identifies a valid jar file.

sqlcode: -20200

sqlstate: 46001

SQL20201N

The install, replace or remove of jar-id failed as the jar name is invalid.

The jar name specified on the install, replace or remove jar procedure was invalid. For example, the jar id may be of the improper format, may not exist to be replaced or removed, or can not be installed as it already exists.

Ensure the jar id is of the correct format. If the jar id exists, it may need to be removed before it can be installed. For the remove or replace procedures, ensure the jar id exists.

sqlcode: -20201

sqlstate: 46002

SQL20202N

The replace or remove of jar-id failed as class is in use by routine routine-name (specific name specific-name).

The specified class in the jar file is currently in use by a defined procedure, or the replacement jar file does not contain the specified class for which a procedure is defined.

Ensure all procedures referencing the classes being removed are dropped and resubmit the replace or remove procedure.

sqlcode: -20202

sqlstate: 46003

SQL20203N

User defined function or procedure function-name has a Java method with an invalid signature.

The signature of the java method used to implement the function or procedure was invalid. For example, the method may have parameters that are not mappable to the parameters on the corresponding create statement or the method for a procedure may specify a return value.

Reissue the corresponding CREATE statement specifying parameters that match the Java method, or correct the parameters or return type of the Java method and rebuild the class.

sqlcode: -20203

sqlstate: 46007

SQL20204N

The user defined function or procedure function-name was unable to map to a single Java method.

The identified function or procedure either failed to find a matching Java method, or found more than 1 matching Java method.

Correct either the Java method or corresponding create statement so that the function or procedure call resolves to a single Java method.

sqlcode: -20204

sqlstate: 46008

SQL20205N

The user defined function or procedure function-name has an input argument with a null value that could not be passed to the method.

A function created with "CALLED ON NULL INPUT" or procedure has an input parameter with a null value but the Java datatype of this argument does not support null values. Examples of Java datatypes that do not support null values are BOOLEAN, BYTE, SHORT, INT, LONG or DOUBLE.

If the method is to be called with null values, ensure the input Java types are capable of accepting a null value. For functions, the function could also be created with "RETURNS NULL ON NULL INPUT".

sqlcode: -20205

sqlstate: 39004

SQL20206W

The procedure function-name returned too many result sets.

The specified procedure returned more results sets than were specified on the CREATE PROCEDURE statement.

Modify the procedure to return fewer result sets, or drop and recreate the procedure specifying the correct number of result sets.

sqlcode: +20206

sqlstate: 0100E

SQL20207N

The install or remove jar procedure for jar-id specified the use of a deployment descriptor.

The DEPLOY or UNDEPLOY parameter of the install or replace jar procedure was non-zero; this parameter is not supported and must be zero.

Reissue the procedure with the DEPLOY or UNDEPLOY parameter set to zero.

sqlcode: -20207

sqlstate: 46501

SQL20208N

The table table-name was not created. Reason code: reason-code.

The table cannot be created because it violates a restriction as indicated by the following reason code:

1

The table that is used to define a staging table is not a materialized query table that was defined with the REFRESH DEFERRED option.

2

The materialized query table that is used to define a staging table already has a staging table associated with it.

3

A materialized query table that references nicknames cannot be created if the CREATE TABLE statement is issued from a non-catalog database partition.

4

A materialized query table that references a protected table, a view that depends on a protected table, or a nickname on which caching is not allowed cannot be created.

5

A security policy cannot be added to a materialized query table or to a staging table.

6

A materialized query table cannot have more than one DB2SECURITYLABEL column, and that column should not be wrapped in any function.

7

A materialized query table that references protected tables with more than one DB2SECURITYLABEL column cannot be created.

8

If a referred base table has a DB2SECURITYLABEL column, the column must appear in the fullselect of the query.

9

When a table, tableA, is altered to become a materialized query table, if a column in the fullselect of the query is of type DB2SECURITYLABEL, the corresponding column of tableA must also be of type DB2SECURITYLABEL.

10

A staging table cannot be created for a shadow table.

Respond according to the reason code:

1

Specify a materialized query table that was created with the REFRESH DEFERRED option to define the staging table.

2

Specify a materialized query table that is not associated with a staging table.

3

Issue the CREATE TABLE statement from the catalog database partition.

4

Correct the fullselect that is specified in the CREATE TABLE statement so that it does not violate any of the restrictions that are outlined in the explanation under reason code 4.

5

Remove the SECURITY POLICY clause from the CREATE TABLE statement

6

Reference a protected table that has at most one DB2SECURITYLABEL column and that column should not be wrapped in a function.

7

The materialized query table should have at most one DB2SECURITYLABEL column.

8

Select the same DB2SECURITYLABEL column for the materialized query table as referred to in the base table.

9

To alter a table, tableA, to become a materialized query table, define the fullselect so that any DB2SECURITYLABEL column in the fullselect corresponds to a column in tableA that is of type DB2SECURITYLABEL.

10

No action is required. A staging table cannot be created on a shadow table.

sqlcode: -20208

sqlstate: 428FG

SQL20209N

The option-type option is not valid for table table-name with reason code reason-code.

The specified option is not valid as indicated by the following reason codes:

1

The READ ACCESS option cannot be specified on a table that is in the Set Integrity Pending No Access state.

2

The FULL ACCESS option is not valid if the table still has integrity types that are not checked.

3

The FULL ACCESS option is only valid on a table in the Normal No Data Movement state or on a detached table.

4

The FULL ACCESS option cannot be specified with the IMMEDIATE UNCHECKED option if the table is in the Normal No Data Movement state.

5

The PRUNE option is not valid on a table that is not a staging table.

6

The PRUNE and INCREMENTAL options cannot be specified simultaneously.

7

The ALL option cannot be specified with the IMMEDIATE UNCHECKED option if the table needs integrity checking due to an operation that involved data partitioning.

8

The ALL or GENERATED COLUMN option cannot be specified with the IMMEDIATE UNCHECKED option if the table's database partitioning key, table-partitioning key, multidimensional clustering key, or range-clustering key references a generated column whose expression has been altered through an ALTER TABLE statement.

9

Neither the ALLOW READ ACCESS option nor the ALLOW WRITE ACCESS option can be specified on a table that is to have its identity column values generated for all rows nor on a materialized query table that is to be fully refreshed nor on a table that have been loaded and is to have its generated column or identity column values computed.

10

The ALLOW QUERY OPTIMIZATION USING REFRESH DEFERRED TABLES option can only be specified on a REFRESH DEFERRED materialized query table.

11

The option is not valid on a text-maintained summary table.

12

The option is not valid on a text-maintained staging table.

13

The ALL option cannot be specified with the IMMEDIATE UNCHECKED option when the SET INTEGRITY statement has more than one target table and any one of the target tables is a partitioned table that has both an attached data partition and a nonpartitioned user index.

14

The GENERATE IDENTITY option cannot be specified in a SET INTEGRITY statement if the specified table is a system-period temporal table.

15

The FORCE GENERATED option cannot be specified if the table is a system-period temporal table.

16

The FOR EXCEPTION clause cannot be specified if the table is a system-period temporal table.

1

Do not specify the READ ACCESS option.

2

Use the FULL ACCESS option with the IMMEDIATE CHECKED option, or specify ALL as the integrity option with the IMMEDIATE UNCHECKED option.

3

Use the FULL ACCESS option with the IMMEDIATE CHECKED option.

4

Use the FULL ACCESS option without the IMMEDIATE UNCHECKED option.

5

Remove the table that is not a staging table from the statement.

6

Specify only one of PRUNE or INCREMENTAL.

7

Instead of specifying the ALL option, specify explicitly those integrity-options that are desired to be unchecked with the IMMEDIATE UNCHECKED option. Then issue another SET INTEGRITY statement with the IMMEDIATE CHECKED option to check the integrity of data partitioning for the table.

8

Omit the ALL or GENERATED COLUMN option from those integrity-options that are desired to be unchecked with the IMMEDIATE UNCHECKED option. Then issue another SET INTEGRITY statement with the IMMEDIATE CHECKED and FORCE GENERATED options to recompute the generated column values based on the new expression. The FORCE GENERATED option can be omitted if the data in the table are guaranteed to satisfy the new generated column expressions.

9

Specify the ALLOW NO ACCESS option on a table.

10

Remove the ALLOW QUERY OPTIMIZATION USING REFRESH DEFERRED TABLES option.

11

Remove the text-maintained summary table from the statement.

12

Remove the text-maintained staging table from the statement or specify the IMMEDIATE CHECKED option.

13

Reissue the SET INTEGRITY statement with a supported combination of options and target table. For example, issue the SET INTEGRITY statement with the ALL and IMMEDIATE UNCHECKED options while specifying only the affected partitioned table as a target; or issue the SET INTEGRITY statement with the IMMEDIATE CHECKED option and multiple target tables instead.

14

Omit the GENERATE IDENTITY option when the NOT INCREMENTAL option is specified for a system-period temporal table.

15

Remove the FORCE GENERATED option if the table is a system-period temporal table.

16

Remove the FOR EXCEPTION clause if the table is system-period temporal table.

sqlcode: -20209

sqlstate: 428FH

SQL20211N

The specification ORDER BY, OFFSET, or FETCH clause is invalid.

An ORDER BY, OFFSET, or FETCH clause is not allowed in:

• the outer fullselect of a view
• the outer fullselect in the RETURN statement of an SQL Table function
• a materialized query table definition
• a subselect which is not enclosed in parentheses

A FETCH FIRST n ROWS ONLY is not allowed in:

• the outer fullselect in the RETURN statement of an SQL Table function
• a materialized query table definition
• a subselect which is not enclosed in parenthesis

In case of:

subselect

Enclose the subselect including the ORDER BY, OFFSET, or FETCH clause in parentheses.

OFFSET or FETCH clause

Use the ROW_NUMBER() OVER() clause in conjunction with a predicate in the where clause. The following example is equivalent to SELECT NAME FROM emp OFFSET 3 ROWS FETCH NEXT 6 ROWS ONLY:

SELECT name FROM
  (SELECT
     ROW_NUMBER() OVER() AS m, name
     FROM emp
  ) AS e
WHERE m > 3 AND m < 10

Note that LIMIT is an alternative syntax for the FETCH clause.

ORDER BY clause

Use ORDER BY in the query using the view, the materialized query table, or the SQL table function instead.

sqlcode: -20211

sqlstate: 428FJ

SQL20212N

User defined routine function-name encountered an exception attempting to load Java class class-name from JAR JAR-name. Original exception underlying-exception.

A ClassNotFoundException has occurred. The ClassNotFoundException may reference an original Java exception which further describes why the class wasn't found. For example, the underlying exception might be an I/O error that occurred trying to read a JAR file, or an SQL error occurred reading the JAR from the data dictionary. As much of the following tokens that will fit within the SQLCA limits will be returned, as appropriate.

The function-name identifies the specific name of the external Java function or procedure whose execution encountered the ClassNotFoundException.

The class-name identifies the Java class whose definition could not be found.

The JAR-name optionally identifies the installed JAR expected to contain the identified class. '(none)' will be present unless the external Java function or procedure is defined to be in an installed JAR.

The underlying-exception optionally contains the toString() of the underlying exception that resulted in this ClassNotFoundException, if any. '(none)' will be present if there is no underlying exception.

Execute an ALTER PROCEDURE to specify where the class is to be found, make sure the class is in the specified JAR or the system classpath, or correction the condition reported by the underlying-exception.

sqlcode: -20212

sqlstate: 46103

SQL20223N

The encryption or decryption operation failed because the encryption facility is not installed or is not functioning correctly.

You can encrypt data in database tables by using built-in encryption functions. You can encrypt data in transit between DB2 clients and database servers by using encryption authentication.

This message is returned when an attempt is made to encrypt or decrypt data either in storage or in transit, but the encryption facility is not available to service the encryption or decryption request.

To use the encryption facility, perform the following troubleshooting steps:

1. Verify that the the encryption facility is installed by issuing the db2ls command.
2. If the encryption facility is not installed, install it before using encryption or decryption operations.
3. If the encryption facility is installed but it is not working correctly, uninstall and then reinstall the encryption facility.

sqlcode: -20223

sqlstate: 560BF

SQL20225W

The buffer pool operation (DROP) will not take effect until the next database startup because the buffer pool is in use.

The DROP BUFFERPOOL statement was issued and completed successfully, however a table space is still using this buffer pool. Even though a table space may be reassigned to a different buffer pool, the table space reassignment may only take effect on the next database restart. If the table space in question is dropped by the time this operation commits, then this buffer pool will be removed from memory at that time. Until the next database restart, this buffer pool may remain in memory and a CREATE or ALTER of any other buffer pool that would reuse this buffer pool ID may be deferred.

Restart the database to delete the buffer pool from memory.

sqlcode: 20225

sqlstate: 01657

SQL20227N

Required clause is missing for argument number of expression.

expression expression requires that a clause be specified for argument number number. If expression is XMLATTRIBUTES, then an AS clause is required for the XML attribute name. If expression is XMLFOREST, then an AS clause is required for the XML element name. The statement cannot be processed.

Correct the statement by providing the required clause for the argument.

sqlcode: -20227

sqlstate: 42633

SQL20230N

The procedure name may not be specified by a host variable in the CALL statement and the arguments may not be specified with a USING DESCRIPTOR clause.

The procedure name must be specified as an identifier in the CALL statement and the arguments must be explicitly provided. A host variable may not be used for the procedure name. The USING DESCRIPTOR clause may not be used to specify the arguments.

The CALL statement must be rewritten to provide an identifier for the procedure name and to explicitly list the arguments. If either the procedure name or the arguments are not known until run time, use a dynamically prepared CALL statement.

For applications being migrated from a release previous to V8, the CALL_RESOLUTION DEFERRED precompile option can be used until the applications are rewritten to use the dynamically prepared CALL statement.

sqlcode: -20230

sqlstate: 42601

SQL20238N

The table table-name is defined as CCSID UNICODE and cannot be used in an SQL function or SQL method.

In a non-Unicode database, only tables with the ASCII encoding scheme may be referenced inside an SQL function or SQL method. Since the table table-name is defined as CCSID UNICODE, it may not be used in an SQL function or an SQL method.

Do not use CCSID UNICODE tables in an SQL function or SQL method.

sqlcode: -20238

sqlstate: 560C0

SQL20239N

Tables created in the Unicode encoding scheme cannot be a typed table, or contain graphic types, the XML type, or user-defined types.

In a non-Unicode database, tables created in the Unicode encoding scheme cannot be a typed table and also cannot contain columns defined with any graphic type, the XML type, or user-defined type.

Remove the CCSID UNICODE clause from the table definition or remove the graphic type, the XML type, or user-defined type from the table definition.

sqlcode: -20239

sqlstate: 560C1

SQL20240N

Invalid specification of a column column-name of type DB2SECURITYLABEL. Reason code: reason-code.

For a column of type DB2SECURITYLABEL the specification of an attribute in a CREATE TABLE or ALTER TABLE statement may be invalid for the following reason.

4

A security label column cannot be defined for a created temporary table or a declared temporary table.

10

A column of type DB2SECURITYLABEL cannot be defined as a generated column.

Correct the specification of the column of type DB2SECURITYLABEL and resubmit the statement.

sqlcode: -20240

sqlstate: 42963

SQL20241N

Writing a history file entry for dropped table table-name failed.

Dropped table recovery is enabled on the table space in which the dropped table table-name resides. When a table space has dropped table recovery enabled, a history file entry is created as part of a table drop. This history file is contains data which is useful during the recovery of a dropped table. The writing of the new history file entry for the dropped table failed. As a result, the table drop could not be completed.

A possible cause for such a failure is a full file system where the history file is located.

Ensure that the history file can be written to by the database manager. If you are not concerned about dropped table recovery, disable this feature and reissue the drop table statement.

sqlcode: -20241

sqlstate: 560C2

SQL20242N

The sample size specified in the TABLESAMPLE clause is not valid.

The sample size specified in the TABLESAMPLE clause must be a positive numeric value greater than zero and less than or equal to 100.

The statement was not processed.

Change the sample size specified in the TABLESAMPLE clause to a valid numeric value greater than zero and less than or equal to 100.

sqlcode: -20242

sqlstate: 2202H

SQL20243N

The view view-name is the target in the MERGE statement, but is missing the INSTEAD OF trigger for the operation operation.

The view view-name is a direct or indirect target in the MERGE statement and has an INSTEAD OF trigger defined for it, but does not have INSTEAD OF triggers defined for all operations. The trigger for the operation operation is not present.

Create INSTEAD OF triggers for the UPDATE, DELETE and INSERT operations on view view-name, or drop all INSTEAD OF triggers for the view.

sqlcode: -20243

sqlstate: 428FZ

SQL20247N

Table table-name cannot be partitioned and contain a column with data type DATALINK.

An attempt was made to create or alter table table-name in such a way that would create a partitioned table that contained a column with data type DATALINK. A table cannot be both partitioned and contain such a column.

Create or alter the table to be either partitioned or to include a column of data type DATALINK, but not both.

sqlcode: -20247

sqlstate: 429BH

SQL20249N

The statement was not processed because the package named package-name needs to be explicitly rebound.

The package package-name contains a section that must be rebound.

Explicitly rebind the package using either the REBIND command or the BIND command. To preserve function and data type resolution, specify the RESOLVE CONSERVATIVE option on the REBIND command.

sqlcode: -20249

sqlstate: 560C5

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 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:

1. The execution of the delete rule of constraint constraint-name1 will fire the BEFORE trigger name and the body of this BEFORE trigger modifies a column that is part of the foreign key of constraint constraint-name2 or modifies a column that is referenced by a generated column which is part of the foreign key of constraint constraint-name2.
2. The execution of the delete rule of constraint constraint-name1 will trigger the update of the generated column name and the generated column itself is part of the foreign key of constraint constraint-name2.
3. With the addition of the BEFORE trigger or generated column, name, the execution of both constraints constraint-name1 and constraint-name2 would cause an update of the same column.

The statement cannot be processed.

The action corresponding to the reason code is:

1. Change the BEFORE trigger definition so that the BEFORE trigger will not be fired when the delete rule of constraint constraint-name1 is executed, or change the body of the BEFORE trigger so that it does not modify a column that is part of the foreign key of constraint constraint-name2 nor modify a column that is referenced by a generated column which is part of the foreign key of constraint constraint-name2.
2. Change the generated column expression so that the generated column will not be updated when the delete rule of constraint constraint-name1 is executed or change foreign key of constraint constraint-name2 so that it does not include the generated column.
3. Change the BEFORE trigger definition or generated column expression so that the execution of both constraints constraint-name1 and constraint-name2 would not cause an update of the same column.

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.

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.

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:

1

The relationship is self-referencing and is specified with a delete rule of RESTRICT or SET NULL and the table is a dependent in a relationship with a delete rule of CASCADE.

2

The relationship is specified with a delete rule of CASCADE, and a self-referencing relationship with the delete rule of RESTRICT or SET NULL already exists on the table.

3

The foreign key overlaps with a foreign key of an existing relationship and their delete rules are either not the same or one of them is SET NULL.

4

The relationship is specified with a delete rule of CASCADE which would cause the descendent table to be delete-connected to its ancestor table through multiple relationships where at least two such relationships have overlapping foreign keys and their delete rules are either not the same or one of them is SET NULL.

5

At least one of the conflicting referential constraints is specified with a delete rule of SET NULL and its foreign key definition overlaps with either the partitioning key, or a dimension of an MDC table.

6

The relationship is specified with a delete rule of CASCADE which would cause the descendent table to be delete-connected to its ancestor table through multiple relationships where at least one of the relationships is specified with a delete rule of SET NULL and its foreign key definition overlaps with either the partitioning key, or a dimension of an MDC table.

7

The new referential constraint definition conflicts with existing referential constraints when BEFORE triggers and generated columns are considered.

8

The new referential constraint will cause another pair of conflicting referential constraints to co-exist in the delete-connected graph when BEFORE trigger and generated columns are considered.

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:

1

Change the delete rule to CASCADE or NO ACTION or eliminate the particular FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.

2

Change the delete rule to NO ACTION, RESTRICT, or SET NULL or eliminate the particular FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.

3

Do not specify a column in the foreign key definition that is already contained in the existing foreign key definition or if the delete rule of the existing referential constraint is not SET NULL, change the delete rule of the new constraint to be the same.

4

Change the delete rule to NO ACTION, RESTRICT, or SET NULL or eliminate the particular FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.

5

Do not specify a column in the foreign key definition that is already contained in the existing partitioning key definition or eliminate the particular FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.

6

Change the delete rule to NO ACTION, RESTRICT, or SET NULL or eliminate the particular FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.

7

Change the delete rule to NO ACTION or remove the triggers fired by the referential constraint or do not create the new referential constraint.

8

Change the delete rule to NO ACTION, RESTRICT, or SET NULL or eliminate the particular FOREIGN KEY clause from ALTER TABLE statement.

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.

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.

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:

1. The view's outermost fullselect is not a UNION ALL.
2. The view contains nested UNION ALL operations other than in the outermost fullselect.
3. Not all view columns are updatable.
4. Two columns of the view are based on the same column of the base table.
5. One of the underlying views has an INSTEAD OF UPDATE trigger defined on it.
6. The view contains references to system-period temporal tables or application-period temporal tables.

The view cannot be created.

Depending on the reason code, do the following:

1. Omit the WITH ROW MOVEMENT clause. It is not applicable for views without UNION ALL.
2. Rewrite the view body so that UNION ALL only occurs on the outermost fullselect.
3. Omit columns that are not updatable from the view definition.
4. Rewrite the view body so that each column of a base table is only referenced once in the view definition.
5. Omit the WITH ROW MOVEMENT clause and use an INSTEAD OF UPDATE trigger on the newly defined view.
6. Remove any reference to a system-period temporal table or an application temporal table.

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:

1. There are table references following the table function.
2. The table function is not referenced in the outer most subselect.
3. The table function is preceded by a table reference which is not referenced by a function argument.
4. The table function is used in the body of a view definition.
5. The table function is used in a fullselect within an XQuery context.
6. The table function is referenced by an OUTER JOIN operator or is nested within other explicit joins (using parentheses in a joined-table clause).
7. The function is referenced in the default clause for a global variable or parameter of a procedure definition.

The statement cannot be processed.

1. Rewrite the query so that the table function is the last table reference in the FROM clause.
2. Move the table function to be in the outermost subselect.
3. Remove the table reference not correlated to in the table function or include an argument in the table function that correlates to the table reference.
4. Remove the table function from the body of the view definition.
5. Remove the table function from the fullselect in the XQuery context.
6. Remove the OUTER JOIN operator or do not place table function in a nested explicit join.
7. Remove the function from the default clause for the global variable or parameter of a procedure definition.

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:

SELECT c1 FROM
   (SELECT c1 FROM t1, t2,
     TABLE(tf1(t1.c1) AS tf), t3)
      AS x, t4

Can be rewritten as:

WITH cte1 AS (SELECT c1 FROM t1,
   TABLE(tf1(t1.c1)) AS tf),
   x AS (SELECT c1 FROM t2, cte1, t3)
     SELECT c1 FROM x, t4;

sqlcode: -20267

sqlstate: 429BL

SQL20268N

Collation cannot be applied. Reason code = 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.

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.

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.

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 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 statement cannot be processed.

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.

sqlcode: -20282

sqlstate: 42724

SQL20284N

No plan was possible to create for federated data source server-name. Reason = reason-code.

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:

1. The ALTER TABLE...DETACH PARTITION operation logically detaches the data partition from the partitioned table.
2. An asynchronous partition detach task converts the logically detached partition into a stand-alone table.

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:

1

The table is the target table of a detach operation and has detached dependents which are required to be incrementally maintained with respect to the current content of this table in order to preserve the integrity of the detached dependents. The statement or command is not allowed because execution of the statement or command would prevent the detached dependents from being incrementally maintained.

2

The table is the target table of a detach operation and is not available because the asynchronous partition detach task has not completed.

3

The table is the source table of a detach operation and has logically detached partitions. The statement or command is not allowed because the asynchronous partition detach task has not completed.

4

The table has detached partitions and there are dependent tables that need to be incrementally maintained with respect to these detached partitions. The statement is not allowed because execution of the statement or command would invalidate the incremental maintenance of the dependent tables.

Respond to this message according to the reason code:

1

Respond to reason code 1 in one of the following two ways:

• Maintain the detached dependent tables and then re-issue the statement or command by performing the following steps:
  1. Identify the detached dependents of the table by querying the SYSCAT.TABDETACHEDDEP catalog view.
  2. Perform integrity processing on the detached dependent tables by issuing the SET INTEGRITY statement with the IMMEDIATE CHECKED option.
  3. Re-issue the statement or command.
• Issue the statement or command without maintaining the detached dependent tables by performing the following steps:
  1. Reset the detached property of the table by issuing the SET INTEGRITY statement with the FULL ACCESS option on the table.
  2. Re-issue the statement or command.
  3. Perform full integrity processing on subsequent SET INTEGRITY statements on the remaining detached dependent tables.

2

Monitor the progress of the asynchronous partition detach task by using the LIST UTILITIES command and wait for the asynchronous partition detach task to complete. Then re-issue the statement or command.

3

Perform the following steps:

1. Monitor the progress of the asynchronous partition detach task by using the LIST UTILITIES command and wait for the asynchronous partition detach task to complete.
2. Verify that the table does not have any logically detached partitions by querying the SYSCAT.DATAPARTITIONS catalog view
3. Re-issue the statement or command.

4

Perform the following steps:

1. Identify the dependent tables that require incremental maintenance.
2. Perform integrity processing on the dependent tables by issuing the SET INTEGRITY statement with the IMMEDIATE CHECKED option on these dependent tables.
3. Re-issue the statement or command.

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:

1

Collecting statistics is not supported for the target object.

2

An attempt was made to collect statistics for a view, but RUNSTATS options were specified that are not supported with a view. For example, the FOR INDEXES option cannot be specified for views.

3

Updating some statistics of the target object type is not supported. For example, data page statistics is not applicable for XML paths indexes.

Respond to this error according to the reason code:

1

Verify that collecting and updating statistics is supported for the specified object. For example, to enable the collecting and updating of statistics for a view, execute the ALTER VIEW statement specifying the ENABLE QUERY OPTIMIZATION clause.

3

Remove RUNSTATS options that are not supported with a view.

3

Verify that the statistics of the target object type can be updated.

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:

1. non-string data that is specified with an explicit string length unit unit for the LENGTH function. A string unit cannot be specified for non-string data.
2. bit data or binary data was specified with a string unit other than OCTETS. CODEUNITS16 or CODEUNITS32 are not valid with bit data or binary string data.
3. OCTETS was used with graphic data and the start parameter is not odd or the length parameter is not even.
4. OCTETS was used with graphic data and the start parameter is not odd.
5. OCTETS was used with graphic data and the code-units parameter is not even.
6. OCTETS or CODEUNITS16 was used with a source string argument that is defined as CODEUNITS32.

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.

WITH
DEP_CNT(TOTAL_DEP) AS (SELECT COUNT(*) FROM
  SYSCAT.TABDEP),
DEP_TAB(SCHEMA, NAME, TYPE, PROPERTY, REFRESH,
  STATUS, CONST_CHECKED, LEVEL) AS
  (SELECT TABLES.TABSCHEMA, TABLES.TABNAME,
       TABLES.TYPE, TABLES.PROPERTY,
       TABLES.REFRESH, TABLES.STATUS,
       TABLES.CONST_CHECKED, 0
   FROM SYSCAT.TABLES TABLES
   WHERE TABLES.TABSCHEMA='<schema name>'
   AND TABLES.TABNAME='<table name>'
     UNION ALL
   SELECT TABDEP.TABSCHEMA, TABDEP.TABNAME,
       TABDEP.DTYPE, TABLES.PROPERTY,
       TABLES.REFRESH, TABLES.STATUS,
       TABLES.CONST_CHECKED,
       DEP_TAB.LEVEL + 1
   FROM SYSCAT.TABDEP TABDEP, DEP_TAB,
     SYSCAT.TABLES TABLES
   WHERE TABDEP.DTYPE IN ('S', 'V', 'W', 'T')
       AND TABDEP.BSCHEMA = DEP_TAB.SCHEMA
       AND TABDEP.BNAME = DEP_TAB.NAME
       AND TABLES.TABSCHEMA = TABDEP.TABSCHEMA
       AND TABLES.TABNAME = TABDEP.TABNAME
       AND DEP_TAB.LEVEL < (SELECT
         DEP_CNT.TOTAL_DEP FROM DEP_CNT))
SELECT DISTINCT * FROM
(SELECT DEP_TAB.SCHEMA, DEP_TAB.NAME
 FROM DEP_TAB
 WHERE STATUS='C'
       AND (DEP_TAB.TYPE = 'S'
       AND DEP_TAB.REFRESH = 'I'
       AND SUBSTR(DEP_TAB.CONST_CHECKED,5,1)<>'F'
       OR DEP_TAB.TYPE = 'T'
       AND SUBSTR(DEP_TAB.PROPERTY,2,1) = 'Y'
       AND SUBSTR(DEP_TAB.CONST_CHECKED,7,1)<>'F')
 ) X;

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:

• An attempt was made to create a partitioned unique index that fails to plainly include one or more of the columns from the table-partitioning key.
• An attempt was made to create a unique partitioned index over XML data on a partitioned table.

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:

1

There is one column specified that is defined with a data type of XML, but the definition is missing the XMLPATTERN clause to specify the index keys to generate for each XML value.

2

An XMLPATTERN clause is present but there are multiple index columns specified.

3

The index is defined as UNIQUE and the XMLPATTERN includes descendant, descendant-or-self axes, '//', xml-wildcards, node(), or processing-instruction().

4

An XMLPATTERN clause is present but the single index column specified is not defined with data type XML.

5

The path expression specified in the XMLPATTERN clause does not start with '/' or '//'.

6

The pattern expression does not include a name test or kind test following '/'.

7

The pattern expression uses an unsupported axis in an axis step. Only the following forward axes are supported: child, attribute, descendant, self, and descendant-or-self.

8

The pattern expression specifies an invalid kind test, or some syntax that is not a valid name test or kind test as supported in a pattern expression.

9

The pattern expression specifies a predicate (an expression enclosed in square brackets), but predicates are not supported for pattern expressions in an XMLPATTERN clause.

10

The pattern expression includes other XQuery syntax not supported in an XMLPATTERN clause to which the preceding reason codes do not apply.

11

On a z/OS database server, the number of steps in the pattern expression exceeds the limit of 50 steps when it does not contain a function, or 44 steps when it does contain a function.

12

The argument of a function in the pattern expression does not follow the requirements as specified in the syntax, or the index data type is not correct.

13

The index is defined with at least one part of the index key based on an XMLPATTERN expression.

Respond to this error according to the reason code:

1

Specify the XMLPATTERN clause.

2

If the index is intended as a key for XML data, ensure that only one column defined with a data type of XML is specified. Otherwise, remove the XMLPATTERN clause.

3

Either remove the UNIQUE specification or change the XMLPATTERN definition to remove descendant, descendant-or-self axes, '//', xml-wildcards, node(), or processing-instruction().

4

Either remove the XMLPATTERN clause or change the specified column to a single column defined with a data type of XML.

5

Ensure that the pattern expression begins with '/' or '//'. The XQuery syntax for which '/' or '//' is an abbreviation is not supported for the XMLPATTERN clause of the CREATE INDEX statement.

6

Add a name test or a kind test to the pattern expression following '/'.

7

Remove any reverse axes from the pattern expression. For example, the parent axis must not be used in a pattern expression.

8

Check the pattern expression for kind tests or name tests that do not match the syntax specification for the XMLPATTERN clause of the CREATE INDEX statement. Correct or remove unsupported syntax.

9

Remove any predicates from the pattern expression in the XMLPATTERN clause.

10

Change the pattern expression to remove any syntax that is not supported for the XMLPATTERN clause of the CREATE INDEX statement. If the pattern expression includes an asterisk ('*'), ensure that the name tests in the pattern expression correctly use the wildcard. If used with a QName, there must be a colon before or after the wildcard character, otherwise it becomes a multiplication operator. The asterisk cannot be used as a multiplication operator in the pattern expression. You should also ensure that the XMLPATTERN clause does not include any other XQuery operators, XQuery functions or XQuery FLWR expressions (for, let, where, return).

11

Reduce the number of steps in the pattern expression. If the value to be indexed in the XML documents requires more than 50 steps, the index cannot be created.

12

Check the argument of the function in the pattern expression to determine whether it matches the syntax specification of the XMLPATTERN clause of the CREATE INDEX statement, and check the data type of the indexed values. Also, check that the function you specified is supported in the XMLPATTERN clause. Correct or remove unsupported syntax.

13

Modify the index definition in one of the following ways:

• Remove the XMLPATTERN clause
• Remove any expression-based keys

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.

1

At least one XML node value in an XML value being inserted or updated exceeds a length constraint imposed by the identified index. The index on an XML column is defined to use the SQL type VARCHAR with a specific length specified. The length of one or more XMLPATTERN result values exceeds the user-specified length constraint for the VARCHAR data type.

2

On database servers Version 9.5 and earlier, at least one XML node value in an XML value being inserted or updated is a list data type node that cannot be indexed by the identified index. List data type nodes are not supported in the index.

3

On database servers Version 9.5 and earlier, at least one XML node value is a valid XML value but cannot be cast to the schema data type because it is outside the supported range of values.

4

At least one XML node value is a valid XML value but cannot be cast to the index data type for the identified index because it is outside the supported range of values.

5

At least one XML node value is an invalid XML value for the target index data type for the identified index and the index definition specifies that invalid XML values must return an error (REJECT INVALID VALUES).

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:

SELECT INDNAME,INDSCHEMA
  FROM SYSCAT.INDEXES
  WHERE IID =<index-id> AND
    TABSCHEMA ='schema ' AND TABNAME ='<table-name>'

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:

SELECT DATATYPE, PATTERN
FROM SYSCAT.INDEXXMLPATTERNS
WHERE INDSCHEMA = 'index-schema' AND
 INDNAME = 'index-name'

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>:

SELECT OBJECTNAME
  FROM SYSCAT.XSROBJECTS
  WHERE OBJECTID = '<xml-schema-id>'

1

Use the XML pattern to identify the set of matching XML nodes to determine which string values exceed the length constraint specified by the index. If the XML pattern contains an fn:upper-case function, it is possible that for certain languages the string value after uppercase conversion exceeds the length constraint specified by the index.

2

On database servers Version 9.5 and earlier, use the XML schema name and XML pattern to identify the set of matching XML nodes to inspect and compare against the identified schema data type xml-schema-data-type found in the corresponding schema. Determine which node values are list data type nodes.

3

On database servers Version 9.5 and earlier, use the XML schema name and XML pattern to find the set of matching XML nodes to inspect and compare against the identified schema data type xml-schema-data-type found in the corresponding schema. Determine which node values exceed the supported range of values for the XML schema data type.

4

Use the XML pattern to identify the set of matching XML nodes to inspect and compare against the data type specified for the identified index. Determine which node values exceed the supported range of values for the index data type.

5

Use the XML pattern to identify the set of matching XML nodes to inspect and compare against the data type specified for the index being created. Determine which node values are invalid for the index data type.

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.

1

At least one XML node value in an XML value being inserted exceeds a length constraint imposed by the index that is being created. The index on an XML column is defined to use the SQL type VARCHAR with a specific length specified. The length of one or more XML pattern result values exceeds the user-specified length constraint for the VARCHAR data type.

2

On database servers Version 9.5 and earlier, at least one XML node value in an XML value being inserted into the index during index creation is a list data type node that cannot be indexed by the specified index. List data type nodes are not supported in the index.

3

On database servers Version 9.5 and earlier, at least one XML node value is a valid XML value but cannot be cast to the schema data type because it is outside the supported range of values.

4

At least one XML node value is a valid XML value but cannot be cast to the index data type for the identified index because it is outside the supported range of values.

5

At least one XML node value is an invalid XML value for the target index data type for the identified index and the index definition specifies that invalid XML values must return an error (REJECT INVALID VALUES).

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>:

SELECT OBJECTNAME
  FROM SYSCAT.XSROBJECTS
  WHERE OBJECTID = '<xml-schema-id>'

1

Use the XML pattern to identify the set of matching XML nodes to determine which string values exceed the length constraint specified by the index. If the XML pattern contains an fn:upper-case function, it is possible that for certain languages the string value after uppercase conversion exceeds the length constraint specified by the index.

2

On database servers Version 9.5 and earlier, use the XML pattern to identify the set of matching XML nodes to inspect and compare against the identified schema data type xml-schema-data-type found in the corresponding schema. Determine which node values are list data type nodes.

3

On database servers Version 9.5 and earlier, use the XML pattern to find the set of matching XML nodes to inspect and compare against the identified schema data type xml-schema-data-type found in the corresponding schema. Determine which node values exceed the supported range of values for the XML schema data type.

4

Use the XML pattern to identify the set of matching XML nodes to inspect and compare against the data type specified for the index. Determine which node values exceed the supported range of values for the index data type.

5

Use the XML pattern to identify the set of matching XML nodes to inspect and compare against the data type specified for the index. Determine which node values are invalid for the index data type.

If the index is partitioned and there are newly attached partitions (that is, partitions with the value of 'A' in the STATUS column in the SYSDATAPARTITIONS catalog table), you might not be able to find the invalid node values for the index data type. In this situation, run the SET INTEGRITY statement to bring the newly attached partitions online. The invalid node values might be removed by the SET INTEGRITY statement for violating other constraints, so issue the statement again. If the statement cannot be processed again, then check for invalid node values for the index data type.

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.

1

The number of columns (the COLCOUNT column in SYSCAT.TABLES) of the source and target table does not match.

2

The compression clauses in the source and target tables do not match. There are two possible mismatches: VALUE COMPRESSION and COMPRESSION SYSTEM DEFAULT do not match; and COMPRESS YES STATIC and COMPRESS YES ADAPTIVE do not match.

3

The APPEND mode of the tables does not match.

4

The code pages of the source and target table do not match.

5

The source table is a partitioned table with more than one data partition or with ATTACHED or DETACHED data partitions. A source table that is partitioned can only be attached if it has only one data partition and no ATTACHED or DETACHED data partitions.

6

The source table is a system table, a view, an MQT, a typed table, a table ORGANIZED BY KEY SEQUENCE, a created temporary table, a declared temporary table, a system-period temporal table, or a history table. The source table must be a base table that does not correspond to any of the listed tables.

7

The target and source table are the same. You cannot attach a table to itself.

8

The NOT LOGGED INITIALLY clause was specified for either the source table or the target table, but not both.

9

The DATA CAPTURE CHANGES clause was specified for either the source table or the target table, but not both.

10

The distribution clauses of the tables do not match. The distribution key must be the same for the source table and the target table.

11

The ORGANIZE BY DIMENSIONS clauses of the tables do not match. Only one of the tables has an ORGANIZE BY DIMENSIONS clause specified or the organizing dimensions are different.

15

The security protection on the tables is not identical. The tables are protected by different security policies.

16

Compress clause (COMPRESS NO or COMPRESS YES) does not match.

17

The source table does not have an index that is compatible with the index on the target partitioned table. The index on the target table is either unique or defined on an XML column with the REJECT INVALID VALUES clause.

18

The source table does not have an index that is compatible with the index on the partitioned table and the REQUIRE MATCHING INDEXES clause is specified on the ALTER TABLE statement.

19

The record format of the XML column of source table being attached is not compatible with the record format of the target partitioned table.

20

The source table has row access control activated but the target table does not have row access control activated.

21

The source table has column access control activated with at least one enabled column mask but the target table does not have column access control activated.

22

The target table is an application-period temporal table, but the source table is not an application-period temporal table that contains equivalent BUSINESS_TIME period columns.

30

Only one of the source or target table is a random distribution table using the random by generation method.

99

The target table exists in a table space that has been converted to a large table space, and its indexes have not yet been reorganized or rebuilt to support large RIDs.

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.

1

You can add columns to the table which is missing one or more columns using the statement:

ALTER TABLE ...
  ADD COLUMN ...
  DEFAULT ...

Make sure that the default value of the added column is the same as the default value of the column in the table where the column already exists. Query SYSCAT.COLUMNS.IMPLICITVALUE for the column in the table where the column already exists. If the value is not NULL, then use the default clause of the ALTER TABLE ADD COLUMN statement to set the default value to match the value in SYSCAT.COLUMNS.IMPLICITVALUE.

Note: You can only add columns after the last existing column of the table. If the missing column is not the last column, create a new source table.

Alternatively, you can drop a column from the table that has the extra column:

ALTER TABLE ... DROP COLUMN ....

2

To achieve agreement between value compression values use one of the following statements:

ALTER TABLE ... ACTIVATE VALUE COMPRESSION

ALTER TABLE ... DEACTIVATE VALUE
    COMPRESSION

To achieve row compression agreement use one of the following statements:

ALTER TABLE ... COMPRESS YES

ALTER TABLE ... COMPRESS NO

To achieve adaptive compression agreement use one of the following statements:

ALTER TABLE ... COMPRESS YES ADAPTIVE

ALTER TABLE ... COMPRESS YES STATIC

3

To achieve append mode agreement use one of the following statements:

ALTER TABLE ... APPEND ON

ALTER TABLE ... APPEND OFF

4

Create a new source table.

5

Detach data partitions from the source table until there is a single visible data partition using the statement:

ALTER TABLE ... DETACH PARTITION

Include any necessary set integrity statements. Otherwise, create a new source table.

6

Create a new source table that is not one of the disallowed types.

7

Determine the correct table to use as the source or target table.

8

Either make the table which is not logged initially be logged by issuing the COMMIT statement, or make the table which is logged be not logged initially by entering the statement:

ALTER TABLE .... ACTIVATE NOT LOGGED
    INITIALLY

9

To enable data capture changes on the table that does not have data capture changes turned on, run the statement:

ALTER TABLE ... DATA CAPTURE CHANGES

To disable data capture changes on the table that does have data capture changes turned on, run the statement:

ALTER TABLE ... DATA CAPTURE NONE

10

It is recommended that you create a new source table in this case, because you cannot change the distribution key of a table spanning multiple database partitions. To change a distribution key on tables in single-partition database, run the statements:

ALTER TABLE ... DROP DISTRIBUTION

ALTER TABLE ... ADD DISTRIBUTION
    (key-specification)

11

Create a new source table which matches the target table with respect to the ORGANIZE BY DIMENSIONS clause.

15

The two tables must be protected using the same security policy, have the same column defined as type SYSPROC.DB2SECURITYLABEL, and have the same set of protected columns.

16

Use ALTER TABLE tablename COMPRESS [YES | NO], to ensure that the COMPRESS attributes of the source and target table match.

17

To find the list of indexes on the target partitioned table that do not have a compatible index on the source table, see the administration notification log. Create the unique or XML index on the source table that is compatible with the target partitioned table.

18

Do one of the following:

• To find the list of indexes on the target table that do not have a compatible index on the source table, see the administration notification log. Create the missing index on the source table and try the request again.
• Remove the REQUIRE MATCHING INDEXES clause from the ALTER TABLE statement and try the request again.

19

Update the XML record format of the source table to match the record format of the target table. There are several methods you can use to update the XML record format of a table. Either of the following two methods updates the XML record format of a table:

• Perform an online table move on table using the ADMIN_MOVE_TABLE procedure.
• Perform the following steps:
  1. Use the EXPORT command to create a copy of the table data.
  2. Use the TRUNCATE statement to delete all the rows from the table and release the storage allocated to the table.
  3. Use the LOAD command to add the data into the table.

20

Ensure the table to attach to has the required access controls or deactivate the access controls on the table being attached.

21

Ensure the table to attach to has the required access controls or deactivate the access controls on the table being attached.

22

Respond to reason code 22 in one of the following ways:

• If the source table does not have a BUSINESS_TIME period defined, alter the columns in the source that correspond to the BUSINESS_TIME period columns in the target table by using the ALTER TABLE statement with the ADD PERIOD BUSINESS_TIME action on the source table.
• If the source table has a BUSINESS_TIME period defined, perform the following steps:
  1. Remove from the source table the period that does not match the period in the target table by using the ALTER TABLE statement with the DROP PERIOD BUSINESS_TIME action on the source table.
  2. Add columns to the source table that correspond to the BUSINESS_TIME period columns ing the target table by using the ALTER TABLE statement with the ADD PERIOD BUSINESS_TIME action on the source table.

30

Ensure that both tables are random distribution tables using the random by generation method.

99

Convert the indexes on the target table to support large RIDs by issuing the command: REORG INDEXES ALL FOR TABLE target-tablename ALLOW NO ACCESS.

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.

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 statement cannot be executed.

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:

• Creating an automatic storage table space
• Altering a table space to use automatic storage
• Using automatic storage for a restore operation by running the SET TABLESPACE CONTAINERS command with the USING AUTOMATIC STORAGE clause
• Dropping storage paths from the database

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.

• A table space defined as MANAGED BY AUTOMATIC STORAGE has its containers managed by the database manager. This means that the database manager will automatically extend existing containers or create new containers based on the storage paths defined for the storage group with which the table space is associated. Containers for table space defined as MANAGED BY AUTOMATIC STORAGE cannot be altered by the ALTER TABLESPACE statement.
• The INHERIT option cannot be specified for the DATA TAG, OVERHEAD, or TRANSFERRATE clauses with DMS or SMS table spaces
• The clause 'USING STOGROUP' cannot be used with DMS or SMS table spaces
• STOGROUP cannot be changed for temporary automatic storage table spaces
• DATA TAG cannot be set for a temporary table space or a system catalog table space

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:

• Storage paths are being included in a call to the RESTORE DATABASE API.
• Storage paths are being specified with the ON option of the RESTORE DATABASE command.
• Storage paths are being specified with the SET STOGROUP PATHS command.

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:

• Do not include any storage paths when calling the RESTORE DATABASE API.
• Do not specify the ON option of the RESTORE DATABASE command.
• Do not specify the SET STOGROUP PATHS command.

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.

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:

1

The table object-name1 in table hierarchy object-name2 cannot be transferred because the table is a subtable.

2

The view object-name1 in view hierarchy object-name2 cannot be transferred because the view is a subview.

3

The index object-name1 cannot be transferred because the table that the index is defined on,object-name2, is a declared global temporary table.

4

The method body or function object-name1 cannot be transferred because the method body or function was implicitly generated when user-defined type object-name2 was created.

5

The package object-name1 cannot be transferred because an SQL routine, a trigger, or an index object-name2 depends on the package.

6

The event monitor object-name1 cannot be transferred because the event monitor is active.

7

The transfer of the view object-name1 failed because the view is a system-generated statistical view for the expression-based index named object-name2.

Respond to this message according to the reason code:

1

Transfer the whole table hierarchy.

2

Transfer the whole view hierarchy.

3

Drop the declared global temporary table.

4

Drop the type that created this method or function.

5

Transfer the SQL procedure.

6

Set the event monitor state to inactive.

7

Transfer the ownership of the expression-based index.

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:

1

The user mapping plugin cannot be loaded.

2

The version of the user mapping plugin API reported by the user mapping plugin is not compatible with the version federation supports.

3

A connection to the user mapping repository cannot be established or the connection request timed out.

4

The user mapping entry cannot be found on the user mapping repository.

5

A decryption error occurred while processing the user mapping entry from the user mapping repository.

6

Disconnection from the user mapping repository has failed.

7

Invalid parameter has been passed to the user mapping plugin.

8

Unauthorized invocation of the user mapping plugin has been detected.

9

Terminating the user mapping plugin has failed.

10

Unexpected error detected.

See the federation documentation for details on user mapping plugins. The action is based on the reason-code as follows:

1

Verify that the user mapping plugin exists and is in the correct location.

2

Ensure that the user mapping plugin is using a federation supported version of the user mapping plugin API and that it is reporting the correct version number.

3

Verify that the user mapping repository is up and running and that the repository connection parameters of the user mapping plugin are correct.

4

Create a corresponding user mapping entry on the user mapping repository.

5

Ensure that the decryption logic in the user mapping plugin is implemented correctly.

6

Check if the user mapping repository and network are up and running.

7

Ensure that all the parameter values passed onto the user mapping plugin are correct.

8

Verify that federation has the authority to invoke the user mapping plugin.

9

Verify if plugin level global resources can be released.

10

Ensure the plugin maps the error to one of the defined errors. Trace information for the error may be available in the db2diag log file.

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 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 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 TRUNCATE statement would result in the activation of DELETE triggers. However, the statement specifies RESTRICT WHEN DELETE TRIGGERS (implicitly or explicitly). This can occur when DELETE triggers exist for the table to be truncated, and the result of the TRUNCATE statement would activate the triggers.
• The table to be truncated is the parent table in a referential constraint.

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.

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.

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.

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.

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:

SELECT CONTEXTNAME FROM SYSCAT.CONTEXTS
WHERE SYSTEMAUTHID = <authorization-name>

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:

SELECT ELEMENTVALUE FROM
    SYSCAT.SECLABELCOMPONENTELEMENTS
  WHERE COMPID=(SELECT COMPID FROM
    SYSCAT.SECLABELCOMPONENTS
    WHERE  COMPNAME = component-name)

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:

SELECT COMPNAME FROM
  SYSCAT.SECURITYLABELCOMPONENTS
  WHERE COMPID=(SELECT COMPID FROM
    SYSCAT.SECURITYPOLICYCOMPONENTRULES
    WHERE SECPOLICYID = (SELECT
      SECPOLICYID FROM
      SYSCAT.SECURITYPOLICIES
      WHERE SECPOLICYNAME =
        '<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.

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.

For the LOGICAL_RESTORE stored procedure, more information can be found in the trace log that is generated by the LOGICAL_RESTORE stored procedure.

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:

1. It is granted to one or more users, groups, or roles.
2. It is being used to protect one or more columns.

The user response corresponding to the reason code is:

1. Revoke this label from all users, groups, or roles who have been granted this security label for this security policy. The following query can be used to find all the users who has been granted with this label.

   SELECT GRANTEE FROM SYSCAT.SECURITYLABELACCESS
     WHERE SECLABELID = (SELECT SECLABELID FROM
     SYSCAT.SECURITYLABELS
     WHERE SECLABELNAME = '<object-name>' AND
       SECPOLICYID = (SELECT SECPOLICYID FROM
       SYSCAT.SECURITYPOLICIES
     WHERE SECPOLICYNAME = '<policy-name>' ) )
   

2. For all the tables that use this security label to protect a column, either alter the table to drop this security label or drop the table. The following query can be used to find all protected tables and all the columns that are protected with this label.

   
   SELECT TABNAME, COLNAME FROM SYSCAT.COLUMNS
     WHERE SECLABELNAME = '<object-name>' AND
       TABNAME = (SELECT TABNAME FROM
       SYSCAT.TABLES
     WHERE SECPOLICYID = (SELECT SECPOLICYID FROM
     SYSCAT.SECURITYPOLICIES
     WHERE SECPOLICYNAME = '<policy-name>' ) )
   

sqlcode: -20404

sqlstate: 42893

SQL20405N

The security policy object object-name cannot be dropped because it is currently in use. Reason code reason-code.

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.

SELECT SECPOLICYNAME FROM SYSCAT.SECURITYPOLICIES
  WHERE SECPOLICYID = (SELECT SECPOLICYID FROM
  SYSCAT.SECURITYPOLICYCOMPONENTRULES
  WHERE COMPID = (SELECT COMPID FROM
  SYSCAT.SECURITYLABELCOMPONENTS
  WHERE COMPNAME = '<object-name>' ) )

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.

1

The data type of the columns (TYPENAME) does not match.

2

The nullability of the columns (NULLS) does not match.

3

The implicit default value (IMPLICITVALUE) of the columns are incompatible.

Implicit defaults must match exactly if both the target table column and source table column have implicit defaults (if IMPLICITVALUE is not NULL). Refer to the SQL Reference Manual for details on interpreting the values in IMPLICITVALUE.

4

The code page (COMPOSITE_CODEPAGE) of the columns does not match.

5

The system compression default clause (COMPRESS) does not match.

6

The security label protecting the source-columnname for the source table is not identical to that of target-columnname for the target table. The two tables must have the same set of protected columns and each pair of corresponding columns must be protected with same security label.

7

The row change timestamp attribute of the columns does not match.

8

For structured, XML, or LOB data types, the inline length of the columns (INLINE LENGTH) do not match.

9

If a column mask on source-columnname for the source table exists and is enabled, a column mask on target-columnname for the target table must also exist and be enabled.

10

The ROW BEGIN system-generated attributes of the columns do not match.

11

The ROW END system-generated attributes of the columns do not match.

12

The TRANSCATION START ID system-generated attributes of the columns do not match.

Correct the mismatch in the tables.

1

To correct a mismatch in data type, issue the statement:

ALTER TABLE ... ALTER COLUMN ...
   SET DATA TYPE ...

2

Alter the nullability of the column that does not match for one of the tables by issuing one of the following statements:

ALTER TABLE... ALTER COLUMN...
   DROP NOT NULL ALTER TABLE...
      ALTER COLUMN...   SET NOT NULL

3, 4

Create a new source table.

5

To alter the system compression of the column issue one of the following statements to correct the mismatch:

ALTER TABLE ... ALTER COLUMN ...
   COMPRESS SYSTEM DEFAULT
      ALTER TABLE ... ALTER COLUMN ...
         COMPRESS OFF

6

To alter the security protection of a column, issue one of the following statements:

ALTER TABLE ... ALTER COLUMN ...
   SECURED WITH ... ALTER TABLE ...
      ALTER COLUMN ...
         DROP COLUMN SECURITY

7

When the target-columnname of the target table is defined as a row change timestamp column, the source-columnname must also be defined as a row change timestamp column.

8

Alter the inline length of the column that does not match by issuing the following statement:

ALTER TABLE ... ALTER COLUMN ...
   SET INLINE LENGTH ...

9

Create an enabled mask on the column target-columnname by issuing the following statement, and then try ALTER again.

CREATE MASK ON target-table...
    FOR target-columnname... ENABLE

10

When the target-columnname of the target table is defined as a ROW BEGIN system-generated column, the source-columnname must also be defined as a ROW BEGIN system-generated column.

11

When the target-columnname of the target table is defined as a ROW END system-generated column, the source-columnname must also be defined as a ROW END system-generated column.

12

When the target-columnname of the target table is defined as a TRANSCATION START ID system-generated column, the source-columnname must also be defined as a TRANSCATION START ID system-generated column.

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.

SELECT SECPOLICYNAME
          FROM  SYSCAT.SECURITYPOLICIES
          WHERE SECPOLICYID = policy-id

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:

• A CREATE TABLE statement specifies IMPLICITLY HIDDEN as part of the definition of all columns.
• An ALTER TABLE statement alters any not hidden columns to implicitly hidden

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:

11

Socket communication with the search server failed.

12

Unrecoverable error during a search system operation.

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.

1. A text search function, such as CONTAINS or SCORE, specified a column as an argument but a text search index does not exist for this column.
2. The text search index is inactive.
3. The text search index is invalid. A text search index may be invalidated automatically, for example, if the underlying base table was dropped and recreated.
4. The query combines different types of text search indexes.

Text search processing cannot be performed for the specified column.

1. Ensure that the database is enabled for text search and a text search index has been created on the specified column.
2. Activate the text index with the ALTER INDEX command, with the ACTIVATE option.
3. If the table column has an invalid text search index, drop the text index and create a new one.
4. If the query combines multiple text search indexes, make sure that all indexes are active and of the same type.

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. To fix this conflict, the text search administrator needs to clear the lock: db2ts clear command locks for text connect to database-name

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 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:

• A statement attempted to set the named global variable in one of the following contexts:
  • compound SQL (inline) statements
  • functions where the body is not a compound SQL (compiled) statement
  • methods
  • triggers where the body is not a compound SQL (compiled) statement
• A global variable is being referenced in a procedure that is defined as AUTONOMOUS

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).

1 (ATTRIBUTE CONTENT)

An attribute declared or referenced inside a complex type has been removed or some required attributes have been added as part of the content model. The value of schema-component is the name of the enclosing complex type in the original XML schema and the value of enclosing-schema-component is the name of the element that refers to the complex type. In the case of an anonymous complex type the value of schema-component is empty.

2 (ELEMENT CONTENT)

An element declared or referenced inside a complex type has been removed or some required elements have been added as part of the content model. The value of schema-component is the name of the enclosing complex type in the original XML schema and the value of enclosing-schema-component is the name of the element that refers to the complex type. In the case of an anonymous complex type the value of schema-component is empty.

3 (FACET CONFLICT)

The facet value of the simple type has been changed in a way that is not compatible with the range of values for the simple type. The value of schema-component is the name of the simple type that defines this facet in the original XML schema and the value of enclosing-schema-component is the name of the element or attribute that refers to the simple type. In the case of anonymous simple type the value of schema-component is empty.

4 (INCOMPATIBLE TYPE)

The type of an element or attribute has been changed in a way that results in instance document validation failure or that is not compatible because of a simple type annotation change. The value of schema-component is the name of the type in the original XML schema and the value of enclosing-schema-component is the name of the element or attribute that refers to the type. In the case of an anonymous type the value of schema-component is empty.

5 (MIXED INTO NOT MIXED CONTENT)

The content model of a complex type which is declared as mixed in the original XML schema has been changed to not mixed content in the updated XML schema. The value of schema-component is the name of the complex type in the original XML schema and the value of enclosing-schema-component is the name of the element that refers to the complex type. In the case of an anonymous complex type the value of schema-component is empty.

6 (NILLABLE INTO NOT NILLABLE)

The nillable attribute in an element declaration is turned on in the original XML schema but gets turned off in the updated XML schema. The value of schema-component is the name of the element in the original XML schema and the value of enclosing-schema-component is empty.

7 (REMOVED ELEMENT)

A global element declared in schema-component has either been removed from the updated XML schema or made abstract. The value of enclosing-schema-component is empty.

8 (REMOVED TYPE)

The original XML schema contains a global type in schema-component that is derived from another type and the global type gets removed from the updated XML schema. The value of enclosing-schema-component is empty.

9 (SIMPLE TO COMPLEX)

A complex type that contains simple content in the original XML schema cannot be redefined to contain complex content in the updated XML schema. The value of schema-component is the name of the complex type in the original XML schema and the value of enclosing-schema-component is the name of the element that refers to the complex type. In the case of an anonymous complex type the value of schema-component is empty.

10 (SIMPLE CONTENT)

The simple type defined in the original XML schema and the updated XML schema have different base types. The value of schema-component is the name of the simple type in the original XML schema and the value of enclosing-schema-component is the name of the element or attribute that refers to the simple type. In the case of an anonymous simple type the value of schema-component is empty.

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:

• The ARRAY_AGG function invocation includes an ORDER BY clause and the specified sort key is different from the sort key of at least one occurrence of an ARRAY_AGG, LISTAGG, XMLAGG, or XMLGROUP function invocation in the same SELECT clause.
• The ARRAY_AGG function invocation does not include an ORDER BY clause and the specified sort keys are not the same for all invocations of ARRAY_AGG, LISTAGG, XMLAGG, or XMLGROUP functions in the same SELECT clause.

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.

• The following data types are not supported:
  • LONG VARCHAR
  • LONG VARGRAPHIC
  • REFERENCE
  • XML
  • BOOLEAN (prior to Version 9.7.5)
  • user-defined data types other than row data type and array data type
• The array index data type for an associative array must be INTEGER or VARCHAR.
• For Hadoop tables, the only supported nesting is array of rows.
• An argument to UNNEST cannot be a nested array.
• An argument to ARRAY_AGG and the target of ARRAY_AGG cannot be a nested array.
• The target of an ARRAY_AGG cannot be a nested array.
• ARRAY types or ROW types can be nested as elements in other ARRAY types, but there is a maximum nesting level which must not be exceeded.

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:

• Specify a value that is not the null value.
• If the array index data type is integer, specify a value that is a number within the range of integers.
• Specify an array index value that exists in the array.

For an ordinary array:

• If the value is an array index used in an array element specification that is the target of an assignment statement, change the value to be not the null value, not less than 1 and not greater than the maximum cardinality defined for the array.
• If the value is an array index used in an array element specification that is part of an expression or the value is the second argument to the TRIM_ARRAY function, change the value to be not less than 0 and not greater than the cardinality of the 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:

• An argument to a stored procedure call
• The result of a call to the ARRAY_AGG function
• The result of an array constructor used in the right side of a SET statement
• An argument to a cast function

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.

• Parameters to SQL functions:
  • Defined in a module
  • With a compound SQL (compiled) statement as function body not defined in a module
• Return types from SQL functions:
  • Defined in a module
  • With a compound SQL (compiled) statement as function body not defined in a module
• Parameters to SQL procedures
• Local variables declared in SQL functions:
  • Defined in a module
  • With a compound SQL (compiled) statement as function body not defined in a module
• Local variables declared in SQL procedures
• Local variables declared in triggers with a compound compiled SQL statement as trigger body
• Expressions in SQL statements within compound compiled SQL statements
• Global variables

The following is a list of some invalid contexts:

• Parameters or variables in external routines
• Return type of a function with a function body definition defined by a compound SQL (inlined) statement
• Columns in tables
• Data types in SQL statements outside of SQL PL contexts
• Global variable (includes module-variable) being referenced outside of an SQL PL context.
• Input or output parameter to a procedure or function being invoked from outside of an SQL PL context.
• In a partitioned database environment (DPF) or symmetric multiprocessor (SMP) environment, only top level SET and CALL statements can reference objects defined in nested types. A sub-query cannot reference objects with nested types.
• Nested types with global variables, module variables, or PL/SQL package variables in autonomous routines.

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.

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:

1. There are unsupported format elements.
2. The format does not contain a format element, is the empty string, or is all blanks.
3. A format element is specified more than once.
4. The length of the format string argument exceeds the maximum allowable length.
5. There are unsupported separator characters.
6. There are too many format elements.
7. A prefix or suffix format element is specified in the wrong place in the string.
8. There are multiple format elements that represent the same component. For example, the TIMESTAMP_FORMAT function YYYY and YY (format element to indicate the YEAR) must not both be specified in the format string.

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 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.

sqlcode: -20451

sqlstate: 560CO

SQL20452N

Hierarchical query construct name is used out of context.

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 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.

1

The prepared select-statement is not eligible for row change columns. For example, it includes a GROUP BY, join, or UNION. Modify the select-statement so that it supports the returning of distinct row change columns.

2

A column defined AS ROW CHANGE TIMESTAMP does not exist in the table. Alter the table so it has a column with the AS ROW CHANGE TIMESTAMP attribute.

3

A column defined AS ROW CHANGE TIMESTAMP was added to the table, but the table has not yet been reorganized. Reorganize the table.

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:

1. The XDBX data specified is incomplete.
2. An XML sequence was specified for an insert operation and this is not supported.
3. The XDBX data specified for an insert operation contains an unsupported tag.
4. The referenced string ID is not previously defined.
5. The length specified is not correct.

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:

• A constant
• A special register
• A parameter marker
• A variable
• A deterministic function with no external action
• An expression whose operands are any of the previously listed elements

The expression cannot include any of the following elements:

• A column name
• A non-deterministic function
• A function with external action
• An expression whose operands are any of the previously listed 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:

37

A trigger, object-name, is defined for the table and the trigger is not defined as secure.

38

A view is defined on the table, a trigger, object-name, is defined for that view, and the trigger is not defined as secure.

40

The table is either a typed table, or a catalog table.

41

The table is referenced by a materialized query table and the materialized query table references functions with NOT SECURED attribute.

48

The table is the base table of a shadow table.

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:

1

A default row permission cannot be altered.

2

ENABLE cannot be specified because the object is invalid.

The statement cannot be processed.

1

Specify the name of a row permission or column mask that can be changed.

2

For the invalid state, disable the row permission or column mask, then drop and recreate it.

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.

• Do not reference such a column as the input argument to the function.
• Disable or drop the column mask then invoke the function again.

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:

1

The table for which the row permission or the column mask is being defined

2

A table function

3

A user-defined function that is not secure

4

A function that is defined as not deterministic or is defined to have an external action

5

An OLAP specification

6

An XMLEXISTS predicate

7

A ROW CHANGE expression

8

A sequence reference

9

A created or declared temporary table

10

A table that was implicitly created for an XML column

11

A * or name.* in a SELECT clause

12

A column that is defined with a FIELDPROC

13

A language element that requires multiple encoding scheme processing

14

An ordinary SQL identifier that contains a dash (-)

16

A row permission or column mask that includes a period specification

17

A row permission or column mask that references a history table or a table that is defined within a period

18

An aggregate function that does not specify a SELECT clause

19

A nickname

20

A method

21

A pseudocolumn

22

An XMLQUERY scalar function

24

The base table of a shadow table

33

A data type of the return expression that is not the same as the data type of the column on which the column mask is defined

34

A length attribute of the return expression that is not the same as the length attribute of the column on which the column mask is defined

35

A null attribute of the return expression that is not the same as the null attribute of the column on which the column mask is defined

36

A subtype or encoding scheme that is not the same as the corresponding attribute of the column on which the column mask is defined

37

An attribute of the return expression other than the attributes covered

38

The column is referenced in an expression that defines a generated column.

51

A row permission cannot be created for a table that has a security label column.

52

A row permission cannot reference a table that has a security label column.