Explanation

The alias specified in the command or api is not valid. The alias must contain 1 to 8 characters (bytes in MBCS countries) and all the characters must be from the database manager base character set.

The command cannot be processed.

Explanation

The syntax of the database name specified in the command is not valid. The database name must contain 1 to 8 characters and all the characters must be from the database manager base character set.

The command cannot be processed.

Explanation

The drive specified in the command is not valid. The drive is a single character (A to Z) indicating the diskette drive or fixed-disk partition where the database or database directory is located.

The command cannot be processed.

Explanation

The length of the password is expected to be 18 characters or less. However, if the password is to be verified for an APPC conversation, it must be 8 characters or less.

Explanation

There is not enough storage on the specified file system to process the command.

In a partitioned database environment on Windows environments, each node in the partitioned database group must have the exact same physical hard drive specification (letter) available and useable (must contain useable space) for the CREATE DATABASE command to succeed. The physical hard drive letter is specified in the database manager configuration. If DFTDBPATH is left blank the default will be the hard drive where the database product is installed on the instance-owning machine (installation path).

The command cannot be processed.

Explanation

The alias name specified has already been used. If no alias is specified in the catalog database command, the database name is used as the alias. When a database is created, the alias name is the same as the database name.

This error may occur on the catalog database command when the alias already exists in the system database directory.

On the create database command this error may occur in one of the following situations:

• The alias already exists in the system database directory and local database directory.
• The alias already exists in the system database directory but not in the local database directory.
• The alias already exists in the local database directory but not in the system database directory.

Explanation

The application could not connect to the database because the active codepage is different from the one that was active when the database was created.

The command cannot be processed.

Explanation

There are corrupted internal database pages or internal logic error for a table space.

Explanation

The storage group or table space ID specified does not exist. It is either larger than the current maximum storage group or table space ID, or the storage group or table space has been dropped.

Explanation

The command is not supported when issued on a client-only workstation or against remote databases. An example of such a command is cataloging a local database.

The command cannot be processed.

Explanation

The type specified in the Database Environment command is not valid. It must be '0' for an indirect database or '1' for a remote database.

In addition, on the Unix platforms, the type can be '3' for a database that has a DCE global name.

The command cannot be processed.

Explanation

A CATALOG DATABASE command was issued for an indirect entry but no path was specified. Indirect entries must specify the path where the database resides.

The command cannot be processed.

Explanation

There was no nodename parameter specified in the CATALOG DATABASE command for a remote entry. Remote entries must specify the node name of the database.

The command cannot be processed.

Explanation

The database name or alias specified in the command is not an existing database or the database could not be found in the (client or server) database directories or the db2dsdriver.cfg configuration file.

Explanation

The scan of the directory, file, or list is finished.

Explanation

The possible causes of the inconsistent state include:

• The database is offline as a result of an abnormal termination of the previous session (for example, a power failure).
• If the error was encountered when issuing the db2ckupgrade command:
  • The database is online and SQL has been issued which modified data in the database.
  • The database is online and HADR has been enabled.

In DB2 pureScale environments only, possible causes also include:

• The database on this DB2 member is offline as a result of an abnormal termination of the previous session.
• The database is offline across the entire DB2 pureScale instance as a result of an abnormal termination of the previous session.
• An attempt was made to perform an add operation or a drop operation while the database is in an inconsistent state such as: backup pending, rollforward pending, or restore pending. Also, if performing a drop operation, all tablespaces must be in a consistent state.
• The database cannot be configured for HADR.
• An add operation was attempted following one or more drop operations without taking an offline backup.
• If the error was encountered when issuing a command after one of these topology changes:
  1. The source member topology includes some members that are not in the target member topology.
  2. The source database was ESE and the target instance is a DB2 pureScale instance.
  3. The source database was a DB2 pureScale instance and the target instance is ESE.

Explanation

The local logical unit ( local_lu) alias specified in the CATALOG NODE command is not permitted. The local logical unit alias is the local SNA logical unit alias and must be 1 to 8 characters and cannot contain blank characters.

The command cannot be processed.

Explanation

The mode specified in the CATALOG NODE command is not permitted.

The mode parameter identifies the communications profile the Communications Manager uses to set up a session. The mode must be 1 to 8 characters. Valid characters are uppercase or lowercase A through Z, 0 through 9, #, @, and $. The first character must be alphabetic. The system changes lowercase characters to uppercase.

The command cannot be processed.

Explanation

The node name specified in the nodename parameter of the CATALOG NODE command is already cataloged in the node directory on this file system.

The command cannot be processed.

Explanation

The node name specified in the command is not valid. The node name may be 1 to 8 characters and all of the characters must be from the database manager base character set. The specified node name cannot be the same as the local instance name.

The command cannot be processed.

Explanation

The node directory cannot hold any more entries.

The command cannot be processed.

Explanation

The nodename specified in the command could not be found in the node directory.

The command cannot be processed.

Explanation

Not enough random access memory (RAM) is available to process the command.

If a remote procedure was invoked, the remote procedure may use a local variable space that is larger than the allowable maximum (4K).

If the statement involves a user-defined function (UDF), the memory set controlled by the ASLHEAPSZ database manager configuration parameter may be larger than the memory available.

The command cannot be processed.

Explanation

An error occurred in the communications conversation.

The command cannot be processed.

Explanation

There is no connection to a database. Other SQL statements cannot be processed unless an SQL CONNECT was previously executed.

The command cannot be processed.

Explanation

The stop database manager command cannot be processed if there are any applications connected to databases under control of the database manager, or if any databases have been activated, or if there are any active HADR primary or standby database under control of this database manager.

No action is taken.

Explanation

This message is returned when the db2start command is issued when the database manager is already started. The db2start command did not encounter any errors, this message is for your information only.

Explanation

The list node directory command cannot be processed because the node directory could not be found.

The command cannot be processed.

Explanation

The partner_lu alias specified in the CATALOG NODE command was not specified or contains characters that are not valid. The partner_lu alias is the partner SNA logical unit alias and must be 1 to 8 characters and must not contain blank characters.

The command cannot be processed.

Explanation

Either the system database directory or the local database directory cannot hold any more entries.

The command cannot be processed.

Explanation

The system database directory or local database directory could not be found. A database has not been created or it was not cataloged correctly.

The command cannot be processed.

Explanation

The start database manager command has not been processed. It must be processed before a stop database manager, any SQL statement, or utility can be issued.

The command cannot be processed.

Explanation

The database directory cannot be accessed if it is currently being updated. Also, the directory cannot be accessed for update if it is already being accessed for any reason. This situation could exist with either the system database directory or the local database directory.

The command cannot be processed.

Explanation

Damage has occurred to the database. The database cannot be used until it is recovered. All applications connected to the database have been disconnected and all processes running applications on the database have been stopped.

The command cannot be processed.

Explanation

When a user connects to a database, the connection is in shared mode by default. If another user is already connected to the same database in exclusive mode, then the shared connection attempt will fail with this message. Similarly, if a user attempts to access a database in exclusive mode but the database is already being accessed in shared mode then the connect attempt will fail with this message.

This message can also be returned in the following types of scenarios:

• The maximum number of connections to the database has been reached.
• Exclusive use was requested but the database is already in use in exclusive mode by a different user.
• The database has been activated explicitly (shared access), preventing the operation from establishing an exclusive connection to it.
• An attempt was made to drop a database partition while the database is quiesced.

In a pureScale environment, this message can be returned when the following series of events occur:

1. An offline operation, such as backup, restore, or rollforward, was initiated for the database and the operation acquired an exclusive connection to the database.
2. The member on which that offline operation was initiated failed (because of a hardware or software failure, for example) and the exclusive connection that was held by the offline operation was not released.
3. The member on which that offline operation was initiated failed to restart automatically.

Explanation

The problem may have occurred in one of the following situations:

