Explanation

An instance of the database manager has already had at least one database created where an XML object, such as a table with a column of data type XML or a XML schema repository object, was created. Even if the XML objects no longer exist, the database manager instance is still considered to have used XML. Once the database manager instance is known to have used XML in this way, the instance is no longer permitted to have more than a single database partition. Any attempt to add a database partition will return this error.

Explanation

There are no indoubt transactions in the database, nor any transactions that have ended and are waiting to enter the syncpoint process.

Explanation

Explanation

Explanation

The data type of the parameter that was specified for the procedure is not supported by either the federated server or the data source that was accessed.

Explanation

The value for SQL data access (NO SQL, CONTAINS SQL, READS SQL DATA, or MODIFIES SQL DATA), determinism (DETERMINISTIC or NOT DETERMINISTIC), or external action (EXTERNAL ACTION or NO EXTERNAL ACTION) specified in the CREATE PROCEDURE (Sourced) statement does not match the corresponding option of the source procedure.

Explanation

The federated procedure was created successfully but the package body for the source procedure procedure-name at the data source was not found or is invalid.

Explanation

The data source requires a predicate that uses the indicated column. Either the predicate is not in the query, or the predicate is in the query but was not made available to the data source wrapper during query compilation.

Explanation

In order for the SYSTOOLSPACE and SYSTOOLSTMPSPACE table spaces to be created, they must be defined in the IBMCATGROUP database partition group.

Explanation

An SQL error occurred while attempting to issue the ARCHIVE LOG command for database db-name on database partition partition-list.

Explanation

The specified database is not configured for roll-forward recovery on the specified node(s). If ",..." is displayed at the end of the node list, see the administration notification log for the complete list of nodes.

The database is not rolled forward on the specified node(s).

(Note : if you are using a partitioned database server, the node number(s) indicate which node(s) the error occurred on. Otherwise, it is not pertinent and should be ignored.)

Explanation

The specified database is not in roll-forward pending state on the specified node(s). This may be because the database has not been restored, or was restored with the WITHOUT ROLLING FORWARD option, or roll-forward recovery is complete on these nodes.

If ",..." is displayed at the end of the node list, see the administration notification log for the complete list of nodes.

The database is not rolled forward.

(Note : if you are using a partitioned database server, the node number(s) indicate which node(s) the error occurred on. Otherwise, it is not pertinent and should be ignored.)

Explanation

The timestamp parameter specified for the point-in-time stopping value is not valid. The timestamp must be entered in ISO format (YYYY-MM-DD-hh.mm.ss.<ssssss> where YYYY represents year, MM represents month, DD represents day, hh represents hours, mm represents minutes, ss represents seconds, and ssssss represents optional microseconds).

The database is not rolled forward.

Explanation

The specified archive log file exists in the database log directory or the overflow log directory on the specified database partition, but the file is not valid.

Rollforward recovery processing stops.

(Note: If you are using a partitioned database server, the database partition number indicates the database partition on which the error occurred. Otherwise, this value is not pertinent and should be ignored.)

Explanation

The specified archive log file was found in the log directory or the overflow log directory but does not belong to the specified database.

Rollforward recovery processing stops.

(Note: If you are using a partitioned database server, the database partition number indicates the database partition on which the error occurred. Otherwise, this value is not pertinent and should be ignored.)

Explanation

For rollforward recovery, log files must be processed in correct sequence. The log file sequence is determined by the database that has been restored or by the log files that have been processed. For table space-level rollforward recovery, moreover, the log files must be processed in the sequence through which the current state of the database was reached. The specified archive log file was found in the log directory or the overflow log path for the database on the specified database partition, but the log file is not in the correct log sequence.

Rollforward recovery processing stops.

(Note: If you are using a partitioned database server, the database partition number indicates the database partition on which the error occurred. Otherwise, this value is not pertinent and should be ignored.)

Explanation

When a rollforward operation fails, is interrupted, or finishes but does not include the STOP or COMPLETE option, you must continue the rollforward operation by calling the ROLLFORWARD command, or the db2Rollforward API, again. However, a rollforward cannot be continued to a point in time that is earlier than the point-in-time value that was specified for the previous rollforward operation.

This message is returned when a rollforward operation is a continuation of a previous rollforward operation that did not complete and the previous rollforward operation was to a point in time that is later than the point in time specified for this rollforward operation. When continuing a rollforward operation that was to a point in time, the new rollforward must be one of the following:

• a rollforward to the same point in time
• a rollforward to a later point in time
• a rollforward to the end of logs

This error can happen with both database and table space rollforward operations.

When this error occurs, rollforward processing stops.

Explanation

The database is configured for log archiving, and a log file was archived with an integrity verification failure. This log file will not be usable if it is required by a database recovery operation, such as Restore, Rollforward or other operations which may require archived log file data. In addition, the db2ReadLog API or other tools which read log file data will not be able to process this log file.

An integrity verification failure occurs when the database engine's verification checking finds a problem with the log before it is archived. Detailed information related to the verification checking failure is written to the db2 diagnostic log file (db2diag.log).

Explanation

Rollforward processing is unable to retrieve a required log file. This error is sometimes returned because the target system to which you are attempting to restore the backup image does not have access to the facility being used by the source system to archive its transaction logs.

(Note: If you are using a partitioned database server, the database partition number indicates the database partition on which the error occurred. Otherwise, this value is not pertinent and should be ignored.)

Explanation

An attempt has been made to use table space level roll-forward recovery but it is already running. Only one agent can be executing roll-forward recovery at any given time.

Explanation

The LANG environmental variable is set to a language that is not supported by the database manager. Processing cannot continue.

Explanation

This message can occur after crash recovery, database level roll-forward recovery, or table space level roll-forward recovery. For database level roll-forward recovery, the database is available for use if the STOP option was specified. One or more table spaces on the specified members or nodes are not available. This could happen if:

• One or more table spaces receive I/O errors during recovery.
• One or more table spaces may require storage definition following recovery.
• One of more table spaces are unusable and must be dropped.
• One or more table spaces have been taken offline.
• Additional table spaces are restored while a table space level roll-forward recovery is already in progress.
• The database is rolled forward past a previous point-in-time table space roll-forward, causing all table spaces involved to be placed in restore pending state.

The table spaces that are offline can be identified on the specified members or nodes by the MON_GET_TABLESPACE table function. In environments other than DB2 pureScale environments, the db2dart utility can also be used. The administration notification log will provide more information on specific table spaces.

If ",..." is displayed at the end of the member or node list, see the administration notification log for the complete list of member or nodes.

Note: The member or node numbers provide useful information only in DB2 pureScale environments and partitioned database environments. Otherwise, the information should be ignored.

Explanation

Table space level roll-forward recovery has stopped on the specified members or nodes before all qualifying table spaces could be rolled forward.

This message can be returned for the following types of reasons:

• The transaction table is full.
• All table spaces being rolled forward received I/O errors.
• Point-in-time table space level roll-forward encountered an I/O error on one of the table spaces being rolled forward.
• Point-in-time table space level roll-forward encountered an active transaction that made changes to one of the table spaces being rolled forward. This transaction could be an indoubt transaction.
• The table space level roll-forward was interrupted and, before it was resumed, all table spaces that were being rolled forward are restored again.
• The table space rollforward state information has become corrupted or been lost.
• A lock timeout or deadlock occurred.

If ",..." is displayed at the end of the member or node list, see the administration notification log for the complete list of members or nodes.

