Explanation

The result can be invalid or inconsistent data, or a subset of the expected data.

These are the runtime tokens:

operation-name

The type of processing, such as INSERT.

table-name

The name of the table for which the action was attempted.

table-type

Identifies whether the table is a Hadoop table or an HBase table.

log-entry-ID

The log-entry-identifier is composed of three parts:

• A three-letter prefix that indicates which log file includes diagnostic details.
• A three-digit number that indicates on which database partition the log file resides.
• An identifier that is printed in the log file near the related diagnostic details.

For example, the operation might be INSERT into an HBase table. You can load multiple files of HBase data into an HBase table with one INSERT statement. However, the insert operation is not atomic and cannot be rolled back. So, if an error occurs while the data is being loaded, some data is left in the table. If the table contains indexes, it is possible that the indexes might be out of synchronization with the data in the table.

Explanation

A database partition group must contain at least one node that can be used in a partition map. If a node is added to a database partition group WITHOUT TABLESPACES, it cannot be included in the partition map because there are no containers for the table spaces defined on the database partition group. If a node is added LIKE another node and the other node does not have containers for all table spaces on the database partition group then neither node can be included in the partition map.

Explanation

The database partition group IBMTEMPGROUP can be specified if and only if the table space is a system temporary table space.

Explanation

A database partition must have containers defined for all the system temporary table spaces defined in the database partition group IBMTEMPGROUP for this database before it can be included in a database partition group.

Explanation

All the table spaces specified in the CREATE TABLE statement must belong to the same database partition group.

Explanation

All the table spaces in a database partition group must have containers defined on all the database partitions. Otherwise, that database partition should not be included in a redistribution of a database parititon group or in a LIKE DBPARTITIONNUM clause of the ALTER DATABASE PARTITION GROUP statement.

Explanation

For the CREATE TABLESPACE, the USING clause without the ON DBPARTITIONNUMS clause can only be specified once.

For the ALTER TABLESPACE, the ADD clause without the ON DBPARTITIONNUMS clause can only be specified once.

The statement was not processed.

Explanation

In CREATE TABLESPACE statement, every USING clause specifies the ON DATABASE PARTITION clause. However not all the database partitions in the database partition group are included, and therefore not all database partitions in the database partition group have containers.

The statement is not processed.

Explanation

The ALTER TABLESPACE and CREATE TABLESPACE statement includes container specification for all the database partition in the database partition group. The specification of the containers that is not followed by an ON DATABASE PARTITION clause is redundant and has been ignored.

The statement has been processed.

Explanation

This warning indicates that a change being made using the ALTER DATABASE PARTITION or ALTER TABLESPACE statements has not caused the partitioning map for the database partition group to be changed. The partitioning map for a database partition group is only changed immediately by these statements if there are no tables defined using any table space defined in the database partition group or the database partition being dropped is not in the partitioning map.

This warning is issued in the following cases:

• One or more database partitions are added using ALTER DATABASE PARTITION ADD DATABASE PARTITION
• One or more database partitions are dropped using ALTER DATABASE PARTITION DROP DATABASE PARTITION
• Containers are added for table space and no further containers are required for a database partition to be used.

For all of these cases, a table is already defined using a table space in the database partition group.

Explanation

A required clause is missing in the CREATE PROCEDURE or ALTER MODULE statement used to define procedure procedure-name. LANGUAGE clause, EXTERNAL clause, and PARAMETER STYLE clause must be specified. An external procedure defined in a module must be completely specified since only SQL procedures allow prototypes to be published.

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

Explanation

The database partition group for the table space has not been defined for the buffer pool. The table space cannot be created or altered to use this combination of database partition group and buffer pool.

The statement cannot be processed.

Explanation

There is not enough disk space to allocate active log files. Possible reasons include:

• There is insufficient space available on the device used to store the recovery logs.
• If userexits are enabled, the userexit program may be failing due to an incorrect path, incorrect install directory, sharing violation, or other problem.
• If log archiving is enabled, the log archiving method may not be functioning or the target might be inaccessible.

Explanation

The clauses specified in the ALTER TABLESPACE statement cannot be used in conjunction with each other.

1

The CONVERT TO LARGE clause must be specified by itself.

2

The BEGIN NEW STRIPE SET container clause cannot be specified with any other container clauses (ADD, DROP, EXTEND, REDUCE or RESIZE).

3

When adding or removing space from the table space:

1. EXTEND and RESIZE can be used in the same statement, provided that the size of each container is increasing.
2. REDUCE and RESIZE can be used in the same statement, provided that the size of each container is decreasing.
3. EXTEND and REDUCE cannot be used in the same statement, unless they are being directed to different database partitions.
4. ADD cannot be used with REDUCE or DROP in the same statement, unless they are being directed to different database partitions.
5. DROP cannot be used with EXTEND or ADD in the same statement, unless they are being directed to different database partitions.

4

