Explanation

An attempt was made to use raw device containers but one of the following conditions is true:

• Raw devices are not supported on this platform.
• Raw device containers cannot be specified via the SET TABLESPACE CONTAINERS command for auto-resize table spaces.
• Raw device containers are not supported in a DB2 pureScale environment.

Explanation

One of the following conditions is true:

1. An ALTER TABLESPACE statement involving container operations or the REBALANCE clause has previously been issued by this application or another and has yet to be committed.
2. A rebalance is in progress.

Explanation

The map structure keeps a record of how the table space address space is mapped to the various containers. If this gets too complicated, it does not fit in the table space file.

Explanation

Neither the distribution key nor the table partitioning key can have a LONG column, DATALINK column, XML column, or structured type column.

The statement cannot be processed.

Explanation

The table table-name cannot be created in a database partition group. The table must have at least one column that can be used as the distribution key. Columns of the following data types cannot be used in a distribution key:

• BLOB
• CLOB
• DATALINK
• DBCLOB
• LONG VARCHAR
• LONG VARGRAPHIC
• XML
• Structured type
• A user-defined data type based on any of the previously listed data types

The statement cannot be processed.

Explanation

The specified member range is not valid.

The statement cannot be processed.

Explanation

You can only add or drop a partitioning key on a table in a single database partition group.

The statement cannot be processed.

Explanation

For the CREATE DATABASE PARTITION GROUP statement, a database partition number can only appear once in the ON DBPARTITIONNUMS clause.

For the CREATE TABLESPACE and ALTER TABLESPACE statement, a database partition number can appear only once and in only one ON DBPARTITIONNUMS clause.

For the ALTER DATABASE PARTITION GROUP statement or REDISTRIBUTE DATABASE PARTITION GROUP command, one of the following occurred:

• The database partition number appeared more than once in the ADD DBPARTITIONNUMS or the DROP DBPARTITIONNUMS clause.
• The database partition number appeared in both the ADD DBPARTITIONNUMS and the DROP DBPARTITIONNUMS clause.
• The database partition number to be added is already a member of the database partition group.

The statement cannot be processed.

For a call WLM_ALTER_MEMBER_SUBSET statement, the member to be added is already a member of the member subset.

Explanation

The specified member number or database partition number member-number is not valid for one of the following reasons:

• The member number or database partition number is not in the valid range of 0 to 999.
• The member number or database partition number is not in the configuration file.
• The member number or database partition number is not part of the database partition group, therefore the requested operation cannot be processed.
• The statement referenced an event monitor that that is defined to run on a member that does not exist in the instance.
• The member number specified in the WLM_ALTER_MEMBER_SUBSET statement is not in the member subset.

The statement cannot be processed.

Explanation

The statement cannot be processed.

Explanation

Because the database contains the maximum number of partitioning maps (32,768), you cannot create a new database partition group, alter a database partition group, or redistribute an existing one.

The statement cannot be processed.

Explanation

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

1

The primary key, each unique constraint, and each unique index must contain all distribution columns of the table.

2

Updating the distribution key column value is not supported.

3

A foreign key cannot include any nullable distribution key columns when defined with ON DELETE SET NULL. This is a special case of reason code 2 because defining such a constraint would result in attempting to update a distribution key column.

5

Views created with the WITH CHECK OPTION clause should not use functions (or reference views that use functions) that:

• are non-deterministic
• have side effects
• are related to the placement of data, for example, nodenumber or partition functions

These functions must also not be present within a referenced view if the new view is created with the CASCADED check option.

6

A transform cannot be defined for a user-defined distinct type.

7

Long fields can only be defined using a table space with a page size that is 4 KB. A LARGE TABLESPACE can only be created using a 4 KB page size.

8

Structured types are not supported as columns of a table or structured type attribute data types prior to DB2 Version 7.1.

9

Triggers are not supported on typed tables.

10

A single default table space cannot be selected because the table has one or more LOB columns that must be placed in a table space with a 4 KB page size and the rowsize or number of columns in the table requires a table space with an 8 KB page size.

11

A typed table or typed view cannot be created using a structured type that has no attributes.

12

The type of a source key parameter must be a user-defined structured type or a distinct type that is not sourced on the LOB, XML, LONG VARCHAR, or LONG VARGRAPHIC data type.

13

Check constraints cannot be defined on a typed table or the WITH CHECK OPTION clause cannot be specified on a typed view.

14

Referential constraints cannot be defined on a typed table or to a parent table that is a typed table.

15

A default value cannot be defined for reference type columns.

16

A reference data type or structured data type cannot be used as a parameter data type or a returns data type of a user-defined function prior to DB2 UDB Version 7.1. Otherwise, a scoped reference data type or an array data type cannot be used as a parameter data type or returns data type of a routine. A structured data type or an array data type cannot be used as a return column of a table or row function.

17

The SET INTEGRITY statement cannot be used for a typed table.

18

Column-level UPDATE and REFERENCES privileges cannot be granted on a typed table, typed view, or nickname.

19

A default value must be specified when defining a default for a column of a typed table.

20

ALTER TABLE is not supported for a materialized query table.

21

A column cannot be dropped or have its length, data type, security, nullability, or hidden attribute altered on a table that is a base table for a materialized query table.

22

Materialized query tables cannot be defined in a CREATE SCHEMA statement.

23

REPLICATED can be specified only for a materialized query table defined with REFRESH DEFERRED.

24

The triggered-action in a BEFORE trigger cannot reference a materialized query table defined with REFRESH IMMEDIATE.

25

Only one materialized query table can be specified for a SET INTEGRITY statement.

26

The database partition group being redistributed contains at least one replicated materialized query table.

27

A replicated materialized query table cannot be defined on a table that does not have a unique index existing on one or more columns that make up the replicated materialized query table.

28

A typed table or materialized query table cannot be renamed.

29

The FOR EXCEPTION clause cannot be specified with a materialized query table in the SET INTEGRITY statement.

30

Typed tables and typed views cannot be defined in a CREATE SCHEMA statement.

31

A distribution key cannot be defined with more than 500 columns.

32

A table defined using a multipartition database partition group or a single-partition database partition group on other than the catalog partition does not support DATALINK columns defined with FILE LINK CONTROL.

33

An underlying table of a materialized query table defined with REFRESH IMMEDIATE cannot be the child of a referential constraint with a cascading effect (that is, with the option ON DELETE CASCADE or ON DELETE SET NULL).

34

The underlying object relational feature is not supported in the current release.

35

A sequence or an identity column cannot be created in a Version 7 multinode database environment.

36

Activation of a multinode Version 7 database that contains sequences or identity columns is not allowed.

38

An index using an index extension is not supported in a multiple partition database partition group prior to DB2 UDB Version 8.1 FixPak 6.

39

Nicknames or OLE DB table functions cannot be referenced directly or indirectly in the body of an SQL function or SQL method.

40

The function IDENTITY_VAL_LOCAL cannot be used in a trigger or SQL function.

41

A single SQL variable statement cannot assign values to both a local variable and a transition variable.

42

The execution of a trigger, method, or function using SQL control statements and the execution of a dynamic compound statement in a multinode database are not allowed.

43

One or more of the specified options are currently not supported.

44

The following EXPLAIN MODES are not supported in MPP, SMP, and Data Joiner:

• COUNT CARDINALITIES
• COMPARE CARDINALITIES
• ESTIMATE CARDINALITIES

45

APPEND mode is not supported for multidimensional clustering (MDC) or insert time clustering (ITC) tables.

46

INPLACE table reorganization is not supported for multidimensional clustering (MDC) or insert time clustering (ITC) tables.

47

Index extensions are not supported for multidimensional clustering (MDC) or insert time clustering (ITC) tables.

48

Changes to the dimension specification of a multidimensional clustering (MDC) table are not supported.

49

Clustering indexes are not supported for multidimensional clustering (MDC) or insert time clustering (ITC) tables.

50

A user-defined temporary table cannot be a multidimensional clustering (MDC) or insert time clustering (ITC) table.

51

Issuing DDL operations that affect expression-based indexes from a database partition that is not the catalog database partition is not supported.

52

The expression of a generated column cannot be modified or added to a column that was not generated using an expression if that column is a distribution key column or was used in the ORGANIZE BY clause, the PARTITION BY clause, or the DISTRIBUTE BY clause.

53

A column with a LONG VARCHAR, LONG VARGRAPHIC, LOB, or XML type, a distinct type on any of these types, or a structured type cannot be specified in the select-list of a scrollable cursor.

54

INPLACE table reorganization is not supported for the specified system catalog table.

55

Federated database system support and the concentrator feature cannot be active at the same time.

56

Online index reorganization in rebuild mode is not supported for spatial indexes in ALLOW WRITE mode.

57

Online index reorganization is supported on multi-dimensionally clustered (MDC) or insert time clustering (ITC) tables in ALLOW WRITE mode only when the CLEANUP option or RECLAIM EXTENTS option is specified.

58