• The system cannot open, read from, or write to a database file.
• The system cannot create the database because an error occurred while the system was creating a database file or a directory for the database.
• The system cannot drop the database because an error occurred while the system was deleting a database file or a directory for the database.
• The system cannot create the database because an interrupt was received while the system was creating or deleting a database file or a directory for the database.
• The system cannot locate the database subdirectory or database configuration file during connect.

Problem causes are ordered in terms of their frequency of occurrence:

• A log file cannot be found in the active log path directory.
• There may be a problem with the database directory the operation is being attempted on.
• There may be inadequate disk space to complete the operation.

The database cannot be used.

Explanation

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

Explanation

The node directory could not be accessed because of an I/O error.

The command cannot be processed.

Explanation

Either the system database directory or the local database directory cannot be accessed. This error may occur not only when the system is cataloging or uncataloging a database but also when the system is accessing a database that is cataloged in the directory.

The command cannot be processed.

Explanation

Each application that attaches to a database causes some private memory to be allocated. To manage memory use, you can configure the maximum number of concurrent applications that can be connected (both local and remote) to a database by setting the maxappls configuration parameter.

This message is returned when the number of applications connected to the database is equal to the maximum value defined in the configuration file for the database.

Explanation

The application attempted to start an inactive database but the number of active databases already equals the maximum value defined in the system configuration file.

The command cannot be processed.

Explanation

A system error occurred. Some possible reasons for this error are:

• The database manager is not installed correctly or the environment is not set up correctly.
• On UNIX-based systems, db2iupdt may need to be run in order to update the database manager instance to enable acquisition of a new system configuration or access to function associated with the installation or removal of certain product options, FixPaks, or modification levels.
• You might get this message if you are not using the correct DB2 Administration Server password.

The command cannot be processed.

Explanation

The CREATE DATABASE command failed while initializing the system catalogs.

Explanation

The user may have pressed the interrupt key sequence.

Processing is stopped.

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

Explanation

An indirect entry in the database directory points to another non-HOME entry.

The command cannot be processed.

Explanation

The authorization specified at logon is not valid for either the data source or the database manager. One of the following occurred:

• The authorization contains more than 30 characters for Windows platforms or 128 characters for other platforms.
• The authorization contains characters not valid for an authorization. Valid characters are A through Z, a through z, 0 through 9, #, @ and $.
• The authorization is PUBLIC or public.
• The authorization begins with SYS, sys, IBM, ibm, SQL or sql.
• The authorization violates some data source-specific naming convention.

The command cannot be processed.

Explanation

An application cannot create a database while connected to another database.

Binding a bind file to one database while already connected to another database is not permitted.

The command cannot be processed.

Explanation

The use parameter in the START USING DATABASE or CONNECT TO command must be either an S for shared or an X for exclusive use. If connecting to a database usingDB2 Connect , only shared access is allowed. Mnemonic equates for these values are provided in the SQLENV.H file.

The command cannot be processed.

Explanation

The connection to the database has been lost.

The command cannot be processed.

Explanation

The database specified in the UNCATALOG DATABASE command is a home database. Home databases cannot be uncataloged because their directory entries are deleted when the database is dropped.

The command cannot be processed.

Explanation

One of the following conditions is true:

• The value specified for the database directory or storage path does not exist or is inaccessible.
• The value specified for the database directory or storage path contains characters that are incompatible with the code page of the database.
• Storage paths must have an absolute path name and cannot be relative.
• An attempt is being made to activate or connect to a database but a storage path cannot be found or it is inaccessible.
• An attempt is being made to restore an automatic storage database while maintaining the storage paths defined in the backup image. However, a storage path cannot be found or it is inaccessible.
• A rollforward is attempting to replay a log record related to adding storage paths but a storage path cannot be found or it is inaccessible.
• An attempt is being made to drop a storage path that is not associated with the database.

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

The statement or command cannot be processed.

Explanation

The path specified in the path parameter of the command is not valid. Either there is no path with that name, or a path has been specified when the DB2_CREATE_DB_ON_PATH registry variable is disabled (Windows only).

In a partitioned database environment on Windows or UNIX environments, each node in the partitioned database group must have the same hard drive specification (path) available with usable space for the CREATE DATABASE command to succeed. The hard drive path is specified in the database manager configuration. If DFTDBPATH is left blank the default will be the hard drive path where the database product is installed on the instance-owning machine (installation path).

The command cannot be processed.

Explanation

The system is currently processing an interrupt so another interrupt is not honored.

The interrupt request is ignored.

Explanation

The system is currently processing a COMMIT. The user entered an interrupt key sequence.

The interrupt request is ignored.

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

Explanation

The system is currently processing a ROLLBACK. The user entered an interrupt key sequence.

The interrupt request is ignored.

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

Explanation

Eight database directory scans in this process are already open. No more than eight open scans are allowed.

The command cannot be processed.

Explanation

An attempt was made to read the contents of the system database directory, but no entries existed.

Explanation

The handle parameter specified in the Directory Scan command is not valid. The handle must be the one returned from the OPEN DIRECTORY SCAN or the OPEN NODE DIRECTORY SCAN command.

The command cannot be processed.

Explanation

A directory scan command was issued before the scan was opened.

The command cannot be processed.

Explanation

The specified authorization ID does not have the CONNECT privilege to access the database. The CONNECT privilege must be granted before the user can connect to a database. This error is also returned when a switch user request is made with a user ID allowed on the trusted connection but that user ID does not hold CONNECT privilege on the database. The connection is put in an unconnected state.

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

The command cannot be processed.

Explanation

Although the restart database operation was successful, existing indoubt transactions still need to be resolved. The database is usable, but if the indoubt transactions are not resolved before the last connection to the database is dropped, then the database will again require a restart before it can be used.

In a DB2 pureScale environment, the effect of the indoubt transactions depends on which DB2 member they are associated with, and the type of recovery operation that just completed. If the indoubt transactions are associated with the DB2 member from which the restart operation was issued, the database will be usable but any data associated with the indoubt transactions will not accessible. If the restart command initiated a group crash recovery and the indoubt transactions are associated with a different DB2 member, that DB2 member will remain inconsistent until it undergoes member crash recovery and the indoubt transactions will not be available for resolution until that member crash recovery completes.

Explanation

The database path parameter specified in the command does not exist. If the path is not specified, the default path defined in the system configuration file is used, and it does not exist.

In a partitioned database environment on Windows environments, each node in the partitioned database group must have the exact same physical hard drive specification (letter) available and useable (must contain useable space) for the CREATE DATABASE command to succeed. The physical hard drive letter is specified in the database manager configuration. If DFTDB is left blank the default will be the hard drive where the database product is installed on the instance-owning machine (installation path).

The command cannot be processed.

Explanation

The command to start the database manager completed successfully.

Explanation

The command to stop the database manager completed successfully.

Explanation

One or more utilities were not bound to the database. The list file list-name contains a list of the bind files. The numbers in list indicate the relative positions of the unbound files in the list file.

The listed utility bind files are not bound to the created or upgraded database.

Explanation

Explanation

Explanation

A user ID in a CONNECT TO or ATTACH TO statement does not belong to a domain defined in the DB2DOMAINLIST environment variable.

Explanation

The database is not a local database. A local database is cataloged as indirect in the system database directory and this entry references a home entry in the local database directory on the same node. Remote databases cannot be dropped.

The command cannot be processed.

Explanation

The application program used an address that is not valid for the database 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 this 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

This message can be returned in multiple scenarios:

• The database manager was incorrectly terminated. (On UNIX-based systems, for example, this situation might occur if the processes were terminated with the "kill" command, rather than the STOP DATABASE MANAGER command).
• Another application or user might have removed the database manager resources. (On UNIX-based systems, for example, a user with sufficient privilege might have accidentally removed an Interprocess Communication (IPC) resource owned by the database manager, using the "ipcrm" command).
• The use of system resources by another application conflicts with the use of system resources by the database manager. (On UNIX-based systems, for example, another application might be using the same keys that the database manager uses for creating IPC resources).
• Another instance of the database manager might be using the same resources. This situation could occur on UNIX-based systems if the two instances are on different file systems and the sqllib directories happen to use conflicting IPC keys.