A container clause cannot be used in conjunction with the REDUCE option when altering automatic storage managed table spaces.

5

A container clause must be specified when altering nonautomatic storage managed table spaces.

6

Temporary table spaces and system-managed table spaces (SMS) cannot be converted to use automatic storage.

7

There are no storage groups in the database.

8

Database-managed table spaces (DMS) that have DEVICE containers cannot be converted to use automatic storage using the ALTER TABLESPACE statement.

9

The REBALANCE clause must be specified by itself.

10

The REDUCE MAX clause or the REDUCE with a specified size clause can only be used with table spaces having the Reclaimable Storage attribute and managed by automatic storage.

11

Table spaces without the Reclaimable Storage attribute cannot use clauses to reduce or lower the high water mark.

12

The REDUCE option with the MAX, numeric value, PERCENT, or STOP clauses, and the LOWER HIGH WATER MARK option including the STOP clause, must be specified and run without any other options, including each other.

13

The ADD, DROP, RESIZE, EXTEND, REDUCE, LOWER HIGH WATER MARK, and BEGIN_STRIPE_SET clauses cannot be used in conjunction with the MANAGED BY AUTOMATIC STORAGE clause or the USING STOGROUP clause.

14

The USING STOGROUP clause cannot be specified when altering an automatic storage hybrid table space.

Explanation

The size specified in an ALTER TABLESPACE statement using the RESIZE action is smaller than the current size of the table space container. You can only increase the size of a container.

Explanation

When HADR is enabled, it is recommended that the database configuration parameter LOGINDEXBUILD is set to ON, and the database or database manager configuration parameter INDEXREC is set to either RESTART or ACCESS. Otherwise, any index creation, recreation, or reorganization on the current or future primary database server may not be recovered on the current or future secondary database server using HADR. Those indexes which cannot be recovered will be marked as invalid and will be rebuilt implicitly either at the end of the HADR takeover process or after the HADR takeover process when indexes are to be accessed.

Explanation

If the database configuration parameter LOGINDEXBUILD is not set to ON before HADR is started, any index creation, recreate, or reorganization on the current or future primary database server may not be recovered on the current or future secondary database server using HADR.

Explanation

Start HADR cannot complete. The explanation corresponding to the reason code is:

1

The database was not in roll forward-pending or roll forward-in-progress state when the START HADR AS STANDBY command was issued.

2

START HADR AS PRIMARY cannot be issued on an HADR standby database.

3

START HADR AS STANDBY cannot be issued on an active database.

9

Database upgrade is in progress on an active HADR standby.

98

A valid HADR license is not installed. The command did not complete successfully.

99

The command was issued in a multi-partition instance environment.

Explanation

The explanation corresponding to the reason code is:

1

The database is not recoverable because circular logging is in use.

2

The database has infinite active logging enabled.

3

The database has DATALINKS enabled.

4

Invalid entry for the hadr_local_host configuration parameter.

5

Invalid service name for the hadr_local_svc configuration parameter.

6

Invalid service name for the hadr_remote_svc configuration parameter.

7

The primary database failed to establish a connection to its standby database within the HADR timeout interval. There are multiple scenarios that can cause this error condition. For example, this message can be returned with reason code 7 if the value of the hadr_timeout configuration parameter or the hadr_peer_window configuration parameter on the primary database is not the same as the value on the standby database.

8

The value of one or more of the following HADR database configuration parameters is NULL:

• hadr_local_host or hadr_local_svc
• hadr_remote_host, hadr_remote_svc, or hadr_remote_inst in an environment other than DB2 pureScale.
• hadr_target_list in a DB2 pureScale environment.

9

The database is configured to use raw logs. However, HADR does not support the use of raw I/O (direct disk access) for database log files.

10

The command was interrupted by HADR shutdown due to a STOP HADR command, deactivation of the database, or an internal error.

11

The entries specified by the hadr_remote_host, hadr_local_host, or hadr_target_list configuration parameter do not resolve to the same IP format.

12

Invalid entry for the hadr_remote_host configuration parameter.

13

An HADR standby database cannot start without at least one regular buffer pool. A buffer pool could not be started due to insufficient memory.

14

The entries for the hadr_target_list configuration parameter do not contain the pair specified in the hadr_remote_host and hadr_remote_svc configuration parameters.

15

An entry for the hadr_target_list configuration parameter cannot be resolved into a valid TCP/IP address.

16

The entries specified for the hadr_target_list configuration parameter are not in the correct format.

17

The hadr_replay_delay configuration parameter can only be set to a non-zero value if the hadr_syncmode configuration parameter is SUPERASYNC.

18

The hadr_replay_delay configuration parameter can only be set to 0 on a HADR primary database.

19

Cannot start as primary database because another primary database is detected.

20

The hadr_syncmode database configuration parameter cannot be SYNC or NEARSYNC in a DB2 pureScale environment.

21