Note: The member or node numbers provide useful information only in DB2 pureScale environments and partitioned database environments. Otherwise, the information should be ignored.

Explanation

The operation cannot find the specified log file in the archive, database log directory, or overflow log directory for the given log stream. The operation reading the logs has been stopped. This operation was either a recovery operation, a rollforward operation, a call to the db2ReadLog API, or any other operation that requires access to the transaction logs.

If the operation was a crash recovery, the database is left in an inconsistent state. If the operation was a rollforward operation, the operation has stopped and the database is left in rollforward pending state.

Explanation

The database needs to be rolled forward. For database level roll-forward recovery, the point-in-time must be to the end of logs because a database level roll-forward to end of logs is already in progress. To continue the roll forward, the same stoptime must be specified.

The database is not rolled forward.

Explanation

The stop time passed to the rollforward utility must be greater than or equal to the time the backup ended on the specified nodes.

If ",..." is displayed at the end of the node list, see the administration notification log for the complete list of nodes.

(Note: If you are using a partitioned database server, the node number or numbers indicate which nodes the error occurred on. Otherwise, it is not pertinent and should be ignored.)

Explanation

A request was made to bring the database or subset of table spaces out of rollforward pending state by specifying caller action SQLUM_ROLLFWD_STOP, SQLUM_STOP, SQLUM_ROLLFWD_COMPLETE, or SQLUM_COMPLETE. However, the database or at least one of the table spaces to be rolled forward was backed up online. The request cannot be granted until the database or all table spaces have been rolled forward to the end of the online backup timestamp on the specified node.

This error can also occur if not all the log files are provided to perform the requested recovery.

(Note : if you are using a partitioned database server, the node number indicates which node the error occurred on. Otherwise, it is not pertinent and should be ignored.)

Explanation

The Restore utility validates that the containers needed by each table space being restored are currently accessible on the system. Where possible, the Restore utility will create the containers if they do not exist. If they cannot be created, are currently in use by another table space, or are inaccessible for any other reason, then the list of containers needed must be corrected before the restore operation can continue.

In a redirected restore, the state of each container of a non-automatic storage table space being restored is set to "storage must be defined". This makes it possible to use the SET TABLESPACE CONTAINERS command or API against the containers to redefine their storage.

For table spaces using automatic storage, the only way to redefine container paths is to use the SET STOGROUP PATHS command for a specific storage group or the ON keyword when you issue the RESTORE DATABASE command to redefine all the storage groups paths. You cannot use the SET TABLESPACE CONTAINERS command or API against automatic storage table spaces.

Explanation

An error occurred during index recreation while performing a database restart or following a table reorganization which may have prevented some of the indexes from being recreated successfully. Details can be found in administration notification log.

Database restart or Reorg table was successful.

Explanation

At least one of the table spaces specified by the roll-forward to point in time has already been rolled forward to an earlier point in time. It cannot be rolled forward any further.

Explanation

The connection was lost because the database server broke the pipe. The current transaction has been rolled back.

Explanation

Attempts to connect to the named pipe failed because the connection was refused by DB2. There is a limit to the number of connections that are allowed on the named pipe.

Explanation

The name of the named pipe is already in used by another process. Named pipe support did not start.

Explanation

The server has not started its named pipe support, or the server is using a different name for the named pipe.

Explanation

The alternate pipe name set by the environment variable DB2PIPENAME is invalid.

Explanation

Named pipe failed because the operating system ran out of resources (swapping space, disk space, file handles). The current transaction has been rolled back.

Explanation

The server has not started its named pipe support, or the instance name is incorrect.

Explanation

The remote server is running on a 64-bit platform that does not support non-SQL requests from Version 7 (or earlier) 32-bit clients.

Explanation

The input to function-name passed to the code page conversion function contains a byte sequence that is not a valid character in the input code page, from-code-page. Each invalid byte sequence was replaced with the substitute character when converting to to-code-page. The inserted substitute character may or may not be included in the final result. If an invalid byte sequence appears at the end of the input, it is omitted from the result rather than replaced with a substitute character.

If function-name is *N, the invalid byte sequence was encountered while the input value was being converted to code page 1232 for internal processing.

Explanation

Either an incorrect value was specified or the protocol(s) specified are not supported by the target database. The acceptable values are:

• Unix platforms: TCPIP and APPC
• Windows: TCPIP, APPC (Windows 32-bit only), and NPIPE

If more than one value is specified, then they must be delimited by a comma.

Note that this message may be returned from an intermediate node involved in your connection. For example, if you are trying to connect to a DRDA server via a DB2 Connect gateway and your client workstation does not use global directory services, this message may be returned from the DB2 Connect gateway.

Explanation

An error has been detected by the directory services subsystem. Refer to the token values for details. The following is the explanation of the token values:

directory-services-type

The type of the directory services being used. Valid tokens include:

• DCE

API

The application programming interface used to access the listed directory services. Valid tokens include:

• XDS/XOM

function

The name of the directory services subsystem function that returned the error code.

rc

The error code returned from the indicated function. The meaning of the value is specific to the API being used.

For XDS functions such as ds_read, the return code values can be found in the DCE include file xds.h.

For XOM functions such as om_get, the return code values can be found in the DCE include file xom.h.

Note that this message may be returned from an intermediate node involved in your connection. For example, if you are trying to connect to a DRDA server via a DB2 Connect gateway and your client workstation does not use global directory services, this message may be returned from the DB2 Connect gateway.

Explanation

The global name of the database or database manager instance cannot be NULL and cannot be longer than 255 characters. It must start with either "/.../" or "/.:/".

Note that this message may be returned from an intermediate node involved in your connection. For example, if you are trying to connect to a DRDA server via a DB2 Connect gateway and your client workstation does not use global directory services, this message may be returned from the DB2 Connect gateway.

Explanation

An error has been detected in one of the global database directory entries used. Refer to the following error codes for details:

1

The database object does not contain authentication information

2

Both the database object and the database locator object do not contain communication protocol information

10

Entry not a database object

11

Native database name in the database object is either not found or too long

12

Database protocol in the database object is either not found or too long

13

Invalid authentication value found in the database object

14

Insufficient or invalid communication protocol information in the database object

15

Database locator object name not found in the database object

16

Database locator object name in the database object invalid

20

Entry not a database locator object

22

Insufficient or invalid communication protocol information in the database locator object

30

Entry not a routing information object

31

Target database information not found in the routing information object

32

Insufficient information for the target database in the routing information object

33

No appropriate gateway found in the routing information object

34

Invalid flag for authentication at gateway

35

Database locator object name for the gateway invalid

36

Database name in the target database information attribute of the routing information object is either not found or too long

37

Database protocol in the target database information attribute of the routing information object is either not found or too long

Note that you may also see this message if the DCE subsystem is not operational, or if you do not have sufficient privilege to read the DCE directory entry.

Note that this message may be returned from an intermediate node involved in your connection. For example, if you are trying to connect to a DRDA server via a DB2 Connect gateway and your client workstation does not use global directory services, this message may be returned from the DB2 Connect gateway.

Explanation

In order to use global directory services, a directory path name must be specified either in the dir_path_name database manager configuration parameter, or in the DB2DIRPATHNAME environment variable. You either did not specify it, or the name you specified is not valid.

Note that this message may be returned from an intermediate node involved in your connection. For example, if you are trying to connect to a DRDA server via a DB2 Connect gateway and your client workstation does not use global directory services, this message may be returned from the DB2 Connect gateway.