Explanation

The node directory release number does not match the product expected release number. The node directory could be from a previous release.

Explanation

The application program used an address that is not valid for this 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 this 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 count parameter.

The command cannot be processed.

Explanation

The application program used an address that is not valid for the handle parameter.

The command cannot be processed.

Explanation

The application program used an address that is not valid for the buffer parameter.

The command cannot be processed.

Explanation

The application program used a nname parameter address that is invalid. 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 local_lu 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 has used an address that is not valid for the partner_lu 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 has used an address that is not valid for the mode 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 cannot be processed.

Explanation

The default values for some kernel parameters on some operating systems are not sufficient for running a database. If any other software is running on the same system as the DB2 database, the other software will compete for operating system resources, which makes configuring kernel parameters more difficult. To simplify kernel parameter configuration, the database manager automatically adjusts some kernel parameter settings when an instance is started on some operating systems. Also, there is a tool called db2osconf that you can use with some operating systems to determine recommended minimum operating system kernel settings for running a database system.

This message is returned when the database manager is unable to allocate shared memory, during activities such as activating a database or rolling a database forward, because an operating system kernel memory limit, such SHMMAX on Linux, has been reached.

Explanation

The application could not connect to the database because the database manager could not allocate the number of application heap 4K pages specified in the database configuration file. The system is out of 4K pages. The command cannot be processed.

Explanation

The command received an error from the operating system that prevents further processing.

The command cannot be processed.

Explanation

The CREATE DATABASE or UPGRADE DATABASE command could not open the list file containing the list of utility bind files. The list file should be located in the bnd subdirectory of the sqllib subdirectory.

The utility bind files are not bound to the created or upgraded database.

Explanation

The CREATE DATABASE or UPGRADE DATABASE command could not bind the utility bind files to the database.

The utility bind files are not bound to the newly created or upgraded database.

Explanation

CREATE DATABASE was interrupted while binding the utilities to the database. The interrupt key sequence may have been pressed.

The utility bind files are not bound to the newly created database.

Explanation

The release number of the precompiled application program or utility is not compatible with the release number of the installed version of the database manager.

The error will also occur if the application program is using down-level database manager libraries or DLLs while accessing the installed version of the database manager configuration file.

The command cannot be processed.

Explanation

The release number of the database is not the same release number of the instance. This release number was set when the database was created, when the database was upgraded, or the highest version, release, modification, and fix pack level defined in the system catalog.

The command cannot be processed.

If the error occurred during a database upgrade or database restore, you are attempting to upgrade or restore an incompatible release of database.

If the error occurred on the first connection after removing a fix pack, you are attempting to connect to a database which is only supported from higher fix pack level.

Explanation

Authentication of a user is completed using a security facility outside of the DB2 database system (part of the operating system or a separate product.) Authorization is performed using DB2 facilities (using DB2 tables and configuration files.) This message can be returned when there is a problem with either authentication or authorization.

Troubleshooting authentication and authorization problems is complicated by the fact that multiple agents are controlling access at different levels (local operating system login credentials, Windows user groups, domains, third-party security services such as Kerberos, the context in which a command is executed, DB2 authority levels, and database objects, just to name a few.)

Here are some common scenarios, listed by operating environment, in which this message can be returned:

Windows operating systems using groups

Here is a description of a scenario in which this message could be returned in a Windows environment using groups:

DB2 database configuration:

• The database product was installed with the database manager instance user set to the Windows LocalSystem account (or set to another local Windows account.)
• The DB2_GRP_LOOKUP environment variable is not set.

Action that fails:

• A user attempts to connect to a database using a two-part user ID that is defined at a remote domain.

Reason for the failure:

• Because the environment variable DB2_GRP_LOOKUP is not set, the database manager attempts to enumerate the groups at the location where the user ID is defined. However, because the database manager is running under the context of the LocalSystem account, the database manager does not have authority to access the network to enumerate the groups at the location where the user ID is defined.

Windows operating systems using Kerberos

In a Windows environment in which Kerberos authentication is being used, this message can be returned when an attempt is made to log on to a computer with an account that is not a domain account.

Windows operating systems using Extended Security

In a Windows environment with Extended Security enabled, this message can be returned if a user ID that is not a member of the local DB2USERS group or DB2ADMNS group attempts to use or modify a database resource.

Lightweight Directory Access Protocol (LDAP) environments

In an LDAP environment, this message can be returned if the user ID or the DB2 Connect gateway does not have the authority to perform the CATALOG DATABASE, CATALOG ... NODE, or CATALOG DCS DATABASE command.

The Windows command prompt

On Windows Vista or later versions of the Windows operating system, the command prompt might have standard user privileges, even if the user has administrative privileges. This message can be returned if a command that requires administrative privileges is executed from a command prompt that has only standard privileges.

Federated database environments

In federated environments, this error could happen at the federated server or at the federated data source.

Explanation

The command cannot be processed.

Explanation

The node directory cannot be scanned or used while it is being updated. Also, the directory cannot be accessed for update if it is already being accessed for any reason.

The command cannot be processed.

Explanation

Eight node directory scans are already open in this process and no more than eight are allowed.

The command cannot be processed.

Explanation

A command was issued on a node that does not support the command, or the system environment was found to be set up incorrectly for this node type. For example, a database was cataloged as LOCAL on a client node.

The command cannot be processed.

Explanation

Either the node name listed in the database directory for a remote database or the node name specified on an attach command was not cataloged in the node directory.

The command cannot be processed.

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

Explanation

A connection to a database was requested but the application is already connected to the specified database.

The command cannot be processed.

Explanation

A write operation was attempted to a database residing on a write-protected diskette.

The statement cannot be processed.

Explanation

The Catalog Database command specified node name name but that is not cataloged in the node directory. The node name must be cataloged before the remote database can be used.

The CATALOG DATABASE command completed successfully.

Explanation

A connection to the remote database name on node node-name was requested, and the remote node does not accept the authorization ID and password combination specified for this node (either in the remote authorization tables or at runtime).

Federated system users: This error can also occur when any of the following is true:

• There is no user mapping and the remote authorization ID or remote password does not match the authorization ID and password that were specified when connecting to the DB2 federated database.
• The user mapping does not specify the REMOTE_PASSWORD option, and no password was specified when connecting to the DB2 federated database.
• The user mapping does not specify the REMOTE_PASSWORD option, and the remote password does not match the password specified when connecting to the DB2 federated database.
• The user mapping does not specify the REMOTE_AUTHID option, and the remote authorization ID does not match the authorization ID specified when connecting to the DB2 federated database.
• The remote authorization ID or remote password do not match those specified on the user mapping.

The request cannot be processed.

Explanation

No database name was provided to proceed with database upgrade.

The statement cannot be processed.

Explanation

The UPGRADE DATABASE command was completed successfully. If issued on a non-HADR standby database, you can now access this database.

Note that this message will also be returned if the database was already at the current level and was not upgraded.

If issued on an HADR standby database, the database metadata has been upgraded to the current level and the HADR replay service has begun in the background. The database is in upgrade in progress state and can not accept new connections if reads on standby is enabled until it has replayed all upgrade log records received from the primary database.

Explanation

The application program has used an address for the program name that is not valid.

The command cannot be processed.

Explanation

The remote application procedure contains an SQL CONNECT RESET statement.

The remote procedure is not allowed to continue.

Explanation

The function within the DLL (dynamic link library) cannot be found.

The command cannot be processed.

Explanation

When loading the DLL (dynamic link library) module, the command was interrupted, perhaps by Ctrl+Break.

Processing is stopped.

Explanation

An unexpected error occurred when trying to load the DLL (dynamic link library) module specified in the program name field.

The command cannot be processed.

Explanation

This message is returned when the database manager fails to load a dynamic link library (DLL).

Explanation

The data area is not initialized correctly.

The command cannot be processed.

Explanation

The DLL (dynamic link library) module or program name syntax is not correct.

The command cannot be processed.

Explanation