The value specified by the hadr_local_svc configuration parameter conflicts with client/server communication ports.

22

The value specified by the hadr_local_svc configuration parameter conflicts with fast communication manager (FCM) communication ports.

23

The value specified by the hadr_local_svc configuration parameter conflicts with cluster caching facility (CF) communication ports.

24

Failed to allocate TCP socket buffer specified by DB2 registry variable DB2_HADR_SOSNDBUF.

25

Failed to allocate TCP socket buffer specified by DB2 registry variable DB2_HADR_SORCVBUF.

26

A table space is not available.

27

The hadr_peer_window database configuration parameter is not set to 0 in a DB2 pureScale environment.

28

SSL communication failed between the primary database and the standby database. Possible reasons for failure are:

1. The database configuration parameter HADR_SSL_LABEL is set to an invalid certificate name
2. The SSL_SVR_KEYDB configuration parameter or the SSL_SVR_STASH configuration parameter is not set to a valid value.

29

The hadr_syncmode database configuration is not set to SYNC or NEARSYNC when automated failover is enabled.

98

A valid HADR license is not installed. The command did not complete successfully.

99

An internal error occurred during HADR startup.

Explanation

The explanation corresponding to the reason code is:

1

The command was issued on a standard database.

2

The command was issued on an active HADR standby database.

3

The command was interrupted by HADR shutdown due to a STOP HADR command, deactivation of the database, or an internal error.

98

A valid HADR license is not installed. The command did not complete successfully.

99

The command was issued in a multi-partition instance environment.

Explanation

The TAKEOVER HADR command failed. The explanation corresponding to the reason code is:

1

An unforced takeover (role switch) can be performed only when the HADR standby database is in one of the following states:

• peer state
• remote catchup state with SUPERASYNC mode.
• in assisted remote catchup (applicable only in a DB2 pureScale environment)

2

The HADR standby database attempted a forced takeover. Forced takeover is not allowed when any log stream is in local catchup state.

3

The standby was created from an online backup, and takeover was attempted before the standby had replayed through to the end point of that backup in the log.

4

The command was issued against a standard or HADR primary database.

5

The command was issued against an inactive standby database.

6

An error occurred while switching the primary database to a standby database.

7

A communication error occurred during takeover.

8

The attempted takeover failed because a conflicting command (START HADR, STOP HADR, ACTIVATE DATABASE, or DEACTIVATE DATABASE) or an internal error was encountered on either the primary or the standby database.

9

The HADR standby database attempted a forced takeover with the PEER WINDOW ONLY command parameter specified. The takeover failed because the standby database was not in a peer window when it attempted the forced takeover. Either a peer window is not configured on the standby database, or the forced takeover was attempted outside any peer window that is configured on the standby database.

10

The TAKEOVER HADR command was run in a DB2 high availability environment. The cluster manager returned an error that prevented the takeover operation from completing. The takeover operation failed. The DB2 high availability disaster recovery (HADR) databases that were involved in the takeover operation remain in the state they were in before the takeover operation was attempted.

11

A takeover (either forced or unforced) is not allowed on an HADR standby that has replay delay enabled.

12

The HADR standby database attempted an unforced takeover (role switch). In a DB2 pureScale environment, unforced takeover is not allowed when any member on the primary is in member crash recovery (MCR) pending or in-progress state.

15

A takeover (either forced or unforced) is not allowed on an HADR standby that is upgrade in progress.

98

A valid HADR license is not installed. The command did not complete successfully.

99

The command was issued in a multi-partition instance environment.

Explanation

Circular logging cannot be used on a database in HADR primary or standby role. HADR requires recoverable databases.

Explanation

Infinite active logging cannot be enabled on a database in either HADR primary or standby role.

Explanation

The statement or command failed. The explanation corresponding to the reason code is:

1

An isolation level other than UR is used and the DB2_STANDBY_ISO registry variable is turned off.

2

The query attempted to access an invalid index.

3

An attempt was made to execute a query against a read-enabled HADR standby database and there is one of the following problems with the query:

• The query attempted to use a data types which cannot be used in queries against a read-enabled HADR standby database.
• The query attempted to use a LOB or XML value that is not stored as inline data in the database table.

4

The query attempted to access a created or declared temporary table.

5

A write operation was attempted on an HADR standby database.

6

The operation attempted an implicit rebind on an HADR standby database.

7

An attempt was made to query a column-organized table on an HADR standby database.

8

An attempt was made to execute the SET INTEGRITY statement on an HADR standby database.

Explanation

Table space level restore or rollforward on either an HADR primary or HADR standby database is not allowed.

Explanation

The separator that is used in the TERMINATED BY clause can be specified only as a single byte ASCII character. The specified separator, separator-char, contains more than one character, or consists of a multi-byte unicode character.

Explanation

The explanation corresponding to the reason code is:

1

The command is not supported on an HADR standby database.

2