Explanation

In order to use global directory services to access a remote database with a database protocol that is not native to this client, the name of a routing information object must be specified either in the route_obj_name database manager configuration parameter, or in the DB2ROUTE environment variable. You either did not specify it, or the name you specified is not valid.

Note that this message may be returned from an intermediate node involved in your connection. For example, if you are trying to connect to a DRDA server via a DB2 Connect gateway and your client workstation does not use global directory services, this message may be returned from the DB2 Connect gateway.

Explanation

Explanation

The function requested using this command is not supported on this platform.

Explanation

The DCE principal name in the catalog database operation was invalid. DCE principal names are subject to the following conditions:

• If AUTHENTICATION is specified as DCE, a principal name must be included in the catalog statement.
• If AUTHENTICATION is not specified as DCE, a principal name can not be included in the catalog statement.
• The maximum length of the principal name is 1024 bytes.

Explanation

Explanation

An error occurred when mapping a DCE principal to a DB2 authorization id. Refer to the following reason codes:

1

Missing or invalid DCE user to DB2 authorization id mapping.

2

Missing or invalid DCE group to DB2 authorization id mapping.

Explanation

An attempt to restart the security daemon has failed after communication between the agents and the security daemon was severed or the security daemon terminated abnormally. All new connections to the database manager will be rejected, as authentication is not possible.

Explanation

The TCP/IP security type SOCKS in the TCP/IP protocol structure of the Catalog Node command is invalid with authentication type DCE.

Explanation

Database manager processing failed due to an internal DCE error.

Explanation

Explanation

The invocation of the security audit API caused an error to occur. Reasons:

1. Audit is already started.
2. Audit is already stopped.
3. Invalid checksum for audit configuration file.
4. The default or user-provided audit pathname is too long.
5. Could not update the audit configuration file. Either the filesystem is full or the permissions do not allow write.
6. Configuration File not found. Either the file or the directory which contains the file does not exist.
7. The extract file is not found.
8. Invalid format of audit records during extract. The file is corrupted.
9. The file does not exist.
10. Access to the file is denied due to file permissions.
11. The active audit log has already been archived and new events can not be logged to it.
12. Out of disk space (disk full).
13. File I/O error during Extract or Archive.
14. Extract can not be performed on the active audit log file.

Explanation

The security audit extract facility completed its processing succesfully and extracted the specified number of records.

Explanation

The server principal name specified in the database catalog statement does not exist in the DCE registry. Because of this a DCE ticket could not be obtained for the database server.

Explanation

The Database Connection Services Directory Service failed because of file errors while trying to access the Database Connection Services directory file.

The function cannot be processed.

Explanation

The directory cannot be found. The directory may have been deleted.

The function cannot be processed.

Explanation

An attempt was made to read the contents of the Database Connection Services directory, but no entries existed.

Processing continues, but subsequent commands expecting entries to be available cannot be processed.

Explanation

The entry cannot be added to the Database Connection Services directory because the directory has already reached its maximum size.

The function cannot be processed.

Explanation

The application program has used an address for this parameter that is not valid. Either the address points to an unallocated buffer or the buffer is not large enough to contain the required input.

The function cannot be processed.

Explanation

A local database name was specified that contains characters that are not valid. All characters must be from the database manager base character set.

The function cannot be processed.

Explanation

The Database Connection Services directory service failed because no entry could be found in the Database Connection Services directory that corresponds to the input local database name.

The function cannot be processed.

Explanation

The entry could not be added to the directory because an entry for that local database name already exists in the directory.

The function cannot be processed.

Explanation

The length values in the Database Connection Services directory entry structure should not be less than zero nor greater than the maximum length for the element it represents.

The function cannot be processed.

Explanation

A request to copy all the directory entries was received, but either a prior request to collect the entries was not received or the prior request to collect the entries failed.

The function cannot be processed.

Explanation

A request to access the Database Connection Services directory failed. Access to the Database Connection Services directory is dependent on the type of access requested and the current activity in the directory. If the request is for the intention of updating the directory, then the directory must not be active. If the request is to read the directory, then access is allowed if the directory is not being updated.

The function cannot be processed.

Explanation

The structure ID received in the directory entry structure does not represent a recognized value.

The function cannot be processed.

Explanation

The database audit facility encountered an error when invoked to record an audit event to the trail. There is no space on the file system the audit log resides on. Free up space on this file system or prune the audit log to reduce its size.

Explanation

Explanation

Explanation

An attempt has been made to issue a DB2 workstation database specific command or command option against a host database through DB2 Connect or federated server. The following commands generate this error when issued against a DB2 for MVS*, DB2 for OS/400* or SQL/DS* database:

• OPSTAT (Collect Operational Status)
• GETAA (Get Administrative Authorizations)
• GETTA (Get Table Authorizations)
• PREREORG (Prepare to Reorganize Table)
• REORG (Call Reorganize Function)
• RQSVPT/ENSVPT/RLBSVPT (Subtransaction Requests)
• RUNSTATS (Run Statistics).
• COMPOUND SQL ATOMIC STATIC (Atomic Compound SQL)
• ACTIVATE DATABASE
• DEACTIVATE DATABASE

As well, the following commands generate this error with incorrect options:

• IMPORT (Import table) The filetype must be IXF, commitcount must be 0 for offline import or must not be automatic for online import, and the first word in the Action String (for example, "REPLACE into ...") must be INSERT.
• EXPORT (Export table) The filetype must be IXF.

The command cannot be processed.

Explanation

The file or directory name cannot be accessed because either the file permissions are incorrect, the file path is incorrect, or there is insufficient space in the directory or path.

If you are using a cluster manager, this error can be returned if the database manager failed to add the given path to the cluster manager configuration. Error messages from the cluster manager will be recorded in the db2diag log file.

Explanation

An attempt to perform an implicit connection failed. The syntax of the database alias name specified by the DB2DBDFT environment variable is not valid. The database name must contain 1 to 8 bytes and all the characters must be from the database manager base character set.

The command cannot be processed.

Explanation

An attempt to perform an implicit connection failed. The database name specified by the DB2DBDFT environment variable does not name an existing database. The database could not be found in the database directory.

The command cannot be processed.

Note that a CONNECT RESET request issued within a distributed unit of work will attempt an implicit connect to the default database. This may be the reason for this error.

Explanation

The resolved path specified on the command exceeds the maximum length supported by the database manager. The resolved path must be no longer than 215 characters in length. During a Create Database, Catalog Database, Open Database Directory for scan, and change database comment commands, the database manager instance name is appended to the end of the specified path.

Explanation

The symbolic destination name in the CPIC protocol structure of the Catalog Node command is either not specified or longer than the allowable length. The name must be 1 to 8 bytes in length.

Explanation

The CPIC security type specified in the CPIC protocol structure of the Catalog Node command is invalid. The security type specifies the security information that will be included when a database client allocates a conversation with a partner LU, as specified by the LU 6.2 architecture. Correct values for security type are:

SQL_CPIC_SECURITY_NONE

No access security information will be included.

Note: This is not supported when using federated server. When DB2 Connect is used, it is only supported when authentication type is DCE, KERBEROS, or SERVER_ENCRYPT.

SQL_CPIC_SECURITY_SAME

A userid will be included together with an indicator specifying that the userid is already verified. This is not supported when authentication type SERVER is used with DB2 Connect or federated server, or when authentication type is DCE, KERBEROS, or SERVER_ENCRYPT.