For a Version 8 database: the XML data type can be used only as a transient data type and cannot be stored in the database nor returned to an application.

59

A function or method that contains SQL statements cannot be used in a partitioned database environment.

60

The ALTER TABLE ALTER COLUMN SET INLINE LENGTH statement is not allowed because there is an object of type VIEW, either typed or untyped, that depends on the typed table.

61

A text search function cannot be used in the expression for check constraints or generated columns.

62

The WITH CHECK OPTION clause cannot be used with views that reference text search functions directly or depend on other views referencing text search functions.

63

A column with a LOB type, distinct type on a LOB type, A column with a LONG VARCHAR, LONG VARGRAPHIC, DATALINK, LOB, XML type, distinct type on any of these types, or structured type cannot be specified in the select-list of an insensitive scrollable cursor.

64

Federated processing is not supported on this platform.

65

Altering the nickname local type from the current type to the specified type is not allowed.

66

The built-in transform group SYSSTRUCT is not supported.

67

Nicknames or views on nicknames cannot be specified as target in a MERGE or UPDATE statement.

68

In a partitioned database, the maximum number of distinct NEXT VALUE expressions supported in an SQL statement is 55.

69

Delete from view would cause a descendent table to be delete-connected via multiple paths to two or more tables that appear in the view definition. Either a check constraint or trigger defined on the descendent table needs to be fired according to the final result which is not guaranteed.

70

A column cannot be dropped, or have its length, data type, security, or nullability altered on a table which is a base table of a view enabled for query optimization.

71

CALL statement cannot be used in a trigger, a SQL function, a SQL method or a dynamic compound statement in a partitioned database environment.

72

A nullable column cannot be changed to become an identity column.

73

Backup images in a partitioned database environment are not allowed to include logs.

74

Updating a status field in the recovery history file by time stamp is not allowed.

75

Automatic statistics profiling is not supported on a multiple database partition system, on a system where SMP is enabled, or on a federated system.

83

For versions of DB2 database prior to V9.7, the statement cannot be processed because DATA CAPTURE CHANGES and COMPRESS YES are not compatible.

87

The following types of tables cannot be defined as partitioned tables: typed tables, staging tables, user temporary tables, and range clustered tables.

89

REORG INDEX is only supported for nonpartitioned indexes on partitioned tables or for the CLEANUP ONLY ALL option.

90

For versions of DB2 database prior to Version 9.7, the PARTITIONED clause cannot be specified on the CREATE INDEX statement because partitioned indexes are not supported.

91

For versions of DB2 database prior to V9.7, the statement cannot be processed because DATA CAPTURE CHANGES is not supported for a table that has a compression dictionary.

92

Detaching from a table that is the parent of an enforced referential integrity constraint is not allowed.

93

Detaching a partition is not allowed for partitions that contain data that was appended using LOAD INSERT, and that have dependent materialized query tables or dependent staging tables that have not been incrementally refreshed with respect to the appended data.

95

A table with an attached partition whose integrity has not been verified yet cannot be altered to be a materialized query table.

97

Altering this data type is not supported for an element of the multinode distribution key, data distribution key, or MDC organizing dimension.

98

Altering the type of an identity column is not supported.

99

An alter table set data type changed the external UDF used by a check constraint.

102

A security policy cannot be added to a typed table.

103

On database servers Version 9.5 and earlier, online index reorganization in ALLOW WRITE mode is not supported for tables with XML columns.

104

In place table REORG is not allowed if an index on an XML column is defined on the table.

105

The REORG INDEX command is supported only for block indexes in CLEANUP or RECLAIM EXTENTS mode.

106

Attaching a partition to a materialized query table is not supported.

109

A text search function cannot be applied to the text index of a partitioned table if the text search function does not directly reference the partitioned table or is a member of a sub-select that contains an OUTER JOIN clause.

110

For SECLABEL, SECLABEL_BY_NAME, and SECLABEL_TO_CHAR, the security policy name parameter must be a string constant.

111

An audit policy cannot be associated with a typed table.

112

The health monitor does not support configuration of actions and notifications on non-root installations.

113

Use of a Compound SQL (compiled) statement in the body of a trigger or SQL table function is not supported in partitioned database environments.

114

Partitioned spatial indexes are not supported.

115

The function cannot be revalidated.

116

The same name was used for more than one named parameter marker in a compound SQL (compiled) statement that is dynamically prepared or executed.

119

If a field of a ROW variable has an ARRAY type, then array element values cannot be directly retrieved by specifying the corresponding index value for the element on the ROW variable field reference.

120

An attempt was made to insert data into an unsupported type of table.

121

The period-definition of a row-organized table must not include the MAINTAINED BY USER clause.

122

The period-definition of a column-organized table must include the MAINTAINED BY USER clause.

Explanation

The index file for the table with fid fid is required during processing. The file is either missing, or it is not valid.

The statement cannot be processed, and the application is still connected to the database. This condition does not affect other statements that do not use the index on this table.

Explanation

This message can be returned for two reasons:

1. The database is in "restore pending" state

As a result of a previous operation, the database is in "restore pending" state. While the database is in "restore pending" state, attempts to connect to the database will fail.

2. The database is in "upgrade pending" state

If the db2ckupgrade utility finds that a database is ready to be upgraded, the db2ckupgrade utility will set the read-only database configuration parameter UPGRADE_PENDING to 1. While this database configuration parameter is set to 1, the database is said to be in "upgrade pending" state. While the database is in "upgrade pending" state, attempts to connect to the database will fail.

Explanation

Commit processing encountered an error. The transaction has been put in the commit state, but the commit processing might not have completed. The application's database connection has been terminated.

The cause of the error is indicated by the reason-code:

1

A node or data source involved in the transaction has failed.

2

Commit was rejected on one for the nodes. Check the administration notification log for details.

Explanation

Explanation

Additional containers cannot be added to a system managed table space. The exception to this is when a database partition group was modified to add a node without table spaces, then containers can be added once on the new node using the ALTER TABLESPACE command. In general, the table space must be managed by the database in order to add additional containers.

The statement cannot be processed.

Explanation

A table in the specified table space does not contain all of its parts in that table space. If more than one table spaces are specified, then a table in one of the specified table spaces does not contain all of its parts in the list. The base table, indexes, or long data may be in another table space, so dropping the table space(s) will not completely drop the table. This would leave the table in an inconsistent state and therefore the table space(s) cannot be dropped.

Explanation

A database must contain at least one system temporary table space with the same page size as the page size of the catalog tablespace. Dropping table space tablespace-name would remove the last system temporary tablespace with a page-size page size from the database.

Explanation

This message is returned when an attempt is made to create a table with properties that are not supported with the type of table space in which the table is being created.

This message can be returned when the following types of SQL statements are executed:

• CREATE TABLE
• CREATE GLOBAL TEMPORARY TABLE
• DECLARE GLOBAL TEMPORARY TABLE

Examples of the kinds of incompatibilities that can cause this message to be returned include the following situations:

• An attempt was made to create a regular table in a table space that is not a REGULAR or LARGE table space.
• An attempt was made to create or declare a temporary table in a table space that is not a USER TEMPORARY table space.
• An attempt was made to create an insert time clustering (ITC) table in a table space that is not a managed by database table space.
• An attempt was made to create a column-organized table in a table space that is not defined as MANAGED BY AUTOMATIC STORAGE and does not have an associated storage group.

Explanation

If the primary table space is a system managed table space, all table parts must be contained in that table space. A table can have parts in separate table spaces only if the primary table space, index table space and long table space are database managed table spaces.

Explanation

The CREATE TABLE, CREATE GLOBAL TEMPORARY TABLE, or DECLARE GLOBAL TEMPORARY TABLE statement did not specify a table space, and a table space of the right type (USER TEMPORARY for created temporary table or declared temporary table) with sufficient page size (at least pagesize), over which authorization ID user-name has USE privilege, could not be found.

Sufficient page size for a table is determined by either the byte count of the row or the number of columns.

Explanation

The CREATE TABLE or GRANT USE OF TABLESPACE statement specified a table space named SYSCATSPACE which is reserved for catalog tables.

Explanation

A LARGE table space is defined to store large objects and long strings. These objects can only be stored in table spaces that are defined as automatic storage.

This message is returned when an attempt was made to create a large table space as a system managed table space.

Explanation

One of the following conditions is true on one or more database partitions:

1

One of the containers assigned to this SMS table space has reached the maximum file size. This is the likely cause of the error.

2

All the containers assigned to this DMS table space are full. This is the likely cause of the error.

3

A rebalance is in progress, but has not progressed far enough to enable the newly added space to be used.

4

A redirected restore is being done to containers that are too small.

5

A rollforward is being done following a redirected restore and all the containers assigned to this tablespace are full.

6

A rollforward skipping add containers is being done and all the containers assigned to this tablespace are full.

7

An attempt was made to create a table space with less than 5 usable extents.

8

An auto-resize table space has reached its maximum size and all of the containers are full. Alternately, there is not enough space between the current size and the maximum size for containers to be extended or added so an automatic increase in space is not possible.