There is not enough random access memory (RAM) to load the specified DLL (dynamic link library) module.

The command cannot be processed.

Explanation

The remote stored procedure changed the data type of the nth sqlvar in the output SQLDA; n is the sequence number of the first mismatched sqlvar.

The stored procedure does not return any data.

Explanation

The remote stored procedure changed the data length of the nth sqlvar in the output SQLDA; n is the sequence number of the first mismatched sqlvar.

The stored procedure does not return any data.

Explanation

The remote procedure changed the sqld field in the output SQLDA; sqld is the number of used sqlvars in the SQLDA.

The stored procedure does not return any data.

Explanation

The specified database requires a backup to be taken to provide a starting point for rollforward recovery.

Explanation

The specified database is enabled for roll-forward recovery and it has been restored but not rolled forward.

No connection was made.

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

Explanation

The database is in an inconsistent state because a system error occurred during a backup function.

No connection was made.

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

Explanation

The database is in an inconsistent state because a system error occurred during a restore function or a restore is still in progress.

No connection was made.

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

Explanation

The database is in an inconsistent state because a system error occurred during a backup or restore function. It cannot be determined if backup or restore was being processed.

No connection was made.

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

Explanation

The application used an address for the node structure 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 command cannot be processed.

Explanation

The application used an address for the protocol structure parameter that is not valid. Either the address points to an unallocated buffer or the address points to the incorrect protocol buffer.

The command cannot be processed.

Explanation

The protocol type specified in the node structure for the Catalog command does not represent a recognized value. The valid protocol types are defined in the sqlenv header files.

The command cannot be processed.

Explanation

The remote workstation name specified in the protocol structure for the Catalog command is not specified or contains characters that are not valid.

The command cannot be processed.

Explanation

The adapter number specified in the protocol structure for the Catalog command is not valid.

The command cannot be processed.

Explanation

The network ID specified in the APPN protocol structure for the Catalog command is not valid. The network ID identifies the SNA network where the remote logical unit (LU) resides. The network ID must be 1 to 8 characters. Valid characters are A through Z, a through z, 0 through 9, #, @, and $. The first character must be alphabetic or a special character: #, @, or $. Lowercase characters are changed to uppercase by the system.

The command cannot be processed.

Explanation

The remote logical unit (LU) name specified in the APPN protocol structure for the Catalog command is not valid. The remote LU name is the remote SNA logical unit name and must be 1 to 8 characters. Valid characters are A through Z, a through z, 0 through 9, #, @, and $. The first character must be alphabetic or a special character: #, @, or $. Lowercase characters are changed to uppercase by the system.

The command cannot be processed.

Explanation

When loading data into a table, you can cause the load utility to establish consistency points after each time a given number of rows have been processed. Consistency points allow an interrupted load operation to be restarted from the latest consistency point.

You can specify how many rows to load between consistency points by using the SAVECOUNT parameter to the load command. Some utilities, such as db2move, use the load utility and set a SAVECOUNT value by default.

There are some restrictions on using consistency points. When an attempt is made to use consistency points in an unsupported way, the load operation proceeds, but consistency points are not created. This message can be printed in two general scenarios:

• The LOAD command is invoked directly, and the SAVECOUNT parameter is specified
• The load utility is used by another utility, and that other utility specifies a SAVECOUNT value by default

The reason code indicates the restriction that was encountered:

1

Consistency points are not supported when loading data into MDC or ITC tables.

2

Consistency points are not supported with the specified file type.

3

Consistency points are not supported when loading data into partitioned tables.

4

Consistency points are not supported when loading data into tables containing XML columns.

5

Consistency points are not supported when loading data data into column-organized tables.

Explanation

New stored srocedure process could not be started because there are insufficient resources for a new process to be created.

Explanation

New stored procedure process could not be started because the maximum number of processes allowed to be present at the server at the same time has been reached.

Explanation

The DB2 architecture is designed so that applications run in a different address space than the database server. Running applications in a different address space prevents application programming errors from overwriting database manager internal buffers or files, and prevents application errors from crashing the database manager. The fenced mode process (db2fmp) is responsible for executing fenced stored procedures and user-defined functions in a different address space than the database server.

This message is returned when the db2fmp process terminates abnormally while running the named routine. The db2fmp process could have terminated abnormally for many reasons, including the following reasons:

• There was a coding error, such as division by zero or an out-of-bounds pointer reference, in the implementation of the stored procedure or user-defined function that the db2fmp process was executing.
• Another process terminated the db2fmp process using a signal, such as the termination signal SIGTERM.
• SQLJ.INSTALL_JAR failed while installing a Java routine because the fenced user does not have permission to create or write to the necessary directories on the server.

Explanation

An illegal command has been made within the scope of stored procedure.

The procedure is not allowed to continue.

Explanation

The “sqlind” or the “sqldata” pointer within the sqlvar of the output SQLDA has been altered within the user prepared DARI function.

The stored procedure does not return any data.

Explanation

A command that requires SYSADM authorization is not allowed in a stored procedure if the database authentication type is CLIENT.

The stored procedure does not return any data.

The procedure is not allowed to continue.

Explanation

The value that was specified for the number of segments was out of range. The valid range is from 1 to 256.

Explanation

The value that was specified for the default table space extent size (dft_extentsize) is out of range. The valid range is from 2 to 256.

Explanation

Either the list of containers could not be accessed or some failure occurred while attempting to remove them or the database directory.

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

Explanation

A CREATE INDEX operation was attempted on an existing index. Since the index had not yet been migrated to support deferred uniqueness checking, this migration was performed.

The migrated format of the unique index will allow multiple row updates to check the uniqueness of the columns of the index at the end of the update statement instead of when each row is updated.

Explanation

The size of the current table space is too big. The size of a REGULAR table space is limited to 0x0100 0000 (16777216) pages while the size of LARGE and TEMPORARY table spaces are limited to 0x7FFF FEFF (2147483391) pages.

Explanation

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

The prepare of the dynamic INSERT, UPDATE, DELETE, or SELECT statement was successful. An SQLCODE -905 might be issued if the execution of the prepared statement exceeds the ASUTIME value specified in the RLST.

Explanation

In a partitioned database environment, the file extension corresponds to the database partition node number. The files are located in the directory specified by the DIAGPATH database manager configuration parameter.

Explanation

There is an existing file using the file name specified in the INSPECT command.

The command cannot be processed.

Explanation

The file could not be accessed because of an I/O error. The system cannot open, read from, or write to the file. The file may be incomplete or the disk may be full.

The utility stops processing.

Explanation

In the same transaction, the last remaining index on a table was dropped and then a new index was created on the same table. The index creation either failed with an error, sqlcode, or was rolled back by a ROLLBACK TO SAVEPOINT statement (sqlcode=0). A rollback of the index creation cannot be successfully completed when a drop index of the last remaining index on a table has not yet been committed. The entire transaction is rolled back for either of these cases. Note that indexes are also created or dropped by adding or dropping unique or primary key constraints in an ALTER TABLE statement.

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

Explanation

Explanation

The table-name specified for index reorganization has no indexes.

Explanation

Because the table free space is well managed for MDC and ITC tables, the TOTALFREESPACE file type modifier is unnecessary and will be ignored.

Explanation

The index needs to be refreshed, however, the index resides in a table space which is currently in backup pending state and it cannot be refreshed.

Explanation

A CLP error was encountered. Use the clp-msg-id information to look up the appropriate message details for the indicated CLP message.

Explanation

The application program used an address that is not valid for this 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

Explanation

The specified priority is not within the legal range of 0 - 100.

Explanation

The specified utility ID could not be found. Either an invalid ID has been specified or the utility has already completed.

Explanation

There has been an attempt to throttle a utility that does not support throttling.

Explanation