SQL_CPIC_SECURITY_PROGRAM

Both a userid and a password will be included. This is not supported when authentication type CLIENT is used with DB2 Connect or when authentication type is DCE, KERBEROS,or SERVER_ENCRYPT.

Explanation

The host name in the TCP/IP protocol structure of the Catalog Node command is either not specified or longer than the allowable length. The name must be 1 to 255 characters in length and cannot be all blanks.

Explanation

The service name is the TCP/IP protocol structure of the Catalog Node command is either not specified or longer than the allowable length. The name must be 1 to 14 characters in length and cannot be all blanks.

Explanation

An attempt was made to route a request through a database server node or DB2 Connect server node using an unsupported combination of client and target database server, or from a non-LUW DRDA client to a DRDA target database through a LUW database server or DB2 Connect server. The request must be routed directly from the client to the node on which the target database is running.

Explanation

An application requestor name was specified that contains characters that are not valid. All characters must be from the database manager base character set.

Explanation

The system cannot resolve the address of the remote host. Possible causes are:

• An incorrect hostname value was specified when the TCP/IP node was cataloged.
• The correct hostname was specified, but was not defined in any TCP/IP name server accessible to your client node, nor in the client's hosts file.
• The TCP/IP name server where the hostname was defined was not available at the time you tried to connect.
• TCP/IP is not running.
• The remote host was cataloged on this client using the CATALOG TCPIP6 NODE command. However, the remote host does not support IPv6.

Explanation

Federated system users: this situation can also be detected by the data source.

Explanation

Explanation

One or more SQL substatements within a Compound SQL statement resulted in SQL errors (negative return codes).

The error tokens will not be returned for CLI/ODBC applications. CLI/ODBC applications can use SQLGetDiagRec, SQLGetDiagField, or SQLError APIs to get more information about each error.

Explanation

Explanation

A workstation name has not been specified in the client database manager configuration file.

Explanation

The File Server name specified in the command/API is missing or invalid.

Explanation

The Object Name specified in the command/API is missing or invalid.

Explanation

One or more system catalogs contain orphan rows that can cause a database upgrade to fail.

Explanation

A cluster manager error occurred that prevented successful processing of the current environment command or SQL statement. The error occurred at execution time.

The command or statement cannot be processed. The current transaction is not rolled back and the application remains connected to the database.

Explanation

The table space size could not be reduced any further because no free space exists above the table space high water mark.

Explanation

Explanation

No FCM channels are available. FCM is unable to increase the number of channels automatically because the maximum value has been reached.

The statement cannot be processed.

Explanation

An attempt to reuse a connection failed because the connection was in a transaction. The connection is now in an unconnected state.

Explanation

Transparent DDL statements create objects at a data source. Certain column options that can be specified for objects created at the federated server are not supported via transparent DDL statements. The specific column option specified for column column-name is indicated by the reason-code as follows:

1. lob-options
2. unique-constraint, referential-constraint, or check-constraint
3. default-clause
4. generated-column-spec (not including the default-clause)

The statement cannot be processed.

Explanation

During the execution of routine routine-name an attempt was made to reference an SQL variable or SQL parameter of data type XML that cannot be referenced because a recent commit or rollback operation has caused its value to no longer be available.

Referencing variables or parameters of data type XML in SQL procedures after a commit or rollback operation occurs without first assigning new values to these variables is not supported.

Explanation

Explanation

The ALTER TABLE ... DETACH PARTITION statement cannot be processed. The data partition has been attached within the same unit of work (UOW) and so the table has a pending modification to be made.

Explanation

The data type you specified is an invalid type mapping or an unsupported data type.

Explanation

More than 65533 instances of this cursor have been opened since the first instance was opened at this nesting level.

Explanation

An interrupt request was received during switch user processing. The switch user request did not complete and the connection has been placed in the unconnected state.

Explanation

The user attempted to interrupt a process which is not interruptible.

Explanation

If a command takes longer than a pre-defined timeout period, a dialog box pops up asking if the (Windows client) user wants to interrupt it or not.

Note that this message is applicable in Windows environments only, and will only be seen in a dialog pop up box.

Explanation

Some changes to the database manager configuration could not be applied immediately. For these parameters, the changes become effective only after the database manager is started. This typically occurs after a DB2START on a server and after the application restarts on a client.

Explanation

The database configuration command has been successfully processed. However, not all changes were processed right away.

Changes to database configuration parameters can only take effect dynamically if you are connected to the database. Not all configuration parameters support dynamic update, meaning that they will not take effect until the database is deactivated and reactivated.

Explanation

One or more of the configuration parameters were set to AUTOMATIC in a case where the parameter does not support AUTOMATIC.

Explanation

Processing failed for the server side security plug-in plugin-name. The explanation corresponding to the reason-code is:

1

Security plug-in not found.

2

Unable to load the security plug-in.

3

More than one Kerberos security plug-in is specified in the SRVCON_GSSPLUGIN_LIST database manager configuration parameter.

4

No Kerberos based security plug-in is found and Kerberos is specified in the SRVCON_AUTH or AUTHENTICATION database manager configuration parameter.

5

Required API is missing in the security plug-in.

6

Wrong security plug-in type.

7

Error encountered during unloading of the security plug-in.

8

Invalid security plug-in name.

9

The version of the APIs reported by the security plug-in is not compatible with DB2.

10

Security plug-in encountered an unexpected error on the database server

11

The SRVCON_GSSPLUGIN_LIST database manager configuration parameter is not set and GSSPLUGIN or GSS_SERVER_ENCRYPT is specified in the SRVCON_AUTH or AUTHENTICATION database manager configuration parameter.

12

The communication exit library name in the database manager configuration parameter COMM_EXIT_LIST is invalid.

13

The communication exit library can not be found.

14

The communication exit library can not be loaded.

15

The communication exit library is missing a required API.

16

The communication exit library encountered an error when loading.

17

The version of the APIs reported by the communication exit library is not compatible with DB2.

Explanation

Explanation

Resource policy does not support the current operating system configuration.

Explanation

The resource policy file is invalid.

Explanation

The current XML document is invalid.

Explanation

An attempt was made to quiesce an instance or database which would have caused an overlapping quiesce, such as quiescing an instance while a database is already quiesced by another user.

Quiesce type type refers to the instance or database already quiesced and is a '1' for an instance and a '2' for a database.

Explanation

Before performing maintenance activities, you can force users off of a database manager instance or database by quiescing the instance or database.

This message is returned when an attempt is made to quiesce an instance or database which is already quiesced.

Explanation

An attempt was made to quiesce a database or instance while the user issuing the quiesce has uncompleted units of work. Quiesce cannot be issued while in this state.

Explanation

Unquiesce failed because the instance or database is not quiesced.

Explanation

The instance or database is quiesced, but you are not the quiescer.

Explanation

The value may be out of range or invalid.

Explanation

The sourced procedure cannot be created or invoked using a wrapper defined as fenced.

Explanation

The sourced procedure cannot be created or altered at this data source.

Explanation

This redistribute operation completed successfully, however the database partition group is only partially redistributed. As a result, redistributed tables in the database partition group could use a different partitioning map than tables that have not been redistributed. Also, if collocation between redistributed and non-redistributed tables existed before the redistribute operation, the collocation property between these tables is temporarily disabled. Query performance may not be optimal.

Reason codes:

1

The redistribute request specified a table list, which did not include all the tables in the specified database partition group. As a result, other tables in the database partition group, which were not listed in the request, are not redistributed.