9

An automatic storage table space is being created with a value for initial size that does not result in an equal distribution of container space. As a result, a higher value is being used but this value is larger than the maximum size specified.

10

A DMS table space enabled for auto-resize has not reached its maximum size but one of the file systems on which the containers exists is full and the container cannot grow.

11

A DMS table space enabled for auto-resize has not reached its maximum size and the file systems on which the table space resides are not full. However, a container operation (or a subsequent rebalance) is in progress and the auto-resize capability is suspended until it is complete.

Explanation

A process attempted to access a table space which is in an invalid state, for which the intended access is not allowed.

• If the table space is in a quiesced state ("Quiesced: SHARE", "Quiesced: UPDATE", or "Quiesced: EXCLUSIVE"), only processes which also hold the table space in a quiesced state are allowed access to the table space.
• If the table space is in any other state, only the process which is performing the action that caused the current table space state is allowed access to the table space.
• A system or user temporary table space cannot be dropped which contains active system temporary tables, create temporary tables, or declared temporary tables.
• The SET CONTAINER API cannot be used to set the container list unless the table space is in the "Restore pending" state.

Explanation

An attempt was made to change the state of a table space. Either the new state is not compatible with the current state of the table space, or an attempt was made to turn off a particular state and the table space was not in that state.

Explanation

An internal database file could not be created.

Explanation

This error may be caused by one of the following conditions:

• A container (directory, file or raw device) was not found.
• A container is not tagged as being owned by the proper table space.
• A container tag is corrupt.

This error can be returned during database startup and during the processing of the ALTER TABLESPACE SQL statement.

Explanation

Table space containers cannot be shared. The possible causes of this error include the following.

• A CREATE TABLESPACE or ALTER TABLESPACE statement included a container that is already in use by another table space.
• A CREATE TABLESPACE or ALTER TABLESPACE statement included a container from a table space that has been dropped but the drop statement has not been committed.
• An ALTER DATABASE PARTITION statement used to add a database partition used the containers of a LIKE database partition that is on the same physical database partition. These containers would therefore already be in use.
• A CREATE TABLESPACE or ALTER TABLESPACE statement is attempting to use the same container on more than one logical database partition on a single physical database partition. The same containers cannot be used for more than one database partition on the same physical database partition.
• An ADD DATABASE PARTITION command or API used the containers from the system temporary table spaces of a LIKE database partition that is on the same physical database partition. These containers would therefore already be in use.
• A CREATE TABLESPACE statement, ALTER TABLESPACE statement, or CREATE DATABASE command included a DMS container from another database that no longer exists but was not dropped properly. The container is not actually in use but it is tagged as being in use. Therefore, the DB2 data server will not allow it to be used until it is untagged. However, it is very important to verify that the container is not in use by the same database or another database when untagging it. If the container is in use when you untag it, the database (or databases) involved will be corrupted.
• A REORG attempted to automatically select a DMS temporary table space for use, and although one with the correct page size exists, it is currently in use by another REORG command.
• The ADD DBPARTITIONNUM option of the REDISTRIBUTE command, which was used to add a database partition, creates table space container names on the newly added database partition based on the table space container names of the table spaces on the lowest numbered database partition. If these container names specify absolute paths, and if the new database partition is on the same physical device as a database partition using the same container names, then the containers for the new partition would already be in use.
• A RESTORE DATABASE command has found containers from a database that no longer exists but was not dropped properly.
• A temporary staging database was created for a transport operation, and then an attempt was made to create a table space on the target database while the temporary staging database still exists.

Explanation

The total space required to store the list of containers exceeds the space allotted for this table space in the table space file.

Explanation

This message is returned when an attempt is made to create a database object when there are already the maximum number of that type of database object defined for the database.

Explanation

Explanation

The container path violates one of the following requirements:

• Container paths must be valid fully-qualified absolute paths or valid relative paths. The latter are interpreted relative to the database directory.
• For EXTEND, REDUCE, RESIZE and DROP operations, the specified container path must exist.
• The path must be read/write accessible to the instance id (check file permissions on UNIX-based systems).
• Containers must be of the type specified in the command (directory, file or device).
• Containers (directories) in system managed table spaces must be empty when designated as containers and must not be nested underneath other containers.
• The containers for one database must not be located underneath the directory of another database, and they may not be underneath any directory that appears to be for another database. This rules out any directory of the form SQLnnnnn, where 'n' is any digit.
• The container must be within the file size limit for the operating system.
• Containers (files) for dropped database managed table spaces can only be reused as containers (directories) for system managed table spaces after all agents terminate and vice versa.
• During a redirected restore, an SMS container was specified for a DMS table space or a DMS container was specified for an SMS table space.
• The specified type of the container for an EXTEND, REDUCE, RESIZE, or DROP operation does not match the type of the container (FILE or DEVICE) that was specified when the container was created.

This message will also be returned if any other unexpected error occurred which prevents DB2 from accessing the container.

If you are using a cluster manager, this error can be returned if the database manager failed to add the database container path to the cluster manager configuration. If the cluster manager cannot access this path, the cluster manager will not be able to successfully manage a failover involving this path. Error messages from the cluster manager will be recorded in the db2diag log file.

Explanation

The container that you are attempting to add has already been assigned to the table space.

Explanation

A variable, expression, or parameter in position number could not be used as specified in the statement because its data type is incompatible with the intended use of its value.

This error can occur as a result of specifying an incorrect host variable or an incorrect SQLTYPE value in a SQLDA on an EXECUTE or OPEN statement. In the case of a user-defined structured type, the associated built-in type of the host variable or SQLTYPE might not be compatible with the parameter of the TO SQL transform function defined in the transform group for the statement. In the case of performing an implicit or explicit cast between character and graphic data types, this error indicates that such a cast was attempted with a non-Unicode character or graphic string.

The statement cannot be processed.

Explanation

The value of an input host variable was found to be out of range for its use in the SELECT, VALUES, or prepared statement.

One of the following occurred:

• The corresponding host variable or parameter marker used in the SQL statement is defined as string, but the input host variable contains a string that is too long.
• The corresponding host variable or parameter marker used in the SQL statement is defined as numeric, but the input host variable contains a numeric value that is out of range.
• The terminating NUL character is missing from the C language NUL-terminated character string host variable.
• Federated system users: in a pass-through session, a data source-specific restriction might have been violated.

This error occurs as a result of specifying either an incorrect host variable or an incorrect SQLLEN value in an SQLDA on an EXECUTE or OPEN statement.

The statement cannot be processed.

Explanation

An embedded SELECT, VALUES, FETCH or assignment statement assigns to a host variable, but the data type of the variable is not compatible with the data type of the corresponding SELECT-list, VALUES-list, or right-hand side of the assignment statement element. For a user-defined data type, the host variable might be defined with an associated built-in data type that is not compatible with the result type of the FROM SQL transform function defined in the transform group for the statement. For example, if the data type of the column is date or time, the data type of the variable must be character with an appropriate minimum length.

The statement cannot be processed.

Explanation

A FETCH, VALUES, SELECT, or assignment into a host variable list failed because the host variable was not large enough to hold the retrieved value.

The statement cannot be processed. No data was retrieved.

Explanation

A FETCH, assignment, or embedded SELECT or VALUES operation resulted in the retrieval of a NULL value to be inserted into a host variable for which no indicator variable was provided. An indicator variable must be supplied if a column can return a NULL value.

The statement cannot be processed. No data was retrieved.

Explanation

The host variable name is not declared in any DECLARE SECTION.

The statement cannot be processed.

Explanation

The host variable name has already been declared in a DECLARE SECTION.

The definition is ignored. The previous definition is used.

Explanation

The limit on the number of host variables is dependent on how many will fit in the HOST_VARS column of SYSPLAN. This limit has been reached.

The remaining variable declarations are ignored.

Explanation

The value of an input host variable was found to be NULL but the corresponding use in the SELECT, VALUES, or prepared statement did not specify an indicator variable.

The statement cannot be processed.

Explanation

The maximum number of host variables was exceeded in the statement.

The statement cannot be processed.

Explanation

When evaluated, the length specification for the string host variable, whose entry in the SQLDA is indicated by <var-number> (based at 1), was negative or greater than the maximum defined for that host variable.

The statement cannot be processed.

Explanation

This message can be returned when a host variable is used in the following invalid ways:

• A host variable, variable_name, is used in a dynamic SQL statement or in a DDL statement.
• A host variable, variable_name, that is a structure is used in a place where structure references are not permitted.

Explanation

The number of variables specified in the EXECUTE or OPEN statement does not equal the number of variables required for the parameter markers appearing in the SQL statement.

If a parameterized cursor is referenced, the number of cursor arguments is not the same as the number expected.

Explanation

The host variable name is not declared correctly for one of the following reasons:

• The type specified is not one that is supported.
• The length specification is 0, negative, or too large.
• An initializer is used.
• An incorrect syntax is specified.
• A host variable array with cardinality larger than the maximum allowed value is specified.