The value to be assigned for a column of a result set from the ADMIN_CMD procedure either is greater than the maximum value for the data type of the column or is less than the minimum value for the data type. If the value was greater than the maximum value, then the maximum value for the data type has been assigned. If the value was less than the minimum value, then the minimum value for the data type has been assigned. For an SMALLINT data type, the value assigned for the maximum is 32767 and the mimimum is -32768. For an INTEGER data type, the value assigned for the maximum is 2147483647 and the mimimum is -2147483648. For a BIGINT data type, the value assigned for the maximum is 9223372036854775807 and the mimimum is -9223372036854775808.

Explanation

The utility operation ID provided is not valid. It cannot be null and it must be a value previously returned from the SYSPROC.ADMIN_CMD procedure for a utility that was executed by it. However, once the messages have been removed from the server by the SYSPROC.ADM_REMOVE_MSGS procedure, the utility operation ID can no longer be used to refer to the messages on the server.

Explanation

The routine routine-name is disallowed from being invoked in a trigger. Triggers do not support executing an API, execution of a COMMIT statement and the return of result sets.

Explanation

The directory directory-name may contain database sensitive information and so access to it is restricted. In order to maintain database integrity, applications cannot create a new file, read from a file, write to a file, or delete a file under this directory.

Explanation

You can access the IBM database system with the IBM Data Server Provider for .Net.

This message is returned when there is a problem with the database product installation. This message can also be returned when the Windows extended security feature is enabled and the ID that is used to start the Internet Information Systems (IIS) service does not belong to the DB2ADMNS group or to the DB2USERS group.

The reason code for this message is intended for IBM support personnel only.

Explanation

The Terminate and Stay Resident (TSR) network driver for the specified communications protocol has not been loaded. The TSR must be loaded before attempting to use network communications.

Explanation

Metadata information about one of more DataLink columns of the table are missing on DB2 DataLinks Managers. Reconcile processing has failed. Table is placed in DataLink Reconcile Not Possible (DRNP) state.

Explanation

One of more DB2 DataLinks Managers referred to by the table data became unavailable during reconcile exception processing. Reconcile processing has failed. Table is placed in DataLink Reconcile Pending (DRP) state.

Explanation

Data capture is not supported with certain identifier types exceeding specific lengths. In processing the attempted change, it was found that the identifier ident-name of type ident-type is too long. The identifier types and the maximum lengths allowed for data capture enablement are as follows:

1. column. Column names cannot be longer than 128 bytes for data capture to be enabled.
2. table. Table names cannot be longer than 128 bytes for data capture to be enabled.
3. schema. Schema names cannot be longer than 128 bytes for data capture to be enabled.

Explanation

An error occurred while processing the SQLDA or host variable(s) in the SQL statement.

The call parameter list, which is created by the precompiler, may not be correct if the application programmer has modified the output of the precompiler, used a variable name beginning with SQL in the application program, or over-written the call parameter list in another way.

Also, if an SQLDA is passed directly by the application, it may not be initialized correctly.

The statement cannot be processed.

Explanation

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

The statement processing continued returning a null indicator of -2.

Explanation

The processing of an arithmetic expression resulted in division by zero. This warning may be returned with a row other than the row which caused the warning. For example, this occurs with arithmetic expressions in predicates or when the query is processed using system temporary tables. The warning may be issued again since it is also returned whenever a null indicator variable is set to -2.

The statement processing continued, using null as the result of the division expression and possibly returning a null indicator of -2.

Explanation

The processing of an arithmetic expression has resulted in an arithmetic overflow, underflow or other arithmetic exception. This warning may be returned with a row other than the row which caused the warning. For example, this occurs with arithmetic expressions in predicates or when the query is processed using system temporary tables. The warning may be issued again since it is also returned whenever a null indicator variable is set to -2.

The statement processing continued, using null as the result of the arithmetic expression and possibly returning a null indicator of -2.

Explanation

The Load utility encountered an error associated with the REMOTEFETCH media. This is due to one of the following reasons:

1

A connection to the database-name specified in the REMOTEFETCH media arguments could not be made.

2

The source table-name specified in the REMOTEFETCH media arguments does not exist or the source table is inaccessible.

3

The source query specified in the REMOTEFETCH media arguments could not be PREPARED.

4

The result set from the source table or query is not compatible with the target table definition.

5

An error occurred while fetching records from the source table or query.

Explanation

The Explain facility has been invoked to explain a statement, previously compiled with REOPT ONCE, but an error occurred as described by one of the following reason codes:

1. The specified statement could not be found in the package cache.
2. The cached statement has not been compiled using REOPT ONCE.
3. The cached statement has been compiled in multiple environments with REOPT ONCE, and can't be uniquely identified.
4. No values could be found for the cached reoptimized statement.
5. A column of an Explain table is too small. The additional-information identifies the schema name, table name and column name as well as the column size required to contain the data generated by the Explain facility, using the format schema-name.table-name.column-name (recommended-size).

   The additional-information might be truncated if the names are very long. The db2diag log file will contain more detail.

Explanation

The database partition dbpartition is not available. This error can occur when new storage paths are being used as part of a RESTORE command, or when a BACKUP command using the ON DBPARTITIONNUM clause is being run.

Explanation

The maximum number of storage paths for a storage group is 128 and this has been reached. The CREATE DATABASE command or ALTER STOGROUP statement issued may contain too many paths or the database may already be using the maximum number allowed.

Explanation

The restore operation specified a list of storage paths when restoring to a non-catalog partition in a partitioned database. This is not supported.

Explanation

A previous attempt was made to restore the catalog partition specifying a list of automatic storage paths in a partitioned database, and that restore failed. Any subsequent restore operations on the catalog partition must also specify a list of automatic storage paths. This restriction is removed from the database once the database is returned to normal state via a rollforward operation.

Explanation

A database partition expression using the $N notation was found in the specified path path but it is either not permitted or not specified correctly. The reason codes are as follows:

1

A database partition expression was used as part of the database path, specified either implicitly as the first storage path or explicitly using the DBPATH ON option, and this is not permitted.

2

A database partition expression was found within the path but it could not be evaluated due to an error in the syntax.

3

The database partition expression specified a number outside the permitted range. If a number is specified before the N argument ($[number]N), then the number can be from 2 to 6 inclusive.

Explanation

The Load utility has automatically reduced the number of Partitioning Agents in order to optimize REMOTEFETCH parallelism.

Explanation

Incompatible values for parameters have been provided to the command or API.

Explanation

OLE, OLEDB and CLR routines can only be created and run on database servers in Windows operating system environments. The current database server is not in a Windows operating system environment. The routine cannot be invoked from this server.

Explanation

The object of type object-type identified by object-name is defined using the keyword FEDERATED but the fullselect in the statement does not reference a federated database object.

The statement cannot be processed.

Explanation

The object identified by object-name references a federated object (such as an OLE DB table function, federated routine, federated view, or a nickname), where the actual data exists at a data source. When the data source data is accessed, the user mapping and authorization checking is based on the user that initiated the operation.

If the object-type is SUMMARY TABLE, then the operation is refreshing the data for the materialized query table. The user that invoked the REFRESH TABLE or SET INTEGRITY statement that causes the refresh may be required to have the necessary privileges to access the underlying data source object at the data source.

If the object-type is VIEW, then any user of the view may be required to have the necessary privileges to access the underlying data source object at the data source.

If the object-type is PROCEDURE, FUNCTION, or METHOD then the invoker of the routine may be required to have the necessary privileges to access the underlying data source object at the data source for any SQL statements in the routine.

If the object-type is PACKAGE and this message results from precompiling or binding an application, then the invoker of the application may be required to have the necessary privileges to access the underlying data source object at the data source for any static SQL statements in the application.

If the object-type is PACKAGE and this message results from creating an SQL or XQuery procedure, then the invoker of the procedure may be required to have the necessary privileges to access the underlying data source object at the data source for any SQL statements in the procedure.

In any case, an authorization error may occur when the attempt is made to access the data source object.

Explanation

The database manager received an OLE error code while trying to communicate with the OLE automation server of user defined function (UDF) or stored procedure routine-name (specific name specific-name). HRESULT hresult is the returned OLE error code, and message text is the retrieved error message.

Explanation