2

The STOP AT parameter was specified with the redistribute request, and the value was reached before the redistribute operation completed.

Explanation

An unexpected Kerberos security error occurred during authentication.

Explanation

Authentication failed because the Security Support Provider Interface (SSPI) was not available.

Explanation

Authentication failed because Kerberos support is not installed.

Explanation

The target principal name that was specified in the CATALOG DATABASE command is not valid.

Explanation

The connection failed because either the client or server was unable to complete mutual authentication.

Explanation

The parameter named in the error message is invalid, incorrectly specified, or is incompatible with one of the other redistribute options specified.

Reason codes:

1

An invalid redistribution option was specified. The distribution option can be one of "U" (Uniform), "T" (Target map), "C" (Continue), or "A" (Abort).

2

The maximum number of partition numbers in a partition list must be less than or equal to the maximum number of partitions allowable in a cluster.

3

Invalid STOP AT parameter value. The STOP AT value must be ISO format, with a length of 26. The format must be "yyyy.mm.dd.hh-mm-ss-nnnnnn".

7

Invalid STATISTICS parameter value. The value must be either DB2REDIST_STAT_USE_PROFILE ('P') or DB2REDIST_STAT_NONE ('N').

8

The length of a table name is out of range. The maximum length of the name of each table is (SQL_MAX_IDENT + SQL_MAX_IDENT +2).

9

Invalid table option parameter. The table option value must be either DB2REDIST_TABLES_FIRST ('F') or DB2REDIST_TABLES_ONLY ('O').

10

Missing information from input parameter struct. Input struct db2RedistStruct can not be NULL. Also its field struct db2RedistIn can not be NULL.

11

Undefined database partition group name, or bad struct db2Char to database partition group name. Database partition group name must be provided. Struct db2Char which stores the database partition group name must have valid data. Check struct db2Char to database partition group name. When pioData is NULL, iLength has to be zero and vice versa.

12

The structure db2Char that is storing data distribution file name is not valid.

13

The structure db2Char that is storing target partition map file name is not valid.

14

The redistribute option 'T'(target map) was specified, but no target map file is specified.

15

When the redistribute option is 'T'(Target map) or 'A' (Abort), a data distribution file should not be specified.

16

When the redistribute option is 'U'(Uniform), 'C'(Continue) or 'A' (Abort), the target map file should not bespecified.

17

When the redistribute option is 'T'(Target map), 'C'(Continue) or 'A' (Abort), the add partition list, drop partition list should be empty, and the add count and the drop count should be zero.

18

Redistribute options may not be specified more than once.

19

Wrong version number is passed into the API.

20

A typed table specified in the TABLE list is not the root table of the whole hierarchy.

21

Invalid DATA BUFFER parameter value. The value must be greater than 0, and less than the size of util_heap_sz db cfg parameter.

Explanation

A HADR takeover completed successfully, and the cluster manager should now take over responsibility for managing the resource groups on the affected cluster nodes again.

However, the database manager failed to return control of a resource group to the cluster manager. As a result, the cluster manager is not currently controlling that resource group.

If the cluster manager is not controlling this resource group, the cluster manager will not respond to any failures related to that resource group.

Error messages from the cluster manager will be recorded in the db2diag log file.

Explanation

An error occurred when trying to access one or more sources of information requested. The information which could be collected is valid and was returned but some records may be missing.

Explanation

The table designator is not defined to be a table designator in this SQL statement or the table designator cannot be referenced where it is specified in the SQL statement.

The statement cannot be executed.

Explanation

The environment variable DB2INSTANCE is not defined or is not set to a valid instance owner.

Explanation

The request failed because the database is in use by another instance of the database manager (a database may only be used by one instance.) This may be caused by attempting to access a database located on a mounted file system accessible to another instance located on another machine.

This can also occur if you have an open connection (via SNA) to a database and the database manager was brought down abnormally.

Explanation

Only 1 instance of prep, bind, import, or export can be running at any one time within WINDOWS.

Explanation

The environment variable DB2PATH is not defined or is not set to a valid directory path.

Explanation

The new instance can not be set for the application because the instance is not defined.

This message can be returned when the current user does not have the required authority to execute in the current instance environment.

Explanation

The request to switch to another instance failed because the application is using multiple contexts.

Explanation

Request to switch to another instance failed because the application is connected to a database or attached to an instance.

Explanation

DB2 service did not start due to a logon failure.

Explanation

The routine routine-name is not supported in a partitioned database environment. The return data type of the RID function does not uniquely identify a row across database partitions. The RID function is supported in a non-partitioned database environment for compatibility with DB2 for z/OS.

Explanation

Two wrapper or server options have dependency on each other. Whether an option can be dropped or added depends on the existence of another option. Please view section Changes Related to DDL Statements for the examples of how this sqlcode is used.

Explanation

The authentication type supplied is not one of the supported types.

The command can not be processed.

Explanation

The user is attempting to connect to a remote database which is cataloged on the local node with a different authentication type from the remote node.

Explanation

Call your system administrator. On unix-based systems, the file db2ckpw may not have the correct permission bits set, or the system may have run out of swap/paging space. On Windows, the DB2 security service may not have been started or the account may be locked.

The command can not be processed.

Federated system users: this situation can also be detected by the data source.

Explanation

The username and/or password supplied is incorrect or not a valid username/password combination or the database to which you are attempting to connect to has an authentication type of SERVER and no username and password was supplied on the CONNECT TO statement.

If DB2 Connect is being used, the problem may be that the DCS directory entry for the host connection could not be found.

The command can not be processed.

Federated system users: this situation can also be detected by the data source.

Explanation

Your password has expired.

Explanation

The application failed to authenticate due to an error while communicating to the local DB2 authentication server.

Explanation

Shared sort memory is not available and is required for this operation.

Explanation

The utility does not support the option_name option with feature.

Explanation

An AUDIT USING statement for object object-name of type object-type attempted to associate the audit policy for the specified object, but an audit policy audit-policy is already in use. Only one audit policy can be associated to a particular object. The statement could not be processed.

Explanation

An AUDIT statement specifying the REMOVE option attempted to remove an association with the object object-name of type object-type, but an association does not exist The statement could not be processed.

Explanation

Explanation

The clause, clause, that is specified is valid for a service subclass but is not valid for a service superclass. When creating or altering a service subclass use the UNDER clause.

Explanation

The possible reason codes are as folows:

31

The table contains data of type XML created on a database server Version 9.5 or earlier. The redistribute utility cannot process tables that have XML columns containing data of type XML created on a database server prior to Version 9.7.

Explanation

The specification of a row change timestamp column is invalid. A row change timestamp column cannot be:

• A column of a foreign key.
• A column of a functional dependency DEPENDS ON clause.
• A column of a database partitioning key.
• Defined for a temporary table.

The statement cannot be executed.

Explanation

The table designator is not defined to be a table designator in this SQL statement or the table designator cannot be referenced where it is specified in the SQL statement. The statement cannot be executed.

Explanation

The statement was processed through parts of the system to collect diagnostic information using service features. The necessary steps to allow further processing of the statement have not been completed.

Explanation

The wrapper library is not compatible with the release and fix pack level of database product installed at the federated server. The wrapper library is compatible with the releases of DB2 listed in list-of-DB2-releases. The most common cause of this error is one of the following:

• You installed a DB2 fix pack, but did not install the corresponding InfoSphere Federation Server fix pack.
• During the installation of a InfoSphere Federation Server fix pack, the script to link the fenced wrapper library did not run or did not complete successfully.
• You installed a patch for InfoSphere Federation Server that requires running a script to link the fenced wrapper library. The script did not run or did not complete successfully.
• You put incompatible product libraries in the database product install directory.

Explanation

IBM tested the wrapper with only the data source server versions in the list list-of-data-source-versions. If you use the wrapper to access the version of the data source server that you specified on the CREATE SERVER or ALTER SERVER statement, then you might get errors or unexpected results.

Explanation

Changing the database configuration parameter (DB config parameter) DECFLT_ROUNDING may have several unintended consequences. Any calculation using the DECFLOAT data type could produce a different result with the new rounding mode.

The following is a list of some of the most significant consequences:

• Previously constructed MQTs could contain results that differ from what would be produced with the new rounding mode.
• A trigger whose execution is potentially dependent on rounding mode could produce different results now, based on the new rounding mode. However, even if the results of a trigger can be affected by the rounding mode, changing it will have no effect on data that was already written.
• It is possible for constraints that allowed data to be inserted into a table, will now, if re-evaluated, reject that same data. Similarly it is possible for constraints that did not allow data to be inserted into a table, would now, with the new rounding mode, accept that same data.
• The value of a generated column whose calculation is dependent on DECFLT_ROUNDING could be different for two rows identical except for the generated column value, if one row was inserted before the change to DECFLT_ROUNDING and the other was inserted after.
  • Note: rounding mode is not compiled into packages, so static SQL does not need to be recompiled after changing DECFLT_ROUNDING.

The value of the configuration parameter was not changed dynamically but will only become effective after all applications disconnect from this database. If the database was activated, it must be deactivated.

Explanation

The reason code indicates why the operation failed:

1

Only automatic storage table spaces are supported in a DB2 pureScale environment.

The CREATE TABLESPACE or CREATE DATABASE statement failed because the table space was not specified as MANAGED BY AUTOMATIC STORAGE.

2

Enabling automatic storage is not supported in a DB2 pureScale environment.

Because no type of storage other than automatic storage is supported in a DB2 pureScale environment, the statement for altering a table space that uses any other type of storage to use automatic can return this reason code.

3

Dropping storage paths that are used for automatic storage table spaces is not supported in a DB2 pureScale environment.

As a result, the DROP STORAGE clause is not supported with the ALTER DATABASE statement in a DB2 pureScale environment.

4

Creating a database partition group on any database partition other than database partition number 0 is not supported in a DB2 pureScale environment.

As a result, the following clauses are not supported in the CREATE DATABASE PARTITION GROUP statement in DB2 pureScale environments:

• ON DBPARTITIONNUMS
• ON DBPARTITIONNUM, specifying a database partition other than 0

5

Altering database partition groups is not supported in a DB2 pureScale environment.

As a result, the ALTER DATABASE PARTITION GROUP statement is not supported.

6

The CREATE TABLE statement failed because the specified table type is not supported in the current environment.

The following types of tables are not supported in a DB2 pureScale environment:

• Multidimensional clustering (MDC) tables
• Insert time clustering (ITC) tables
• Range-clustered tables (RCT)

7

Online index reorganization operations are not supported in a DB2 pureScale environment.

9

Creating or dropping a database on a specified database partition is not supported.

As a result, the following actions are not supported in DB2 pureScale environments:

• Specifying the AT DBPARTITIONNUM clause in a CREATE DATABASE or DROP DATABASE command
• Calling the sqlecran API or the sqledrpn API

11

Altering database containers is not supported in a DB2 pureScale environment.

As a result, the following clauses are not supported with the ALTER TABLESPACE statement in a DB2 pureScale environment:

• ADD <database-container-clause>
• BEGIN NEW STRIPE SET <database-container-clause>
• DROP <database-container-clause>
• REBALANCE
• RESIZE <database-container-clause>
• USING STOGROUP

13

The db2ReadLogNoConn API is not supported.

14

Adding database partitions using the START DATABASE MANAGER command with the ADD DBPARTITIONNUM clause is not supported in a DB2 pureScale environment. Dropping database partitions using the STOP DATABASE MANAGER command with the DROP DBPARTITIONNUM clause is not supported in a DB2 pureScale environment.

16

The PRUNE LOGFILE command is not supported.

17

The following configuration parameter is not supported in a DB2 pureScale environment:

• HEALTH_MON - Health monitoring

18

The specified create buffer pool or alter buffer pool operation is not supported.

19

In a DB2 pureScale environment, if the ROLLFORWARD and RECOVER commands are issued with the ON DBPARTITIONNUMS clause or with the ON DBPARTITIONNUM clause (either as part of the database partition list clause or the log overflow clause), the database partition specified must be 0.

20

Unable to add a CF or additional members to this host. The maximum cumulative number of CFs and members on this host has already been reached.

23

A restore operation with the REBUILD option is not supported in a DB2 pureScale environment.

24

A point-in-time recovery operation (rollforward or recover with the TO <isotime> option, or rollforward with the TO END OF BACKUP option) is not supported in a DB2 pureScale environment.

26

The SET CLIENT command does not support the CATALOG_DBPARTITIONNUM clause in a DB2 pureScale environment.

27

Infinite logging is not supported in a DB2 pureScale environment.

28

The use of raw devices for database logging is not supported in a DB2 pureScale environment.

29

The QUIESCE TABLESPACES FOR TABLE command failed because quiescing table spaces is not supported in a DB2 pureScale environment. Quiescing a database or a database manager instance is supported in a DB2 pureScale environment.

Explanation

The database manager has reached an internal limit while evaluating an expression, of long or large object string result type, that contains concatenation operators.

Explanation

Explanation

One of the containers to be used in a database managed table space is either too large or too small. A container must be at least 2 * extentsize pages in length. The maximum size of a container is operating system dependent. The most common system limit is 2 gigabytes (524288 4K pages).

Explanation

The query includes a column with a data type of BLOB, CLOB or DBCLOB. In general, such data types cannot be handled from clients available prior to Version 2.1.

The error occurred for a condition that corresponds to warning SQLCODE +238. See this message for details that explain the condition. The client level receiving this message cannot process BLOB data types. It may be able to handle CLOB and DBCLOB data types by using the SUBSTR function or by setting the data type in the SQLDA to one of the character data types available in Version 1 if the LOB column is not larger than the supported length of the character data type.

Explanation

Explanation

Any command/API that accepts a userid and password will not accept a password without a userid.

Explanation

If an explicit 'attach to instance' has not been performed, instance commands try to form an implicit attachment to a default instance. The default instance is determined from the DB2INSTDFT and DB2INSTANCE environment variables. If neither of these are set, then no implicit attachment can be formed.

Explanation

The application is not attached to an instance. The attempted command/API cannot be executed unless there is an existing instance attachment.

Explanation

In order to successfully process the command, an attachment to a node other than that which currently exists is required. The application must either: 1) have no attachment when the command is issued, or 2) already be attached to the node required by the command.

Explanation

The CATALOG NODE command or API does not allow an entry whose nodename matches the value of the DB2INSTANCE environment variable.

Explanation

When specific database names are provided to the database monitor, those databases must reside either at the node to which you are currently attached or at the local node.

Explanation

When the application is remote from the server, relative paths are not allowed.

Explanation