The variable remains undefined.

Explanation

The variable remains undefined.

Explanation

The end of input was reached during processing of a DECLARE SECTION.

Precompilation is terminated.

Explanation

An END DECLARE SECTION statement was found, but there was no previous BEGIN DECLARE SECTION.

The statement cannot be processed.

Explanation

Either the INDICATOR variable name is not a small integer or the STATEMENT variable name is not a character data type.

The statement cannot be processed.

Explanation

If the operation is an insert or an update, the value of the table partitioning key for the row is not within range of values for any defined data partition.

If the operation is altering a table to become a partitioned table, then there exists one or more rows in the table with a table partitioning key value that is not within the range of values for any defined data partition.

The statement cannot be processed.

Explanation

String constant or input host variable string-constant-or-host-variable contains a path name list that is not valid. The maximum number of schema names for the SQL path (FUNCPATH bind option or CURRENT PATH special register) or package path (CURRENT PACKAGE PATH special register) has been exceeded. See the Limits appendix of the SQL Reference for details of this limit.

The statement or command cannot be processed.

Explanation

If the reason-code is 12, code-point is the invalid code point. Otherwise, code-point is either blank or an additional reason code returned by an exit. If the string is the value of an input host variable, the position-number is the ordinality of the variable in the SQLDA. If the string is not the value of a host variable, the position-number is blank.

The statement cannot be processed.

Explanation

The operation failed because there is no code page conversion between the source-code-page and target-code-page. This may be due to one of the following reasons:

1. The character repertoires of the source code page and the target code page are incompatible, and therefore may cause character loss and corruption when converting between the source and target code pages.
2. This specific code page conversion is not supported.

Some of the possible operations that can cause this error include:

• Connecting a client to a database where the client's code page is different from the database code page.
• Executing an SQL statement where the client's code page is different from the database code page.
• Importing or exporting an IXF file where the file's code page is different from the database code page.
• Federated system users: the data source does not support the specified code page conversion.

Explanation

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.

Explanation

The decimal number is used in a context where the scale must be zero. This can occur when a decimal number is specified in a CREATE or ALTER SEQUENCE statement for START WITH, INCREMENT, MINVALUE, MAXVALUE or RESTART WITH.

The statement cannot be processed.

Explanation

The statement cannot be processed.

Explanation

The common table expression name name is used in the definition of more than one common table expressions in the statement. The name used to describe a common table expression must be unique within the same statement.

The statement cannot be processed.

Explanation

The common table expression name1 refers to name2 in a FROM clause within its fullselect and name2 refers to name1 in a FROM clause within its fullselects. Such forms of cyclic references are not allowed.

The statement cannot be processed.

Explanation

The statement cannot be processed.

Explanation

The recursive common table expression name must include the specification of the column names following the identifier of the common table expression.

The statement cannot be processed.

Explanation

The recursive common table expression name has a column column-name that is referred to in the iterative fullselect of the common table expression. The data type, length and code page are set based on the initialization fullselect for this column. The result of the expression for the column column-name in the iterative fullselect has a different data type, length or code page that may result in failure to assign the value for the column.

The statement cannot be processed.

Explanation

The statement cannot be processed.

Explanation

The statement cannot be processed.

Explanation

The absence of this syntax in the recursive common table expression may result in an infinite loop. The data or some other characteristic of the recursive common table expression may allow the successful completion of the statement anyway.

Explanation

The statement cannot be executed.

Explanation

INSERT INTO T1 
  VALUES(
    NEXT VALUE FOR sequence1 + 5, 'a'
    ),
    (
    NEXT VALUE FOR sequence1 + 5, 'b'
    ),
    (
    NEXT VALUE FOR sequence1 + 5, 'c'
    )

INSERT INTO T1 
  VALUES(
    NEXT VALUE FOR sequence1 + 5, 'a'
    ),
    (
    NEXT VALUE FOR sequence1 + 5, 'b'
    ),
    (
    NEXT VALUE FOR sequence1 + 4, 'c'
    )

Explanation

The ALTER statement, CREATE statement, or DECLARE GLOBAL TEMPORARY TABLE statement is invalid for one of the following reasons:

• A LOB, LONG VARCHAR, LONG VARGRAPHIC, XML, or structured type column cannot be used in a key.
• A LOB, LONG VARCHAR, LONG VARGRAPHIC, XML, or structured type column cannot be used in a unique constraint.
• A LOB, LONG VARCHAR, LONG VARGRAPHIC, XML, or structured type column cannot be used in a generated column.
• A LONG VARCHAR, LONG VARGRAPHIC, SYSPROC.DB2SECURITYLABEL, XML, or structured type column cannot be used in a created temporary table.
• A LONG VARCHAR, LONG VARGRAPHIC, SYSPROC.DB2SECURITYLABEL, distinct type, or structured type column cannot be used in a declared temporary table.
• A LOB column cannot be used in an index definition.
• An XML column can only be used in an index definition if it is the only column and an XMLPATTERN clause is specified.
• A structured type column can only be used in an index definition if it is the only column and has an associated index extension specified.
• The definition of a column mask or a row permission cannot reference a LOB or XML column.
• A column mask cannot be defined for a LOB or XML column.
• In Hadoop tables:
  • Columns whose type is array cannot be used in a unique definition.
  • Columns whose type is row cannot be used in a unique definition.
  • Columns whose type is array cannot be used in primary key definitions.
  • Columns whose type is row cannot be used in primary key definitions.
  • Columns whose type is array cannot be used in index definitions.
  • Columns whose type is row cannot be used in index definitions.
  • The first column cannot have a data type of array or row.

The same restrictions apply to a distinct type column where the base data type is subject to one of the restrictions in the listed previously.

The statement cannot be processed.

Explanation

The element of the SQLDA at position position-number is for a data type that either the application requestor or the application server does not support. If the application is not using the SQLDA directly, position-number could represent the position of an element in the select list or a parameter of a CALL statement.

The statement cannot be processed.

Explanation

The element of the SQLDA at position position-number is for a data type that either the application requestor or the application server does not support. If the application is not using the SQLDA directly, position-number could represent the position of an input host variable, parameter marker, or a parameter of a CALL statement.

The statement cannot be processed.

Explanation

Large Object data types (BLOB, CLOB, and DBCLOB) may be created in sizes up to 2 gigabytes (2147483647 bytes). Logging of data values is allowed only upon objects which are less than or equal to than 1 gigabyte (1073741823 bytes) in size. Therefore, large objects greater than 1 gigabyte in size can not be logged.

Explanation

You can create a table index which includes expression-based keys. This message is returned when an attempt is made to create an index that includes expression-based keys, and one of the following conditions exists:

• There is something invalid about one of the expression-based key definitions
• The table does not support expression-based keys

The runtime token expression-number identifies which key expression in the statement is invalid. For example, if there are two key expressions in the CREATE INDEX statement, and the second key expression is invalid, the value of expression-number will be: "2". If the expression number cannot be determined, a default value of "*" will be returned.

The reason code indicates what was invalid about the key expression:

1

The key expression contained a subquery.

2

The key expression did not contain a reference to at least one column.

3

The key expression referenced a special register or the key expression referenced a function that depends on the value of special register.

5

The key expression included a user-defined function.

6

The same key expression appears more than once in the index definition.

15

The key expression referenced a global variable or the key expression referenced a function that depends on the value of a global variable.

16

The key expression referenced a sequence.

17

The key expression referenced an unsupported type of function:

• A non-deterministic function
• A function with external actions
• A function that has an unsupported access level:
  • READ SQL DATA
  • MODIFIES SQL DATA

18

The key expression included a value with an unsupported data type.

19

The key expression included an aggregate function or an OLAP specification.

20

The SCOPE clause was included in the index definition and the key expression contained one of the following:

• Dereference operation
• A TYPE predicate
• A CAST specification

21

The key expression includes an XMLQUERY expression or an XMLEXISTS expression.

22

An attempt was made to create an expression-based index on a table that does not support expression-based indexes.

23

The key expression referenced an unsupported type of function such as the LIKE predicate.

24

The result data type of the expression-based key is not indexable.

Explanation

The database manager attempted to generate a value for an identity column or sequence object, however all allowable values have already been assigned.

The statement cannot be processed.

Explanation

DATALINK values in table table-name may not be valid because the table is either in Datalink Reconcile Pending (DRP) or Datalink Reconcile Not Possible (DRNP) state. While in either of these states, control of the files on the DB2 Data Links Manager is not guaranteed.

Statement processing continues.

Explanation

The operation was successful as some of what was specified completed successfully, but some parts of the operation were unsuccessful.

Explanation

The exception exception-type occurred while doing an operation-type operation on a field whose data type is DECFLOAT. The exception occurred while processing an arithmetic expression.

The DECFLOAT exception may occur due to a temporary internal copy of the data that was converted to DECFLOAT for the operation.