The user defined function (UDF) or stored procedure routine-name (specific name specific-name) has raised an exception. The message text shows the textual description of the exception returned by the routine.

Explanation

The OLE DB data source object of the specified OLE DB provider could not be instantiated or initialized. hresult is the returned OLE DB error code, and message-text is the retrieved error message.

The following shows a partial list of HRESULTS and possible causes.

0x80040154

Class (OLE DB provider) not registered.

0x80040E73

The initialization string specified does not conform to specification.

0x80004005

Unspecified error (during initialization).

Explanation

The specified OLE DB provider returned an OLE DB error code. hresult is the returned OLE DB error code, and message-text is the retrieved error message.

The following shows a partial list of HRESULTS and possible causes.

0x80040E14

The command contained one or more errors, for example, syntax error in pass-through command text.

0x80040E21

Errors occurred, for example, the supplied columnID was invalid (DB_INVALIDCOLUMN).

0x80040E37

The specified table does not exist.

Explanation

EXPLAIN will not be able to insert into these tables until they are migrated using DB2EXMIG, or dropped and created with the EXPLAIN.DDL CLP script for the current version of DB2.

Explanation

If value is NO, then at least one static SQL statement in the package includes a reference to either a nickname or OLE DB table function or OLE DB procedure. In this case, you must specify FEDERATED YES to bind the package.

If value is YES, then no static SQL statement in the package includes a reference to either a nickname or OLE DB table function or OLE DB procedure. In this case, you must specify FEDERATED NO to bind the package.

The package is not created.

Explanation

The object identified by object-name references a federated object (such as an OLE DB table function, federated routine, federated view, or a nickname) where the actual data exists at a data source.

If a non-federated view is being altered and the fullselect now refers to a federated database object, either directly or indirectly, then FEDERATED must be specified.

If a federated view is being altered and the fullselect still refers to a federated database object, either directly or indirectly, then NOT FEDERATED must not be specified.

If a materialized query table is being created and the fullselect refers to a federated database object, either directly or indirectly, then NOT FEDERATED must not be specified.

If an SQL routine is being created and the routine refers to a federated database object, either directly or indirectly, then NOT FEDERATED must not be specified.

Explanation

The CREATE DATABASE or UPGRADE DATABASE command could not create a detailed deadlocks event monitor for the created or upgraded database.

Explanation

The source and target columns are not compatible. This may be a result of an incorrect ordering of the columns in the SELECT or VALUES statement, or of an incorrect ordering of the METHOD P or METHOD N specification.

Explanation

An invalid METHOD was specified for the specified file type.

Explanation

The LOAD utility encountered an error with the SQLCODE sqlcode and has stopped processing.

Explanation

Column col-spec does not exist in the result of the query.

Explanation

The filetype specified does not allow more than max-input-sources input sources to be specified for a single load.

Explanation

This is an informational message indicating that a load from an SQL statement has begun.

Explanation

Row number row-num has been rejected because the value corresponding to target column col-num is not a valid value for that column.

Explanation

The Tools Catalog Database database-name creation or initialization failed at server-name. SQLCODE = SQLCODE.

Explanation

Backup completed successfully. One or more Data Links File Managers were not available during backup processing. Additional verification are needed from the Data Links File Managers when they are available.

Explanation

The keyword value specified for the command is invalid. For numeric values, the value may be outside a defined range. For other types, the value specified is not in the defined set of valid values.

Explanation

The command you have entered is not supported in your current configuration involving either a pre-V8 client or server. The possible reason codes are as follows:

1

Scrollable cursors are not supported from a pre-V8 client through a V8 or later gateway to a database server.

2

Utility commands are not supported from a pre-V8 client through a V8 or later gateway to any database server.

3

Access to a pre-V8 server through a V8 or later gateway is not supported.

4

Utility commands are not supported to a pre-V8 server from a V8 or later client.

5

Pre-V8 clients may only access tables, table functions, and procedures that are created with the CCSID value whose corresponding code page is the same as the database code page.

6

Tablespace point-in-time rollforward commands are not supported from a pre-V9 client to a V9 or later server because some of the function of these commands runs on the client side. The pre-V9 client is NOT able to perform these operations when connected to a V9 or later server.

7

The back-level API is not supported in the current client-server configuration.

98

Operation not supported to a pre-V8 server from a V8 or later client.

99

Operation not supported from a pre-V8 client to a V8 or later server.

Explanation

The command cannot be processed.

Explanation

The command cannot be processed.

Explanation

The value specified for the handle parameter in the GET NEXT DATABASE STATUS BLOCK or the FREE DATABASE STATUS RESOURCES function calls is not valid. The handle must be the one returned as the positive function value from the COLLECT DATABASE STATUS function call.

This is the second COLLECT DATABASE STATUS call made from the process. The first COLLECT DATABASE STATUS call terminates and its handle can no longer be used.

The command cannot be processed.

Explanation

A request was made for user status on a database, but the database has no users connected.

The command cannot be processed.

Explanation

This version of the database manager does not support the active code page or territory code or both.

The command cannot be processed.

Choose an active code page and territory code supported by this version of the database manager.

Federated system users: if necessary isolate the problem to the data source rejecting the request and choose an active code page and territory code supported by both the federated server and the data source.

Explanation

This version of DB2 does not support the active code page or territory code or both, as specified by the Create Database command.

The command cannot be processed.

Explanation

Explanation

The Communication Manager configuration file name specified on the CATALOG NODE command was not found either in the path specified or in the CMLIB directory on the default drive.

The command cannot be processed.

Explanation

The Load utility is unable to allocate all requested memory. Success of the operation is unaffected, but performance might be suboptimal. The memory available to the Load utility is determined either by the value of the DATA BUFFER Load option, or by the value of the util_heap_sz database configuration parameter.

Explanation

The logical partner unit name specified in the CATALOG NODE function does not exist in the Communications Manager configuration file located in the CMLIB directory on the default drive.

A logical unit profile of the specified name was created.

Explanation

One or more of the DOS Requester/WINDOWS Requester configuration values returned was defaulted. The parameter may not be defined in the DOS Requester/WINDOWS Requester configuration file or the configuration file could not be opened or an error occurred reading the file.

Explanation

The computer name specified in the NPIPE protocol structure for the Catalog command is not valid. The size of the computer name must be 15 characters or less.

The command cannot be processed.

Explanation

The instance name specified for the Catalog command is not valid. The size of the instance name must be 8 characters or less.

The command cannot be processed.

Explanation

The change password logical unit (LU) name specified in the APPN protocol structure for the CATALOG command is not valid.

The change password LU name is the remote SNA LU name and must be 1 to 8 characters. Valid characters are A through Z, a through z, 0 through 9, #, @, and $. The first character must be alphabetic or a special character: #, @, or $. Lowercase characters are changed to uppercase by the system.

The command cannot be processed.

Explanation

The transaction program (TP) name specified in the APPN protocol structure for the CATALOG command is not valid.

The TP name is the remote SNA Application TP name and must be 1 to 64 characters. Valid characters are A through Z, a through z, 0 through 9, #, @, and $. The first character must be alphabetic or a special character: #, @, or $.

The command cannot be processed.

Explanation

The LAN adapter address specified in the APPN protocol structure for the CATALOG command is not valid.

The LAN adapter address is the remote SNA LAN adapter address and must be a 12-hexadecimal number.

The command cannot be processed.

Explanation

The code page of the database does not support graphic data. The data types GRAPHIC, VARGRAPHIC, LONG VARGRAPHIC, and DBCLOB are not valid for this database. The GRAPHIC literal and the VARGRAPHIC scalar functions are not valid for this database.

The statement cannot be processed.

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

Explanation

An SQL operation is using a data type of REAL (single-precision floating point number) as an input or output variable. The REAL data type is not supported on the target database for this request.

The statement is not processed.

Explanation

All of the pages in the bufferpool are currently being used. A request to use another page failed.

The statement cannot be processed.

Explanation

The instance was unable to allocate enough private virtual memory to process the request. This may be a result of shared memory allocations made in other (unrelated) processes.