This error is caused by sending a DB2 request to a server which does not understand the database protocol being used to transmit the request. This situation will occur most frequently when sending a DB2 ATTACH request to a server listed in your node directory which is not a DB2 Version 2 or greater server. This error will also arise if you send an attach request to DB2 for AS/400, DB2 for MVS, or DB2 for VM and VSE servers.

Explanation

In order to successfully process the command, a connection to a database other than that which currently exists is required. The application must either: 1) have no connection when the command is issued, or 2) already be connected to the database required by the command.

Explanation

1. Version 7 does not support client/server connections between 32 bit and 64 bit platforms.
2. Version 8 Windows 64-bit database server does not support client/server connections from Version 7 64-bit clients.

Explanation

You can use the stored procedures SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE and SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE to configure database server automated maintenance activities such as automatic backup, automatic reorganization, and automatic statistics collection.

Before you can use SYSPROC.AUTOMAINT_SET_POLICY, SYSPROC.AUTOMAINT_SET_POLICYFILE, SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE, these stored procedures must be bound to the database against which you will run them. The bind file for these stored procedures is called db2policy.bnd.

The database server attempts to automatically bind these automated maintenance policy configuration stored procedures for you. However, this automatic binding or rebinding failed.

You will not be able to use these stored procedures until they are bound to the database.

Explanation

You can use the stored procedures SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE and SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE to configure database server automated maintenance activities such as automatic backup, automatic reorganization, and automatic statistics collection.

When you call SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE, you can specify an XML file that contains the automated maintenance policy details that you want to configure. In this case, the file specified could not be opened.

No new automated maintenance policy configuration was applied.

Explanation

You can use the stored procedures SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE and SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE to configure database server automated maintenance activities such as automatic backup, automatic reorganization, and automatic statistics collection.

There are two forms of SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE: one version of this stored procedure takes a parameter that is the name of an XML file that contains automated maintenance configuration details, and the other version of this stored procedure takes a LOB parameter containing automated maintenance configuration details in XML format.

The XML in the automatic maintenance configuration file or LOB parameter passed to SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE contains invalid XML at the line specified. The column number indicates the location within that line of the error.

No new automatic maintenance configuration was applied.

Explanation

You can use the stored procedures SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE and SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE to configure database server automated maintenance activities such as automatic backup, automatic reorganization, and automatic statistics collection.

There are two forms of SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE: one version of this stored procedure takes a parameter that is the name of an XML file that contains automated maintenance configuration details, and the other version of this stored procedure takes a LOB parameter containing automated maintenance configuration details in XML format.

An internal error occurred while processing the XML in the automatic maintenance configuration file or LOB passed to SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE.

No new automatic maintenance configuration was applied.

Explanation

You can use the stored procedures SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE and SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE to configure database server automated maintenance activities such as automatic backup, automatic reorganization, and automatic statistics collection.

The stored procedure SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE was unable to collect existing automated maintenance configuration information because it could not find any default automated maintenance policies.

No automatic maintenance configuration information was collected.

Explanation

With some GRANT statements, you can use the WITH GRANT OPTION clause to give the specified user (or groups) the ability to grant privileges to others.

The WITH GRANT OPTION is ignored when it is used in combination with certain privileges. This message is returned when an attempt is made to specify the WITH GRANT OPTION with privileges that it does not apply to.

All valid privileges were granted.

Explanation

Explanation

Explanation

The user attempted to attach a context to a thread, and the thread is already using a context.

Explanation

The user attempted to destroy an application context while it is still in use. Either there is a thread attached to the context, or the context has a CONNECT or ATTACH associated with it. A CONNECT RESET or DETACH must be done (if a CONNECT or ATTACH has been done), and all threads must detach from the context before it can be destroyed.

Explanation

A context type of SQL_CTX_MULTI_MANUAL is in effect, but the current thread or process has not been attached to a context.

Explanation

You can use the stored procedures SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE and SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE to configure database server automated maintenance activities such as automatic backup, automatic reorganization, and automatic statistics collection.

There are two forms of SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE: one version of this stored procedure takes a parameter that is the name of an XML file that contains automated maintenance configuration details, and the other version of this stored procedure takes a LOB parameter containing automated maintenance configuration details in XML format.

An internal error occurred while processing the XML in the automatic maintenance configuration file or LOB passed to SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE.

No automatic maintenance configuration was collected.

Explanation

You can use the stored procedures SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE and SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE to configure database server automated maintenance activities such as automatic backup, automatic reorganization, and automatic statistics collection.

The automated maintenance configuration file or LOB parameter passed to SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE contains invalid XML according to the given reason code:

1

The PathName element does not specify a valid path. For example, this message is returned if the specified path does not exist.

2

The SQL syntax of the FilterClause element is not valid.

3

The database manager attempted to validate the XML input file or LOB parameter you passed to SYSPROC.AUTOMAINT_SET_POLICY using a schema document in the /home/misc directory. The database manager could not find the schema document.

4

The first element in the XML input file or LOB parameter is not valid XML.

5

The encoding of the input XML file is not UTF-8.

No new automatic maintenance configuration was applied.

Explanation

You can use the stored procedures SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE and SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE to configure database server automated maintenance activities such as automatic backup, automatic reorganization, and automatic statistics collection.

When you call SYSPROC.AUTOMAINT_GET_POLICY or SYSPROC.AUTOMAINT_GET_POLICYFILE, you can specify the name of an XML file into which the output from the stored procedure should be saved. In this case, the file specified could not be created or written to.

No automated maintenance policy configuration information was saved.

Explanation

The db2tdbmgr command successfully migrated the database to the current level, but the scheduler was not started successfully for the reason indicated by the reason code:

1

The Tools Catalog Database configuration in the DB2 Administration Server configuration parameters is not correct.

2

The database manager containing the Tools Catalog Database has not been started.

3

The Tools Catalog Database is being used by another scheduler.

4

Unexpected error occurred when starting the scheduler.

Explanation

An invalid registration information pointer was passed to the register/deregister database server command/API.

Explanation

Register/deregister database server was issued from an invalid node.

Explanation

An invalid registration location was passed to the register/deregister database server command/API.

Explanation

The file server name specified in the configuration command/API or in the database manager configuration file is missing or invalid.

Explanation

The object name specified in the configuration command/API or in the database manager configuration file is missing or invalid.

Explanation

The IPX socket number specified in the configuration command/API or in the database manager configuration file is missing or invalid.

Explanation

A duplicate object name was found when trying to register the database server object name on the NetWare file server.

Explanation

A bindery login using NWLoginToFileServer cannot be performed if a NetWare directory services connection is already established to the specified file server.

Explanation

Issuing register/deregister is not necessary since the database manager configuration file has been configured for IPX/SPX direct addressing. ie. Fileserver and objectname have been specified as '*'.

Explanation

The db2tdbmgr command successfully migrated the database to the current level.

Explanation

Explanation

The SECURITY option for a TCP/IP node has a value other than 'SOCKS'. This option is used to enable the TCP/IP node being cataloged to use SOCKS protocol support to traverse a firewall. No value other than 'SOCKS' is permitted.

Explanation

A request was attempted which is only valid for a syncpoint manager connection, but the syncpoint manager instance is not connected to.

Explanation

The administration task cannot be added, updated, or removed because the table table-name that is used to store information about the tasks cannot be used as required. The table exists but cannot be used in its existing state. The administration task tables are automatically created when administration tasks are added to the database system. If the table was created in some other way, it may not be usable for administration task operations.

Explanation

The SYSPROC.ADMIN_TASK_REMOVE procedure attempted to remove a set of tasks, but not all were removed. The tasks that were not running were removed by the procedure, but any tasks that were running when the procedure attempted to remove them were not removed.