Any of the exceptions can occur during the processing of a built-in function. If the operation-type is FUNCTION, then the exception occurred while processing either an input, intermediate, or final value. The cause could be that the value of a parameter is out of range.

Statement processing continues.

Explanation

You can represent the SQL null value in an application program by using an indicator variable with a host variable. You can also represent the default value or the unassigned value by using an extended indicator with host variables.

There are some restrictions on how and where extended indicators can be used. For example, values of default (-5) or unassigned (-7) must not be used for extended indicator variables in a VALUES clause that specifies more than one row of values.

This message is returned when a value of default (-5) or unassigned (-7) is used in a context in which these values are not allowed.

Diagnostic information in the runtime token position:

• In general, the position given by the runtime token postition is the ordinal of the host variable that is using the extended indicator.
• If position is 0, a mismatch in extended indicator support occurred. Extended indicator support was not explicitly enabled or disabled for the dynamically prepared UPDATE statement, and there was a mismatch between the extended indicator support that was explicitly enabled or disabled for the dynamically prepared SELECT statement that is the target of the update and the extended indicator support for the bind or precompile.

Explanation

The DB2 Data Links Manager dlm-name is not registered to the database. Registered DB2 Data Links Managers are ignored if the database manager configuration parameter DATALINKS is set to NO. The DB2 Data Links Manager may have been dropped using the DROP DATALINKS MANAGER command. It is possible that a new incarnation of the DB2 Data Links Manager with the same name is currently registered; in that case, the error pertains to one or more previously dropped incarnations of that DB2 Data Links Manager.

The statement cannot be processed.

Explanation

All parameters for functions defined with LANGUAGE SQL must have a parameter-name for each parameter.

The statement cannot be processed.

Explanation

An attempt was made to do one of the following:

• Create a table with more than one IDENTITY column.
• Add an IDENTITY column to a table which already has one.
• Create a table with more than one ROWID column.
• Add a ROWID column to a table which already has one.
• Create a table with more than one security label column.
• Add a security label column to a table that already has one.
• Create a table with more than one row change timestamp column.
• Add a row change timestamp column to a table that already has one.
• Create a table with more than one row-begin column.
• Add a row-begin column to a table that already has one.
• Create a table with more than one row-end column.
• Add a row-end column to a table that already has one.
• Create a table with more than one transaction start-ID column.
• Add a transaction start-ID column to a table that already has one.
• Define a period more than once in a table.

The ROWID data type is supported in DB2 for z/OS and DB2 for iSeries.

The statement cannot be processed.

Explanation

A DEFAULT clause was specified when defining or changing column or SQL variable name. The data type for the column definition or SQL variable declaration does not support DEFAULT. A CREATE or ALTER TABLE statement cannot use the DEFAULT clause when defining the following:

• an identity column
• a ROWID column
• an XML column
• a row change timestamp column
• a security label column
• a row-begin column
• a row-end column
• a transaction-start-ID column
• a random distribution key column of a random distribution table using random by generation method

The statement cannot be processed.

Explanation

The following situations may be the cause of this error.

MODIFIES SQL DATA must be specified if the body of the function defined with LANGUAGE SQL can modify SQL data or if it calls a function or a procedure that can modify SQL data.

READS SQL DATA must be specified if the body of the function defined with LANGUAGE SQL contains a subselect or if it calls a function that can read sql data.

The statement cannot be processed.

Explanation

The SQL routine includes at least one statement that assigns a value to the SQLSTATE or SQLCODE special variables. These variables are assigned values by processing of SQL statements in the SQL routine. The value assigned may therefore be over-written as a result of the SQL statement processing. Furthermore, the assignment of a value to the SQLSTATE special variable does not activate any handlers.

The routine definition was processed successfully.

Explanation

One of the data types must be a user-defined type. The source type and the target type cannot be the same data type.

The statement cannot be processed.

Explanation

The statement cannot be processed.

Explanation

If the runtime token specific-name is an empty string, then the function resolved to the built-in function identified by the runtime token function-name.

This message can be returned in many scenario. Here is a short list of some of the possible situations in which this message can be returned:

• The specific function is a scalar, column, or row function where only a table function is expected (such as in the FROM clause of a query).
• The specified function has OUT or INOUT parameters and the context in which the function is used is not supported. A compiled function can be invoked only if the function invocation is the sole expression on the right hand side of a SET variable statement that is in a compound SQL (compiled) statement.
• The specified function is not a generic table function, but a typed-correlation clause was specified.

Explanation

The statement cannot be processed.

Explanation

The application is running with DB2 rules, and has requested that LOB data be returned as a LOB in one FETCH statement, and as a locator in another FETCH statement. This is not permitted.

Explanation

A routine object-name (specific name specific-name) attempted to execute an SQL statement (other than CLOSE cursor) during FINAL CALL (call-type = 255) processing. This is not allowed.

Explanation

The operation using operator cannot be processed for one of the following reasons:

• The data types of the operands must be comparable and compatible but there is at least one pair of types that is not comparable or compatible.
• The data type of an operand is XML which cannot be compared (with itself or any other type).
• The data type of an operand is DATALINK which cannot be compared (with itself or any other type).
• The data type of an operand is a structured type which cannot be compared (with itself or any other type).
• Columns of type array from two Hadoop tables cannot be compared directly.
• Columns of type row from two Hadoop tables cannot be compared directly.

Federated system users: this data type violation can be at the data source or at the federated server.

Some data sources do not provide the appropriate values for operator. In these cases the message token will have the following format: "<data-source>:UNKNOWN", indicating that the actual value for the specified data source is unknown.

The statement cannot be processed.

Explanation

An invalid operand is specified for the arithmetic function or operator operator.

The statement cannot be processed.

Explanation

The alias <name> has been defined upon:

• a table, view, module, or sequence which currently is not defined in the database
• another alias which resolves to a table, view, module, or sequence which is not defined in the database.

The object <name2> is the undefined object. This object must exist before any SQL statement (other than CREATE ALIAS) can successfully use the newly created alias. The specified alias <name> is created.

An inoperative view is considered to be undefined for the purposes of creating an alias.

Explanation

An INSERT or UPDATE statement specifies a value that is longer than the maximum-length string that can be stored in the column indicated.

The statement cannot be processed.

Explanation

The specified numeric literal is not in the acceptable range.

The proper ranges for SQL values are as follows:

• For FLOAT values:
  • 0
  • In the positive range of +2.225E-307 to +1.79769E+308
  • In the negative range of -1.79769E+308 to -2.225E-307.
• -9999999999999999999999999999999. to 9999999999999999999999999999999. for DECIMAL values
• -2147483647 to 2147483647 for INTEGER values
• -32768 to +32767 for small integer (SMALLINT) values.

In certain contexts the literal may have further restrictions that result in this error.

Federated system users: this range violation can be at the data source or at the federated server. The proper ranges for SQL values located in data source tables depend on the data source. To determine the correct range, see the appropriate documentation for the data source. Some data sources do not provide the appropriate values for literal. In these cases the message token will have the following format: "<data source>:UNKNOWN", indicating that the actual value for the specified data source is unknown.

Range-clustered tables: the ending value of a range definition is smaller than the starting value.

The statement cannot be processed.

Explanation

The value of a host variable or a numeric value calculated during processing of the UPDATE or INSERT SQL statement is outside the target column range. This problem may be caused by the values occurring in the object column, the SQL operation being performed on those values, or both.

The statement cannot be processed.

Explanation

One of the following occurred:

• The update or insert value was NULL, but the object column was declared as NOT NULL in the table definition. Consequently:
  • NULL values cannot be inserted into that column.
  • An update cannot set values in that column to NULL.
  • A SET transition-variable statement in a trigger cannot set values in that column to NULL.
• The update or insert value was DEFAULT, but the object column was declared as NOT NULL without WITH DEFAULT in the table definition. Consequently:
  • A default value of NULL cannot be inserted into that column.
  • An update cannot set default values of NULL in that column.
  • A SET transition-variable statement in a trigger cannot set default values of NULL in that column.
• The column name list for the INSERT statement omits a column declared NOT NULL and without WITH DEFAULT in the table definition.
• The view for the INSERT statement omits a column declared NOT NULL and without WITH DEFAULT in the base table definition.
• An alter table statement attempted to alter the column with SET NOT NULL, but the existing table data contained a row with the NULL value.

If the value for name is of the form "TBSPACEID=n1, TABLEID=n2, COLNO=n3", then the column name from the SQL statement was not available when the error was issued. The values provided identify the tablespace, table, and column number of the base table that does not allow NULL value.

Federated system users: this situation can be detected by the federated server or by the data source. Some data sources do not provide the appropriate values for name. In these cases the message token will have the following format: "<data source>:UNKNOWN", indicating that the actual value for the specified data source is unknown.

HBase or Hadoop users: This situation can occur when the underlying Hadoop or HBase data is being read and one of the following happens:

• The underlying data contained NULL in a column that is declared as NOT NULL.
• An invalid value was encountered (which is implicitly treated as NULL) in a column that is declared as NOT NULL.