Connection requests are not allowed while an HADR database is switching roles on takeover.

3

The UPGRADE DATABASE command is not supported on an HADR standby database.

4

Connection requests to an HADR standby database are not allowed while the replay-only window is active. The replay-only window is active when DDL or maintenance operations are being replayed on the standby.

5

Connection requests to an HADR standby are not allowed until the standby reaches the highest replay log position of a previous standby activation.

6

This database is an old primary database. It cannot be started because the standby has become the new primary through forced takeover.

7

The command cannot be processed while the standby replay is being restarted on the DB2 pureScale cluster.

9

Connection requests to an HADR standby are not allowed while database upgrade is in progress.

Explanation

This error occurs when the START HADR command is issued on a database which is already running in the desired role.

Explanation

The runtime token name represents the SQL column or the HBase column mapping name.

The reason-code is a numeric value that indicates the reason for the error:

1

The SQL column ''<name>'' is not mapped to an HBase column. All SQL columns must be specified in the HBase COLUMN MAPPING clause.

2

The SQL column ''<name>'' is mapped in multiple HBase COLUMN MAPPING clauses. You cannot specify the same SQL column in more than one HBase COLUMN MAPPING clause.

3

The HBase key or column qualifier name was provided multiple times in the COLUMN MAPPING clause

4

The KEY column mapping was not specified in the CREATE TABLE(HBASE) statement. You cannot create an HBase table without specifying a row key.

Explanation

The Java class class-name that is specified in the class-type or in reference to a class, cannot be located.

The class-type indicates the context of the class, such as SERDE, INPUTFORMAT, OUTPUTFORMAT, or STORAGE HANDLER.

The log identifier in the token log-entry-id is composed of three parts:

• A three-letter prefix that indicates which log file includes diagnostic details.
• A three-digit number that indicates on which database partition the log file resides.
• An identifier that is printed in the log file near the related diagnostic details.

Explanation

A code page is a mapping that determines how characters are represented internally. Collation determines how characters are compared (for the purposes of sorting or merging, for example.) The code page and collation of a database are set when the database is created and cannot be changed.

For some code pages and collations, some functionality is restricted.

This message is returned when an attempt is made to create a table that uses functionality that is not supported with the database code page and collation.

Explanation

The keystore configuration file is parsed in order to setup the database manager instance with a keystore.

This message is returned when an error occurs while parsing the keystore configuration file for one of the following reasons:

1

A line in the configuration file is invalid.

2

A line in the configuration file is too long.

3

An EOF condition was encountered in the configuration file.

4

The configuration file could not be opened.

5

The configuration file could not be read.

6

A parameter in the configuration file is missing or not set.

7

A parameter in the configuration file has an invalid value. When this message is returned with reason code 7, the name of the parameter is included in the runtime token value.

8

A parameter in the configuration file is conflicting with another parameter. When this message is returned with reason code 8, the names of the parameters are included in the runtime token value.

Explanation

DB2 native encryption stores encryption keys in a centralized key manager when the KEYSTORE_TYPE database manager configuration parameter is KMIP. To use this functionality, you must perform the following set-up and configuration tasks:

1. Configure a centralized key manager for storing encryption objects, such as secret keys.
2. Configure SSL between the DB2 server and the centralized key manager.
3. Create a centralized key manager configuration file.
4. Configure the DB2 database manager to use the centralized key manager configuration file by setting encryption configuration parameters, such as KEYSTORE_TYPE and KEYSTORE_LOCATION.

This message is returned when the database manager fails to connect to the centralized key manager or an error is returned from the centralized key manager while performing one of several types of operations:

• Creating an encrypted database
• Creating an encrypted backup image of a database
• Restoring an encrypted backup image
• Issuing a DB2 command, such as db2cklog, against an encrypted database

The reason code indicates more specifically the reason for the failure:

1

Automatic creation of a new master key and master key label is not allowed.

2

The centralized key manager configuration file specified in the KEYSTORE_LOCATION database manager configuration parameter does not exist.

3

No password was given (the password required to open the SSL keystore is not stashed and no password was provided with the command.)

4

The given password (the password that is stashed or that was provided with the command) is not valid to access the SSL keystore file.

5

An SSL error was encountered. When this message is returned with reason code 5, the ssl-error is included in the runtime token value.

6

An authentication error was encountered from the centralized key manager.

7

An authorization error was encountered from the centralized key manager.

8

A KMIP error was encountered from the centralized key manager.

Explanation

DB2 native encryption stores encryption keys in a PKCS #11 key manager when the KEYSTORE_TYPE database manager configuration parameter is PKCS11. To use this functionality, you must perform the following set-up and configuration tasks:

1. Configure a PKCS #11 key manager for storing encryption objects, such as secret keys.
2. Configure a PKCS #11 vendor library to access the PKCS #11 key manager.
3. Create a PKCS #11 keystore configuration file.
4. Configure the DB2 database manager to use the PKCS #11 keystore configuration file by setting encryption configuration parameters, such as KEYSTORE_TYPE and KEYSTORE_LOCATION.