Explanation

The database manager allocates and deallocates memory at various times. Memory might be allocated to a particular memory area when a specific event occurs (for example, when an application connects), or memory might be reallocated in response to a configuration change.

In general, this message is returned when the database manager cannot perform an operation because of one of the following problems:

• There are insufficient database manager memory resources
• There are insufficient environment memory resources

Specifically, this message can be returned when there are allocation or configuration problems with the following types of memory resources:

• The instance memory
• The amount of physical memory available in the system
• The number of shared memory identifiers allocated in the system
• The size of the shared memory segment
• The amount of paging or swapping space available in the system

Explanation

Explanation

All available memory in the Application Support Layer heap has been used.

Explanation

There are many reasons for which this message can be returned, including the following reasons:

Client/server configuration problems

• In client/server environments using the TCP/IP protocol: The port number assigned to the TCP/IP service name on the client is not the same as the port number on the server. The error condition can be detected by the federated server or by the data source.

A database manager agent was unavailable

• The database manager was stopped or had not been started on the database server.
• An administrator forced a database agent off the system.
• A database manager process terminated abnormally.

The user ID had insufficient authority

• The user ID was forced off of the system when another user with SYSADM authority issued a FORCE QUIESCE command. The FORCE QUIESCE command forces off of the system all users who do not have CONNECT QUIESCE authority for the database or instance or who do not belong to a group that has CONNECT QUIESCE authority.
• In Windows operating system environments: Extended Security was enabled, and the user ID was not a member of the DB2USERS or DBADMINS group.

Database directory conflicts

• There were two databases, one local and one remote, with the same database name and same database alias.
• A local database was cataloged as a remote database.
• After a change was made to the way that one or more databases were cataloged, the changes did not take effect because the database manager is still using a cached copy of the database cataloging information.

A configured database limit or a system resource limit was reached

• The application was using more transaction log space than allowed by the max_log database configuration parameter or the num_log_span database configuration parameter.
• There were insufficient coordinator agents to process the application requests. Applications that hold locks in WITH HOLD cursors and are queued for execution in concentrator mode might cause active agents to be held up waiting for those locks.
• The connection was idle for longer than the time specified in the CONNECTIONIDLETIME threshold.
• A unit of work on the connection lasted longer than the time specified in the UOWTOTALTIME threshold and the connection was terminated because the threshold action specified FORCE APPLICATION.
• A query took longer than the time specified in the SQL_ATTR_QUERY_TIMEOUT statement attribute.

The requested function is not supported

• An attempt was made to connect to a member that was in restart light mode.

Database activation on a newly added member

• If the first activation of a database on a newly added member is in progress, a subsequent database connection attempt on the newly added member will fail until the first activation is complete.

Explanation

An operating system process, thread, or swap space limit was reached. You can find more information about the problem in the administration notification log.

Explanation

The number of client connections is already equal to the maximum value defined for the instance in the system configuration file.

This error might be reported for system-driven connections used for maintenance operations. Such connections are capped at a percentage of the active user workload. When no more connections are allowed, these operations will be retried at a later time automatically.

The operation cannot be processed.

Explanation

The value or format of a statistic provided for an updatable catalog is either invalid, out of range, or inconsistent. The most common checks for value, range and format are (corresponding to code):

1

Numeric statistics must be -1 or >= 0.

2

Numeric statistics representing percentages (eg. CLUSTERRATIO) must be between 0 and 100.

3

This message is returned with reason code 3 when an attempt is made to update HIGH2KEY or LOW2KEY (or both) in a way that violates the rules for updating column statistics manually.

4

PAGE_FETCH_PAIRS related rules:

• Individual values in the PAGE_FETCH_PAIRS statistic must be separated by a series of blank delimiters.
• There must be exactly 11 pairs in a single PAGE_FETCH_PAIR statistic.
• There must always be a valid PAGE_FETCH_PAIRS value if the CLUSTERFACTOR is > 0.
• Individual values in PAGE_FETCH_PAIRS statistics must not be longer than 19 digits and must be less than the maximum integer value (MAXINT = 9223372036854775807).
• Buffer size entries of PAGE_FETCH_PAIRS must be ascending in value. Also, any buffer size value in a PAGE_FETCH_PAIRS entry cannot be greater than MIN(NPAGES, 1048576) for 32-bit platforms and MIN(NPAGES, 2147483647) for 64-bit platforms where NPAGES is the number of pages in the corresponding table.
• "fetches" entries of AVGPARTITION_PAGE_FETCH_PAIRS must be descending in value, with no individual fetches entry being less than NPAGES. Also, any "fetch" size value in a AVGPARTITION_PAGE_FETCH_PAIRS entry must not be greater than CARD (cardinality) statistic of the corresponding table.
• If buffer size value is the same in two consecutive pairs, then page fetch value must also be the same in both the pairs.

5

CLUSTERRATIO and CLUSTERFACTOR related rules:

• Valid values for CLUSTERRATIO are -1 or between 0 and 100
• Valid values for CLUSTERFACTOR are -1 or between 0 and 1
• Either CLUSTERRATIO or CLUSTERFACTOR must be -1 at all times.
• If CLUSTERFACTOR is a positive value, it must be accompanied by a valid PAGE_FETCH_PAIR statistic.

6

The cardinality of a column (COLCARD statistic in SYSCOLUMNS) or column group (COLGROUPCARD in SYSCOLGROUPS) cannot be greater than the cardinality of its corresponding table (CARD statistic in SYSTABLES).

7

No statistics are supported for user-defined structured types. For columns with the following data types, statistics support is limited to AVGCOLLEN and NUMNULLS: LONG VARCHAR, LONG VARGRAPHIC, BLOB, CLOB, and DBCLOB.

8

A statistic is inconsistent with other related statistics for this entity or is invalid in this context.

9

For tables that are not partitioned, the following table partitioning statistics in SYSSTAT.INDEXES cannot be updated: AVGPARTITION_CLUSTERRATIO, AVGPARTITION_CLUSTERFACTOR, AVGPARTITION_PAGE_FETCH_PAIRS, DATAPARTITION_CLUSTERFACTOR

10

AVGPARTITION_PAGE_FETCH_PAIRS related rules:

• Individual values in the AVGPARTITION_PAGE_FETCH_PAIRS statistic must be separated by a series of blank delimiters.
• There must be exactly 11 pairs in a single AVGPARTITION_PAGE_FETCH_PAIR statistic.
• There must always be a valid AVGPARTITION_PAGE_FETCH_PAIRS value if the AVGPARTITION_CLUSTERFACTOR is > 0.
• Individual values in AVGPARTITION_PAGE_FETCH_PAIRS statistics must not be longer than 19 digits and must be less than the maximum integer value (MAXINT = 9223372036854775807).
• Buffer size entries of AVGPARTITION_PAGE_FETCH_PAIRS must be ascending in value. Also, any buffer size value in a AVGPARTITION_PAGE_FETCH_PAIRS entry cannot be greater than MIN(NPAGES, 1048576) for 32-bit platforms and MIN(NPAGES, 2147483647) for 64-bit platforms where NPAGES is the number of pages in the corresponding table.
• "fetches" entries of AVGPARTITION_PAGE_FETCH_PAIRS must be descending in value, with no individual fetches entry being less than NPAGES. Also, any "fetch" size value in a AVGPARTITION_PAGE_FETCH_PAIRS entry must not be greater than CARD (cardinality) statistic of the corresponding table.
• If buffer size value is the same in two consecutive pairs, then page fetch value must also be the same in both the pairs.

11

AVGPARTITION_CLUSTERRATIO and AVGPARTITION_CLUSTERFACTOR related rules:

• Valid values for AVGPARTITION_CLUSTERRATIO are -1 or between 0 and 100.
• Valid values for AVGPARTITION_CLUSTERFACTOR are -1 or between 0 and 1.
• Either AVGPARTITION_CLUSTERRATIO or AVGPARTITION_CLUSTERFACTOR must be -1 at all times.
• If AVGPARTITION_CLUSTERFACTOR is a positive value, it must be accompanied by a valid AVGPARTITION_PAGE_FETCH_PAIR statistic.