The value of name can be specified as schema-name.table-name.column-name.

The statement cannot be processed.

Under some circumstances, the token name may not be filled in (sqlerrmc field of the SQLCA not filled in).

Explanation

The data type of the value to be assigned to the column, parameter, SQL variable, or transition variable by the SQL statement is incompatible with the declared data type of the assignment target.

For Hadoop tables:

• Array column values cannot be assigned to array variables.
• Row column values cannot be assigned to row variables.
• Complex type (array or row) column values and variables are not compatible for assignment.

The statement cannot be processed.

Explanation

As specified in the SQL statement, the operand of the COUNT function does not conform to the rules of SQL syntax. Only COUNT(*) and COUNT(DISTINCT column) are allowed.

The statement cannot be processed.

Explanation

The specified value is too long. A floating-point string has a maximum length of 30 characters. A decimal floating-point string has a maximum length of 42 characters.

The statement cannot be processed.

Explanation

In the context of the SQL statement, a fullselect is specified that can have only one column as a result.

The statement cannot be processed.

Explanation

During processing of the SQL statement, an overflow condition arose when converting from one numeric type to another. Numeric conversion is performed according to the standard rules of SQL.

Federated system users: numeric conversion can occur at the federated server, at data sources, or both.

The statement cannot be processed. No data was retrieved, updated, or deleted.

Explanation

There are various statements where this error may occur.

• It may occur within a SELECT or VALUES statement that includes set operations (UNION, INTERSECT, or EXCEPT). The corresponding columns of the subselects or fullselects that make up the SELECT or VALUES statements are not compatible.
• It may occur within an INSERT statement that is inserting multiple rows. In this case, the corresponding columns of the rows specified in the VALUES clause are not compatible.
• It may occur within a SELECT or VALUES statement where the VALUES clause is used with multiple rows. In this case, the corresponding columns of the rows specified in the VALUES clause are not compatible.
• It may occur with a UNION ALL clause with two Hadoop tables, each having a column of type ARRAY.

It may occur within the array constructor, when the data type of the two values listed in the constructor are not compatible.

See Assignments and Comparisons in the SQL Reference for details on data type compatibility.

The statement cannot be processed.

Explanation

One of the SELECT or VALUES statements connected by a set operator specifies a result column that is longer than 254 bytes. VARCHAR or VARGRAPHIC result columns longer than 254 bytes can be used only with the UNION ALL set operator.

The statement cannot be processed.

Explanation

    ? > ?

The statement cannot be processed.

Explanation

This message can be encountered in many scenarios, and can be returned for multiple reasons.

Examples of reasons this message can be returned:

• The DEFAULT keyword was specified as the only argument of a datetime arithmetic operation.
• A parameter marker is used in a statement that is not a prepared statement. (Note that references to the PARAMETER function in the first argument of the XQuery function db2-fn:sqlquery are also considered to be parameter markers.)
• A null value was specified as an argument of an XML function (such as XMLQUERY, for example.)
• All result expressions of a CASE expression are untyped.

Explanation

A specified decimal division is not valid because it will result in a negative scale.

The formula used internally to calculate the scale of the result for decimal division is:

Scale of result = 31 - np + ns - ds

where np is the precision of the numerator, ns is the scale of the numerator, and ds is the scale of the denominator.

Federated system users: Decimal division can occur at the federated server, at data sources, or both. The specified decimal division results in an invalid scale for that data source.

The statement cannot be processed.

Explanation

The function function-name has a character string argument that contains a character that is not valid in a numeric SQL constant. The function may have been called as a result of using the CAST specification with function-name as the target data type or when an argument is implicitly cast to a numeric data type. The function or data type used in the SQL statement may be a synonym for function-name.

If a decimal character is specified in the DECIMAL function then that is the character that must be used in place of the default decimal character.

Explanation

The operands of a set operator such as UNION, EXCEPT, or INTERSECT must have the same number of columns. The rows in a VALUES clause must have the same number of columns.

The statement cannot be processed.

Explanation

A locator variable is in error. Either it has not had a valid result set locator or LOB locator variable value assigned to it, the locator associated with the variable has been freed, or the result set cursor has been closed.

If variable-position is provided, it gives the ordinal position of the variable in error in the set of variables specified. Depending on when the error is detected, the database manager may not be able to determine variable-position.

Instead of an ordinal position, variable-position may have the value "function-name RETURNS", which means that the locator value returned from the user-defined function identified by function-name is in error.

Explanation

An application executing in a CONNECT TYPE 2 environment or Distributed Transaction Processing (DTP) environment such as CICS has attempted to execute an SQL dynamic COMMIT statement. The SQL dynamic COMMIT statement cannot be executed in this environment.

Federated system users: SQL dynamic COMMIT statements cannot be executed during a pass-through session.

Explanation

An application executing in a CONNECT TYPE 2 environment or Distributed Transaction Processing (DTP) environment such as CICS has attempted to execute an SQL dynamic ROLLBACK statement. The SQL dynamic ROLLBACK statement cannot be executed in this environment.

Federated system users: SQL dynamic ROLLBACK statements cannot be executed during a pass-through session.

Explanation

The SQL statement that was issued is required to execute before any other SQL statement that initiates a unit of work. Following are possible situations:

• The SQL statement must be first in the unit of work and SQL has been issued against the connection within the unit of work.
• The SQL statement must be first in the unit of work and a WITH HOLD cursor is currently open for the connection.

Note that when the statement is DISCONNECT ALL, it causes the DISCONNECT to be directed against all connections, so the request will fail if any of the connections violate the previously described restrictions.

Explanation

A maximum of 4,000,000 concurrent LOB locators per unit of work, is supported by DB2.

Explanation

An abnormal termination has occurred while the named UDF was in control.

Explanation

A user interrupt or client interrupt has occurred while the routine, trigger or anonymous block was in control.

An anonymous block has no object name or specific name and is identified with an object type of "BEGIN...END".

Encountering this message might indicate some problem in the logic, such as an infinite loop or wait.

Explanation

An untyped expression (parameter marker or null value) in the statement has been determined as having the user-defined type udt-name or a reference type with the target type udt-name based on the context in which it is used. An untyped expression cannot have a user-defined type or reference type as its data type unless it is part of an assignment (VALUES clause of INSERT or SET clause of UPDATE) or it is being explicitly cast to a user-defined distinct data type or reference data type using the CAST specification.

The statement cannot be processed.

Explanation

The value value required truncation by a system (built-in) cast or adjustment function, which was called to transform the value in some way. The truncation is not allowed where this value is used.

The statement cannot be processed.

Explanation

The value that was specified for clause clause is not supported and has been replaced with the identified supported value value.

Explanation

The SQLSTATE value specified by the RAISE_ERROR function or on the SIGNAL or RESIGNAL statement does not conform to the rules for an application defined SQLSTATE.

Explanation

The value of an input host variable code in the C programming language requires a NULL-terminator character at the end of the string.

The statement cannot be processed.

Explanation

Query optimization is one of the factors that affect application performance. The SQL and XQuery compiler performs several steps to produce an access plan that can be executed.

In general, this message is returned when the complexity of a query requires resources that are not available or when optimization boundary conditions were encountered.

The reason code indicates in more detail why the performance might be sub-optimal:

1

The join enumeration method was altered due to memory constraints

2

The join enumeration method was altered due to query complexity

3

Optimizer cost underflow

4

Optimizer cost overflow

5

Query optimization class was too low

6

Optimizer tolerated an inconsistent statistic

13

An optimization guideline could not be applied

15

Chosen plan materializes an intermediate result set, whose size might exceed the limit imposed by the registry variable DB2_OPT_MAX_TEMP_SIZE

16

The query contains XQuery transform expressions that are not parallelized in a database partitioned environment.

The statement will be processed.

Explanation

This error or warning occurred as a result of execution of the RAISE_ERROR function or the SIGNAL SQLSTATE statement in a trigger. An SQLSTATE value that starts with '01' or '02' indicates a warning.

Explanation

The function function-name was referenced in the user's statement. However, because the SOURCE clause was used in the definition of this function, it has turned out that function source-function actually implements the function. (It may be a direct or an indirect definition path from function-name to source-function.) At compile time, the encapsulator (DB2 code which acts on behalf of a function) for source-function has returned the error identified by sqlcode.

Explanation

This occurs in a reference to routine routine-name, when the database manager cannot find a routine it can use to implement the reference. There are several reasons why this could occur:

• routine-name was either incorrectly specified or does not exist in the database.
• A qualified reference was made, and the qualifier was incorrectly specified.
• The user's SQL path does not contain the schema to which the desired function or method belongs, and an unqualified reference was used.
• The user's SQL path does not contain the module to which the desired routine belongs.
• The module-qualified routine reference is made from outside the module but the module routine is not published.
• The wrong number of arguments was included.
• The right number of arguments was included in the function or method reference, but the data types of one or more of the arguments is incorrect.
• Named arguments were used which do not match the parameter names of routine routine-name.
• There are one or more routines with the same name and number of parameters declared in the current compound statement.
• There are one or more routines with the same name declared in the outer compound statements within which the current compound statement declaring a routine is nested.
• The routine does not exist in the database with the same function id that was used when the package was bound (applies to static statements).
• The mutator method corresponding to an attribute assignment used in an UPDATE statement could not be found. The data type of the new value for the attribute is not a data type that is the same or promotable to the data type of the attribute.
• The routine invoker is not authorized to execute the routine.
• The server time was reset or changed.
• The database was restored on a server with a different time or time zone.
• The time associated with the members in multi-partitionned database environments is out of sync.

Explanation

Explanation

Too many arguments were specified in the reference to routine routine-name. The maximum allowable is 90.

Explanation

This message is returned when a built-in or user-defined routine (procedure, function, or method) fails.

The contents of the third run-time token, text, varies:

• When this message is returned because a user-defined routine failed, the contents of the third run-time token, text, is whatever was implemented by the creator of the routine.
• In general, when this message is returned because a built-in routine failed, the contents of the third run-time token, text, will contain an embedded error code:

  Example 1 - In this example, text refers to message DBA7904N.

  [IBM][CLI Driver][DB2/AIX64] SQL0443N Routine 
  "SYSPROC.ALTOBJ" (specific name "ALTOBJ") has
  returned an error SQLSTATE with diagnostic text 
  "DBA7904, DBAD".  SQLSTATE=38553

  Example 2 - In this example, text refers to sqlcode -805.

  [IBM][CLI Driver][DB2/AIX64] SQL0443N Routine 
  "SYSIBM.SQLTABLES" (specific name "TABLES") has
  returned an error SQLSTATE with diagnostic text 
  "SYSIBM:CLI:-805".  SQLSTATE=38553

• When this message is returned because a built-in function in the SYSFUN schema failed, the third run-time token, text, is of the following format:

  SYSFUN:nn

  where nn is a reason code having the following meaning:

  01

  Numeric value out of range

  02

  Division by zero

  03

  Arithmetic overflow or underflow

  04

  Invalid date format

  05

  Invalid time format

  06

  Invalid timestamp format

  07

  Invalid character representation of a timestamp duration

  08

  Invalid interval type

  09

  String too long

  10

  Length or position in string function out of range

  11

  Invalid character representation of a floating point number

  12

  Out of memory

  13

  Unexpected error

Explanation

The database manager is trying to access the body of code that implements routine routine-name (specific name specific-name), and cannot access it for the reason given by reason code code (the codes are listed below). The file implementing the routine is identified by library-or-path, and the function by function-code-id.

The library name, path name, or the function name might be truncated due to a limit on the maximum available token length. The following query can be used to get the complete library path and function names from the system catalog views:

     SELECT implementation
     FROM syscat.routines
     WHERE specificname = 'specific-name'

1

Path name library-or-path is longer than the maximum (255 bytes).

2

The database manager instance path name could not be retrieved from DB2.

3

The path library-or-path could not be found.

4

The file in library-or-path could not be found, because of one of the following reasons:

1. The routine library associated with the routine is not available in the location specified by the EXTERNAL clause in the routine CREATE statement definition.
2. The routine library is dependent on a shared library that cannot be located (within the concatenation of directories specified in the LIBPATH environment variable in UNIX-based systems, or the PATH environment variable in Windows systems). There can be multiple levels of this indirection involved, leading to this reason code. For example, routine body X can be found, and it needs shared library Y which can also be found. But Y needs another shared library Z that cannot be located.
3. This is a partitioned database and the library is not located in one of the partitions on which the user-defined function was run.

5

There is insufficient memory to load the library containing the function or one or more symbols could not be resolved. This reason code indicates one of the following situations:

1. One or more symbols might not have been resolved. The routine library might be dependent on a shared library that cannot be located (using the concatenation of directories specified in the LIBPATH environment variable in UNIX-based systems, the PATH environment variable in INTEL systems).
2. The routine has a 64-bit library which is not supported within a 32-bit instance, or, the routine has a 32-bit library or DLL within a 64-bit instance that is incompatible with the routine definition.
3. There was insufficient memory to load the library containing the function.

6

The function function-code-id could not be found in the library that was named.

7

The symbol given as the function name (function-code-id) is not the name of a valid function in the named library.

8

The "load" system function has failed, for reasons other than those given in this message. The object file might not have been linked properly or not have been linked at all.

9

There was insufficient memory to resolve the function name function-code-id in the library identified in library-or-path.

10

The "loadquery" system call has failed. This can only happen on UNIX operating systems, and is a symptom that the database manager has not been installed correctly.

11

The agent process is searching for a particular database manager function that should be in the libdb2.a library, and it cannot find it. This can only happen on UNIX operating systems, and is a symptom that the database manager is not correctly installed.

15

System or network access has been denied. This can happen in Windows environments if the EXTERNAL NAME specification in the routine definition statement does not specify a full path, or the function does not exist in the directory called db2_installation_path\function, necessitating a search using the PATH environment variable. For example, if the PATH contains a LAN drive prior to the directory containing your function and the instance is running under the SYSTEM account, this reason code can result.

16

Multiple Java methods that could match the function function-code-id were found.

Other:

An unidentified system failure has occurred.

Federated system users: if this user defined function is a function template (and thus no code is required to reside on the federated server), consider modifying the SQL statement or statistics to enable this function to be evaluated on the remote data source.

Explanation

The value value was truncated when transformed in some way by a system (built-in) cast, adjustment, or codepage-conversion function. This is a warning situation.

The value being transformed may be one of:

• The output of a routine (user-defined function (UDF) or method), and is being transformed because of a CAST FROM specification in the routine definition.
• The output of a routine (user-defined function (UDF) or method) that is sourced on another function and the result needed to be transformed.
• The output of a built-in string processing routine that needed to perform codepage conversion during processing, for example, due to a string length unit specification.

Explanation

The clause keyword was included more than once in the statement. This is a warning condition.

Explanation

Too many parameters were specified when defining routine routine-name. The routine definition statement may be a CREATE FUNCTION, CREATE PROCEDURE, CREATE TYPE (method definition), or ALTER TYPE (method definition).

Explanation

An error was found in the EXTERNAL NAME clause of the CREATE statement for user defined function (UDF), user-defined method, or procedure routine-name. The rules for the library/function identification are as follows:

For all languages, no leading or trailing blank characters are permitted between the single quotes, object identifiers, or the separating characters (for example, ' <a> ! <b> ' is invalid). Path and file names, however, may contain blanks if the platform permits.

Explanation

This is not permitted.

This error will also be returned if the length field of the scratchpad is altered by the routine.

Explanation

An error was made in the data-item part of the statement defining routine routine-name. The user's statement contained the invalid type type, or it contained a user defined type (UDT) which is based on the invalid type type. The routine definition may be a CREATE FUNCTION, CREATE PROCEDURE, CREATE TYPE (method definition), or ALTER TYPE (method definition).

data-item is a token that identifies the area of the problem in the statement. For example, "PARAMETER 2" or "RETURNS" or "CAST FROM".

In an autonomous transaction, a block of statements within the transaction can be committed even if that transaction is rolled back. You can use the AUTONOMOUS keyword with the CREATE PROCEDURE command to create a procedure that will commit its work even if it is called from within a unit of work which is rolled back.

Explanation

Explanation

A problem casting the result of routine routine-name has been identified. The CAST FROM data type is not castable to the RETURNS data type, and it should be. See the SQL Reference for details on casting between data types.

Explanation

The signature of a function consists of the function name, the number of parameters defined for the function, and an ordered list of the types of the parameters.

The signature of a method consists of the method name, the subject type of the method, the number of parameters defined for the method, and an ordered list of the types of the parameters.

The signature of a procedure consists of the procedure name and the number of parameters defined for the procedure (data types are not considered).

This can occur when:

• There already is a function or procedure (routine-name) in the schema, module, or compound SQL (compiled) statement with the same signature as the function or procedure being created. If you are altering a module to add a routine body to a defined routine prototype, the routine already has a routine body definition.
• There already is a procedure (routine-name) in an outer compound SQL (compiled) statement with the same name as the procedure being declared.
• There already is a method (routine-name) for the subject type with the same signature as the method specification being added or the method body being created

The statement cannot be processed.

Explanation

If the SPECIFIC name is specified as a two part name, the schema-name1 portion must be the same as the schema-name2 portion of the routine-name. Note that the schema-name2 portion of routine-name may have been specified directly or it may have defaulted to the authorization ID of the statement. If the routine is a method, schema-name refers to the schema name of the subject type of the method.

Explanation

The user has supplied an explicit SPECIFIC name specific-name in the definition of routine routine-name, but this name already exists as the SPECIFIC name for a function, method, or procedure in the schema or module.