Explanation

The SQL statement that was specified as the PROCEDURE_INPUT for the scheduled administrative task was executed but the result could not be used as input to the procedure procedure-name that was specified for the scheduled administrative task. The SQL statement must result in no more than one row with the same number of columns in the result as there are arguments to the procedure.

Explanation

The most likely reason for the I/O error is a file system or hardware error.

The statement cannot be processed; and the utility or transaction of which this statement is a part will be rolled back.

Explanation

The SET CLIENT command or api or the environment variable DB2NODE was used to set the node for CONNECT or ATTACH to database-partition-number2. In order to CONNECT or ATTACH to this node, the Database Manager TCP/IP listener must be configured and running on the server instance instance (database partition number database-partition-number1).

Explanation

The SET CLIENT command or api or the environment variable DB2NODE was used to set the node for CONNECT or ATTACH to database-partition-number2. Subsequent CONNECT or ATTACH processing was unable to locate this node in the db2nodes.cfg file on the instance instance-name (node database-partition-number1).

Explanation

The DB2NODE environment variable indicates the node the application will attempt to connect to. If DB2NODE is unset or is blank, the application will attempt to connect to the default node. Otherwise, DB2NODE must be set to the node number of one of the nodes defined on the same host as the application.

Explanation

The end-of-log information on this node does not match the corresponding record on the catalog node. This can be caused by restoring the database on various nodes with backups taken from different times.

Explanation

The system time difference for the machines in the configuration (listed in the db2nodes.cfg file) is greater than the max_time_diff database manager configuration parameter.

Explanation

The system time difference for the machines in the configuration (listed in the db2nodes.cfg file) is greater than the max_time_diff database manager configuration parameter.

If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.

Explanation

The system time difference for the machines in the configuration (listed in the db2nodes.cfg file) is greater than the max_time_diff database manager configuration parameter.

This warning message is returned to read-only transactions because they are not affected by this condition. However, other transactions would be rolled back. This message is to inform the user about this condition so that action can be taken at the earliest possible time.

If ",..." is displayed at the end of the member list, see the syslog file for the complete list of members.

Explanation

The CONNECT RESET was successful but a system error such as a node failure or a communications error may have occurred.

Explanation

The transaction was rolled back because:

1. An implicit or explicit CLOSE CURSOR failed, or
2. A table was being created with the NOT LOGGED INITIALLY option, or NOT LOGGED INITIALLY was activated for an existing table. During the same unit of work, either an error occurred, or a ROLLBACK TO SAVEPOINT statement was issued. This unit of work is rolled back, with the following effects:
   • Any table that was created in this unit of work is dropped or put into DROP PENDING state.
   • Any NOT LOGGED INITIALLY tables that were activated in the transaction are marked inaccessible, and can only be dropped.
   • The sqlcode will be 0 if a ROLLBACK TO SAVEPOINT was issued in the transaction.
3. A rollback to savepoint failed or release savepoint failed.
4. A severe error occurred during an atomic array input operation.
5. An error occurred during the creation of a system temporary LOB that was to be used to maintain a LOB locator value for a LOB column of a declared temporary table or created temporary table whose rows were being deleted.

The runtime token, sqlcode, indicates the underlying sqlcode that was returned.

Explanation

An attempt was made to access a table where one of its objects is not accessible. The table may not be accessible because of one of the following reasons:

• The table had NOT LOGGED INITIALLY activated when the unit of work was rolled back.
• The table is a partitioned created temporary table or declared temporary table and one or more database partitions failed since the temporary table was instantiated or declared.
• ROLLFORWARD encountered the activation of NOT LOGGED INITIALLY on this table or a NONRECOVERABLE load on this table.

Access to this table is not allowed because its integrity cannot be guaranteed.

Explanation

Explanation

Explanation

Valid values for the DISCOVER parameter in the database manager configuration file are: DISABLE, KNOWN, or SEARCH.

Explanation

An example of a valid value for the DISCOVER_COMM parameter in the database manager configuration file is TCPIP.

Explanation

This is a warning that the BUFFPAGE database configuration parameter will be ignored if none of the database's buffer pools is defined with a size of -1. -1 indicates that the buffer pool is to use the BUFFPAGE parameter as the number of buffer pool pages.

Explanation

Add database partition server processing failed for database partition server partitionnum. The sqlcode, sqlstate, and message token list (each token is separated by the vertical bar character) are provided. The message tokens may be truncated. See the corresponding message for the sqlcode for further explanation of the error.

Explanation

The request failed because of an ongoing add operation. Until the specified database partition or member is added, the request is not allowed.

Explanation

A database partition server or member cannot be added or dropped when the database or instance is in the specified state.

Explanation

In a partitioned database environment, this message is returned when a new database partition server was added to a single-partition database environment. At the completion of the add database partition server operation, the new database partition server is not active until the database manager instance is restarted.

In a DB2 pureScale environment, the message is returned when a new DB2 member or cluster caching facility (CF) is added to an instance. After the member or CF is added, it is not active until the member or CF is restarted.

Explanation

The instance is managed by the DB2 cluster nmanager. When the newly added database partition server is configured, it can be managed by the cluster manager.

Explanation

Database has already been explicitly started (activated) on one or more nodes.

Explanation

The database cannot be deactivated if there are any applications connected to the specified database.

Explanation

The database cannot be deactivated because the specified database was not active.

Explanation

The ACTIVATE DATABASE, DEACTIVATE DATABASE, or ARCHIVE LOG command cannot proceed because the application is already connected to a database.

Explanation

There is already database connection on one or more nodes.

Explanation

There is still database connection to one or more nodes. The database will be shut down when the last connection disconnects from the database.

Explanation

Database was not explicitly started on one or more nodes when deactivate database was executed.

Explanation

Activate/Deactivate database is successful at least on the catalog node and coordinator node, however, on some other node(s) an error has occurred.

Explanation

Beginning in DB2 Version 9.7, type-1 indexes are no longer supported and they must be converted to type-2 indexes. Type-2 indexes were introduced in DB2 UDB Version 8 as a replacement for type-1 indexes in order to improve concurrency by minimizing next-key locking and using columns with length greater than 255 bytes as part of the index key.

The db2ckupgrade command identifies all type-1 indexes and generates the generated-file CLP script file in the same directory as the command logfile. The CLP script contains a REORG INDEXES ALL statement with the ALLOW WRITE ACCESS and CONVERT options for each identified type-1 index. It can be executed to convert all the identified type-1 indexes to type-2 indexes.

During database upgrade, any remaining type-1 indexes are marked invalid. The database manager will automatically rebuild the indexes as type-2 indexes on the first table access after database upgrade. No access to the table will be allowed until the index rebuild has completed.

Explanation

Database upgrade was successful; however, additional user action may be required because one or more of the following conditions were detected:

• Database upgrade altered NOT FENCED routines to FENCED and NOT THREADSAFE or altered user defined wrappers to FENCED on UNIX and Linux operating systems.
• Database upgrade could not successfully collect statistics on the system catalog tables.
• Database upgrade detected identifiers called NULL.
• Database upgrade marked indexes for rebuild on one or more tables.
• Database upgrade detected asterisks in workload connection attributes.
• Database upgrade detected databases enabled for XML Extender.
• Database upgrade detected databases enabled for DB2 WebSphere MQ functions.
• Database upgrade could not successfully re-validate or rebind packages.