12

DATAPARTITION_CLUSTERFACTOR related rules:

• Valid values for DATAPARTITION_CLUSTERFACTOR are -1 or between 0 and 1.

13

AVGCOMPRESSEDROWSIZE related rules:

• Valid values for AVGCOMPRESSEDROWSIZE are -1, or between 0 and AVGROWSIZE.

14

AVGROWCOMPRESSIONRATIO related rules:

• Valid values for AVGROWCOMPRESSIONRATIO are -1, or greater than 1.

15

PCTROWSCOMPRESSED related rules:

• Valid values for PCTROWSCOMPRESSED are -1, or between 0 and 100, inclusive.

Explanation

The drop database command has completed successfully, however, there are some nodes where the database alias or database name was not found. It is possible that DROP DATABASE AT NODE was already performed on these nodes.

Explanation

One of the following has occurred:

1. A system error, such as member failure or connection failure, has occurred. The application is rolled back to the previous COMMIT.

   Note that in the case of DB2 utility functions, the behavior is described as follows:

   Import

   The application is rolled back. If the COMMITCOUNT parameter was used, the operation is rolled back to a previous committed point.

   Reorg

   The operation is aborted and must be resubmitted.

   Redistribute

   The operation is aborted, however, some of the operation might have been successful. Issuing the request again with the "continue" option will restart the operation from the point of failure.

   Rollforward

   The operation is aborted and the database is still in rollforward pending state. The command must be resubmitted.

   Backup/Restore

   The operation is aborted and must be resubmitted.

2. The service port numbers assigned for FCM (Fast Communication Manager) communications are not the same on all the members in the database manager instance. Check the services file being used on all members to ensure that the ports are the same. The ports are defined using the format:

      DB2_<instance>       xxxx/tcp
      DB2_<instance>_END   xxxx/tcp

   where <instance> is the instance name and xxxx is the port number. Ensure that these port numbers are not being used for DB2 remote client support.

Explanation

Explanation

The value specified for the count parameter of the Force command is not valid. The value specified must either be a positive integer or SQL_ALL_USERS. A value of 0 will result in an error.

Explanation

The value specified for the mode parameter of the Force command is not valid. Only asynchronous mode is supported for the Force command. The parameter must be set to the value SQL_ASYNCH.

Explanation

The following functionality is supported only for Unicode databases:

• The NCHAR, NVARCHAR, and NCLOB data types.
• Specifying a UCS-2 hexadecimal constant using the format UX'hex-digits'.
• The NCHAR, NVARCHAR, NCLOB, TO_NCHAR, TO_NCLOB and EMPTY_NCLOB scalar functions.
• A graphic expression as the first argument of the VARCHAR scalar function.
• A graphic expression as the first argument of the VARGRAPHIC scalar function when a second argument is specified.
• Specifying CODEUNITS32 when defining a character string data type.
• Specifying CODEUNITS16 or CODEUNITS32 when defining a graphic string data type.

• Column-organized tables.

Explanation

Only REGULAR DMS table spaces can be converted to a LARGE DMS table space. The system catalog table space, SMS table spaces, and temporary table spaces cannot be converted to be a LARGE table space.

Explanation

The partitioned table has data partitions in multiple regular DMS table spaces. The table space must contain all of the data partitions of a partitioned table in order to be converted to be a LARGE table space.

Explanation

The table space in which this table resides was converted to a LARGE table space via the CONVERT TO LARGE clause of the ALTER TABLESPACE statement. The table itself cannot support large RIDs until all previously existing indexes on the table have been reorganized or rebuilt to support large RIDs. The index(es) must be reorganized or rebuilt to support future growth of this table.

Explanation

The table space being converted can, following COMMIT, support a storage capacity larger than that of a regular table space. The maximum page number for a data page in a regular table space is 0x00FFFFFF. For a table to support a page number above 0x00FFFFFF, the indexes on the table must be reorganized or rebuilt.

Explanation

Explanation

On database servers Version 9.5 and earlier, the use of XML data store features is restricted to databases having only one database partition. Features such as defining columns of data type XML, registering XML schema repository objects, and XQuery expressions are not available within a partitioned database environment.

Explanation

An attempt was made to acquire a quiesce state on a table space which has already been quiesced by 5 processes.

Explanation

The value for a table space attribute was out of range. The identified attribute is the field name of this structure.

Explanation

The statement cannot be processed because there was an attempt to use an XML feature in a context where it is not supported. The reason-code indicates the context:

1

On database servers Version 9.5 and earlier, columns of data type XML are not supported in a table that is organized by dimensions.

2

On database servers Version 9.5 and earlier, columns of data type XML are not supported in a partitioned table.

3

Columns of data type XML cannot be added to a table with existing type-1 indexes. Starting in Version 9.7, type-1 indexes are discontinued and are replaced with type-2 indexes.

4

A distribution key cannot be defined for a table with an XML column.

5

Columns of data type XML are not supported in a view that is the target of an INSTEAD OF trigger.

6

References to transition variables of data type XML are not supported in a trigger definition.

7

For a table containing columns of data type XML, an operation that drops XML columns must drop all of the XML columns in the table in a single ALTER TABLE statement.

On database servers Version 9.5 and earlier, and for a table containing columns of data type XML, a REORG-recommended operation cannot be specified in an ALTER TABLE statement.

8

A column of data type XML is supported by the wrapper associated with the nickname definition only if the column definition has no options. Such a column references the contents of an XML document returned from the data source.

9

References to XML data types or values in compound SQL (compiled) statements in functions, triggers, or compound SQL (inlined) statements are not allowed. XML is only supported in compound SQL (compiled) statements in procedures.

100

In a partitioned database environment, tables with XML columns are only supported in the database partition that contains the database catalog tables, the IBMCATGROUP database partition.

101

Prior to DB2 Version 9.7, the ADD DBPARTITIONNUM command and the REDISTRIBUTE DATABASE PARTITION GROUP command are not supported on a database partition group that contains tables that have XML columns.

102

In a partitioned database environment, annotated XML schema decomposition is supported on only the database partition that contains the database catalog tables, the IBMCATGROUP database partition.

103

In a partitioned database environment, the following XML-related commands are only supported in the database partition that contains the database catalog tables, the IBMCATGROUP database partition:

• COMPLETE XMLSCHEMA
• REGISTER XMLSCHEMA
• ADD XMLSCHEMA DOCUMENT
• REGISTER XSROBJECT

104

In a partitioned database environment, for an application to process XML data, the application must be connected to the database partition that contains the database catalog tables, the IBMCATGROUP database partition.

105

SQL functions that have parameters or variables of type XML are not supported in a partitioned database environment.

Explanation

The UPGRADE DATABASE command checks whether the database has a db2look operation table called SYSTOOLS.DB2LOOK_INFO, and drops this table if it exists. The drop table command fails if the database owns a table with the same name but a different column definition.

Explanation

A disconnect has been issued against a database which is acting as the TM database. The disconnect cannot be completed until the next COMMIT is processed.

Explanation

The maximum number of concurrent database connections has been reached for an environment where the number of connections is restricted or must be predefined.

Explanation

Explanation

The application was precompiled with the option SYNCPOINT ONEPHASE or SYNCPOINT NONE, or the SYNCPOINT connection setting was changed to one of these values using the SET CLIENT API. These settings are invalid for applications which cause transaction processing syncpoint commands (for example CICS SYNCPOINT) to be executed. Note that SYNCPOINT ONEPHASE is the default precompiler option.

Explanation

You attempted to access a database that had not been opened by the transaction manager. A database must be defined to the transaction manager in order to participate in the two-phase commit process.

Explanation

The db2ckupgrade command has identified an occurrence of the DATALINK data type which will cause database upgrade to fail.

Database objects which use the DATALINK data type include tables, views, functions, methods, distinct types and structured data types.