Explanation

  "=","<",">",">=","<=",
  "&=","&>",,"&<",
  "!=","!>","!<","<>",
  SOME, ANY, ALL, NOT, AND, OR,
  BETWEEN, NULL, LIKE, EXISTS, IN,
  UNIQUE, OVERLAPS, SIMILAR, and MATCH.

Explanation

In a reference to function, method, or stored procedure routine-name by signature, no matching function, method, or stored procedure could be found.

If a data type is used that can accept a parameter, then the type parameter is optional. For example, for CHAR(12), you can either specify the parameter (CHAR(12)) or omit it (CHAR()). If you specify the parameter, then the DBMS will only accept an exact match on the data type and the data type parameter. If you omit the parameter, then the DBMS will accept a match on data type only. The CHAR() syntax provides a way to tell the DBMS to ignore data type parameters when finding a matching function.

Note also that in the DROP FUNCTION/PROCEDURE, COMMENT ON FUNCTION/PROCEDURE and TRANSFER OWNERSHIP FUNCTION/PROCEDURE/METHOD statements, an unqualified reference is qualified with the statement authorization ID, and this is the schema where the problem can be found. In the SOURCE clause of a CREATE function, the qualification comes from the current path. In this case, there is no matching function in the entire path.

A function cannot be sourced on the COALESCE, DBPARTITIONNUM, GREATEST, HASHEDVALUE, LEAST, MAX (scalar), MIN (scalar), NULLIF, NVL, RID, RAISE_ERROR, TYPE_ID, TYPE_NAME, TYPE_SCHEMA, or VALUE built-in functions.

The statement cannot be processed.

Explanation

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.

Explanation

An SQLSTATE of the form 01Hxx was returned to DB2 by the command or routine command-or-routine-name (with specific name specific-name), along with message text text. If command-or-routine-name is a command, then specific-name will contain the value ''*N''.

Explanation

The valid SQLSTATEs that a routine can return are 38xxx (error), 38502 (error) and 01Hxx (warning). This routine routine-name (specific name specific-name) returned an invalid SQLSTATE state, along with message text text. The routine is in error.

Explanation

The stored procedure named by procedure-name completed normally. However, the stored procedure exceeded the defined limit on the number of query result sets the procedure can return.

generated-nbr-results

identifies the number of query result sets returned by the stored procedure.

max-nbr-results

identifies the defined limit on the number of query result sets for the stored procedure.

Only the first max-nbr-results query result sets are returned to the SQL program that issued the SQL CALL statement.

Explanation

There is a system related problem involved with the running of a fenced mode routine (user-defined function or method). The exact nature of the problem is indicated by code. This is NOT a user problem. Possible reason codes are:

Explanation

This message is returned as a result of issuing a CALL SQL statement. It indicates that the stored procedure procedure-name has number-results result sets associated with it.

The statement completed successfully.

Explanation

This message is returned as a result of closing a cursor. It indicates that another result set exists for stored procedure procedure-name and the cursor was re-opened on the next result set. There are a total of max-nbr-results result sets from the stored procedure.

The statement completed successfully.

Explanation

A parameter in an SQL procedure is declared as OUT and the corresponding argument is not a valid assignment target. For functions only, a parameter is declared as OUT or INOUT and the corresponding argument is not an SQL variable, global variable, or SQL parameter.

A constant or an expression is an example of an invalid argument for OUT or INOUT parameters.

For example, if a function named my_function was declared to have one OUT parameter, the following function call is not valid because the argument that is passed to the OUT parameter cannot have values assigned to it:

SET my_variable = my_function( 1 + 2 );

Explanation

A routine has an input argument with a null value but was defined with a parameter style that does not pass null indicators, or the data type of this parameter does not support null values.

Explanation

The invocation of routine name failed. Use reason code reason-code to find out more details about the cause of the failure.

Explanation

The function or method routine-name (specific name specific-name) did not close all its open cursors before the invoking statement completed. Functions and methods must close all cursors before the invoking statement completes.

Explanation

This message is returned when an attempt is made to either create a user-defined data type or to upgrade a database having a user-defined data type with a name that is the same name of a built-in data type.

Explanation

In order for the CREATE of a sourced user defined function (UDF) to be valid, the result type (type-1) of the source function must be castable to the RETURNS type (type-2) of the function being created. There is no supported cast between these data types. See the SQL Reference for details on casting between data types.

Explanation

References to a function or stored procedure without a signature is permitted, but the named function or store procedure function-name must be unique in its schema and is not. If the routine is a method, a reference without a signature is permitted but this named method must be unique for the data type.

Note that in the DROP FUNCTION/PROCEDURE and COMMENT ON FUNCTION/PROCEDURE statements, an unqualified reference is qualified with the statement authorization ID, and this is the schema where the problem can be found. In the SOURCE clause of a CREATE FUNCTION, the qualification comes from the current path. In this case, the first schema in the path containing a function with this name had other functions by the same name.

Federated system users: For a pass-through session, if the statement is a CREATE FUNCTION MAPPING statement, this error indicates that an attempt was made to create a function mapping from one remote function to more than one local function.

Explanation

When object B is said to be dependent on object A, actions taken on object A could significantly affect object B. For example, when you drop a table any objects that are directly or indirectly dependent on that table could be either deleted or made inoperative. Because of these possible outcomes for dependent objects, some types of actions fail if there are dependencies on the object that is target of the action.

This message is returned when an attempt to drop, alter, transfer ownership of, or revoke privileges on a target object fails because other objects directly or indirectly depend on that target object.

Examples of scenarios in which this message can be returned:

• If object-type1 is ALIAS, the dependencies for DROP might include a row permission or a column mask which references this alias.
• If object-type1 is SYNONYM, the dependencies for DROP might include a row permission or a column mask which references this synonym.
• If object-type1 is VIEW, the dependencies for DROP might include a row permission or a column mask which references this view.
• If object-type1 is TABLE:
  • Dependencies for DROP might include a row permission or a column mask which references this table.
  • A system-period temporal table might exist that uses this table as the corresponding history table.
  • If object-type2 is INDEX, there might be an expression-based index that depends on the columns of the table.
• If object-type1 is TABLESPACE, a system-period temporal table might exist for which the corresponding history table resides in this table space.
• For a DB2 for z/OS server, if object-type1 is DATABASE, a system-period temporal table might exist for which the corresponding history table resides in this database.

Explanation

Either the procedure identified in an ASSOCIATE LOCATORS statement has not yet been called within the application process, or the procedure has been called, but an explicit or implicit commit occurred before the statement.

Explanation

where GEL represents the element shown as grouping-expression-list in the syntax diagram of the GROUP BY clause.

In some instances the value “---” will be shown for element 2. In this case “---” represents one of CUBE, ROLLUP, GROUPING SETS, or GEL.

The statement cannot be processed.

Explanation

Explanation

One or more of the data types in the statement is BINARY or VARBINARY. This is not supported in the current version of DB2.

Explanation

The program used to implement the body of a routine is not allowed to execute SQL statements. This routine routine-name (specific name specific-name) contains SQL statements or this routine calls a procedure that uses SQL statements, such as the SYSPROC.ADMIN_CMD procedure.

Explanation

The function function-name is defined for use as a predicate, returning a boolean result. Such a result is not valid in a select list.

The statement cannot be processed.

Explanation

A number (number) was specified that is not valid in the context in which it was specified. The minimum allowed value in this context is minval. The maximum allowed value in this context is maxval. n must be within the range specified by minval and maxval (minval =< n => maxval).

If creating or altering a table space, the minimum and maximum values may be dependant on the page size of the table space. Refer to the SQL Reference for more details on table space limits.

Explanation

A required clause is missing in the definition of routine routine-name. If EXTERNAL was specified, one of the following clauses must also be specified: LANGUAGE, PARAMETER STYLE.

If defining an SQL function, the SQL function body must be included unless using the PUBLISH action of ALTER MODULE to define an SQL function prototype.

Explanation

The parameter in position number of function function-name is in error and the CREATE cannot be performed. The parameter in position number of the source function is not castable to the corresponding parameter of the function being created.

Explanation

The body of user defined function (UDF) or method routine-name (specific name specific-name) has returned an invalid date, time or timestamp value.

An example of a syntactically invalid date value is '1994-12*25': the '*' should be a '-'. An example of a numerically invalid time value is '11.71.22': there is no 71st minute in the hour.

Explanation

The number of result set locators specified on the ASSOCIATE LOCATORS statement is less than the number of result sets returned by the stored procedure. The first “n” result set locator values are returned, where “n” is the number of result set locator variables specified on the SQL statement.

The SQL statement is successful. The SQLWARN3 field is set to 'Z'.

Explanation

The prepare of a dynamic INSERT, UPDATE, DELETE, or SELECT SQL statement resulted in a cost estimate that exceeded the error threshold value specified in the resource limit specification table (RLST).

The prepare of the dynamic INSERT, UPDATE, DELETE, or SELECT statement was unsuccessful.

Explanation

An attempt was made to assign a cursor to a result set but multiple cursors have been allocated for procedure procedure-name.