This message is returned when the database manager fails to connect to the PKCS #11 key manager or an error is returned from the PKCS #11 key manager while performing one of several types of operations:

• Creating an encrypted database
• Creating an encrypted backup image of a database
• Restoring an encrypted backup image
• Issuing a DB2 command, such as db2cklog, against an encrypted database

The reason code indicates more specifically the reason for the failure:

1

The PKCS #11 keystore configuration file specified in the KEYSTORE_LOCATION database manager configuration parameter does not exist.

2

No password was given (the password required to access the PKCS #11 keystore is not stashed and no password was provided with the command.)

3

The given password (the password that is stashed or that was provided with the command) is not valid to access the PKCS #11 keystore.

4

The given password (the password that is stashed or that was provided with the command) is locked.

5

The given password (the password that is stashed or that was provided with the command) is expired.

6

The given password (the password that is stashed or that was provided with the command) is not initialized.

7

An unexpected error was encountered from the PKCS #11 key manager. The error is included in the runtime token value.

8

The PKCS #11 vendor library specified in the PKCS #11 keystore configuration file can not be loaded.

9

The provided master key label already exists in the PKCS #11 keystore.

10

Multiple objects with the same label exist in the PKCS #11 keystore.

11

The PKCS #11 keystore is write-protected.

12

There are no slots available in the PKCS #11 keystore.

13

The PKCS #11 slot specified by slot label or slot ID was not found.

14

The user is not authorized to perform the command or operation in the PKCS #11 keystore.

Explanation

This message is returned in the following scenario:

1. You are using database software at a certain version and fix pack level, code level B, and while running you modify database object X.
2. You fall back to an earlier code level A.
3. While running on code level A, you try to access object X.

The database object that is encountering the code level problem is listed in the runtime token object-name. The runtime tokens marker1 and marker2 are for use by IBM support, if necessary.

Explanation

You can use index extensions to specify how the database manager indexes user-defined data types. You create index extensions by issuing the CREATE INDEX EXTENSION statement. When creating an index on a table that contains user-defined data types, you can specify an index extension to manage the index by including the EXTEND USING clause in the CREATE INDEX statement. An index that uses an index extension is often referred to as an extended index.

This message is returned when a statement accesses a table that contains an extended index that was created before the current database product level was applied.

Explanation

The member or CF failed to start due to an incorrectly configured /var/ct/cfg/netmon.cf file.

Explanation

The procedure NNSTAT was not able to create the SYSPROC.FED_STATS table to keep a history of the statement that was run. The table space with sufficient page size (at least pagesize) could not be found.

Explanation

The procedure NNSTAT accepts a server definition, schema, and nickname as input and one or more of these objects could not be found.

Explanation

The remote schema has changed. Either the remote table or view, or one of its columns or the column data types have changed since the nickname was created.

Explanation

The pointer to structure sqle_request_info passed as a parameter to the catalog admin command/api was invalid. For Client Configuration Assistance request this pointer must not be NULL.

Explanation

The specified request type is not supported for this command.

Explanation

There is no entry in the node directory that is catalogued by the given request type.

Explanation

An attempt to modify a package has been made that is disallowed. This could occur for one of two reasons.

1. The package is a CLI dynamic SQL package (package schema is NULLID and package name begins with SYSSH, SYSSN, SYSLH, SYSLN) and the operation(rebind, drop or invalidation of the package) is not allowed if there is another application currently in a unit of work that is using the package.
2. The database manager is currently operating in "No Package Lock" mode. This mode has been activated by setting the DB2_APM_PERFORMANCE registry environment variable to "ON".

In No Package Lock mode, the following classes of operations are prevented from being executed because of their impact on packages:

• An operation that invalidates packages.
• An operation that makes a package inoperative.
• Binding, rebinding (explicitly or implicitly) or dropping a package.

Since the requested operation would affect the package pkgschema.pkgname_0Xcontoken in one of these ways, the operation is disallowed.

Explanation

You can configure a federated data source to work with ODBC drivers that only support one active statement on a connection by setting the DB2_ONE_REQUEST_PER_CONNECTION server option to 'Y'. In general, if you are using a ODBC driver that supports more than one active statement on a connection, the DB2_ONE_REQUEST_PER_CONNECTION server option should not be set at all, or should be set to 'N'.

This message is returned when an attempt is made to execute multiple statements on one connection against a federated data source for which the DB2_ONE_REQUEST_PER_CONNECTION server option has been set to 'Y'.

Explanation

A nickname is an identifier that an application uses to reference a data source object, such as a table or view. In a federated environment, to refer to objects that are in the federated system but not in the federated database itself you must use nicknames or three-part names.

There are some restrictions on the use of nicknames in insert, update, or delete operations in federated environments. These restrictions include the following examples:

• An INSERT, UPDATE, or DELETE statement that is nested in a subclause of a larger SQL statement cannot reference a nickname.
• An SQL procedure that performs insert, update, or delete operations cannot reference a nickname.
• Insert, update, or delete operations in the body of a trigger cannot reference a nickname.

This message is returned when an attempt is made to use a nickname in an insert, update, or delete operation in one of these ways that are not supported.

Explanation

There are multiple components in the X/Open Distributed Transaction Processing (DTP) model for two-phase commit transaction:

• Transaction identifiers
• Transaction managers
• Resource managers

In federated systems there is an additional component:

• The federated server becomes a federated transaction manager

The federated transaction manager performs some transaction management functions on behalf of the transaction manager, and communicates with the transaction manager using an XA interface. A federated transaction manager receives two-phase commit requests in from the client or transaction manager and sends federated two-phase commit requests out to federated data sources.

This message is returned when one federated server, B, receives a federated two-phase commit request from another federated server, A, and federated server B must send a federated two-phase commit request to a data source C.

Explanation

Different federated data sources support different SQL statement syntax. This message is returned when an attempt is made to use SQL syntax or an SQL clause that is not supported by the specified federated data source, or which is incompatible with the current configuration of the the specified federated data source.

This message can be returned for the following reasons:

• An attempt was made to execute an SQL statement that includes the DEFAULT keyword for a value against a federated data source that does not support executing that SQL statement with the DEFAULT keyword in its query language syntax.
• An attempt was made to open an updatable cursor with a federated data source which was configured to disallow insert, update, or delete operations. Specifically, a statement that contains the FOR UPDATE OF clause is executed against a data source for which the DB2_IUD_ENABLE server option is set to 'N'.

Explanation

An access plan specifies an order of operations for accessing data necessary to resolve an explainable statement. The query optimizer produces an access plan whenever an explainable SQL or XQuery statement is compiled.

This message is returned when the optimizer has produced an invalid access plan for a federated environment. The reason code indicates what aspect of the access plan is invalid:

1

A part of the predicate cannot be found.

2

The statement includes a positioned update operation or a positioned delete operation. A positioned update or delete operation is an update or delete operation that modifies the data of a result set. Positioned update and delete operations require cursors to be used.

3

An element cannot be found in the columns of a nickname.

This information about what is invalid about the access plan is useful for IBM support personnel only.

Explanation

Performing insert, update, or delete operations referencing a nickname or federated three-part name is not supported on local database partitions.

This message is returned when an attempt is made to open an updatable cursor on the result set of an SQL statement that uses a trusted wrapper to query a table on a local database partition.

Explanation

In a federated environment, many factors affect whether parts of an SQL statement are evaluated locally or remotely, including the following examples:

• Sometimes parts of a SQL statement are executed locally instead of remotely because the query optimizer determines that it is more efficient to do so.
• Other times, parts of a SQL statement are executed locally because they cannot be evaluated at the remote data source. For example:
  • A statement would have to be evaluated locally if an expression in the statement contains a function or syntax that is not supported by the remote data source.
  • An INSERT statement with a VALUES clause and an UPDATE statement with a SET clause must both be evaluated locally.

This message is returned in the following cases:

• An attempt is made to execute a positioned update on a result set of a query that references tables at the federated data source, but an expression in the query can only be evaluated locally.
• An attempt is made to execute a statement that contains some elements that can only be evaluated locally and some elements that can only be evaluated remotely.

Explanation

When issuing a CREATE NICKNAME statement, the federated server defines a local data type for each column or field in that remote data source object. To improve the performance of query processing, the remote column length remote-column-length of column column-name is reduced to column-length. Truncation can occur when the remote table contains long value which exceeding column-length bytes.

Explanation

You cannot create nicknames for remote tables that have XML data type columns when the Database Partitioning Feature is enabled.

Explanation

The wrapper that you specified does not support the type or version of data source that you want to define.

Explanation

When a CREATE SERVER statement references the wrapper that you specified, it must also identify the type-or-version of data source that is to be defined to the federated database.

Explanation

The ALTER SERVER statement is preceded in a unit of work by a SELECT statement that references a nickname for a table or view within the data source (or category of data sources) that the ALTER SERVER statement references.

Explanation

The DROP SERVER statement is preceded in a unit of work by a SELECT statement that references a nickname for a table or view within the data source (or category of data sources) that the DROP SERVER statement references.

Explanation

Explanation

The LOB value was evaluated on a deferred retrieval basis. The LOB value may have changed between the time it was first accessed and when it was actually retrieved.

Explanation

While referencing a data source, the federated server received an unexpected error code from the data source that does not map to a DB2 equivalent.

This error might also be returned if the data source is not available.

Explanation

An attempt was made to create a nickname for an object. One or more columns of that object are of a type currently unknown to the federated server. The name of (one of) the unknown type(s) is listed in the message.

Explanation

A nickname can refer to a remote base table, a remote view, a remote alias/synonym, or a remote nickname. If two operands of a UNION ALL view refer to different nicknames, they may potentially be pointing to the same table (if not both of them are known to be remote base tables). This message is issued to warn the user that potentially one remote base table can get updated/deleted twice via updates/deletes through two operands.

Explanation

Some restrictions apply to using INSERT, UPDATE, or DELETE statements in a federated system.

The reason code indicates the particular reason this message was returned:

1

An attempt was made to insert, update, or delete LOB data through a federated database.

2

An attempt was made to execute an insert, update, or delete operation against a view, which was created with the UNION ALL clause.

Explanation

An invalid value value was specified for a column column-name in a system catalog object object-name.

The statement cannot be processed.

Explanation

An attempt was made to drop or alter a user mapping that is not defined.

Explanation

An attempt was made to drop or alter a server option that is not defined.

Explanation

An unknown warning warning-code occurred at the data source server-name. The tokens for the message are tokens.

Explanation

The RETURNS clause is not specified before the PREDICATE clause that includes the EXPRESSION AS clause. The RETURNS clause may have been included after the predicate specification or may be missing.

The statement cannot be processed.

Explanation

The statement attempts to update the statistics values of NPAGES, FPAGES, or OVERFLOW, for table subtable-name, that is defined as a subtable. For typed tables, these statistics can only be updated using the root table of the table hierarchy.

The statement cannot be processed.

Explanation

The routine (function or method) routine-name is specified in a FILTER clause for a user defined predicate specification or an index extension definition. The routine can not be defined with LANGUAGE SQL.

The statement cannot be processed.

Explanation

The Extended Search Wrapper tried to connect to the remote Extended Search Server host_name on port port_number but the connection could not be established or was terminated by the remote Server.

Explanation

A CREATE NICKNAME statement or ALTER NICKNAME statement contains a user-defined column which has the same name as a fixed column for Wrapper Wrapper_name but uses a different data type.

Explanation

Extended Search object object_name of type object_type could not be found on the remote Extended Search Server es_host_name.

Explanation

None of the data sources specified in option DATASOURCE or in option CATEGORY contains a field name identical to the user-defined column column_name.

Explanation

Some options are required for federation. The option cannot be dropped.

Explanation

The Extended Search wrapper attempted to process the listed search statement, however the query failed because the syntax is incorrect.

Explanation

The Extended Search wrapper tried to use the specified search parameters, but they are not valid for Extended Search.

Explanation

The option cannot be added. Some options are set by the object and cannot be added or overridden by you.

Explanation

The option value cannot be changed. Some options are set by the object and cannot be added or overridden by you.

Explanation

The syntax of the specified option is not valid or the option cannot be set to the specified value. The reason code provides more information about the error. The reason codes are:

01

Unexpected character.

02

Element or attribute name expected but not found.

03

Min/max occurrence expected after reference.

04

More than one colon found in an attribute name.

05

Min/max occurrence is not an integer value.

06

Min/max occurrence out of range.

07

Min occurrence greater than max occurrence.

08

Reference in column template option was not "column".

09

'=' delimiter missing from namespace specification.

10

Opening or closing quotation mark missing from namespace specification.

11

Duplicate reference in template.

12

The wrapper option option-name is not allowed when the database manager instance is 32-bit.

13

The two wrapper options or option values are not compatible. The wrapper option option-name is only valid when "DB2_FENCED" is set to "Y".

14

The wrapper option option-name is not supported on this particular platform.

15

The wrapper cannot be loaded into the DB2 threaded engine on this particular platform as it is not threadsafe.

16

The minimum valid value for the wait-time parameter is 1000 microseconds.

Explanation

Some data sources restrict the operators that can be specified with nickname columns.

Explanation

Characters were truncated when data was transferred between a remote data source and the federated server. Truncation can occur in many situations. Some of these situations include an incorrect nickname column definition (a column is too small for the remote data source column data), or the presence of a conversion or type-cast function that restricts the size of the data returned by the remote data source.

Explanation

You have specified two or more incompatible options or option values.

Explanation

While building an XML document a wrapper encountered a problem substituting values into a template. This may be caused by conflicts between templates at the nickname and column level. The reason codes are:

01

Reference name not found in template. The additional text identifies the missing reference.

02

Cannot substitute an attribute reference with element content. The additional text identifies the reference in error.

Explanation

The table spaces specified are not compatible for one of the following reasons:

1

All table spaces (data, long, index) for a partitioned table must be in the same database partition group.

2

The data table spaces for a partitioned table must be either all SMS, all regular DMS, or all large DMS. The index table spaces for a partitioned index must be all regular DMS or all large DMS.

3

The page size for all data table spaces must be the same. The page size for all index table spaces must be the same. The page size for all long table spaces must be the same. However, the page sizes of data table spaces, index table spaces, and long table spaces can be different from each other.

4

The extent size for each data table space must be the same as the extent sizes of other data table spaces. The extent size for each index table spaces must be the same as the extent sizes of other index table spaces. The extent sizes for all table space used storing long data must also be the same. However, the extent sizes of table spaces used for different purposes do not need to match.

5

Long data for a partitioned table must be stored in the same table space as the data for all data partitions or it must be stored in large table spaces, each of which is distinct from the table space of the corresponding data partition. This error will occur if a LONG IN clause is used that specifies a table space that is different from the data table space but is not a large table space. LONG IN can only be used to specify regular table spaces if they are identical to the data table spaces (i.e. in the case where the LONG IN clause is redundant because it merely specifies the data table spaces, which is the same as the default behavior if LONG IN were omitted entirely).

Explanation

A row could not be inserted into a range-clustered table because the key sequence values fall outside the defined range.

Explanation

Certain functions are not available on range-clustered tables. Reason codes:

1

VALUE COMPRESSION and COMPRESS SYSTEM DEFAULT are not available.

2

A clustering index cannot be created on a range clustered tables.

3

Adding a column is not supported.

4

SET DATA TYPE is not supported.

5

Changing PCTFREE is not supported.

6

Changing APPEND mode is not supported.

7

Column attributes cannot be changed.

8

Typed tables are not supported.

10

The following commands are not supported on a database partition group that was used to define a table space containing a range-clustered table: ALTER TABLESPACE, REDISTRIBUTE DATABASE PARTITION GROUP.

11

The LOAD utility is not supported.

12

Table Reorganization is not supported.

13

Table Truncate is not supported.

14

Columns of type XML cannot be used.

15

COMPRESS YES is not supported.

17

This reason code is returned when an attempt is made to create a range-clustered table in a partitioned database environment and there is a problem with the relationship between the distribution key and the sequence key specified in the CREATE TABLE statement. The problem is: the distribution key, specified with the DISTRIBUTE BY HASH clause, is not a single column subset of the columns of the sequence key, specified with the ORGANIZE BY KEY SEQUENCE clause.

The following examples illustrate this relationship between the distribution key and the sequence key:

Example 1: the distribution key is a single column subset of the sequence key.

CREATE TABLE ...
  ORGANIZE BY KEY SEQUENCE (colA, colB) 
    ... DISTRIBUTE BY HASH (colA)

Example 2 (error): the distribution key is not a single column subset of the sequence key.

CREATE TABLE ...
  ORGANIZE BY KEY SEQUENCE (colA, colB) 
    ... DISTRIBUTE BY HASH (colC)

18

This reason code is returned when an attempt is made to create a range-clustered, materialized query table, and the DISALLOW OVERFLOW clause is specified in the CREATE TABLE STATEMENT. It is not possible to prevent records that have key values that fall outside the defined range from being inserted into range-clustered, materialize query tables.

19

Random distribution tables are not supported.

Explanation

The cursor cursor-name accessing a nickname using wrapper wrapper-name at the federated data source server-name was declared using the option option-name of type option-type, but either the wrapper or the data source itself does not support this option.

The cursor cannot be opened.

Explanation

You can configure a federated server by specifying options with the CREATE SERVER statement, the ALTER SERVER statement, or the SET SERVER statement. Some federated server options are valid for all data sources, while some federated server options are valid for only a few data sources.

This message is returned when an invalid server option is specified. A server option could be invalid for different reasons, including the following example reasons:

• The specified option might not exist
• The specified option might be invalid for the type of data source
• The specified option might be invalid for the particular data source
• The specified option might be invalid for the database object

Explanation

The value that you specified either lacks the proper delimiters or is invalid.

Explanation

You did not specify an option that DB2 requires in order to process the statement that you submitted.

Explanation

You entered a statement that references the same option multiple times.

Explanation

You entered a value for an option that already has a value.

Explanation

You tried to change or delete a value for an option that has not been defined for the data source, data source type, or database object that you're working with.

Explanation

A CREATE INDEX statement for a nickname must have a SPECIFICATION ONLY clause.

Explanation

The port number as specified on the Update Alternate Server command is not valid. The value is either not numeric or its length is not valid. The value must be 1 to 14 characters in length and cannot be all blanks.

Explanation

The request can only be applied to a database server.

Explanation

The host name as specified on the Update Alternate Server command is not valid. The value must be at least 1 to 255 characters in length and cannot be all blanks.

Explanation

The application program used an address that is not valid for the host name parameter. Either the address points to an unallocated buffer or the character string in the buffer does not have a null terminator.

The command cannot be processed.

Explanation

The application program used an address that is not valid for the port number parameter. Either the address points to an unallocated buffer or the character string in the buffer does not have a null terminator.

The command cannot be processed.

Explanation

The command line utility successfully completed the command.

Explanation

The command line utility could not process the command.