SQL1000-1999

SQL Message ID Message Explanation User Response

SQL1000N

alias is not a valid database alias name.

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.

Resubmit the command with the correct alias.

SQL1001N

name is not a valid database name.

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.

Resubmit the command with the correct database name.

sqlcode: -1001

sqlstate: 2E000

SQL1002N

drive is not a valid drive.

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.

Resubmit the command with the correct drive.

SQL1003N

The password is not valid because the syntax is not correct or the password does not match the password of the specified database.

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.

Ensure that the password is not longer than the limit allowed.

sqlcode: -1003

sqlstate: 28000

SQL1004C

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

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.

Choose a different file system or erase some non-database files from the specified file system to make space for the database manager functions.

In a partitioned database environment on Windows environments, follow the following steps:

Determine which hard drive specification (letter) is required. The drive letter is specified in the error message.
Determine which node/s of the database partition are experiencing the problem. You can usually find this information in the db2diag log file of the instance-owning node.
Correct the drive problem on the individual node that is experiencing the problem or change the drive specification in the database manager configuration so that the same drive is available (and has sufficient space) on each and every node of the partitioned database group.
re-issue the command.

SQL1005N

The database alias name already exists in either the local database directory or system database directory.

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.

For the catalog database command, uncatalog the alias from the system database directory and resubmit your original command or catalog the database with a different alias name.

For the create database command, do the following operations corresponding to the three situations listed previously:

Drop the database using the alias name. Resubmit your original command.
Uncatalog the alias. Resubmit your original command.
Catalog the alias into the system database directory. Drop the database using the same alias. Resubmit your original command.

SQL1006N

The code page code-page of the application does not match the code page code-page of the database.

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.

Exit the current application program and return to the operating system. Change the code page for the process and restart the application program.

SQL1007N

Error in finding pages for an object in a table space.

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

Discontinue use of the object or table space. Contact IBM service to inspect the object and the table space.

sqlcode: -1007

sqlstate: 58034

SQL1008C

Invalid storage group or table space ID.

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.

Discontinue use of the database. Save the diagnostic information in the error log and contact IBM Software Support.

sqlcode: -1008

sqlstate: 58036

SQL1009N

The command is not valid.

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.

Possible solutions include:

Issue the specified command from a non client-only workstation or from the workstation where the database resides.
Verify that the database is cataloged correctly.
Issue a different command.

SQL1010N

type is not a valid type parameter.

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.

Resubmit the command with a valid type.

SQL1011N

No drive was specified in the CATALOG DATABASE command for an indirect entry.

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.

Resubmit the command with the required path or change the type.

SQL1012N

No node name was specified in the CATALOG DATABASE command for a remote entry.

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.

Resubmit the command with the nodename parameter or a different type.

SQL1013N

The database alias name or database name name could not be found.

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.

Ensure that the specified database name exists in the system database directory. If the database name does not exist in the system database directory, then the database either does not exist or the database name has not been cataloged.

If the database name appears in the system database directory and the entry type is INDIRECT, ensure that the database exists in the specified local database directory. If the entry type is REMOTE, then ensure that the database exists and is cataloged on the database directories for the server.

For CREATE DATABASE with the AT DBPARTITIONNUM clause, ensure that the database name is in the system database directory with an entry type of INDIRECT and with a catalog database partition number that does not equal -1.

Federated system users: in addition to the previous responses, verify that the database names specified in SYSCAT.SERVERS are all valid. Correct any SYSCAT.SERVERS entry for which the database specified in that entry does not exist.

sqlcode: -1013

sqlstate: 42705

SQL1014W

There are no more entries in the directory, file, or list being scanned.

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

No action is required.

SQL1015N

The database is in an inconsistent state.

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.

If the database is offline as a result of an abnormal termination of the previous session, respond with the following actions:
1. Restart the database using the RESTART DATABASE command. In a partitioned database server environment, the command must be issued on all database partitions.
If this error was encountered when issuing the db2ckupgrade command, respond with the following actions:
1. Perform a clean shutdown of the database.
2. After shutdown, if HADR is enabled on the database, issue the STOP HADR command on the database.
3. Re-issue the db2ckupgrade command.

In a DB2 pureScale environment only:

If the database on this DB2 member is offline as a result of an abnormal termination of the previous session, respond with the following actions:
By default, member crash recovery is automatically initiated in a DB2 pureScale environment, so no user action is required. If member crash recovery is not automatically enabled, perform member crash recovery on this DB2 member by issuing the RESTART DATABASE command.

Some database operations can still complete on other, consistent members even if one member is inconsistent. To access the database during member crash recovery, connect to an active DB2 member. To access this specific member, wait for member crash recovery to complete.
If the database is offline across the entire DB2 pureScale instance as a result of an abnormal termination of the previous session, warn users that the database will not be available until recovery completes. The next step depends on whether group crash recovery is automatically enabled. If it is enabled (the default) then no user action is required. If automatic group crash recovery is not enabled, respond with the following actions:
1. Perform group crash recovery by issuing the RESTART DATABASE command.
2. After the recovery completes, perform member crash recovery on any other members that have indoubt transactions.
Back up databases or table spaces that are in backup pending state, and resubmit add or drop operation.
If using circular logging connect to the database to materialize any existing drop operation, and then proceed to reissue the add.
This is not a supported operation, the databases must be consistent. If this is a copy of the database, make the database consistent on the source, then move it to the target instance.

sqlcode: -1015

sqlstate: 55025

SQL1016N

The local_lu alias name specified in the CATALOG NODE command is not valid.

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.

Verify that the alias is a permitted logical unit name. Verify the characters used in the name. Resubmit the command with a valid logical unit name.

SQL1017N

The mode parameter mode specified in the CATALOG NODE command is not valid.

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.

Verify that the name is a permitted mode name. Verify the characters used in the name. Resubmit the command with a correct mode.

SQL1018N

The node name name specified in the CATALOG NODE command already exists.

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.

If the nodename parameter is typed correctly, continue processing.

Uncatalog the cataloged node in the node directory if the node cataloged information is no longer valid and resubmit the command. If the node cataloged information is valid, define a new node name and resubmit the command using the new node name.

SQL1019N

The node name name specified in the command is not valid.

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.

Ensure the node name is not the same as the local instance name by displaying the value of the DB2INSTANCE environment variable. On UNIX operating systems, display the DB2INSTANCE environment variable by entering the following command:

echo $DB2INSTANCE

On Windows operating systems, display the DB2INSTANCE environment variable by entering the following command:

echo %DB2INSTANCE%

Resubmit the command with the correct node name.

SQL1020C

The node directory is full.

The node directory cannot hold any more entries.

The command cannot be processed.

Uncatalog any unnecessary entries in the node directory.

SQL1021N

The node name name specified in the UNCATALOG NODE command was not found.

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

The command cannot be processed.

If the nodename parameter is correct, the node may already have been uncataloged, and processing can continue. Otherwise, resubmit the command with the correct node name.

SQL1022C

There is not enough memory available to process the command.

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.

Stop the application. Possible solutions include:

Change the MEMMAN NO SWAP, NO MOVE option in the CONFIG.SYS file to SWAP, MOVE.
Remove background processes.
Decrease the values of the configuration parameters that define allocation of memory, including ASLHEAPSZ if UDFs are involved in the failing statement.
Install more random access memory (RAM).
If a remote procedure was invoked, ensure that the remote procedure uses a local variable space that is less than or equal to 4K.
If you are using Remote Data Services, increase the Remote Data Services heap size (rsheapsz) in the server and client configuration because at least one block is used per application.

sqlcode: -1022

sqlstate: 57011

SQL1023C

The communications conversation failed.

An error occurred in the communications conversation.

The command cannot be processed.

Retry the original command. If the error persists, contact your communications administrator.

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

sqlcode: -1023

sqlstate: 08001

SQL1024N

A database connection does not exist.

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.

If the error occurred when disconnecting from the database, continue processing. If the error occurred on another SQL statement, issue an SQL CONNECT statement and resubmit the command or statement.

sqlcode: -1024

sqlstate: 08003

SQL1025N

The database manager was not stopped because databases are still active.

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.

Usually no action is required. To stop the database manager, all active applications must disconnect from all the databases they are using. Alternatively, the user can use the FORCE command to force applications to disconnect, and the DEACTIVATE command to deactivate the database, including any HADR primary or standby databases.

SQL1026N

The database manager is already active.

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.

No response is required.

SQL1027N

The node directory cannot be found.

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

The command cannot be processed.

Issue a CATALOG NODE command with the appropriate parameters and resubmit the current command.

SQL1028N

The HADR standby database is terminated because it is rejected by the primary database.

The HADR standby database is terminated because it is incompatible with its configured primary database.

Investigate the administration notification log and db2diag.log for the primary database and search for ADM12519E for the reason of rejection.

SQL1029N

The partner_lu alias name specified in the CATALOG NODE command is not valid.

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.

Examine the partner_lu for a typing error. Verify that the alias is a permitted logical unit name. Verify the characters used in the alias. Resubmit the command with a correct partner_lu.

SQL1030C

The database directory is full.

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

The command cannot be processed.

Uncatalog any unnecessary entries in the directory. Create new databases on another file system if the local database directory is full.

SQL1031N

The database directory cannot be found on the indicated file system.

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.

Verify that the database is created with the correct path specification. The Catalog Database command has a path parameter which specifies the directory where the database resides.

sqlcode: -1031

sqlstate: 58031

SQL1032N

No start database manager command was issued.

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.

Issue a start database manager command and resubmit the current command.

If using multiple logical nodes, ensure the DB2NODE environment variable is set correctly. The DB2NODE environment variable indicates the node the application will attempt to connect to. DB2NODE must be set to the node number of one of the nodes defined on the same host as the application.

In a DB2 pureScale environment, respond to this message in one of the following ways:

Set the DB2NODE environment variable to a DB2 member that is active.
Rerun the command on a computer that is not configured to run only a cluster caching facility (CF).

sqlcode: -1032

sqlstate: 57019

SQL1033N

The database directory cannot be accessed because it is being used.

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.

Wait until the access has completed, then resubmit the command.

sqlcode: -1033

sqlstate: 57019

SQL1034C

The database was damaged, so all applications processing the database were stopped.

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.

In general, respond to this error by performing the following steps:

Recover the database by issuing the RESTART DATABASE command.
If the RESTART DATABASE command consistently fails, you may want to restore the database from a backup.

In a partitioned database environment, respond to this error by performing the following steps:

Before restoring the database from a backup, refer to the syslog to determine if the RESTART DATABASE command is failing because of database partition or communication failures
If the RESTART DATABASE command is failing because of database partition or communication failures, ensure that the following conditions are true:
- the database manager is up and running
- communication is available among all the database partitions
Resubmit the RESTART DATABASE command, with the db2_all command:
```
db2_all db2 restart database <database_name>
```
If there are indoubt transactions that remain unresolved after the RESTART DATABASE command is completed, run the RESTART DATABASE command multiple times to ensure that all indoubt transactions have been resolved.

In a DB2 pureScale environment, respond to this error by performing the following steps:

Refer to the administration log to determine if the RESTART DATABASE command is failing because the member being restarted is unable to access a shared storage device.
If the RESTART DATABASE command is failing because the member being restarted is unable to access a shared storage device, correct the access problem and retry the RESTART DATABASE command.
If the member being restarted is able to access the shared storage device, issue the RESTART DATABASE command from a different member.
If none of these actions work, restore the database and then perform a rollforward operation.

If you encountered this error during roll-forward processing, respond to this error by performing the following steps:

Restore the database from a backup.
Perform a roll-forward operation again.

If you are installing the sample database, respond to this error by performing the following steps:

Drop the sample database
Install the sample database again

sqlcode: -1034

sqlstate: 58031

SQL1035N

The operation failed because the specified database cannot be connected to in the mode requested.

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:

An offline operation, such as backup, restore, or rollforward, was initiated for the database and the operation acquired an exclusive connection to the database.
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.
The member on which that offline operation was initiated failed to restart automatically.

Perform the following troubleshooting steps:

Identify which user applications or system applications have open connections to the database by using the LIST APPLICATIONS command with the SHOW DETAIL parameter and the GLOBAL parameter.
Wait for those applications that have open connections to close their connections to the database.
Terminate any remaining connections to the database using the following commands or statements:
- QUIESCE DATABASE command
- CONNECT RESET statement
- FORCE APPLICATION ALL command
- DEACTIVATE DATABASE command
In a DB2 pureScale environment restart any member that was shut down while an offline operation was taking place.
If the database is quiesced, unquiesce the database.
Connect again.

sqlcode: -1035

sqlstate: 57019

SQL1036C

An I/O error occurred while accessing the database.

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.

Appropriate responses for the problem causes described in the Explanation are:

To verify if a log file is missing, check the db2diag log file for the presence of a logging error (return code contains SQLO_FNEX). If present, this error will contain the name of the missing log file. Ensure that the file is located in the active log path directory. If the file cannot be located, restore and roll-forward the database to an earlier point in time referenced in a log file preceding the missing log file (use a timestamp that is earlier than that of the missing file).
There may be a problem with the database directory. Check the integrity of the directory. Examples of potential problems include: permissions issues, mount point problems, corruption.
Increase filesystem size.

NOTE: If the error occurred during CREATE DATABASE or DROP DATABASE, a subsequent CREATE DATABASE or DROP DATABASE command attempts to erase files and directories left from the unsuccessful CREATE DATABASE or DROP DATABASE command.

sqlcode: -1036

sqlstate: 58030

SQL1037W

The node directory is empty.

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

No action is required.

sqlcode: +1037

sqlstate: 01606

SQL1038C

An I/O error occurred while accessing the node directory.

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

The command cannot be processed.

Resubmit the command. If the error continues, remove the node directory (sqlnodir under the sqllib directory) and recatalog the node names on the network.

sqlcode: -1038

sqlstate: 58031

SQL1039C

An I/O error occurred while accessing the database directory.

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.

Possible solutions include:

If the error occurred on a diskette system, verify that the correct diskette is in the drive and ready to use. Verify that it is not write-protected.
If the database directory is damaged, restore the databases that were cataloged there from backup versions and catalog them.

If installing the sample database, drop it and install the sample database again.

sqlcode: -1039

sqlstate: 58031

SQL1040N

The statement failed because the maximum number of applications are already connected to the database.

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.

Respond to this message in one of the following ways:

Wait for other applications to disconnect from the database, and then resubmit the statement.
If more applications are required to run concurrently, increase the value of the maxappls database configuration parameter or set maxappls to "AUTOMATIC".

sqlcode: -1040

sqlstate: 57030

SQL1041N

The maximum number of concurrent databases have already been started.

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.

Wait for one of the databases to become inactive. If more databases are required to be active at the same time, increase the value for numdb. The new value takes effect after the next successful database manager start.

sqlcode: -1041

sqlstate: 57032

SQL1042C

An unexpected system error occurred.

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.

To update the instance to acquire a configuration or access to function run DB2IUPDT <InstName>.
If the error occurred while trying to connect to a database, get a trace (instructions below) and call IBM support.

If the problem falls outside of these suggestions, ensure that the system time and date is correctly set, and make sure your system has enough memory and swapping/paging space available.

Resubmit the current command.

If the error continues, stop the database manager and restart it.

If the error still continues, reinstall the database manager.

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Contact your technical service representative with the following information:

Required information:

Problem description
SQLCODE or message number
SQLCA contents if possible
Trace file if possible.

Federated system users: if necessary isolate the problem to the data source rejecting the request. If the problem is with a data source follow the problem determination procedures for that data source.

sqlcode: -1042

sqlstate: 58004

SQL1043C

Database Services could not initialize the system catalogs. Error error was returned.

The CREATE DATABASE command failed while initializing the system catalogs.

Record the message number (SQLCODE) and error in this message.

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Then contact your technical service representative with the following information:

Environment: Application
Required information:
- Problem description
- SQLCODE or message number and error identifier
- SQLCA contents if possible
- Trace file if possible.

SQL1044N

Processing was cancelled due to an interrupt.

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.

Continue processing to handle the interrupt.

If installing the sample database, drop it and install the sample database again.

If starting the database manager, issue a db2stop before issuing any db2 commands.

sqlcode: -1044

sqlstate: 57014

SQL1045N

The database was not found because it was not cataloged correctly.

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

The command cannot be processed.

Verify the entries in all the associated database directories with the directory scan commands.

sqlcode: -1045

sqlstate: 58031

SQL1046N

The authorization ID is not valid.

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.

Log on with a valid authorization ID.

Federated system users: if necessary isolate the problem to the data source rejecting the request and use an authorization ID valid for that data source.

sqlcode: -1046

sqlstate: 28000

SQL1047N

The application is already connected to another database.

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.

Disconnect from the active database and resubmit the command.

SQL1048N

The use parameter parameter in the START USING DATABASE or CONNECT TO command is not valid. It must be an S for shared access, an X for exclusive use or an N for exclusive use at single node. For DB2 Connect connections, only S is supported. N is only supported in MPP configuration.

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.

Resubmit the command with a valid use parameter (preferably from the mnemonic equates).

SQL1049C

The application state is in error. The database connection has been lost.

The connection to the database has been lost.

The command cannot be processed.

Issue a CONNECT RESET statement.

SQL1050N

The database cannot be uncataloged because it is a home database.

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.

Continue processing if the database name was specified correctly.

SQL1051N

The path path does not exist or is not valid.

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.
An attempt is being made to add a remote storage group with more than one storage path or to add a storage path to an existing remote storage group.
When enabling a control file recovery path for the first time, the control file recovery path does not exist.
When enabling a control file recovery path for the first time, one or both of the global and member recovery database directories already exist in the control file recovery path.
When enabling a control file recovery path for the first time, the control file recovery path overlaps with CREATE DATABASE.
When enabling a control file recovery path for the first time, the recovery database directory overlaps with an existing recovery database directory for a different database.
With a previously activated control file recovery path, there are missing or inconsistent recovery control files in the control file recovery database directories, or one or both of the global and member recovery database directories do not exist on activation.

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.

Depending on the condition:

Create the path if it does not exist, or change the permissions of the path if it is inaccessible. Resubmit the statement or command.
Use characters that conform to naming rules for database directory and storage paths.
If specifying a relative storage path name then specify its absolute path name instead. Resubmit the statement or command.
Resolve the issue with the storage path and resubmit the command. If the storage path is no longer available then the database must be restored from a backup image.
Create the storage path if it does not exist, or change the permissions of the path if it is inaccessible. Alternately, the storage paths can be redefined using the ON parameter of the RESTORE DATABASE command or by using the SET STOGROUP PATHS command.
Create the storage path if it does not exist, or change the permissions of the path if it is inaccessible. Alternately, restore the database again and redefine the storage paths associated with the database. When storage paths are redefined during a restore, all subsequent add storage path log records are ignored.
If trying to drop a storage path, ensure that it exists and is associated with the database. Then try the request again.
When using a storage group that is using remote storage, you can only specify a single storage path.
Ensure that the path specified for control file recovery exists.
Examine the contents of the existing recovery database directory, especially whether they are stale, or whether they belong to a different database. Remove the recovery database directory if possible, or specify a different control file recovery path.
Ensure that the paths for CREATE DATABASE and the control file recovery path specify different paths.
Specify a different control file recovery path.
Determine the reason for the missing or inconsistent recovery control files. Recreate the missing recovery control files or directories, or specify a different control file recovery path.

If you are using a cluster manager, correct the problem and resubmit the command:

Ensure that the path resides on a mount point that is supported in a High Availability configuration. Search for "Db2 Recommended file systems" on the IBM documentation website to see a list of all supported mount types. If the path does not need to be failed-over in the event of a failure, add it to the exclusion list by running the command "db2cm -set -option mountMonitoring <mount point> -value no".
If the previous step did not help, open the db2diag log file and look for error messages from the cluster manager.
Respond to the cluster manager error messages in the db2diag log file to correct the underlying problem that prevented the database manager from adding the path to the cluster manager configuration.
Resubmit the command.

sqlcode: -1051

sqlstate: 57019

SQL1052N

The database path path does not exist.

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.

Resubmit the command with the correct database path.

In a partitioned database environment on Windows or UNIX environments, follow the following steps:

Determine which hard drive specification (path) is required. The path is specified in the error message.
Determine which node/s of the database partition are experiencing the problem. You can usually find this information in the db2diag log file of the instance-owning node.
Correct the drive problem on the node that is experiencing the problem, or change the drive specification in the database manager configuration so that the same drive is available and has sufficient space on each node of the partitioned database group.
Re-issue the command.
On Windows if all applications that will access the database are built on at least Version 9 external APIs then the DB2_CREATE_DB_ON_PATH registry variable can be enabled to support a path as the database path.

SQL1053N

An interrupt is already being processed.

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

The interrupt request is ignored.

Wait until the current interrupt processing finishes and resubmit the command.

SQL1054N

A COMMIT is in progress and cannot be interrupted.

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.

Wait until COMMIT is finished and resubmit the request.

SQL1055N

A ROLLBACK is in progress and cannot be interrupted.

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.

Wait until ROLLBACK is finished and resubmit the request.

SQL1056N

There are already eight database directory scans open.

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

The command cannot be processed.

Issue one or more CLOSE DIRECTORY SCAN commands and resubmit the command.

sqlcode: -1056

sqlstate: 54029

SQL1057W

The system database directory is empty.

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

No action is required.

sqlcode: +1057

sqlstate: 01606

SQL1058N

The handle parameter in the Directory Scan command is not valid.

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.

Resubmit the command with a valid handle parameter.

SQL1059N

A Get Next command cannot be processed because no Open Scan command was issued.

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

The command cannot be processed.

Issue an OPEN DIRECTORY SCAN or OPEN NODE DIRECTORY SCAN command and resubmit the current command.

SQL1060N

User authorization-ID does not have the CONNECT privilege.

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.

Contact the system administrator or database administrator for the database and request a GRANT CONNECT for the authorization ID. Resubmit the command.

If this error is returned as a result of a switch user request, then until a switch user request with a valid user ID is made (the user ID that established the trusted connection or a user ID allowed on the trusted connection), if any SQL statement is issued, an error is returned (SQLSTATE 08003). The connection remains trusted when it is taken out of the unconnected state.

Federated system users: if necessary isolate the problem to the data source that rejected the request and ensure that correct privileges have been granted for that data source. Some data sources might use a different name than the CONNECT privilege for the privilege required to connect to a database.

sqlcode: -1060

sqlstate: 08004

SQL1061W

The RESTART DATABASE command completed successfully, but indoubt transactions exist against the database.

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.

Either resolve the indoubt transactions, or be prepared to restart the database whenever you wish to use it. If the transaction manager (TM) that was using the database (in an XA/DTP environment) is available, then the administrator should instruct the TM to resolve the indoubt transactions. Alternatively, with great caution, the administrator can use the CLP to heuristically complete the transactions.

In a partitioned database server environment, the RESTART DATABASE command is run on a per-partition basis. In order to ensure that the database is restarted on all partitions, use the following command:
```
db2_all db2 restart database
  <database_name>
```
Issuing this command will resolve any indoubt transactions if all database partitions are operational.

This command may have to be run several times to ensure that all indoubt transactions have been resolved.
In a DB2 pureScale environment, the user response depends on whether automatic recovery is enabled (the default). If automatic recovery is enabled, the member crash recovery will occur automatically when the database manager process model is started on any member (i.e., through a db2start command or by DB2 cluster services). If automatic recovery is not enabled, a manual member crash recovery must be initiated using the RESTART DATABASE command. In both cases, the indoubt transactions are available for resolution after member crash recovery completes.

SQL1062N

The database path path was not found.

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.

Verify the path or the default path and make sure they exist in the system. Resubmit the command.

In a partitioned database environment on Windows environments, follow the following steps:

Determine which hard drive specification (letter) is required. The drive letter is specified in the error message.
Determine which node/s of the database partition are experiencing the problem. You can usually find this information in the db2diag log file of the instance owning node.
Correct the drive problem on the individual node that is experiencing the problem or change the drive specification in the database manager configuration so that the same drive is available (and has sufficient space) on each and every node of the partitioned database group.
re-issue the command.

SQL1063N

DB2START processing was successful.

The command to start the database manager completed successfully.

SQL1064N

DB2STOP processing was successful.

The command to stop the database manager completed successfully.

SQL1065W

The database was created or upgraded successfully, but an error occurred binding one or more bind files in list list-name. The file(s) in the following position(s) in the bind list file were not bound: list.

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.

Bind the indicated utilities to the database using the list of bind files list-name. Do not use the format option on the binder call.

SQL1066N

DB2START processing was successful. IPX/SPX protocol support was not successfully started.

The IPX/SPX protocol support was not successfully started. Remote clients cannot use IPX/SPX to connect to the server. Possible causes are:

The workstation is not logged in to the NetWare file server.
The workstation does not have authority to create an object in the NetWare file server bindery.
Another database manager on the network is using the same object name specified in the database manager configuration file.

Ensure that the workstation is logged in to the NetWare file server, and has sufficient authority to create an object in the bindery at the file server. The user must be logged in as SUPERVISOR or equivalent. Also ensure that the object name specified in the database manager configuration file is unique for all database managers in the network. Make any corrections, run DB2STOP, and then run DB2START again.

If the problem continues, at the operating system command prompt type DB2TRC ON -L 0X100000. Run DB2START again, then at the command prompt, type DB2TRC DUMP filename to save the trace information. To turn trace off, type DB2TRC OFF. Contact your service coordinator with the trace information.

SQL1067N

DB2STOP processing was not successful. IPX/SPX protocol support was not successfully stopped.

The IPX/SPX protocol support was not successfully stopped. Possible causes are:

The workstation is not logged in to the NetWare file server.
The workstation does not have authority to delete an object in the NetWare file server bindery.

Ensure that the workstation is logged in to the NetWare file server, and has sufficient authority to delete an object in the bindery at the file server. The user must be logged in as SUPERVISOR or equivalent. Make any corrections, and run DB2STOP again.

If the problem continues, at the operating system command prompt type DB2TRC ON -L 0X100000. Run DB2STOP again, then at the command prompt, type DB2TRC DUMP filename to save the trace information. To turn trace off, type DB2TRC OFF. Contact your service coordinator with the trace information.

SQL1068N

The domain that owns the user ID user-ID for the CONNECT or ATTACH statement is not defined in the DB2DOMAINLIST environment variable.

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

Specify the name of the domain which owns the user ID in the DB2DOMAINLIST environment variable by using the DB2SET command.

sqlcode: -1068

sqlstate: 08004

SQL1069N

The database name is not a home database.

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.

If the specified database name was incorrect, resubmit the command with the correct database name. If the specified database name was correct and the intent is to remove the database name from the database directory, use the UNCATALOG DATABASE command.

SQL1070N

The address of the database name parameter is not valid.

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.

Correct the application program so a correct address is used and the input string is null terminated.

SQL1071N

The address of the database alias name parameter is not valid.

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.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL1072C

The request failed because the database manager resources are in an inconsistent state. The database manager might have been incorrectly terminated, or another application might be using system resources in a way that conflicts with the use of system resources by the database manager.

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.

Review the db2diag diagnostic log files for more detailed diagnostic information.

Perform one or more of the following troubleshooting and resource cleanup steps, and then resubmit the request that failed:

Remove all the database manager processes running under the instance ID.
For example, on UNIX-based systems, perform the following steps:
1. List all the database manager processes running under the instance ID by issuing the db2_ps command.
2. Remove those processes by issuing the following command:
```
kill -9 <process-ID>
```
Ensure that no other application is running under the instance ID, and then remove all resources owned by the instance ID.
For example, on UNIX-based systems, perform the following steps:
1. List all IPC resources owned by the instance ID by issuing the following command:
```
ipcs | grep <instance-ID>
```
2. Remove those resources by issuing the following command:
```
ipcrm -[q|m|s] <instance-ID>
```
If you find that two instances can be started individually but cannot be active at the same time, generate new IPC keys for one of those instances by performing the following steps as the instance owner:
For single database partition instances:
1. Delete the sqllib/.ftok file.
2. Run the sqllib/bin/db2ftok command to generate a new .ftok file.
For multiple database partition instances:
1. Create another directory at the same level as sqllib.
2. Move everything from under sqllib to the new directory.
3. Delete sqllib.
4. Rename the new directory to sqllib.

SQL1073N

The node directory release number is not correct.

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

Re-catalog all the node entries and try the command again.

SQL1074N

The address of the password parameter is not valid.

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.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL1075N

The address of the database comment parameter is not valid.

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.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL1076N

The address of the count parameter is not valid.

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

The command cannot be processed.

Ensure that a valid address is used in the application program.

SQL1077N

The address of the handle parameter is not valid.

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

The command cannot be processed.

Ensure that a valid address is used in the application program.

SQL1078N

The address of the buffer parameter is not valid.

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

The command cannot be processed.

Ensure that a valid address is used in the application program.

SQL1079N

The address of the nodename parameter is not valid.

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.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL1080N

The address of the local_lu name parameter is not valid.

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.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL1081N

The address of the partner_lu name parameter is not valid.

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.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL1082N

The address of the mode parameter is not valid.

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.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL1083N

The database cannot be created because the database description block cannot be processed, reason code = reason-code.

The application issued a CREATE DATABASE command, but the database descriptor block (DBDB) could not be processed for one of the following reason codes:

1: The address of the DBDB is not valid.
2: The value of the SQLDBDID field of the DBDB is not valid. It should be set to the value SQLDBDB1.
4: The value of the SQLDBCSS field of the DBDB is not valid. When using the CREATE DATABASE CLP command, the value specified in the COLLATE USING option is invalid.
5: The collation value specified in SQLDBUDC is invalid for collation type SQL_CS_UNICODE. When using the CREATE DATABASE CLP command, the value specified in the COLLATE USING option is not valid for UTF-8 code set.
6: A database cannot be created with an explicit collation type, and implicit code set. You must either specify the code set desired, or leave collation as SQL_CS_SYSTEM. When using the CREATE DATABASE CLP command, you must either specify the code set desired with an explicit collation type, or use implicit collation without COLLATE USING option.

The command cannot be processed.

Correct the error and resubmit the command.

SQL1084C

The database manager failed to allocate shared memory because an operating system kernel memory limit has been reached.

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.

Respond to this error by performing one or more of the following troubleshooting steps:

Generate database configuration recommendations by running the following command:
```
DB2 AUTOCONFIGURE APPLY NONE
```
Increase the operating system kernel setting that limits the amount of operating system memory that is available for the database manager.
Decrease the amount of memory that the database uses by decreasing the database_memory configuration parameter.
On Linux operating systems only: the default value of some kernel configuration parameters, such as SHMMAX, are not large enough for DB2 LUW. Determine the current kernel configuration parameter settings and modify any kernel parameters that are not large enough.

If this error continues to happen after you have performed these troubleshooting steps, collect diagnostic information using the db2support utility and contact IBM software support.

sqlcode: -1084

sqlstate: 57019

SQL1085N

The application heap cannot be allocated.

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.

Possible solutions are:

Lower the size of the application heap (applheapsz) in the database configuration file.
Reduce the maximum number of applications in the database configuration file.
Remove background processes.
Install more memory.

sqlcode: -1085

sqlstate: 57019

SQL1086C

An operating system error error occurred.

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

The command cannot be processed.

Refer to the operating system user publications to determine the nature of the error.

SQL1087W

The database was created or upgraded successfully, but an error occurred while opening the list file name. The DB2 utilities are not bound to the database.

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.

Bind the utilities to the database. Do not use the format option on the binder call.

SQL1088W

The database was created or upgraded successfully but an error occurred while binding the utilities. The utilities are not bound to the database.

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.

Perform the following actions:

Bind the utilities to the database. Do not use the format option on the binder call.
Bind the db2schema.bnd file from the database server.

SQL1089W

The database was created, but the binding of the utilities was interrupted. The utilities are not bound to the database.

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.

Bind the utilities to the database. Do not use the format option on the binder call.

SQL1090C

The release number of the precompiled application program or utility is not valid.

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.

Verify that there is no older version of the database manager libraries or DLLs that will be picked up for your application processing.

If the problem persists, repeat the precompile process with the current database manager. Use only application programs precompiled with a compatible release level of the database manager.

SQL1091C

The release number of the database is unsupported.

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.

If the error occurred during a database upgrade or database restore, you must first upgrade the database to a release supported for database upgrade in the DB2 copy to which you want to upgrade.

If the error occurred the first time you connect to a database after removing a fix pack, restore the database from a backup and then issue the update database to current level command from a DB2 copy at a fix pack level that supports the database.

sqlcode: -1091

sqlstate: 08004

SQL1092N

The requested command or operation failed because the user ID does not have the authority to perform the requested command or operation. User ID: user-id.

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.

In general, respond to this error by performing the following troubleshooting steps:

Work with a system administrator or a database administrator to collect information about the privileges and authority that the given user ID has. Here is an example of one way to collect this type of information about a give user ID:
```
db2 SELECT * FROM TABLE
(SYSPROC.AUTH_LIST_GROUPS_FOR_AUTHID('<ID>'))
```
Identify the attempted operation that failed.
Compare the privileges and authority that the given user ID has with the action that was attempted.
Use a different user ID that has the required authority and privileges, or grant the user ID the required privileges by performing one or more of the following type of administrative actions:
- Add the user ID to the necessary groups
- Alter the authority or privileges of the group to which the user ID already belongs
- Specifically grant the user ID the authority to perform the action using the GRANT statement

Here are some examples of ways to respond to specific scenarios:

Windows operating systems using Kerberos

In a Windows environment in which Kerberos authentication is being used, log on to the computer with a domain account.

Windows operating systems using Extended Security

In a Windows environment with Extended Security enabled, to use or modify a database resource, take on of the following actions:

Add the user ID to the local DB2USERS group or DB2ADMNS group.
Use a user ID that is a member of the local DB2USERS group or DB2ADMNS group.

Lightweight Directory Access Protocol (LDAP) environments

In an LDAP environment, 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, enable users to catalog and uncatalog databases and nodes, or DCS and ODBC directories, without SYSADM authority using the catalog_noauth database manager configuration parameter.

The Windows command prompt

To run a command with full administrative privileges, perform the following steps:

Open a command window that is will run with full administrative privileges using the shortcut called "Command window - Administrator" that is created during the DB2 database install process.
Launch the command from the command window that is running with full administrative privileges.

Federated environments

Determine whether it is the federated server that is returning the error, or the federated data source that is returning the error, and then perform the same troubleshooting steps described in this message.

SQL1093N

The user is not logged on.

A user must be logged on before any command requiring authorization can be processed. Possible causes for this error include:

Unable to get a user ID.
An unexpected operating system error occurred when attempting to log on.
The application is running in a background process.
The user cancelled an attempted logon.

The command cannot be processed.

Log on with a valid user ID and resubmit the command. If several concurrent processes are attempting to log on, wait a few seconds and retry the logon procedure.

sqlcode: -1093

sqlstate: 51017

SQL1094N

The node directory cannot be accessed because it is being updated.

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.

Resubmit the command after the update is finished.

sqlcode: -1094

sqlstate: 57009

SQL1095N

There are already eight node directory scans open.

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

The command cannot be processed.

Issue one or more CLOSE NODE DIRECTORY SCAN commands. Resubmit the command.

sqlcode: -1095

sqlstate: 54029

SQL1096N

The command is not valid for this node type.

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.

Verify that the command and parameters are correct for the node type. Also verify that the environment where the command is to be processed is correct. Resubmit the command.

SQL1097N

The node name was not found in the node directory.

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.

Verify that the node name listed in the database directory or as the object of the attach command is cataloged in the node directory. If the node is not listed in the node directory, submit a CATALOG NODE command.

Federated system users: in addition to these actions, also verify that the node names listed in all the SYSCAT.SERVERS entries are correct. If the node is not listed in the node directory and the server is a member of the DB2 family, issue a CATALOG NODE command for that node.

sqlcode: -1097

sqlstate: 42720

SQL1098N

The application is already connected to this database.

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

The command cannot be processed.

No action is necessary.

sqlcode: -1098

sqlstate: 53056

SQL1099N

The diskette is write-protected.

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

The statement cannot be processed.

Verify you are using the correct diskette. Remove protection from the diskette, if necessary.

SQL1100W

The node name name specified in the Catalog Database command has not been cataloged in the Node Directory.

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.

Issue a CATALOG NODE command.

SQL1101N

Remote database name on node node-name could not be accessed with the specified authorization id and password.

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.

Resubmit the request with a valid authorization ID and password combination for the remote system.

sqlcode: -1101

sqlstate: 08004

SQL1102N

A database name was not specified.

No database name was provided to proceed with database upgrade.

The statement cannot be processed.

Specify a database name for upgrade.

SQL1103W

The UPGRADE DATABASE command was completed successfully.

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.

If issued on a non-HADR standby database, perform post-upgrade tasks.

If issued on an HADR standby database, issue the UPGRADE DATABASE command on the primary database.

SQL1104N

The address of the program name parameter is not valid.

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

The command cannot be processed.

Use a correct address in the application program.

SQL1105N

The SQL CONNECT RESET statement is not allowed in a Remote Application Interface procedure.

The remote application procedure contains an SQL CONNECT RESET statement.

The remote procedure is not allowed to continue.

Remove the SQL CONNECT RESET statement and retry the remote procedure.

sqlcode: -1105

sqlstate: 38003

SQL1106N

The specified DLL name module was loaded, but the function function could not be executed.

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

The command cannot be processed.

Ensure that the DLL module is built correctly. Reference the module in the definition file.

sqlcode: -1106

sqlstate: 42724

SQL1107N

An interrupt was received while loading the specified DLL name.

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

Processing is stopped.

Resubmit the command.

sqlcode: -1107

sqlstate: 42724

SQL1108N

An unexpected I/O error or operating system error was received while loading the specified DLL name.

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.

Resubmit the current command. If the error continues, reinstall the database manager.

If reinstallation does not correct the error, record the message number (SQLCODE) and all information in the SQLCA if possible.

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Then contact your technical service representative.

sqlcode: -1108

sqlstate: 42724

SQL1109N

The command was not processed because the database manager failed to load the following DLL: file-name.

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

Respond to this error by performing the following troubleshooting steps:

Identify with which product component the given library file is associated.
Verify the installation of the associated product components. (For example, the path of DB2 database libraries must be included in the environment variable LIBPATH.)

sqlcode: -1109

sqlstate: 42724

SQL1110N

A supplied data area was invalid and could not be used.

The data area is not initialized correctly.

The command cannot be processed.

Ensure that the user-supplied input SQLDA or output SQLDA fields are initialized correctly.

SQL1111N

The program name name specified was invalid.

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

The command cannot be processed.

Ensure that the DLL or program name is specified correctly.

sqlcode: -1111

sqlstate: 42724

SQL1112N

There are not enough system resources to load the specified DLL name.

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

The command cannot be processed.

Stop the application. Possible solutions are:

Change the MEMMAN NO SWAP, NO MOVE option in the CONFIG.SYS file to SWAP, MOVE.
Remove background processes.
Decrease the values of the configuration parameters that define the allocation of memory.
Install more random access memory (RAM).

sqlcode: -1112

sqlstate: 42724

SQL1113N

The data type for sqlvar n in the output SQLDA was changed from type-1 to type-2.

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.

Correct the remote stored procedure so the data type information in the output SQLDA is not changed.

sqlcode: -1113

sqlstate: 39502

SQL1114N

The data length for sqlvar n in the output SQLDA was changed from length-1 to length-2.

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.

Correct the remote stored procedure so the data length information in the output SQLDA is not changed.

sqlcode: -1114

sqlstate: 39502

SQL1115N

The number of sqlvars in the output SQLDA was changed from count-1 to count-2.

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.

Correct the remote stored procedure so the sqld field in the output SQLDA is not changed.

sqlcode: -1115

sqlstate: 39502

SQL1116N

A connection to or activation of database name failed because the database is in BACKUP PENDING state.

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

Back up the database by calling the BACKUP routine or, if roll forward recovery is not required, set the database configuration parameters LOGARCHMETH1 and LOGARCHMETH2 to OFF.

In a DB2 pureScale environment, you must perform an full offline database backup.

sqlcode: -1116

sqlstate: 57019

SQL1117N

A connection to or activation of database name cannot be made because of ROLL-FORWARD PENDING.

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.

Roll forward the database or indicate that you do not wish to roll forward by using the ROLLFORWARD command. Note that if you do not roll forward the database, the records written since the last backup of the database will not be applied to the database.

Federated system users: if necessary isolate the problem to the data source rejecting the request and take recovery action appropriate to that data source to bring the data source to a point of consistency.

sqlcode: -1117

sqlstate: 57019

SQL1118N

A connection to or activation of database name cannot be made because a previous backup is incomplete.

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.

Issue the BACKUP command and then try the command again.

Federated system users: if necessary isolate the problem to the data source rejecting the request and issue the BACKUP command against that data source prior to trying the command again.

sqlcode: -1118

sqlstate: 57019

SQL1119N

A connection to or activation of database name cannot be made because a previous restore is incomplete or still in progress.

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.

Ensure that the database has been successfully restored before trying to re-issue the current command.

Federated system users: if necessary isolate the problem to the data source rejecting the request and issue the RESTORE command against that data source prior to trying the command again.

sqlcode: -1119

sqlstate: 57019

SQL1120N

A connection to or activation of database name cannot be made because a previous backup or restore is incomplete.

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.

Issue the BACKUP or RESTORE command, and then try the command again.

Federated system users: if necessary isolate the problem to the data source rejecting the request and issue the BACKUP or RESTORE command against that data source prior to trying the command again.

sqlcode: -1120

sqlstate: 57019

SQL1121N

The address of the node structure parameter is not valid.

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.

Verify that the program allocates the required buffer area and resubmit the command.

SQL1122N

The address of the protocol structure parameter is not valid.

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.

Verify that the program allocates the required buffer area based on the protocol field in the node structure and resubmit the command.

SQL1123N

The protocol type is not valid.

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.

Verify the protocol type in the node structure and resubmit the command.

SQL1124N

The remote workstation name name is not valid.

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.

Verify the characters specified in the remote workstation name. Resubmit the command with a valid workstation name.

SQL1125N

The adapter number number is not valid.

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

The command cannot be processed.

Verify that the adapter number is valid and resubmit the command.

SQL1126N

The network ID ID is not valid.

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.

Verify the characters specified in the network ID. Resubmit the command with a valid network ID.

SQL1127N

The remote lu name name is not valid.

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.

Verify the characters specified in the remote LU name. Resubmit the command with a remote LU name.

SQL1128W

The load operation proceeded, but consistency points were not created. Reason code: reason-code.

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 into column-organized tables.
6: Consistency points are not supported when loading data into a row-organized table that retains a row length exceeding its page size.

No action is required. The load operation proceeded without using consistency points.

SQL1129N

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

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

Do one of the following:

Reduce the number of users using DB2
Increase the system process limit.

sqlcode: -1129

sqlstate: 42724

SQL1130N

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

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.

Increase the fenced_pool configuration parameter.

sqlcode: -1130

sqlstate: 42724

SQL1131N

A stored procedure process has been terminated abnormally. Routine name: routine-name. Specific name: specific-name.

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.

Respond to this error by performing the following steps:

Ensure that there are no coding errors in the stored procedure or user-defined function that could result in abnormal termination by reviewing and unit-testing the stored procedure or user-defined function code.
Ensure that other application or users will not send termination signals to the db2fmp process by reviewing the activities of all applications that are running on the system and users who are accessing the system.
Run the stored procedure again.

If this message was returned because SQLJ.INSTALL_JAR fails, add the fenced ID to the instance owner's group.

sqlcode: -1131

sqlstate: 38503

SQL1132N

The command is not allowed to execute within a stored procedure.

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

The procedure is not allowed to continue.

Remove the illegal command in the procedure and retry.

sqlcode: -1132

sqlstate: 38003

SQL1133N

A pointer address inside an sqlvar ( index = n ) of the output SQLDA was modified within the DARI (Stored Procedure) function.

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.

Correct the usage of the indicated sqlvar within the output SQLDA so that pointer addresses are not changed within the DARI (Stored Procedure) function routine.

sqlcode: -1133

sqlstate: 39502

SQL1134N

For the database authentication type CLIENT, the command is not allowed within the scope of a stored procedure.

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.

Remove the unauthorized command in the procedure and rerun the stored procedure.

sqlcode: -1134

sqlstate: 38003

SQL1135N

An invalid value was specified for the number of segments when creating a database.

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

Respecify the number of segments and try to create the database again.

SQL1136N

An invalid value was specified for the default table space extent size (dft_extentsize) when creating a database.

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.

Correct the table space extent size and try again.

SQL1137W

The database manager was unable to remove the database path or some of the containers when dropping database dbalias. Cleanup is required.

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.

System managed containers (directories) and database managed file containers may be manually removed using operating system commands. To release device containers, please call your IBM service representative for assistance.

If the log directory has been changed via the New Log Path configuration parameter, then manually unmount the log directory file system and remove the log and database directories.

If you are using a cluster manager, correct the problem and remove the path from the cluster manager configuration:

Review the db2diag log file for error messages from the cluster manager.
Respond to the cluster manager error messages in the db2diag log file to correct the underlying problem that prevented the cluster manager from removing the path from its configuration.
Remove the container paths for this database from the cluster manager configuration using the cluster manager's tools and utilities.

SQL1138W

The unique index name was migrated to support deferred uniqueness checking. A new index was not created.

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.

No action is required.

sqlcode: +1138

sqlstate: 01550

SQL1139N

The total size of the table space is too big.

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.

Check the administration notification log for details. Reduce the size of the table space and correct the SQL statement.

sqlcode: -1139

sqlstate: 54047

SQL1140W

Estimated processor cost of estimate-amount1 processor seconds (estimate-amount2 service units) in cost category cost-category exceeds a resource limit warning threshold of limit-amount service units.

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).

This warning is also issued if DB2's cost category value was "B", and the default action specified in the RLF_CATEGORY_B column in the RLST is to issue a warning.

estimate_amount1: The cost estimate (in processor seconds) if the prepared INSERT, UPDATE, DELETE or SELECT statement were to be executed.
estimate_amount2: The cost estimate (in service units) if the prepared INSERT, UPDATE, DELETE or SELECT statement were to be executed.
cost-category: DB2's cost-category for this SQL statement. The possible values are A or B.
limit-amount: The warning threshold (in service units) specified in the RLFASUWARN column of the 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.

Ensure that there is application logic to handle the warning to either allow the statement to execute or to stop the statement from being executed. If this SQLCODE was returned because the cost category value is "B", it might be that the statement is using parameter markers or that some statistics are not available for the referenced tables and columns. Make sure the administrator has run the utility RUNSTATS on the referenced tables. It might also be that UDFs will be invoked when the statement is executed, or for INSERT, UPDATE, or DELETE statements that triggers are defined on the changed table. Check the DSN_STATEMNT_TABLE or the IFCID 22 record for this statement to find the reasons this SQL statement has been put in cost category "B".

If the warning is caused by an SQL statement that is consuming too much processor resource, attempt to rewrite the statement to perform more efficiently. Another option is to ask the administrator to increase the warning threshold value in the RLST.

sqlcode: +1140

sqlstate: 01616

SQL1141N

The operation completed with errors or warnings. The details are located in the result file file-name that needs to be formatted with the db2inspf utility.

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.

Use the db2inspf utility to format the inspection data result file file-name.

SQL1142N

The operation cannot complete because the file file-name is already in use.

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

The command cannot be processed.

Resubmit the command using a different file name that is not already in use. Or remove the existing file file-name and resubmit the command.

SQL1143N

The operation cannot complete because a file error occurred for the file file-name.

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.

If possible, record all error information from the SQLCA. Look in the diagnostics log file for additional information.

In a database partitioned 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.

sqlcode: -1143

sqlstate: 5UA0A, 5UA0B

SQL1144N

The current transaction was rolled back because creating an index failed. Underlying sqlcode: sqlcode.

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.

Where possible, commit the drop of an index before creating a new index on the same table in order to avoid rolling back the entire transaction.

If the sqlcode is not 0, then refer to the message for the sqlcode for corrective action. All statements in the rolled back transaction need to be issued again. If the sqlcode is zero and the index is dropped within the savepoint scope, the statements may need to be re-ordered to create the new index before dropping the old index on the same table. If the drop and add unique or primary key constraints are in the same ALTER TABLE statement, this may need to be done in two statements, performing the ADD in the first statement and the drop in the second statement.

sqlcode: -1144

sqlstate: 40507

SQL1145N

PREPARE statement is not supported when using a gateway concentrator. Reason code: reason-code.

The statement failed for one of the following reasons, based on reason-code.

1: When gateway concentrator feature is ON, dynamically prepared statements from embedded SQL are not supported. In this configuration, dynamically prepared statements are only supported if the client is a CLI application.
2: When the gateway concentrator feature is ON, dynamically prepared SET statements are not supported.

Based on the reason code, perform the following actions:

1: Change the application to use CLI for dynamic SQL statements, or change the application to use static SQL.
2: Use EXECUTE IMMEDIATE for SET statements.

sqlcode: -1145

sqlstate: 560AF

SQL1146N

There are no indexes on table table-name.

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

Resubmit the command with a valid table name.

SQL1147W

TOTALFREESPACE is ignored for MDC and ITC tables.

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

No action required.

SQL1148N

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.

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.

Complete a database or table space backup and resubmit the query or command.

SQL1149N

CLP error clp-msg-id with short text clp-msg-short-text returned. Refer to CLP message documentation for details.

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

See the CLP message information for details on what action to take.

sqlcode: -1149

sqlstate: 5U007

SQL1150N

The address of the user id parameter is not valid.

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.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL1151N

Load REMOTEFETCH media options are invalid. Reason Code: reason-code.

The Load utility was invoked using the REMOTEFETCH media type, but one or more specified arguments is incompatible or invalid. This is due to one of the following reasons:

1: The server does not support the REMOTEFETCH media type.
2: The source database name was not specified.
3: The password field was specified without the user-id field.
4: One of the source table-name or schema fields was specified without the other.
5: Both the source table-name and source statement fields were specified.
6: Neither the source table-name nor source statement fields were specified.
7: The isolation-level specified is invalid.
8: One of the specified arguments exceeds the maximum applicable size for that argument.
9: The SQLU_REMOTEFETCH_ENTRY API structure was not setup correctly.
10: The database server does not support user defined tenant.
11: An error was encountered when accessing the input tenant name in the SQLU_REMOTEFETCH_ENTRY API structure.

The responses corresponding to each reason code are:

1: Ensure that the server level is version 9 or greater.
2: Ensure that the source database-name is specified. This field is mandatory.
3: Do not specify the password field without specifying the user-id field.
4: If providing a source table-name instead of a source query, ensure that you specify both the source table-name and schema.
5: Specify either the source table-name and schema, or the source statement, not both.
6: Specify the source table-name and schema, or the source statement.
7: Ensure that the isolation level specified is correct.
8: Ensure that the arguments provided and their length tokens (API) are all valid.
9: Ensure that the SQLU_REMOTEFETCH_ENTRY API structure is set-up and initialized correctly. Unused fields should be NULL. Length values should be set.
10: Ensure that the database server supports user defined tenant.
11: Ensure that the SQLU_REMOTEFETCH_ENTRY API structure is set-up and initialized correctly for tenant name and length.

SQL1152N

Invalid utility priority.

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

Reissue the command with a valid priority.

SQL1153N

The utility ID utility-ID does not exist.

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

Verify that the utility exists and resubmit the command. To determine if the utility has completed, review the database manager snapshot data.

SQL1154N

Unable to set the priority for a utility that does not support throttling.

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

The utility will continue to run unthrottled.

SQL1155W

A numeric value that is out of range for the data type has been replaced with the maximum or minimum value, as appropriate.

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.

See the db2diag log file for the actual values returned by the ADMIN_CMD procedure.

sqlcode: +1155

sqlstate: 01608

SQL1156N

The utility operation ID is not valid.

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.

The messages were neither retrieved nor removed from the server. Verify that the correct value was provided. The SYSPROC.ADMIN_CMD procedure returns SQL statements in the MSG_RETRIEVAL and MSG_REMOVAL columns of the first result set. They contain the operation ID that corresponds to the utility being executed. Use these SQL statements for message retrieval or removal.

sqlcode: -1156

sqlstate: 5U008

SQL1157N

The routine routine-name cannot be invoked in a trigger.

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.

Remove the routine reference from the trigger definition.

sqlcode: -1157

sqlstate: 42987

SQL1158N

The directory directory-name is restricted from access.

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.

Specify a different directory name.

sqlcode: -1158

sqlstate: 42832

SQL1159N

An error occurred during initialization of the IBM Data Server Provider for .NET. Reason Code: reason-code.

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.

Respond to this message by performing one or more of the following actions:

If this is the first time that the database product was installed on this computer, review the install logs for any possible errors and then run a repair of the database product from the Add or Remove Programs control panel applet.
If the Windows extended security feature is enabled, ensure that the application ID and user ID that uses the database product belongs to the DB2ADMNS or DB2USERS group.
Uninstall the database product and then reinstall the database product again.

If the error continues, collect the following diagnostic information and contact IBM support:

The reason code that was returned with this message
Installation logs

SQL1160N

The DOS network-protocol TSR has not been loaded.

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.

Ensure that the TSR for the specified communications protocol has been successfully loaded, then run your application again.

SQL1161W

Reconcile processing failed. DataLink column(s) not defined on DB2 DataLinks Manager(s). Check the administration notification log for details.

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.

To take the table out of DataLink Reconcile Not Possible state, follow the procedure mentioned under “Removing a table from the DataLink Reconcile Not Possible state” in the Administration Guide.

SQL1162W

Reconcile processing failed. DB2 DataLinks Manager(s) became unavailable during exception processing.

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.

Run reconcile again.

SQL1163N

The table cannot be enabled for data capture as the identifier name ident-name of type ident-type is too long.

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:

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

If data capture is to be enabled for this table than ensure that the identifiers in question do not exceed the maximum sizes indicated in the Explanation. Otherwise disable data capture for the table in order to use longer identifier names.

sqlcode: -1163

sqlstate: 42997

SQL1164N

The SQLDA or host variables, of type type, used in the SQL statement are not valid. Reason code reason-code, host variable/SQLVAR number var-number.

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.

Host variable/SQLDA types:

1: input host variable(s) or SQLDA
2: output host variable(s) or SQLDA

In SQL statements with host variables, use the host variable number to count in from the beginning of the statement (or substatement, in the case of compound SQL) to locate the invalid host variable. For statements using an SQLDA, the SQLVAR number is used to locate the invalid SQLVAR. For an input SQLDA, count only input host variables or SQLVARs; similarly for output. Note that this number is based at 1, and may not be applicable to all reason codes. Reason codes are interpreted as follows:

1: SQLDA.SQLN is less than SQLDA.SQLD
2: SQLVAR.SQLTYPE is invalid.
3: The length specified in SQLVAR.SQLLEN or SQLVAR2.SQLLONGLEN is incorrect for the SQL type given in SQLVAR.SQLTYPE.
4: A Large Object SQLVAR is present, but the SQLDOUBLED field of SQLDA.SQLDAID is not set to '2'.
5: An input varchar is supplied whose current length (from the length field of the varchar itself) is greater than the maximum length. The maximum length is determined by the declaration (in the case of a host variable) or by the setting of SQLVAR.SQLLEN (in the case of a user-defined SQLDA).
6: An input Large Object is passed in whose current length (either in the length field of the LOB itself, or as indicated by the SQLVAR2.SQLDATALEN pointer) is greater than the maximum length. The maximum length is determined by the declaration (in the case of a host variable) or by the setting of SQLVAR2.SQLLONGLEN (in the case of a user-defined SQLDA).
7: A double-byte character Large Object has an odd value indicated by the SQLVAR2.SQLDATALEN pointer, which is always in terms of bytes, even for DBCLOBs.
8: The SQLDATA pointer is invalid or points to insufficient storage.
9: The SQLIND pointer is invalid or points to insufficient storage.
10: The SQLDATALEN pointer is invalid or points to insufficient storage.
11: A specific number of input host variables/SQLVARS is expected for the current SQL statement.

The statement cannot be processed.

Examine the application program for any errors noted. Note that the programmer should not attempt to modify the precompiler output.

sqlcode: -1164

sqlstate: 07002

SQL1165W

A value cannot be assigned to a host variable because the value is not within the range of the host variable's data type.

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.

Verify that table definitions are current and that the host variable has the correct data type. For the ranges of SQL data types, refer to the SQL Reference.

sqlcode: +1165

sqlstate: 01515

SQL1166W

Division by zero was attempted.

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.

Examine the SQL statement to determine the cause of the problem. If the problem is data dependent, it is necessary to examine the data processed when the error occurred.

sqlcode: +1166

sqlstate: 01564

SQL1167W

Arithmetic overflow or other arithmetic exception occurred.

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.

Examine the SQL statement to determine the cause of the problem. If the problem is data dependent, it is necessary to examine the data processed when the error occurred. Refer to the SQL Reference to see the valid ranges for the data types.

sqlcode: +1167

sqlstate: 01519

SQL1168N

Load REMOTEFETCH media error. Reason Code: reason-code.

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.

The responses corresponding to each reason code are:

1: Ensure that the database-name, userid, and password arguments are all correct.
2: Ensure that the table-name is correct.
3: Ensure that the query is valid.
4: Ensure that the source table/query and target table have compatible column definitions.
5: Examine the db2diag log file to determine the source of the error.

SQL1169N

An error occurred while explaining the statement. Reason code = reason-code.

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:

The specified statement could not be found in the package cache.
The cached statement has not been compiled using REOPT ONCE.
The cached statement has been compiled in multiple environments with REOPT ONCE, and can't be uniquely identified.
No values could be found for the cached reoptimized statement.
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.

The user response corresponding to the reason code is:

Ensure that the statement text specified matches the statement text for the statement in the package cache.
Recompile the statement using REOPT ONCE. See the Command Reference for details.
Ensure that the statement has a unique environment with REOPT ONCE setting.
Ensure that the statement gets explained on the database partition it was originally reoptimized on.
Decide whether the required column size can be accommodated in your table and database. If it can, increase the column size using the ALTER TABLE statement.

sqlcode: -1169

sqlstate: 560C9

SQL1170N

The operation cannot continue because database partition dbpartition is not available.

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.

Resubmit the BACKUP or RESTORE command after the database partition becomes available. If the unavailable database partition cannot be made available, resubmit the RESTORE command without specifying the new storage paths, or exclude the database partition from the BACKUP command.

sqlcode: -1170

sqlstate: 5U013

SQL1171N

Maximum number of storage paths has been reached.

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.

If this error occurred as part of a CREATE DATABASE command then too many storage paths were specified. Reduce the number of storage paths and re-issue the command.

If this error occurred as part of an ALTER STOGROUP statement then either there were more than the maximum allowed number of paths specified, or the number of paths specified plus the number of paths already in use by this storage group is greater than the maximum. Decrease the number of storage paths specified in the ALTER statement and resubmit it.

sqlcode: -1171

sqlstate: 5U009

SQL1172N

The restore operation on a non-catalog database partition cannot specify automatic storage paths.

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

Either perform the restore operation again without specifying a list of storage paths, or first restore the catalog partition using the new list of storage paths.

sqlcode: -1172

sqlstate: 5U010

SQL1173N

The restore operation must specify automatic storage paths.

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.

Perform the restore operation again, specifying a list of automatic storage paths.

sqlcode: -1173

sqlstate: 5U011

SQL1174N

Invalid or incorrect use of database partition expression in path path. Reason code = reason-code.

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.

Remove the database partition expression from the database path. Alternatively, if the database path is being derived from the first storage path in the list, explicitly provide a database path using the DBPATH ON option where the given database path does not contain a database partition expression. Correct the database partition expression. Resubmit the command.

sqlcode: -1174

sqlstate: 5U012

SQL1175I

The number of Load Partitioning Agents was reduced to optimize REMOTEFETCH execution.

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

SQL1176N

The values assigned to parameter parameter-1 and parameter parameter-2 are incompatible.

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

Modify one of the parameters and resubmit the command. See the Command or API Reference for more information on valid values.

SQL1177N

Run time execution of routine routine-name (specific name specific-name) failed in the current database server environment.

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.

Please create the OLE, OLEDB or CLR routine on a database server in a Windows operating system environment and try again to invoke the routine from that database server.

sqlcode: -1177

sqlstate: 42997

SQL1178N

The federated object-type called object-name does not reference a federated database object.

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.

Remove the keyword FEDERATED from the statement.

sqlcode: -1178

sqlstate: 429BA

SQL1179W

The object-type called object-name may require the invoker to have necessary privileges on data source objects.

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.

Granting privileges to the object may not be sufficient to support operations that access the data from the data source. User access may need to be granted at the data source for the underlying data source objects.

If the object-type is PACKAGE and this message results from precompiling or binding an application, specify option FEDERATED YES on the PRECOMPILE (PREP) or BIND command.

If the object-type is PACKAGE and this message results from creating an SQL or XQuery procedure, set the precompile and bind options for SQL and XQuery procedures to include option FEDERATED YES. You set the precompile and bind options for SQL and XQuery procedures by setting registry variable DB2_SQLROUTINE_PREPOPTS or calling procedure SYSPROC.SET_ROUTINE_OPTS. For example, to set the registry variable, issue the following command at an operating system command prompt:


db2set DB2_SQLROUTINE_PREPOPTS="FEDERATED YES"

sqlcode: +1179

sqlstate: 01639

SQL1180N

Routine routine-name (specific name specific-name) has caused an OLE error. HRESULT=hresult. Diagnostic text: message-text.

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.

The following shows a partial list of error messages, HRESULTS, and possible causes. The error message text may be changed by OLE, and new error codes may be added by OLE.

Unknown interface (0x80020001):: The specified OLE object does not support the IDispatch interface.
Type mismatch (0x80020005):: One or more of the SQL data types do not match the data types of the method arguments.
Unknown name (0x80020006):: The specified method name was not found for the specified OLE object.
Invalid number of parameters (0x8002000E):: The number of arguments passed to the method is different from the number of arguments accepted by the method.
Invalid class string (0x800401F3):: The specified ProgID or CLSID is invalid.
Class not registered (0x80040154):: CLSID is not properly registered.
Application not found (0x800401F5):: Local server EXE not found.
DLL for class not found (0x800401F8):: In-process DLL not found.
Server execution failed (0x80080005):: Creation of the OLE object failed.

Consult the OLE Programmer's Reference Guide for a complete documentation, including the meaning of the special terminology.

sqlcode: -1180

sqlstate: 42724

SQL1181N

Routine routine-name (specific name specific-name) has raised an exception with description message-text.

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.

The user will need to understand the meaning of the exception. See the author of the routine.

sqlcode: -1181

sqlstate: 38501

SQL1182N

User defined function function-name could not initialize data source object of specified OLE DB provider. HRESULT=hresult. Diagnostic text: message-text.

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).

Verify proper registration of the OLE DB provider and correct initialization of the parameters in the connection string. Consult Microsoft OLE DB Programmer's Reference and Data Access SDK for a complete documentation of HRESULT codes and Data Link API connection string syntax in OLE DB Core Components.

sqlcode: -1182

sqlstate: 38506

SQL1183N

User defined function function-name received an OLE DB error from specified OLE DB provider. HRESULT=hresult. Diagnostic text: message-text.

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.

Consult Microsoft OLE DB Programmer's Reference and Data Access SDK for a complete documentation of HRESULT codes.

sqlcode: -1183

sqlstate: 38506

SQL1184N

One or more EXPLAIN tables were not created using the current version of DB2.

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

Correct the definitions of the Explain tables to match the SQL Data Definition Language statements provided for the Explain tables in the EXPLAIN.DDL CLP script in the misc directory under sqllib.

If you created the Explain tables in the past using the provided script, you can either migrate the tables using the db2exmig tool or drop and re-create them with the EXPLAIN.DDL CLP script from the current version of Db2. If you have customized your Explain tables rather than using the definitions provided in the EXPLAIN.DDL file, adjust your table definitions to better match the ones in the current EXPLAIN.DDL file.

After adjusting your Explain table definitions, re-issue the command.

sqlcode: -1184

sqlstate: 55002

SQL1185N

FEDERATED value is incorrectly used in binding the package.

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.

Specify the correct FEDERATED option.

SQL1186N

The object object-type named object-name is either being altered to become a federated object, or being created as a federated object, without specifying the FEDERATED clause.

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.

To alter a non-federated view to become a federated view, specify the FEDERATED clause.

To alter a federated view that continues to be a federated view, do not specify the NOT FEDERATED clause.

To create a materialized query table in which the fullselect refers to a federated database object, either directly or indirectly, do not specify the NOT FEDERATED clause.

To create an SQL routine which refers to a federated database object, either directly or indirectly, do not specify the NOT FEDERATED clause.

sqlcode: -1186

sqlstate: 429BA

SQL1187W

The database was created or upgraded successfully but an error occurred while creating the detailed deadlocks event monitor event-monitor-name. The detailed deadlocks event monitor was not created.

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

Create a detailed deadlocks event monitor if desired.

SQL1188N

Column src-col-num of the SELECT or VALUES statement is not compatible with table column tgt-col-num. The source column has sqltype src-sqltype, and the target column has sqltype tgt-sqltype.

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.

Correct the command so that the source and target columns are compatible, and then resubmit the command.

SQL1189N

The LOAD METHOD specified is invalid for the specified file type.

An invalid METHOD was specified for the specified file type.

Resubmit the command with a different METHOD.

SQL1190N

The LOAD utility encountered SQLCODE sqlcode, SQLSTATE sqlstate, and message tokens token-list.

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

Look up the SQLCODE sqlcode in the Message Reference. Take the required corrective actions, and then resubmit the command.

SQL1191N

Column col-spec specified in the METHOD parameter does not exist.

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

Correct the invalid column specification and resubmit the command.

SQL1192W

Too many input sources were specified for the current filetype. The maximum number allowed is max-input-sources.

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

Resubmit the command with a number of input sources that does not exceed max-input-sources.

SQL1193I

The utility is beginning to load data from the SQL statement statement.

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

No action is required.

SQL1194W

The value in row row-num corresponding to target column number col-num is not valid. The row has been rejected.

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

Possible reasons are :

A numeric value is not within the minimum or maximum range of its target column.
A character value is too long for its target column.

Examine the input value. If necessary, define a new table replacing target column col-num with a more appropriately defined column and repeat the process.

SQL1195N

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

Refer to the user response for the SQLCODE returned from the operation.

SQL1196W

Backup completed successfully. However, one or more Data Links File Managers could not be contacted. The timestamp for this backup image is backup-image-timestamp.

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.

Bring up the Data Links File Managers that were unavailable during backup processing. Once all the Data Links File Managers can be contacted, the database manager will automatically complete the final verification for this backup image.

SQL1197N

Invalid value specified for keyword keyword in command command.

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.

Determine from reference documentation for the command what are valid values and make the appropriate change. If this error has been returned by an API, determine from the reference documentation for the command API what are valid values for the corresponding API option and make the appropriate change.

SQL1198N

This command is not supported in the current downlevel client-server configuration. Reason code = reason-code.

The command you have entered is not supported in your current configuration due to an incompatibility between the server and client. 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.
100: Tablespace point-in-time rollforward commands are not supported from the current client against the current database level. You must update your client to a level compatible with the current database level in order to run these commands.

The action is based on the reason code as follows:

1: Do not use scrollable cursors from a downlevel client through a gateway. Use a direct client-server connection or upgrade your client to a compatible release.
2: Do not issue utility commands from a downlevel client through a gateway. Use a direct client-server connection or upgrade your client to a compatible release.
3: Use a compatible level of gateway or configure a direct connection (non-gateway) to the server.
4: Use a compatible client level to issue V8 utility commands.
5: Use a V8 or later client to access tables, table functions and procedures that are created with the CCSID value whose corresponding code page is the different than the database code page.
6: Resubmit the rollforward to a point in time command using a V9.1 client. Alternatively, roll forward to the end of logs (instead of to a point in time).
7: Use a newer version of the API in order to proceed in the current client-server configuration.
98: Use a compatible level of client to issue this command or consider upgrading your server's level of code.
99: Use a compatible level of server to issue this command or consider upgrading your client's level of code.
100: Update your client to level compatible with the current database level and resubmit the rollforward to a point in time command.

sqlcode: -1198

sqlstate: 42997

SQL1200N

The object parameter is not valid.

The value specified for the object parameter in the COLLECT DATABASE STATUS function call is not valid. Valid values are:

SQLE_DATABASE: Status is to be collected for a single database.
SQLE_DRIVE: Status is to be collected for all LOCAL databases on a single path.
SQLE_LOCAL: Status is to be collected for all LOCAL databases.

The command cannot be processed.

Correct the object parameter and resubmit the COLLECT DATABASE STATUS function call.

SQL1201N

The status parameter is not valid.

The value specified for the status parameter in the COLLECT DATABASE STATUS function call is not valid. Valid values are:

SQLE_SYSTEM: System status is to be collected.
SQLE_DATABASE: System status and database status is to be collected.
SQLE_ALL: System status, database status and user status is to be collected.

The command cannot be processed.

Correct the status parameter and resubmit the COLLECT DATABASE STATUS function call.

SQL1202N

Status has not been collected.

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.

Correct the handle parameter and resubmit the COLLECT DATABASE STATUS function call.

SQL1203N

The database has no users connected.

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

The command cannot be processed.

Verify the database name and the connection status. Resubmit the command with a database currently being used.

SQL1204N

The code page code-page and/or territory code territory-code is not supported by the installed version of the database manager.

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.

Exit the current program and return to the operating system.

sqlcode: -1204

sqlstate: 22522

SQL1205N

The code page code-page and/or territory code territory that has been specified is not valid.

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.

Refer to the Create Database command in the Command Reference for details of valid code page and territory code pairs supported by DB2/2.

SQL1206N

PRUNE LOGFILE is not supported in this database configuration.

The PRUNE LOGFILE request is not supported if:

the database is not in recoverable mode. A database is in recoverable mode if LOGARCHMETH1 is set to DISK, TSM, VENDOR, USEREXIT, or LOGRETAIN, or if LOGARCHMETH2 is set to DISK, TSM, or VENDOR.
the active logfile path is set to a raw device.

Do not issue the PRUNE LOGFILE command for this database.

SQL1207N

Communication Manager configuration file name cannot be found.

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.

Resubmit the command with the correct configuration file name and path.

SQL1208W

The performance of the Load utility might be constrained by the available memory.

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.

If appropriate, increase the memory limits for future invocations of the Load utility.

SQL1209W

The partner_lu name name specified in the CATALOG NODE function does not exist. One was created.

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.

No action is required.

SQL1210W

Default values were returned for one or more configuration file parameters.

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.

Ensure that the DOS Requester/WINDOWS Requester configuration file exists in the appropriate path and that the parameters are explicitly defined.

SQL1211N

The computer name name is not valid.

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.

Verify that the computer name is valid and resubmit the command.

SQL1212N

The instance name name is not valid.

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.

Verify that the instance name is valid and resubmit the command.

SQL1213N

The change password LU name name is not valid.

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.

Verify the characters specified in the change password LU name.

Resubmit the command with a valid change password LU name.

SQL1214N

The transaction program name name is not valid.

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.

Verify the characters specified in the TP name.

Resubmit the command with a TP name.

SQL1215N

The LAN adapter address address is not valid.

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.

Verify the LAN adapter address.

Resubmit the command with a valid LAN adapter address.

SQL1216N

Graphic data and graphic functions are not supported for this database.

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.

Resubmit the command with valid data types.

sqlcode: -1216

sqlstate: 56031

SQL1217N

The REAL data type is not supported by the target database.

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.

Replace the declaration of any host variable that corresponds to the SQL data type of REAL with a declaration that corresponds to an SQL data type of DOUBLE in your application.

sqlcode: -1217

sqlstate: 56099

SQL1218N

There are no pages currently available in bufferpool buffpool-num.

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

The statement cannot be processed.

The bufferpool is not large enough to provide pages to all database processes or threads at this time. The bufferpool is too small or there are too many active processes or threads.

The statement may be successful if executed again. If this error occurs frequently, some or all of the following actions may prevent further failures:

increase the bufferpool size
decrease the maximum number of database agents and/or connections
decrease the maximum degree of parallelism
decrease the prefetch size for table spaces that are in this bufferpool
move some table spaces into other bufferpools.

sqlcode: -1218

sqlstate: 57011

SQL1219N

The request failed because private virtual memory could not be allocated.

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.

The problem may be corrected by:

Stopping other applications running on the machine, especially those that use large amounts of shared memory.

sqlcode: -1219

sqlstate: 57011

SQL1220N

The database manager failed to allocate shared memory.

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

Respond to this message by investigating the current memory configuration:

Set the instance_memory database manager configuration parameter to AUTOMATIC.
Validate that sufficient memory resources are available to satisfy the database manager's requirements, and those of the other programs running on the system.
On Linux 32-bit, increase the kernel parameter shmmax to 256 MB. On Linux 64-bit, increase the kernel parameter shmmax to 1GB.
Where appropriate, free system resources for the database manager to use, by stopping other programs that are using the system.

SQL1221N

The Application Support Layer heap cannot be allocated.

The Application Support Layer heap could not be allocated. The cause of this error may be insufficient memory resources either for the database manager or the environment in which its operations are being attempted. Memory resources that can cause this error include:

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

One or more of the following:

Validate that sufficient memory resources are available to satisfy the database manager's requirements, and those of the other programs running on the system.
Reduce the aslheapsz configuration parameter.
Where appropriate, stop other programs using the system.

sqlcode: -1221

sqlstate: 57011

SQL1222N

Not enough storage is available in the Application Support Layer heap to process the request.

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

Increase the aslheapsz configuration parameter.

sqlcode: -1222

sqlstate: 57011

SQL1224N

The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt.

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.

Reconnect to the database.

If the connection continues to fail, perform the following troubleshooting steps with the assistance of a database administrator:

Federated environments only: Determine whether it is a federated data source that is returning the error or the federated database server that is returning the error.
Ensure that client/server configuration is correct:
1. Confirm whether the communication subsystem (including network cables, network cards, and communication protocols such as TCP/IP) is up and running.
2. In client/server environments using the TCP/IP protocol: Assign the same port number to the TCP/IP service name on the client as the port number on the server.
Ensure the database manager is up and running:
1. Determine whether the database manager is up and running.
2. Review the db2diag log files for evidence that a database manager process was interrupted or terminated abnormally.
3. If the database manager is stopped, or if there is evidence in the diagnostic logs of any database manager agents being interrupted or terminating abnormally, restart the database manager.
Ensure that the user ID has authority:
- If the database or instance was quiesced, take one of the following actions:
  - Unquiesce the database or instance.
  - Add the user ID to the group that has CONNECT QUIESCE authority.
- In Windows operating system environments: If Extended Security is enabled, add the appropriate user ID to the local Windows security group DB2USERS or DB2ADMNS.
Remove any database directory conflicts:
1. Compare the contents of the local database directory and the system catalog to the database configuration. In particular, look for the following problems:
  - Ensure that no two databases have the same name or alias as each other.
  - Ensure that local database are cataloged as local, and that any remote databases are cataloged as remote.
2. After making any changes to the ways databases have been cataloged, stop and restart the database manager instance.
Make necessary configuration and application changes to avoid exceeding database or operating system limits:
Determine which limit was exceeded by reviewing db2diag log files, and then make one or more of the following changes:
- Reduce the chance of applications being forced off for using too much transaction log space by make one or more of the following changes:
  - Alter the application to issue more frequent commit statements.
  - Increase the max_log database configuration parameter or the num_log_span database configuration parameter.
- Reduce the chance of applications being forced off because there are insufficient coordinator agents by make one or more of the following changes:
  - Increase the value of max_coordagents relative to the value of max_connections.
  - Reduce the use of WITH HOLD cursors.
- Reduce the chance of connections being closed for being idle for too long by increasing the CONNECTIONIDLETIME threshold.
- Reduce the chance of connections being closed because a unit of work is taking too long to execute by increasing the UOWTOTALTIME threshold.
- Reduce the chance of queries timing out by increasing the SQL_ATTR_QUERY_TIMEOUT statement attribute or using the QueryTimeoutInterval CLI/ODBC configuration keyword.
- In AIX, 32-bit environments: reduce the chance of running out of AIX shared memory by making one or more of the following changes:
  - Catalog the database as a loopback data source using TCP/IP.
  - If the application is using multiple contexts with local protocol, then either reduce the number of connections in the application, or switch to another protocol, such as TCP/IP.
  - Set the EXTSHM parameter if the application supports the EXTSHM parameter and if there are sufficient memory resources to use the parameter.
Alter the application as needed to avoid unsupported usage scenarios:
- To avoid connecting to a DB2 member that is in restart light mode, either specify a member that is not in restart light mode, or do not specify any specific member and allow the database manager to route the connection to an appropriate member.
For DB2 for z/OS servers: collect server diagnostics, such as a z/OS SVC dump, for the application identifier that is reported as the connection correlation token (CRRTKN) and the logical unit of work ID (LUWID) in the z/OS diagnostic messages.

In a DB2 pureScale environment, if a new member has been added you must wait for the activation operation to complete until you open subsequent connections to the database from the new member. Otherwise, connect from another existing member.

sqlcode: -1224

sqlstate: 55032

SQL1225N

The request failed because an operating system process, thread, or swap space limit was reached.

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

Check the administration notification log to determine which limit was reached and increase that limit.

sqlcode: -1225

sqlstate: 57049

SQL1226N

The maximum number of client connections are already started.

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.

Wait for other applications to disconnect from the database. If one or more applications are required to run concurrently, increase the value for max_connections. If the error was returned from a client connection attempt, you might also want to consider setting max_connections to AUTOMATIC to allow any number of connections so long as there is enough memory to support them. If the value for max_connections is larger than the value for max_coordagents, the concentrator feature is turned on.

sqlcode: -1226

sqlstate: 57030

SQL1227N

The catalog statistic value for column column is out of range for its target column, has an invalid format, or is inconsistent in relation to some other statistic. Reason Code = code.

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.

Make sure the new catalog statistic satisfies the indicated range, length and format checks.

Make sure that any updates to statistics are consistent in their inter-relationships (eg. cardinality).

For tables that are not partitioned, do not attempt to update statistics columns that are specific to partitioned tables.

sqlcode: -1227

sqlstate: 23521

SQL1228W

DROP DATABASE has completed but the database alias name or database name name could not be found on num nodes.

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.

This is a warning message only. No response is necessary.

SQL1229N

The current transaction has been rolled back because of a system error.

One of the following has occurred:

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

Try the request again. If the error persists, you can find more information about the problem in the administration notification log. It might be necessary to contact the system administrator for assistance since the most common reason for this error is that a member has failed.
In an environment where the netname and the hostname that are defined in the db2nodes.cfg file are different, this error can be a symptom of a failure in the netname interface. This applies to both multi-partition database environments and DB2 pureScale environments.
Update the service ports to be the same on all the members and try the request again.

The sixth sqlerrd field of the SQLCA will indicate the member number that detected the member failure. On the member that detected the failure, a message will be placed in the db2diag log file that identifies the member that failed.

sqlcode: -1229

sqlstate: 40504

SQL1230W

At least one agent id specified could not be forced.

At least one agent id specified on the Force command could not be forced. Causes of this warning may be:

A nonexistent or invalid agent id was specified.
The agent disconnected from the database manager between the time that the agent ids were collected and the Force command was issued.
The agent id specified was for a parallel agent which cannot be forced.

If a nonexistent or invalid agent id was specified, retry the command using the valid agent id.

SQL1231N

Invalid Force count specified.

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.

Correct the value of count and resubmit the command.

SQL1232N

Invalid Force mode specified.

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.

Set the mode to SQL_ASYNCH and resubmit the command.

SQL1233N

The statement failed because the statement includes the use of functionality that is supported only in Unicode databases or Unicode databases with specific database collations, but the current database is not a Unicode database or is a Unicode database with unsupported database collations.

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.

The following functionality is supported only for Unicode databases with IDENTITY or IDENTITY_16BIT collation:

Column-organized tables.

Respond to the following message by performing one of the following actions:

Re-issue the statement without the functionality that is only supported in Unicode databases or Unicode databases with specific collations.
Re-create the database as a Unicode database or Unicode databases with a supported collation and then re-issue the statement.

sqlcode: -1233

sqlstate: 560AA

SQL1234N

The table space tablespace-name cannot be converted to a LARGE table space.

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.

Verify the attributes of the table space by issuing SELECT TBSPACE, TBSPACETYPE, DATATYPE FROM SYSCAT.TABLESPACES WHERE TBSPACE = 'tablespace-name'. The table space cannot be the system catalog table space (TBSPACE cannot be 'SYSCATSPACE'), must be a DMS table space (TBSPACETYPE must be 'D'), and also must be a REGULAR table space (DATATYPE must be 'A').

sqlcode: -1234

sqlstate: 560CF

SQL1235N

The table space tablespace-name is restricted by table table-name from being converted to be a LARGE table space.

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.

To successfully convert the table spaces of the partitioned table:

For each table space containing data partitions of the partitioned table (except for one of the table spaces), detach the data partitions in these table spaces from the partitioned table. Commit the detach actions.
Convert each of these table spaces using the COVERT TO LARGE option of the ALTER TABLESPACE statement. Commit each statement.
Convert the table space containing the remaining data partitions of the partitioned table. Commit this action.
Rebuild the indexes on the partitioned table using REORG INDEXES ALL FOR TABLE table-name ALLOW NO ACCESS, or by reorganizing the partitioned table.
Reorganize each new table resulting from the detach of data partitions.
Re-attach each table to the partitioned table.

sqlcode: -1235

sqlstate: 560CF

SQL1236N

The REORG command failed. Table table-name cannot allocate a new page because the index with identifier index-id does not yet support large RIDs.

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.

The indexes can be reorganized using the rebuild option of the REORG INDEXES ALL FOR TABLE table-name command. For partitioned tables, ALLOW NO ACCESS must be specified. Alternatively, the table can be reorganized (REORG TABLE without the INPLACE clause) which will not only rebuild all indexes, but will enable the table to support greater than 255 rows per page.

sqlcode: -1236

sqlstate: 55066

SQL1237W

Table space tbspace-name is being converted from REGULAR to LARGE. Indexes on tables in this table space must be reorganized or rebuilt to support large RIDs.

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.

The documentation for the ALTER TABLESPACE statement in the SQL Reference specifies the best practices when using the CONVERT TO LARGE option. Please follow these recommendations to be pro-active in reorganizing or rebuilding all indexes on all tables in this table space to prevent possible future failures when a page number above 0x00FFFFFF is allocated to a table.

sqlcode: +1237

sqlstate: 01686

SQL1238N

The result set specified to be returned to the client is invalid. Reason code = reason-code.

The result set specified by the WITH RETURN TO CLIENT clause in the CREATE PROCEDURE (Sourced) statement is not valid. Possible reason codes are:

1: If the data source is Microsoft SQL Server, Sybase, or Informix, the result set specified by the position number in the returned set of result sets in the WITH RETURN TO CLIENT clause in the CREATE PROCEDURE (Sourced) statement is not equal to 1.
2: If the data source is Oracle, the largest position number in the returned set of result sets in the WITH RETURN TO CLIENT clause in the CREATE PROCEDURE (Sourced) statement is greater than the maximum number of REF CURSORS at the data source.

Actions based on the reason codes are:

1: Remove references to any position number in the returned set of result sets other than 1.
2: Remove references to any position number in the returned set of result sets which is greater than the maximum number of REF CURSORS at the data source.

sqlcode: -1238

sqlstate: 560CI

SQL1239N

On database servers Version 9.5 and earlier, pureXML data store features can be used only in a single-partition database.

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.

On database servers Version 9.5 and earlier, for a database with multiple database partitions, you can input XML data to those functions that accept XML input and either store the output of the function in the database or return it to the application. In this case, to use the features of pureXML storage you need to create a new database in a separate instance in which the database partitioning feature is not used. Similarly, to use the database partitioning feature you must either use a database on which pureXML storage features have not been used, or you need to create a new database in a separate, partitioned database environment.

sqlcode: -1239

sqlstate: 42997

SQL1240N

The maximum number of quiescers has been reached.

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

Wait for one of the processes to release its quiesce state and try again.

SQL1241N

An invalid value was specified for the tbs-name table space definition when creating a database. Attribute is string.

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

Correct the create database request.

SQL1242N

An XML feature is not supported in the context where it is used. Reason code = reason-code.

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.

The action is based on the reason code, as follows:

1

On database servers Version 9.5 and earlier, do not use the XML data type for any column defined in a table that is organized by dimensions.

2

On database servers Version 9.5 and earlier, do not use the XML data type for any column defined in a partitioned table.

3

Use the REORG INDEXES ALL command with the CONVERT parameter to convert existing indexes on the table to type-2 indexes before issuing the ALTER TABLE command to add a column of type XML.

4

Change the table definition to avoid having both a distribution key and an XML column. In a CREATE TABLE statement, you can do this by removing the DISTRIBUTE BY clause (or PARTITIONING KEY clause) or by removing all columns of data type XML. In an ALTER TABLE statement, either drop the distribution key before adding a column of type XML or drop all XML columns before adding a distribution key.

5

Do not specify a view with columns of data type XML as the target of an INSTEAD OF trigger.

6

Do not use transition variables that are of data type XML in a trigger definition.

7

For a table containing multiple columns of data type XML, either do not drop any XML columns or drop all of the XML columns in the table using a single ALTER TABLE statement.

On database servers Version 9.5 and earlier, remove any REORG-recommended alterations from the ALTER TABLE statement.

8

In the nickname definition, check for columns of type XML that have column options. For each column definition that is not correct, change the data type, or remove all column options.

9

Remove the XML data type or value reference from the compound SQL (compiled) statement or include the compound SQL (compiled) statement in an SQL procedure.

100

To create a table with XML columns, create the table in the IBMCATGROUP database partition.

101

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

If this message was returned because an attempt was made to add a new database partition to a database partition group that contains tables that have XML columns, add the new database partition to a database partition group that does not contain tables that have XML columns.
If this message was returned because an attempt was made to redistribute data across a database partition group that contains tables that have XML columns, no response is required. Redistributing data across a database partition group that contains tables that have XML columns is not supported.

102

To decompose XML documents using annotated XML schema decomposition in a partitioned database environment, perform the decomposition on the database partition that contains the database catalog tables, the IBMCATGROUP database partition.

103

To perform XML-related actions, run the required command on the IBMCATGROUP database partition.

104

To process XML data, connect the application to the catalog partition, the IBMCATGROUP database partition.

105

To use the SQL function in a partitioned database environment, alter the function to remove any parameters and variables of type XML.

sqlcode: -1242

sqlstate: 42997

SQL1243W

Dropping SYSTOOLS.DB2LOOK_INFO db2look operation table failed.

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.

Check the definition of the SYSTOOLS.DB2LOOK_INFO table after the database upgrade is complete. If it is a system created table, it should be dropped manually. If it is a user created table, it should be renamed. Otherwise, ALTER TABLE and COPY SCHEMA statements will fail to execute.

SQL1244W

Disconnect for transaction manager database server-name will occur at next COMMIT.

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.

If it is necessary that the database which is acting as the TM database be disconnected immediately, issue a COMMIT statement before execution continues.

sqlcode: +1244

sqlstate: 01002

SQL1245N

Connection limit has been reached. No more connections are allowed from this client.

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

Before making any connections, set the maximum number of connections by issuing the SET CLIENT command.

sqlcode: -1245

sqlstate: 08001

SQL1246N

Connection settings cannot be changed while connections exist.

One of the following occurred:

An attempt was made to change the connection settings for an application using the SET CLIENT API. This was rejected because one or more connections exist.
The application contains both DB2 Call Level Interface API calls and calls to functions containing embedded SQL, and the connection management was not invoked using the CLI APIs.

Possible actions:

Ensure that the application disconnects from all servers before attempting to issue the SET CLIENT API (sqlesetc or sqlgsetc) or CLP command.
Ensure that all connection management requests are issued via the DB2 Call Level Interface APIs if CLI is being used by the application.

SQL1247N

Applications running in an XA transaction processing environment must use the SYNCPOINT TWOPHASE connection setting.

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.

Possible actions:

Re-precompile the application using the precompiler option SYNCPOINT TWOPHASE.
Modify the program such that the SET CLIENT API is called to set the connection option to SYNCPOINT TWOPHASE prior to any other processing.

sqlcode: -1247

sqlstate: 51025

SQL1248N

Database database-alias not defined with the transaction manager.

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.

Define the database as a resource manager to the transaction manager of your Distributed Transaction Processing environment. For example, in a CICS environment this requires adding the database to the XAD file and provides the database alias name in the XAOpen string of the XAD entry.

sqlcode: -1248

sqlstate: 42705

SQL1249N

The DATALINK data type is not supported. db-object must be dropped or altered to avoid using the DATALINK data type.

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.

Remove or update the database object identified by db-object which references the DATALINK data type before attempting to upgrade the database.

SQL1250N

A database partition is not added because XML features have been used in the instance.

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.

If any of the databases that are part of the instance are using columns of data type XML or XML schema repository objects, then a different instance will be required to establish an instance with multiple database partitions.

If the databases in the instance are not actually intended for storage of XML data, the instance must be cleansed of all references to XML data. Indicators still exist in the instance and the databases, even when there are no longer columns of data type XML and XML schema repository objects. There are two approaches to clearing the instance XML indicator and database level XML indicators.

Export non-XML data from the existing databases in the instance. Create a new instance with new databases. Import the data into the database in the new instance.
Use a password protected db2pdcfg option to change the XML indicators in the database configuration for each database within the instance and for the database manager configuration of the instance. Before this is done, it is extremely important that no database in the instance includes any columns of type XML and that the XML schema respository of each database is empty. Contact IBM Service to use this option.

SQL1251W

No data returned for heuristic query.

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

No action is required.

SQL1252N

More than one procedure was identified at the data source for the source procedure source-procedure-name specified in the CREATE PROCEDURE (Sourced) statement. Reason code = reason-code.

More than one procedure was identified at the data source for the source procedure procedure-name specified in the CREATE PROCEDURE (Sourced) statement. Possible reason codes are:

1: There are multiple source procedures at the data source with identical source procedure name and source schema name.
2: There are multiple source procedures at the data source with identical source procedure name, source schema name and NUMBER OF PARAMETERS.
3: There are multiple source procedures at the data source with identical source procedure name.

Actions based on the reason codes are:

1: Specify the NUMBER OF PARAMETERS in the CREATE PROCEDURE (Sourced) statement to help uniquely identify the procedure at the data source.
2: Specify the UNIQUE ID in the CREATE PROCEDURE (Sourced) statement to help uniquely identify the procedure at the data source.
3: Specify the source-schema-name in the CREATE PROCEDURE (Sourced) statement to help uniquely identify the procedure at the data source.

sqlcode: -1252

sqlstate: 42725

SQL1253N

The source procedure with the name source-procedure-name was not found at the data source. Reason code = reason-code.

The source procedure specified in the CREATE PROCEDURE (Sourced) statement was not found at the data source. Possible reason codes are:

1: The source object name along with the NUMBER OF PARAMETERS does not identify a procedure at the data source.
2: The source object name along with the NUMBER OF PARAMETERS and UNIQUE ID does not identify a procedure at the data source.
3: The source package name specified in the CREATE PROCEDURE (Sourced) statement is not found at the data source.
4: The source package name specified in the CREATE PROCEDURE (Sourced) statement is marked invalid at the data source
5: The source object name does not identify a procedure at the data source.
6: The source object name specifies a UNIQUE ID, but UNIQUE ID is not supported at the data source.

Actions based on the reason codes are:

1: Verify that the NUMBER OF PARAMETERS specified is correct.
2: Verify that the UNIQUE ID specified is valid for the data source and identifies a procedure at the data source.
3: Verify that the source package name specified is correct.
4: Correct the package definition at the data source.
5: Verify that the source object name specified is correct.
6: Remove the UNIQUE ID clause.

sqlcode: -1253

sqlstate: 42883

SQL1254N

The data type data-type is not supported by the federated server or data source server-name. It was used for parameter parameter-name in the procedure procedure-name.

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.

Specify a supported data type and resubmit the program.

sqlcode: -1254

sqlstate: 428C5

SQL1255N

The option value value specified for procedure procedure-name does not match the corresponding option of the source procedure.

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.

Correct the option value to match the corresponding option of the source procedure.

sqlcode: -1255

sqlstate: 428GS

SQL1256W

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

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.

Ensure that the package body of the source procedure is valid before the federated procedure is invoked.

sqlcode: +1256

sqlstate: 0168A

SQL1257N

The query must contain a predicate using the column column-name in nickname nickname.

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.

If the required column is not used in a predicate in the query, add a predicate that uses the column appropriately. If the required column is in a predicate in the query, restructure the query so that the predicate is valid. Valid predicates are listed in the documentation for the data source.

sqlcode: -1257

sqlstate: 429C0

SQL1258N

The SYSTOOLSPACE and SYSTOOLSTMPSPACE table spaces must be created in the IBMCATGROUP database partition group.

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

Resubmit the CREATE TABLESPACE command and specify the IN IBMCATGROUP clause.

sqlcode: -1258

sqlstate: 560CJ

SQL1259N

The ARCHIVE LOG command failed for database db-name on database partition partition-list due to SQLCODE SQLCODE.

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

Refer to the SQLCODE in the Message Reference for the user response and resubmit the ARCHIVE LOG command.

SQL1260N

Database name is not configured for roll-forward recovery on node(s) node-list.

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.)

Ensure that recovery is required on the specified node(s), then restore the most recent backup version of the database on these nodes.

SQL1261N

Database name is not in rollforward pending state on node(s) node-list, so it does not need to be rolled forward on these nodes.

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.)

Do the following:

Ensure that recovery is required on the specified node(s).
Restore a backup version of the database on these nodes.
Issue the ROLLFORWARD DATABASE command.

SQL1262N

The point-in-time specified for rolling forward database name is not valid.

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.

Ensure that the timestamp is entered in the correct format.

When you issue a ROLLFORWARD DATABASE command, ensure that you are not specifying a year greater than 2105.

SQL1263N

The archive log file logfile is not a valid log file for database database-name on database partition dbpartitionnum and log stream log-stream-ID.

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.)

To determine the correct archive log file, issue the ROLLFORWARD DATABASE command with the QUERY STATUS option. Move the correct archive log file into the database log directory or, if the database is in a consistent state, change the log path to point to the correct archive file, and issue the ROLLFORWARD DATABASE command again. Alternatively, reissue the command with the overflow log path pointing to the correct archive file.

SQL1264N

The archive log file logfile does not belong to database database-name on database partition dbpartitionnum and log stream log-stream-ID.

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.

To determine the first archive log file that does not belong to the database, issue the ROLLFORWARD DATABASE command with the QUERY STATUS option. To continue with rollforward recovery:

If you are using an overflow log path, verify that it applies to the correct database and contains the correct archive files.
If you are not using an overflow log path, find the correct archive log files and copy them into the database log directory.

To stop rollforward recovery, perform one of the following steps before issuing the ROLLFORWARD DATABASE...STOP command:

Remove the invalid log files from the active log path and from the archive path (including the overflow path)
Replace the invalid log files with the correct log files in the active log path and the archive path (including the overflow path)

SQL1265N

The archive log file logfile is not associated with the current log sequence for database database-name on database partition dbpartitionnum and log stream log-stream-ID.

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.

To determine the correct archive log file, issue the ROLLFORWARD DATABASE command with the QUERY STATUS option. Move the correct archive log file into the database log directory or, if the database is in a consistent state, change the log path to point to the correct archive file and issue the ROLLFORWARD DATABASE command again. Alternatively, resubmit the command with the overflow log path pointing to the correct archive file.

SQL1266N

The rollforward operation failed because the specified point-in-time value is not valid. This rollforward operation was a continuation of a previous rollforward operation. The point-in-time value specified for this rollforward operation was earlier in time than the point-in-time value specified for the previous rollforward operation. Database or table space name: database-or-table-space-name. Point-in-time value specified for the previous rollforward operation: timestamp.

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.

Respond to this error in one of the following ways:

Resubmit the ROLLFORWARD command, or db2Rollforward API, specifying a valid point-in-time value.
Resubmit the ROLLFORWARD command, or db2Rollforward API, specifying to rollforward to the end of logs.
Recover from a backup image by performing the following steps:
1. Restore the database or table space subset from a backup image.
2. Resubmit the ROLLFORWARD command, or db2Rollforward API.

SQL1267W

An integrity verification failure occurred on log file logfile for database database-name on database partition dbpartitionnum and log stream log-stream-ID which has been archived. This log file will not be usable.

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).

It is recommended to perform a full database backup operation now, in order to establish a new recovery starting point. This may help to eliminate the need for this log file should database Restore or Rollforward recovery be required. Likewise, if a db2ReadLog API (or other tools which may read archived log file data) cannot process this log file, then the application reliant on the log file data must establish a new starting point in a later log file.

SQL1268N

Rollforward recovery processing has stopped because of error error while retrieving log file logfile for database database-name on database partition dbpartitionnum and log stream log-stream-ID.

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.

Ensure that log archiving is being performed correctly by checking the administration notification log. Correct any errors and resume rollforward recovery.
If the database is configured to use log archiving through a userexit program, check the userexit diagnostic logs to determine whether an error occurred while executing the userexit program. Correct the error and resume rollforward recovery.
Ensure that the target system to which you are attempting to restore the backup image has access to the facility being used by the source system to archive its transaction logs. Make appropriate changes and resume rollforward recovery.

SQL1269N

Table space level roll-forward recovery is already running.

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.

Wait until table space level roll-forward recovery is complete. If more table spaces need recovery, initiate table space level roll-forward recovery again.

SQL1270C

The LANG environmental variable is set to string. This language is not supported.

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

Set the LANG environmental variable to a language that is supported. For more information please refer to “National Language Support” appendix in the Administration Guide.

Federated system users: see the Federated Systems Guide for NLS information.

SQL1271W

Database name is recovered but one or more table spaces are offline on members or nodes node-list.

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.

Repair or restore the table spaces if necessary and run roll-forward recovery. If the same message occurs, try running table space level roll-forward recovery offline.

SQL1272N

Table space level roll-forward recovery for database name has stopped before completion on members or nodes node-list.

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.
A table space rollforward action is not supported when it involves a database-level update operation.

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.

Check the administration notification log for the cause. Do one of the following depending on the cause:

Use the MON_GET_TABLESPACE table function to determine if the table spaces received I/O errors. If the table spaces received I/O errors, repair them.
If the transaction table became full, increase the MAXAPPLS database configuration parameter or try running table space level roll-forward recovery offline.
If the cause is an active or indoubt transaction, complete the transaction.
If the table spaces were restored after a previous table space level roll forward was interrupted, the previous table space level roll-forward is now canceled. The next table space level roll-forward command will check for table spaces in rollforward pending state.
Cancel the rollforward operation, which will put the table space in restore pending state. Before reissuing the ROLLFORWARD command, restore a table space level backup image.
Ensure that the source database level and target database level are the same.

Run table space level roll-forward recovery again.

SQL1273N

An operation reading the logs on database database-name cannot continue because of a missing log file log-file-name on database partition dbpartitionnum and log stream log-stream-ID.

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.

Recover the missing log file by taking one of the following actions:

Move the specified log file into the database log directory and restart the operation.
If an overflow log path can be specified, restart the operation with the overflow log path, specifying the path that contains the log file.

If the missing log file cannot be found, determine whether one of the following special cases applies:

If the operation is a ROLLFORWARD DATABASE command to maintain a standby system through log shipping, this error might be normal, because some files that are available on the primary site might not yet be available on the standby system. To ensure that your standby system is up-to-date, issue a ROLLFORWARD DATABASE command with the QUERY STATUS option after each rollforward operation to verify that the log replay is progressing properly. If you find that a rollforward operation on the standby system is not making progress over an extended period of time, determine why the log file that is reported as missing is not available on the standby system, and correct the problem. Note that the ARCHIVE LOG command can be used to truncate currently active log files on the primary system, making them eligible for archiving and subsequent replay on the standby system.
If a ROLLFORWARD DATABASE command with the TO END OF LOGS option was issued following a restore operation from an online backup image in which the only available logs are those that were included in the backup image, there are two possible scenarios to consider:
- Scenario 1: All of the log files contained in the backup image are found by the rollforward operation. However, the rollforward operation still looks for log files that were updated following the original backup operation. Bring the database to a consistent state by issuing the ROLLFORWARD DATABASE command with the STOP option (without the TO END OF LOGS option). To avoid this scenario in the future, use the END OF BACKUP option instead of the END OF LOGS option, because the rollforward operation will not look for log files that were updated after the backup was taken.
- Scenario 2: One or more log files that were contained in the backup image were not found by the rollforward operation. These log files are required to bring the database to a consistent state. Attempting to bring the database to a consistent state by issuing the ROLLFORWARD DATABASE command with the STOP option (without the TO END OF LOGS option) will fail with SQL1273N; recover the missing log file, as described earlier in this section.

If the missing log file cannot be recovered:

If the operation is a ROLLFORWARD DATABASE command, you can issue the ROLLFORWARD DATABASE command again with the STOP option (without the END OF LOGS option or the END OF BACKUP option) to bring the database to a consistent state. If this consistency point (immediately prior to the missing log file) is not acceptable, you can restore the database and roll forward to any point in time that is prior to the missing log file by providing an earlier time stamp to the ROLLFORWARD DATABASE command.
If the operation is a ROLLFORWARD DATABASE command with the STOP or COMPLETE option (without the END OF LOGS option or the END OF BACKUP option), the missing log file is needed to bring the database to a consistent state. Because you cannot recover the missing log file, you must restore and roll forward to an earlier point in time (as long as that point in time is not prior to the minimum recovery time).
If the operation is a call to the db2ReadLog or db2ReadLogNoConn API for the purpose of replicating data, resynchronize the replicated tables and terminate the current connection being used by the API. If the API is being used to maintain a disaster recovery site, a backup image that was created after the last time stamp in the missing log file must be restored to the disaster recovery site before any subsequent API calls can complete successfully. If the API is being used for any other purpose, terminate the connection being used by the API and deactivate the database. In all cases, restart the scan by creating a new connection to the database and calling the API with the query action. Use the nextStartLRI as the piStartLRI on the next call to the API.

SQL1274N

The database name requires roll-forward recovery and the point-in-time must be to the end of logs.

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.

For table space level roll-forward recovery, the point-in-time must be to the end of logs for one of the following reasons:

The system catalogs require roll-forward recovery. System catalogs must always be rolled forward to the end of logs to remain consistent with all other table spaces.
A table space level roll-forward to the end of logs is already in progress. To continue the roll forward, the same stoptime must be specified.
The point in time specified for a table space level roll-forward is past the end of the logs of the database. It is very likely that this time is incorrect. If this is the intended recovery stop time, resubmit the command with the END OF LOGS option.

The database is not rolled forward.

Resubmit the ROLLFORWARD command specifying ROLLFORWARD TO END OF LOGS.

SQL1275N

The stop time passed to the rollforward utility must be greater than or equal to timestamp timestamp, because database name on nodes node-list contains information later than the specified time.

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.)

Do one of the following:

Resubmit the command with a stop time greater than or equal to timestamp.
Restore an earlier backup on the specified nodes, then issue the ROLLFORWARD DATABASE command again.

SQL1276N

Database name cannot be brought out of rollforward pending state until roll-forward has passed a point in time greater than or equal to timestamp, because node node-number contains information later than the specified time.

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.)

If the stoptime specified on the ROLLFORWARD command is smaller then timestamp, resubmit the command with a stoptime greater than or equal to timestamp.

Verify that all the log files were provided. the ROLLFORWARD QUERY STATUS command shows which log file is to be processed next. Some of the reasons for missing log files include:

the log path has changed. The file can be found in the old log path.
The database manager is unable to find the log file from the archive location reflected by the current LOGARCHMETH1 or LOGARCHMETH2 database configuration parameters.

If the missing log file is found, copy it to the log path and resubmit the command.

SQL1277W

A redirected restore operation is being performed. During a table space restore, only table spaces being restored can have their paths reconfigured. During a database restore, storage group storage paths and DMS table space containers can be reconfigured.

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.

To determine the list of containers for each table space being restored, use the MON_GET_CONTAINER table function. To specify an updated list for each table space, use the SET TABLESPACE CONTAINERS command or API. This API or command lets you specify whether this should be the initial list of containers (meaning that a subsequent rollforward will redo any "add container" operations described in the database log) or the final list (meaning that the rollforward operation will not redo "add container" operations).

It is also possible that the container(s) or storage path(s) are read-only, in which case the only action required before continuing with the restore is to give read/write access to the container(s) or storage path(s).

To reconfigure the paths of specific storage groups during a database restore, use the SET STOGROUP PATHS command.

When you are ready to proceed with the restore, issue a RESTORE DATABASE command with the CONTINUE keyword to perform the actual restore.

If this warning is returned after issuing the RESTORE DATABASE command with the CONTINUE keyword then that means some table space container or storage group storage path still needs to be defined. Check the db2diag log file for more details.

SQL1278N

An operation that is reading the logs on database database-name cannot continue because of missing data in log file log-file-name on database partition dbpartitionnum and log stream log-stream-ID.

The operation can find the specified log file, but the log file is missing data. The operation found the log file in the archive, the database log directory, or the overflow log directory for the given log stream.

The operation reading the logs is now stopped. This operation is 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 is a crash recovery, then the database is now in an inconsistent state. If the operation is a rollforward operation, the operation stopped and the database is now in a rollforward pending state.

The missing log data might be the result of files being incorrectly copied, or an operating system error.

Recover the missing log file data by taking one of the following actions:

Find a complete version of the log data, move it into the database log directory, and then restart the operation.
If an overflow log path can be specified, restart the operation with the overflow log path, specifying the path that contains the log file with full data.

SQL1279W

Some indexes may not have been recreated.

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.

Examine the administration notification log to determine why the index(es) could not be recreated and correct the problem. The invalid indexes for a table will be recreated when the table is first accessed.

SQL1280N

The stoptime passed to roll-forward must be less than or equal to timestamp for database name because at least one of the table spaces was already rolled forward to this point in time.

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.

Do one of the following:

Resubmit the command with stoptime timestamp.
Restore all table spaces again, and resubmit the command with a stoptime less than timestamp.
Restore the table space backup(s) taken following the earlier table space roll-forward to point in time and resubmit the command with the same stoptime.

Time must be specified in CUT (Coordinated Universal Time).

SQL1281N

The connection to database database-alias has been severed because the pipe pipe-name has been broken.

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

Resubmit the current command. If the error continues, contact your technical service representative.

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Contact your technical service representative with the following information:

Required information:

Problem description
SQLCODE or message number
SQLCA contents, if possible
Trace file, if possible.

sqlcode: -1281

sqlstate: 40504

SQL1282N

The attempt to connect to database database-alias failed because all the pipe instances on pipe-name are busy.

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.

Increase the connection limit on the database server, or terminate some of the applications using named pipe to free up connection resources.

sqlcode: -1282

sqlstate: 08001

SQL1283N

The attempt to connect to database database-alias failed because the pipe pipe-name is in use by another process.

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

Choose a different name by setting the environment variable DB2PIPENAME, or have the other programs which use named pipe use a different pipe name.

SQL1284N

The attempt to connect to database database-alias failed because the pipe pipe-name cannot be found.

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

Start the database manager and ensure the named pipe support starts. If the named pipe support has been started, then ensure the name of the named pipe is the same between the client and server by setting the environment variable DB2PIPENAME to the same value.

sqlcode: -1284

sqlstate: 08001

SQL1285N

The attempt to connect to database database-alias failed because the pipe pipe-name is invalid.

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

The value of the environment variable DB2PIPENAME must be a valid pipe name. The pipe name must be no longer than eight characters, and has the same syntactical restrictions as a normal file name.

sqlcode: -1285

sqlstate: 08001

SQL1286N

The connection to database database-alias has been severed because the operating system ran out of resources for pipe pipe-name.

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

Free up the system resources and try again.

sqlcode: -1286

sqlstate: 40504

SQL1287N

ATTACH to instance instance failed because the named pipe pipe cannot be found.

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

Ensure that the database manager is started at the server and that the named pipe support is started. Ensure that the instance name is correct.

SQL1288N

The remote server does not support this operation.

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.

Perform this operation from a supported client.

SQL1289W

During conversion of an argument to function-name from code page from-code-page to code page to-code-page, one or more invalid characters were replaced with a substitute character, or a trailing partial multi-byte character was omitted from the result.

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.

Ensure that the data being converted does not contain invalid byte sequences.

sqlcode: +1289

sqlstate: 01517

SQL1290N

The value of either the DFT_CLIENT_COMM database manager configuration parameter or the DB2CLIENTCOMM environment variable is not valid.

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.

Correct the value and try again.

sqlcode: -1290

sqlstate: 08001

SQL1291N

A directory services error has been detected. Service: directory-services-type, API: API, function: function, error code: rc.

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:

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.

Ensure that:

The product providing the directory services is properly installed and operational.
You are logged in to the directory services with the appropriate authorization to access the directory entries, if login is required by the directory services provider, for example, DCE.

If the problem persists, consult with your system administrator and/or database administrator to determine the cause of the problem using the set of tokens provided.

sqlcode: -1291

sqlstate: 08001

SQL1292N

The global name of the database or database manager instance is invalid.

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 "/.:/".

Correct the global name and try again.

SQL1293N

An error was found in a global directory entry. Error code: error-code.

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.

Make sure the DCE subsystem is operational and that you have the appropriate privilege to read the directory entry. If the problem persists, inform the database administrator to correct the error in the directory entry.

sqlcode: -1293

sqlstate: 08001

SQL1294N

The directory path name being used for global directory access is not specified or not valid.

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.

Consult your database administrator for the correct name to use, specify it, and try again.

sqlcode: -1294

sqlstate: 08001

SQL1295N

The routing information object name being used for global directory access is not specified or not valid.

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.

Consult with your database administrator for the correct object name to use, specify it and try again.

sqlcode: -1295

sqlstate: 08001

SQL1296N

Valid values must be specified for the DIR_PATH_NAME and DIR_OBJ_NAME database manager configuration parameters if the DIR_TYPE parameter has a value other than NONE.

These three parameters are interrelated. If the DIR_TYPE value is NONE, then the other two are ignored. If the DIR_TYPE value is not NONE, then the other two must both contain valid values. The following rules apply when the DIR_TYPE value is not NONE:

The DIR_PATH_NAME and DIR_OBJ_NAME values cannot be NULL (or blanks).
If the DIR_TYPE value is DCE, then the DIR_PATH_NAME value must start with either of the special DCE strings enclosed in the following quotes: "/.../" or "/.:/".

If you want to change the DIR_TYPE value, make sure the DIR_PATH_NAME and DIR_OBJ_NAME parameters have been specified with the valid values first. If you want to blank out either the DIR_PATH_NAME or the DIR_OBJ_NAME parameter, make sure you set DIR_TYPE to NONE first.

SQL1297N

This command is currently not supported on this platform.

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

Do not use this command.

SQL1300N

Invalid DCE principal name in catalog statement.

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.

Ensure that the principal name conforms to the listed conditions, and resubmit the catalog command.

SQL1301N

An error occurred when accessing the server's DCE keytab file.

An error occurred when accessing the server's DCE keytab file. For a keytab file to be valid, the following conditions must be satisfied:

The server's keytab file exists, has the name keytab.db2, and is in the sqllib/security directory.
There is only a single entry in the keytab file.

Make sure that DCE is started. Next, check that the keytab file exists, and contains a single entry (with rgy_edit). Retry the operation.

SQL1302N

DCE principal to DB2 authorization id mapping error. Reason code: reason-code.

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.

The DCE principal must have an ERA mapping to a DB2 authorization id. Add the missing entry to the DCE registry, and retry the operation.

sqlcode: -1302

sqlstate: 08001

SQL1303N

Security daemon could not be restarted.

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.

Stop the database manager and start it again. If the db2start command fails, follow the user response for that sqlcode.

sqlcode: -1303

sqlstate: 58004

SQL1304N

The TCP/IP security type SOCKS is not valid.

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

Make sure you do not use the combination of TCP/IP protocol with security type SOCKS and authentication type DCE.

sqlcode: -1304

sqlstate: 08001

SQL1305N

An internal DCE error occurred.

Database manager processing failed due to an internal DCE error.

Make sure DCE is started. If the problem persists, contact a service representative for assistance.

sqlcode: -1305

sqlstate: 58004

SQL1306N

An invalid parameter was specified during invocation of the security audit facility. Reason Code: reason-code.

One of the parameters of the security audit API is incorrect. Reasons:

1: An invalid audit option was specified.
2: Invalid pointer to Configure/Describe sqleaucfg structure.
3: Invalid Configure/Describe parameter token.
4: Invalid Configure/Describe parameter value. The value is incorrect or outside the valid range for the parameter.
5: Invalid count specification for Configure/Describe parameter.
6: Insufficient length allocated for Configure/Describe parameter.
7: Invalid pointer to Extract sqleauextract structure.
8: Invalid Extract parameter token.
9: Invalid Extract parameter value. The value is incorrect or outside the valid range.
10: Invalid count specification for Extract parameter.
11: Invalid length for Extract parameter.
12: Invalid Archive parameter value. The value is incorrect or outside the valid range.
13: Invalid path. The length of the path is outside the valid range.
14: The use of a relative path is unsupported.

The system administrator should take specific actions for each of the reasons.

1: Provide the right option value for the audit API call by looking at the sqlutil.h include file.
2: Check to see if a valid pointer has been provided to a Configure/Describe structure.
3: The correct parameter should be specified by looking up the audit facility reference section for the sqleaucfg parameter tokens.
4: Correct the parameter value by looking up the valid values in the audit facility reference.
5: Specify the correct count and allocate/initialize the appropriate length for variable length parameters.
6: Correct the length allocated for Configure/Describe parameter based on the error token that is returned in the SQLCA.
7: Check to see if a valid pointer has been provided to a Extract structure.
8: The correct parameter should be specified by looking up the audit facility reference section for the sqleauextract parameter tokens.
9: Correct the parameter value by looking up the valid values in the audit facility reference.
10: Specify the correct count and allocate/initialize the appropriate length for variable length parameters.
11: Correct the length allocated for Extract parameter based on the error token that is returned in the SQLCA.
12: Correct the parameter value or the parameter length by looking up the valid value in the audit facility reference.
13: Provide a path with a length in the supported range.
14: Specify an absolute path.

SQL1307N

An error occurred during invocation of the security audit facility. Reason Code: reason-code.

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

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

The system administrator should take specific actions for each of the reasons.

No action required.
No action required.
Restore the configuration file from backup or issue 'audit reset' command.
Choose a different audit pathname which is within the filename length limit.
If the file permissions are incorrect,set the permissions to allow write by owner. If the filesystem is full, create free space before proceeding.
If the audit configuration file is missing, then restore it from a backup or issue the 'reset' command to initialize the file to defaults. If the directory is missing, restore from a backup or recreate the database manager instance.
Verify that file exists in the specified path. If file missing, restore from backup if available.
The audit log file is most likely corrupted. If problem persists for other audit log files, notify DB2 service.
Verify that the active log files to be archived or the archived log files to be extracted exist in the specified path.
Correct the file permissions within the file system.
An archived audit log file has been renamed to the active audit log file. The active audit log file must be renamed back to the archived audit log file.
Ensure enough disk space is available.
Check the db2diag log file for details.
Extract must be run on an archived audit log file. Archive the active audit log file before extracting from it.

SQL1308W

The audit Extract Facility completed Processing. num-records records were extracted.

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

If zero records were extracted, the user should verify that the extract pathname contains extract files and the extract parameters are correct.

SQL1309N

Invalid server principal name.

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.

Make sure that the principal name in the database catalog entry corresponds to the DCE principal being used by the database server. It may be necessary to fully qualify the principal name.

sqlcode: -1309

sqlstate: 08001

SQL1310N

The Database Connection Services directory service failed while attempting to access the Database Connection Services directory.

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.

Rerun the function after doing one of the following:

If you are adding an entry to the Database Connection Services directory, ensure that there is sufficient space for the directory file to become larger.
Ensure that no other concurrently running program is trying to access the file.
Verify that the directory file has not been damaged. If it is unrecoverable, you must erase it and recreate it or restore it from a backed-up version.

SQL1311N

The Database Connection Services directory cannot be found.

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

The function cannot be processed.

Use the CATALOG DCS DATABASE command to add an entry to the Database Connection Services directory, or restore the directory from a backed-up version.

SQL1312W

The Database Connection Services directory is empty.

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.

Use the Catalog DCS Database command to add entries to the directory or restore a backed-up version that contains entries.

SQL1313N

The Database Connection Services directory is full.

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.

Delete an entry or entries from the directory before adding any more entries.

SQL1314N

The address of the Database Connection Services directory entry parameter is not valid.

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.

Ensure that the application program has allocated the required buffer area and resubmit the command.

SQL1315N

The local database name is not valid.

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.

Ensure that the characters used in the local database name are from the database manager base character set and resubmit the command.

SQL1316N

No entry was found in the Database Connection Services directory for the specified local database name.

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.

Ensure that the local database name is correct and resubmit the command.

SQL1317N

The local database name already exists in the Database Connection Services directory.

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.

Specify a unique local database name or delete the existing entry and add the new entry.

SQL1318N

The length of element name in the input structure for parameter 1 is not valid.

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.

If an element of the directory entry structure is specified, the associated length value should represent the number of bytes in the element. Otherwise, the length value should be zero. Ensure that all the directory entry structure elements have the required specifications and lengths for the command and resubmit the command.

SQL1319N

The Database Connection Services directory entries have not been collected.

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.

Issue a request to open the directory and collect the entries. Then resubmit this command.

SQL1320N

The Database Connection Services directory cannot be accessed at this time.

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.

Wait for the current activity to complete and resubmit the command.

SQL1321N

The structure ID specified in the directory entry structure is not valid.

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

The function cannot be processed.

Verify the structure ID passed in the directory entry structure is a valid value and resubmit the command.

SQL1322N

An error occurred when writing to the audit log file.

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.

When more space is available, run the audit facility to flush out any data in memory, and to reset the auditor to a ready state.
Ensure that appropriate extracts have occurred, or a copy of the log has been made prior to pruning the log, because deleted records are not recoverable.

sqlcode: -1322

sqlstate: 58030

SQL1323N

An error occurred when accessing the audit configuration file.

db2audit.cfg could not be opened, or was invalid. Possible reasons:

The db2audit.cfg file either does not exist, or has been damaged. Take one of the following actions:
- Restore from a saved version of the file.
- Reset the audit facility configuration file by issuing the reset command from the db2audit executable.

The system administrator should take the suggested action to resolve the problem.

sqlcode: -1323

sqlstate: 57019

SQL1324N

Error converting data from nickname column schema.name.column. Reason Code: reason-code. Value: value.

A data conversion problem occurred while transferring data from or to the remote source. Possible reasons:

1: Numeric value was out of range
2: Numeric value syntax error
3: Base 64 decoding error
4: Hexbin decoding error

Check the data type mapping between the remote type and the local type. Also ensure that the remote system returns valid data.

SQL1325N

The remote database environment does not support the command or one of the command options.

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.

Do not attempt to issue this command against a host database through DB2 Connect or federated server.

SQL1326N

The file or directory name cannot be accessed.

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.

If you are using the IMPORT or EXPORT command using the ADMIN_CMD procedure, this error can be returned if a file or directory path required by the command does not match any of the restricted paths. This error can also be returned if the list of restricted paths is declared incorrectly.

Verify that any path or filename specified in the command is valid, you have the proper permissions to access the path or filename, and there is sufficient space to contain the file. Correct the problem and resubmit the command. If the problem persists, contact your System Administrator.

If you are using a cluster manager, correct the problem and resubmit the command:

Review the db2diag log file for error messages from the cluster manager.
Respond to the cluster manager error messages in the db2diag log file to correct the underlying problem that prevented the database manager from adding the path to the cluster manager configuration.
Resubmit the command.

If you are using the IMPORT or EXPORT command using the ADMIN_CMD procedure, change the file or directory path to a valid path and rerun the command. Also, verify that the list of restricted paths is declared correctly. See DB2_LOAD_RESTRICTED_IO_PATH.

SQL1327N

An implicit connection attempt failed. database-name is not a valid database name.

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.

Correct the database alias name specified by the DB2DBDFT environment variable and resubmit your command. If using the command line processor, then a "db2 terminate" should be issued prior to resubmitting the command. If you do not want an implicit connection to be performed, remove the DB2DBDFT environment variable.

sqlcode: -1327

sqlstate: 2E000

SQL1328N

An implicit connection attempt failed. The database alias name or database name name was not found in the local database directory.

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.

Correct the database alias name specified by the DB2DBDFT environment variable and resubmit the command.
If the intended action is to remove a connection while operating in a distributed unit of work environment, consider replacing the CONNECT RESET statement with a DISCONNECT or RELEASE statement.
If using the command line processor, then a "db2 terminate" should be issued prior to resubmitting the command.
If you do not want an implicit connection to be performed, remove the DB2DBDFT environment variable.

sqlcode: -1328

sqlstate: 42705

SQL1329N

The resolved path specified on the command is too long.

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.

Check that the fully resolved absolute or relative path name, including the database manager instance name, does not exceed 215 characters in length. Correct the path and resubmit the command.

SQL1330N

The symbolic destination name name is not valid.

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.

Verify that the symbolic destination name is specified and that it is not longer than 8 bytes in length. Resubmit the command with a valid symbolic destination name.

SQL1331N

The CPIC security type type is not valid.

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.

Set the security type to one of the types listed in this message and resubmit the command.

sqlcode: -1331

sqlstate: 08001

SQL1332N

The Host Name name is not valid.

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.

Verify that the host name is specified and that it is not longer than 255 characters in length. Resubmit the command with a valid host name.

SQL1333N

The Service Name name is not valid.

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.

Verify that the service name is specified and that it is not longer than 14 characters in length. Resubmit the command with a valid service name.

SQL1334N

The database server or DB2 Connect server cannot be used to route a remote request to a second database server in this configuration.

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.

Uncatalog the database at the client machine and then catalog the database specifying the node on which the database actually resides. Ensure that the node is also cataloged.

SQL1335N

The application requestor name is not valid.

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

Ensure that the characters used in the application requestor name are from the database manager base character set and resubmit the command.

SQL1336N

The remote host hostname was not found.

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.

Make sure that TCP/IP is running and that the hostname specified when cataloging the TCP/IP node is a correct name, and that it is defined in an accessible name server or in the local hosts file.

If the remote host was cataloged on this client using the CATALOG TCPIP6 NODE command but the remote host does not support IPv6, then perform the following steps: (1) Use the UNCATALOG command and (2) recatalog using the CATALOG TCPIP NODE command.

Federated system users: verify that the remote host is cataloged correctly in the SYSCAT.SERVERS view.

sqlcode: -1336

sqlstate: 08001, 08508

SQL1337N

The service service-name was not found.

The system cannot resolve the port number associated with the service-name. Possible causes are:

An incorrect service-name value was specified when the TCP/IP node was cataloged.
The correct service-name was specified, but was not defined in the client's services file.

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

Make sure that the service-name specified when cataloging the TCP/IP node is a correct name, and that it is defined in the local services file.

Federated system users must also ensure that the name is defined in the services file at the data source.

SQL1338N

The symbolic destination name symbolic-destination-name was not found.

The system cannot find the Side Information associated with the symbolic-destination-name you specified. Possible causes are:

An incorrect symbolic-destination-name value was specified when the CPIC NODE was cataloged.
The symbolic destination name and its associated side information have not been defined to the SNA communications subsystem.
The SNA communication subsystem has not been started.

Make sure that the symbolic-destination-name specified when cataloging the CPIC node is a correct name, and that it has been defined to the local SNA communication subsystem.

Start the SNA communication subsystem if it has not been started.

SQL1339N

n SQL error(s) were detected in the execution of a Not Atomic Compound SQL statement, and have the following identification: error1 error2 error3 error4 error5 error6 error7.

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.

Examine the error identification information provided. There will be <n> <errorX> tokens filled in, up to a maximum of 7. Each <errorX> represents an SQL statement error. These errors are listed in the order that they were encountered. If the message text has not been formatted, this information can be found in the second and subsequent tokens of the SQLERRMC field (tokens are separated by a one byte hexadecimal value 0xFF).

Each <errorX> is of the format PPPSSSSS where:

PPP: PPP represents the position of the statement that caused the error within the Compound SQL block, and is left-justified. For example, if the first statement failed, this field would contain the number one ("1 ").
SSSSS: SQLSTATE of the statement that failed.

More information can be found by examining the SQLCA itself. The third SQLERRD field contains the number of rows affected by the compound SQL statement, the fourth SQLERRD field contains the position of the last statement that succeeded, the 5th SQLERRD field contains the number of rows affected by referential integrity when IBM Data Server Client/DB2 Server and SQL/DS databases are accessed, and the 6th SQLERRD field contains the number of statements that failed (returned negative SQLCODES).

sqlcode: -1339

sqlstate: 56091

SQL1340N

The file server fileserver was not found.

The system cannot find the specified file server on the network. Possible causes are:

An incorrect fileserver name was specified when the IPX/SPX node was cataloged.
The correct fileserver name was specified, but the file server was not available at the time the connect was tried.

Make sure that the fileserver name specified when cataloging the IPX/SPX node is correct, and that the file server is available on the network.

SQL1341N

A workstation name must be specified in the client database manager configuration file.

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

Specify a workstation name in the client database manager configuration file.

SQL1342N

The File Server name name is missing or invalid.

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

Verify that a File Server name was specified, that the name does not contain invalid characters, and is not longer than 48 characters in length. Resubmit the command/API with a valid File Server name.

SQL1343N

The Object Name name is missing or invalid.

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

Verify that the Object Name was specified, that the name does not contain invalid characters, and is not longer then 48 characters in length. Resubmit the command/API with a valid Object Name.

SQL1344N

Orphan rows found in the system catalogs. Contact your technical service representative prior to attempting a database upgrade.

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

Contact your technical service representative. Do not attempt a database upgrade until this problem has been resolved.

SQL1345N

Execution failed due to a cluster manager error.

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.

Record the message number. Record all error information from the SQLCA, if possible. Attempt to make the necessary corrective actions based on the cluster manager return code in the db2diag log file and resubmit the command or SQL statement.

Required information:

Problem description
SQLCODE and reason code
SQLCA contents, if possible
Trace file, if possible

sqlcode: -1345

sqlstate: 58038

SQL1348W

The table space could not be reduced in size.

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

A reorg table or index operation may allow space below the high water mark to be freed, allowing a subsequent ALTER TABLESPACE ... REDUCE statement to reduce the size of the table space.

sqlcode: +1348

sqlstate: 0168J

SQL1350N

The application is not in the correct state to process this request. Reason code=rc.

Corresponding to rc:

01: The application is currently processing SQL and cannot process the utility command requested.
02: A Backup request is in progress. A warning was received from the initial utility call indicating that further requests are required before Backup can complete.
03: A Restore request is in progress. A warning was received from the initial utility call indicating that further requests are required before Restore can complete.
04: A Rollforward request is in progress. A warning was received from the initial utility call indicating that further requests are required before Rollforward can complete.
05: A Load request is in progress. A warning was received from the initial utility call indicating that further requests are required before Load can complete.
07: Federated system users: the application cannot process this command after executing SQL statements.

Corresponding to rc:

01: Complete the unit of work (using either COMMIT or ROLLBACK) before reissuing this command.
02-05: Issue the required call(s) to complete the utility in progress, then reissue this command.
07: Federated system users: the application must issue the commands after establishing a connection to the database manager but prior to any other SQL statements.

SQL1351C

No FCM channels are available.

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.

Try the request again after other processes have freed up some of this resource.

If the error persists, increase the number of FCM channels ( fcm_num_channels) specified in the database manager configuration file, then try the request again.

sqlcode: -1351

sqlstate: 57011

SQL1352N

Trusted Connection cannot be reused during a transaction.

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

Before trying to reuse a connection make sure that you perform a commit or rollback.

SQL1353N

A column option for column column-name is invalid in a transparent DDL statement. Reason code = reason-code.

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:

lob-options
unique-constraint, referential-constraint, or check-constraint
default-clause
generated-column-spec (not including the default-clause)

The statement cannot be processed.

Remove or replace the option that is invalid.

sqlcode: -1353

sqlstate: 428GO

SQL1354N

An SQL variable in routine routine-name is not available for reference due to a recent commit or rollback operation.

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.

To prevent the error from occurring, do one or more of the following:

Move the commit or rollback operation to after the SQL statement that references SQL variables or SQL parameters of data type XML.
Remove references to SQL variables or SQL parameters of data type XML that follow commit or rollback operations.
Assign values to SQL variables or SQL parameters of data type XML that will be referenced in SQL statements that follow a commit or rollback operation.
Retry the transaction if the rollback was implicit as a result of conditions such as deadlocks or system failures.

sqlcode: -1354

sqlstate: 560CE

SQL1355N

One or more values specified when retrieving alert configuration settings are invalid. Reason code: reason-code.

One or more values specified when retrieving alert configuration settings are invalid for the reason given by reason code reason-code. The possible reason codes are as follows:

1: The specified object type is invalid.
2: The specified configuration level is invalid.
3: The request to retrieve alert configuration for a particular database failed because the database name is not specified.
4: The request to retrieve alert configuration for a particular object failed because either the database name or the object name is not specified.
5: The object specified does not match the object type.
6: An object was specified but no object level settings were requested.

The action corresponding to the reason code is:

1: To retrieve alert configuration settings for the database manager, specify object type DBM, for the database, specify object type DB, for a tablespace, specify object type TS, for a tablespace container, specify object type TSC.
2: If the object type is DBM, specify configuration level D to retrieve install default settings, or specify G or O to retrieve instance level settings. If the object type is not DBM, specify configuration level D to retrieve install default settings, specify G to retrieve global level settings, or specify O for object level settings.
3: Specify the database name.
4: Ensure both the database name and the object name are specified.
5: Ensure the object specified matches the object type.
6: Specify object name only if you want to retrieve object level settings.

Resubmit the request.

sqlcode: -1355

sqlstate: 560CD

SQL1356N

The data partition cannot be detached from the table tablename.

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.

Either COMMIT or ROLLBACK the pending ATTACH transaction before detaching the partition.

SQL1357N

The specified data type is invalid as the local data type for a data type mapping from a data source. Reason code = reason-code. Altering the local type to the specified data type is not allowed.

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

The reason-code indicates which action to take.

The local data type specified is not compatible with the data type being mapped to from the data source. Specify a data type that is compatible with the one at the data source.
The specified data type is not a built-in data type. Specify an appropriate built-in data type.
The wrapper does not support the data type mapping. Specify a data type supported by the wrapper.

sqlcode: -1357

sqlstate: 42815

SQL1358N

A duplicate cursor cannot be opened.

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

Close all instances of this cursor at this nesting level.

sqlcode: -1358

sqlstate: 54064

SQL1359N

Processing of a trusted context switch user request was cancelled due to an interrupt.

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.

Continue the application. The connection must first be placed back into the connected state by issuing a valid switch user request or by terminating this connection and establishing a new one.

sqlcode: -1359

sqlstate: 51018

SQL1360N

Current processing cannot be interrupted.

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

Do not interrupt the current process.

SQL1361W

Execution time has exceeded timeout value. Do you wish to interrupt it?

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.

There are three choices: YES - interrupt now; NO - continue, don't prompt me; CANCEL - continue, same timeout.

SQL1362W

One or more of the parameters submitted for immediate modification were not changed dynamically. Client changes will not be effective until the next time the application is started or the TERMINATE command has been issued. Server changes will not be effective until the next DB2START command.

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.

To see which parameter changes took effect dynamically and which ones did not, retrieve the database manager configuration parameters and display the parameter details using the following command:

DB2 GET DBM CFG SHOW DETAIL

Changes to database manager configuration parameters can only take effect dynamically if you are attached to the instance. Not all configuration parameters support dynamic update. To see which parameters can be changed dynamically, refer to the Administration Guide.

If several parameters were submitted in a group, submit the parameters individually. In those cases where a configuration parameter could not change dynamically, do one or more of the following:

for user applications: stop and start the application
for CLP: TERMINATE and reconnect
for a server: issue DB2STOP and DB2START

SQL1363W

One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, the database must be shutdown and reactivated before the configuration parameter changes become effective.

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.

To see which parameter changes took effect dynamically and which ones did not, retrieve the database configuration parameters and display the parameter details using the following command:


DB2 GET DB CFG FOR  <database-alias> SHOW DETAIL

If the parameters were submitted in a group, resubmit the parameter updates individually.

For the configuration parameters that do not support dynamic updates, do one or more of the following:

Deactivate the database by using the DEACTIVATE DATABASE command, then reactivate it by using the ACTIVATE DATABASE command.
Rebind your packages after the new configuration parameters take effect so that the new values will be used during the bind.
Use the FLUSH PACKAGE CACHE command to invalidate dynamic statements in the SQL cache.

SQL1364W

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

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

If the parameter changes were submitted as a group, resubmit the changes individually to see which parameter changes were successful.

If only one parameter was submitted then this message indicates that the value AUTOMATIC is not supported for this parameter.

To find out which configuration parameters support the AUTOMATIC value, refer to the Administration Guide.

SQL1365N

db2start or db2stop failed in processing the plugin plugin-name. Reason code = reason-code.

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.

The user response corresponding to the reason-code is:

1: Ensure that the indicated security plug-in is located in the server-plug-in directory.
2: Check the administration notification log file for the cause of the failure. Fix the problem identified by the error message text in the administration notification log.
3: Ensure that only one Kerberos security plug-in is specified in the SRVCON_GSSPLUGIN_LIST database manager configuration parameter.
4: Specify one Kerberos security plug-in in the SRVCON_GSSPLUGIN_LIST database manager configuration parameter or do not specify Kerberos in the SRVCON_AUTH or AUTHENTICATION database manager configuration parameter.
5: Check the administration notification log file for the missing required API name. Add the missing API to the security plug-in.
6: Specify the right type of security plug-in in the appropriate database manager configuration parameter. For example, do not specify a userid-password based security plug-in for the SRVCON_GSSPLUGIN_LIST database manager configuration parameter.
7: Check the administration notification log file for the cause of the failure. Fix the problem identified by the error message text in the administration notification log.
8: Specify a valid security plug-in name. The name should not contain any directory path information.
9: Ensure that the security plug-in is using a supported version of the APIs and that it is reporting a correct version number.
10: Check the administration notification log file on the client and on the server for more information. Fix the problem identified by the error message text in the administration notification log.
11: Specify at least one GSS-API based security plug-in for the SRVCON_GSSPLUGIN_LIST database manager configuration parameter or specify a different authentication type for the SRVCON_AUTH or AUTHENTICATION database manager configuration parameter.
12: Use a library name that is compatible with the communication exit library naming rules.
13: Ensure the indicated communication exit library is located in the standard communication buffer exit library location.
14: Check the db2diag.log for messages indicating the reason that the communication exit library can not be loaded.
15: Check the db2diag.log for the missing API name. Add the missing API to the communication exit library.
16: Check the db2diag.log for any messages returned from the communication exit library. The message indicates the communication buffer exit library encountered an error, not DB2.
17: Use a version of the communication exit library that is compatible with this version of DB2.

SQL1366N

A security plug-in plugin-name processing error occurred on the client. Reason code = reason-code.

The client side security plug-in returned an error. The explanation corresponding to the reason-code is:

Required API is missing in the security plug-in.
Wrong security plug-in type.
Unable to load the client security plug-in.
Unable to unload the security plug-in.
Invalid plug-in name.
The version of the APIs reported by the security plug-in is not compatible with DB2.
Security plug-in encountered an unexpected error.
Invalid client credential.
Security plug-in received an expired credential.

The user response corresponding to the reason-code is:

Check the administration notification log file for the name of the required missing API. Add the missing API to the security plug-in.
Specify the right type of security plug-in in the appropriate database manager configuration parameter. For example, do not specify a userid-password based security plug-in for the SRVCON_GSSPLUGIN_LIST database manager configuration parameter.
Check the administration notification log file for the cause of the failure. Fix the problem identified by the error message text in the administration notification log.
Check the administration notification log file for the cause of the failure. Fix the problem identified by the error message text in the administration notification log.
Specify a valid security plug-in name. The name should not contain any directory path information.
Ensure that the security plug-in is using a supported version of the APIs and that it is reporting a correct version number.
Check the administration notification log file on the client and on the server for more information. Fix the problem identified by the error message text in the administration notification log.
Verify that the client credential (generated by db2secGenerateInitialCred or provided as an inbound delegated credential) is in a format recognized by the security plug-in. As the credential will be used to initate contexts, it must be an INITIATE or BOTH credential.
The user issuing the statement must obtain the appropriate credentials (or re-obtain their initial credentials) and then resubmit the statement.

SQL1367N

Insufficient operating system configuration for resource policy support.

Resource policy does not support the current operating system configuration.

Install the appropriate operating system level or disable the DB2_RESOURCE_POLICY registry variable.

SQL1368N

Invalid resource policy configuration.

The resource policy file is invalid.

Correct the policy definition specified by the file defined by the DB2_RESOURCE_POLICY registry variable.

Disable resource policy support by clearing the DB2_RESOURCE_POLICY registry variable or set DB2_RESOURCE_POLICY to AUTOMATIC for automatic configuration.

SQL1369N

Invalid XML document.

The current XML document is invalid.

Validate the XML document before proceeding.

SQL1370N

An attempt to quiesce instance or database name1 failed because instance or database name2 is already quiesced by user username. Quiesce type: type.

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.

Contact the user who currently has the instance or database quiesced to determine when the instance or database will no longer be quiesced, and retry the request at that time.

SQL1371W

The quiesce operation was not executed because the specified instance or database named name is already quiesced.

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.

No action is required.

SQL1372N

Cannot perform a quiesce while in a transaction.

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.

Complete the unit of work (COMMIT or ROLLBACK) and retry the request.

SQL1373W

Cannot unquiesce instance or database name, because it is not quiesced.

Unquiesce failed because the instance or database is not quiesced.

Ensure that the unquiesce is being issued for the correct instance or database.

SQL1374N

Cannot QUIESCE RESET instance or database name, because it has been quiesced by another user username.

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

Ensure that the quiesce reset is being issued for the correct instance or database.

SQL1375N

An invalid parameter was passed to the api. Parameter parm-code is in error.

parm-code indicates the parameter in error:

1: scope
2: options

The value may be out of range or invalid.

Check the syntax of the api, correct the parameter and try again.

SQL1376N

Creating or invoking a sourced procedure using a wrapper defined as fenced is not supported.

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

Submit the statement using a wrapper defined as unfenced.

sqlcode: -1376

sqlstate: 55069

SQL1377N

Creating or altering the sourced procedure is not supported at this data source.

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

Submit the statement at a supported data source.

sqlcode: -1377

sqlstate: 560CL

SQL1378N

One or more of the parameters submitted for immediate modification could not be changed dynamically and have been rolled back.

Some changes to the database manager configuration could not be applied immediately, and have been rolled back to their previous values.

To see which parameter changes were rolled back, retrieve the database manager configuration parameters and display the parameter details using the following command:

DB2 GET DBM CFG SHOW DETAIL

If several parameters were submitted in a group, submit the parameters individually to isolate the parameters that could not be updated dynamically and were rolled back. For those configuration parameters that were rolled back to their previous values, do the following:

Check the Db2 diagnostic log to determine the reason why the parameter was not able to be changed.
Correct the scenario that led to the error
Re-submit the update

SQL1379W

Database partition group partition_group has been partially redistributed. The number of tables redistributed is number, and the number of tables yet to be redistributed is number. Reason code = reason-code.

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.

Issue another redistribute request specifying the CONTINUE parameter to apply the new distribution to another specified set of tables or to the rest of the database partition group, or specify the ABORT parameter to undo the redistribution operation and return to the old distribution system.

SQL1380N

An unexpected Kerberos security error has occurred.

An unexpected Kerberos security error occurred during authentication.

No action required.

SQL1381N

The Security Support Provider Interface is not available.

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

When running under Windows operating system, ensure that the file security.dll exists under the system directory. Also ensure that SSPI is supported for the operating system that is being used.

SQL1382N

Kerberos support is not available.

Authentication failed because Kerberos support is not installed.

Ensure that Kerberos support is installed and operational, then retry the connection.

SQL1383N

The target principal name is not valid.

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

Remove the database entry that has the invalid target principal name by using the UNCATALOG DATABASE command. Re-catalog the database entry with a valid target principal name using the CATALOG DATABASE command and retry the connection.

When running in a Windows operating system environment, the target principal name is the logon account name of the DB2 service in the format of <domain name>\<user ID>.

SQL1384N

Unable to complete mutual authentication.

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

If the target principal name was specified in the CATALOG DATABASE command, ensure that the target principal name is valid for the server to which the client is attempting to connect or attach.

When running in a Windows operating system environment, the target principal name is the logon account name of the DB2 service in the format of <domain name>\<user ID>.

If the target principal name appears to be invalid, then contact IBM service for assistance.

SQL1385N

The parameter parameter has been specified improperly for the redistribute operation. Reason code = reason-code.

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.

Check the corresponding parameter based on the reason code, ensure that a valid parameter is specified, then call the utility again.

SQL1387W

A DB2 High Availability Disaster Recovery (HADR) takeover completed successfully. However, a HADR resource group remains locked; and the cluster manager is not controlling that resource group.

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.

Manually unlock the resource group so the cluster manager can control the resource group:

Review the db2diag log file for diagnostic information detailing why the database manager failed to unlock the resource group and return control of the resource group to the cluster manager.
Use the cluster manager's tools and utilities to unlock, enable, or monitor the affected resource group.

SQL1388W

An error occurred while trying to access a resource or part of a resource requested. Partial information was still returned. Details are available in the administration notification log with message message-number.

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.

The query results are not complete. Refer to the related entries in the administration notification log for more information then correct and resubmit the command. If the problem persists, contact IBM support.

SQL1389N

Table designator table-designator is not valid for the expression.

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.

Correct the syntax and resubmit the statement. Refer to DB2 SQL Reference for rules for table designator of ROW CHANGE TIMESTAMP expression and ROW CHANGE TOKEN expression, or RID and RID_BIT built-in functions.

sqlcode: -1389

sqlstate: 42703

SQL1390C

The environment variable DB2INSTANCE is not defined or is invalid.

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

Set the DB2INSTANCE environment variable to the name of the instance to use. If you do not know the name of the instance to use or how to set the DB2INSTANCE environment variable to the instance name, refer to the Administration Guide.

Federated system users: refer to the Federated Systems Guide for DB2INSTANCE information.

Ensure your PATH environment variable contains the sqllib/adm path in the home directory of the instance you want to use (for example, /u/instance/sqllib/adm, where /u/instance is the home directory of the instance owner on a UNIX system).

SQL1391N

The database is already in use by another instance of the database manager.

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.

Validate that you are using the correct database and ensure no other instance uses this database.
If the database manager was brought down abnormally, and you have a command line processor connection to it, perform a db2 terminate to close the offending open connection before attempting to connect again.

sqlcode: -1391

sqlstate: 51023

SQL1392N

Multiple instances of applications using prep,-bind,-import,-export is not supported.

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

Within WINDOWS, do not attempt to start more than 1 application that uses prep, bind, import, or export.

SQL1393C

The environment variable DB2PATH is not defined or is invalid.

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

Set the DB2PATH environment variable to the directory where the database manager is installed.

SQL1394N

The instance is not defined.

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.

Ensure that the specified instance exists and that the current user has sufficient authority to execute programs in the current instance environment. Use the db2ilist command to display the list of instances:

   db2ilist

SQL1395N

Unable to switch to another instance because the application is using multiple contexts.

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

Ensure that the application is not using multiple contexts before switching to another instance.

SQL1396N

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

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

Ensure that the application is not connected to any database or attached to any instance before switching to another instance.

SQL1397N

The DB2 service failed to logon.

DB2 service did not start due to a logon failure.

If you are starting the DB2 Administration Server, then use the DB2ADMIN SETID command to set a new logon account. If you are starting a database server on Windows, you can set the logon account for a DB2 service by using the Services dialog box from the Control Panel.

SQL1398N

The routine routine-name is not supported in a partitioned database environment.

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.

Only use the routine in a non-partitioned database environment. Instead of using the RID function, use the RID_BIT function.

sqlcode: -1398

sqlstate: 56038

SQL1399N

Operation operation-name is not valid for option option-name1 because of option option-name2 for object object-name. Reason code= reason-code.

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.

The reason codes are:

01: Option option-name1 cannot be added because option option-name2 for object object-name does not exist.
02: Option option-name1 cannot be dropped because option option-name2 for object object-name exists.

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.

The reason codes are:

01: Add option option-name2 for object object-name. Then add option option-name1.
02: Drop opotion option-name2 for object object-name. Then drop option option-name1.

SQL1400N

Authentication is not supported.

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

The command can not be processed.

The user should reissue the command with a valid parameter value.

SQL1401N

Authentication types do not match.

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.

Federated system users: this message can also appear when:

A data source is identified in SYSCAT.SERVEROPTIONS with SETTING='N' for OPTION ='PASSWORD' and the data source is not running in trusted client mode (that is, the data source expects a password)
The data source is identified in SYSCAT.SERVEROPTIONS with SETTING='Y' for OPTION ='PASSWORD' and the data source is running in trusted client mode (that is, the data source does not expect a password)
There is no server option specified for OPTION='PASSWORD' in SYSCAT.SERVEROPTIONS and the system default value for PASSWORD violates the data source password requirement.

The command can not be processed.

The user should recatalog the database alias on the client node with the same authentication type as the remote database. Resubmit the command.

Federated system users:

If the problem is that the data source requires a password but SYSCAT.SERVEROPTIONS contains SETTING='N' for OPTION='PASSWORD' for that server, alter SYSCAT.SERVEROPTIONS to reflect the true data source password requirement using the ALTER SERVER SQL statement.
If the problem is that the data source does not require a password but SYSCAT.SERVEROPTIONS contains SETTING='Y' for OPTION='PASSWORD' for that server, alter SYSCAT.SERVEROPTIONS to reflect the true data source password requirement using the ALTER SERVER SQL statement.
If the server option for OPTION='PASSWORD' is not set in SYSCAT.SERVEROPTIONS, create an entry using the CREATE SERVER SQL statement to reflect the truedata source password requirement.

sqlcode: -1401

sqlstate: 08001

SQL1402N

Unable to authenticate user due to unexpected system error.

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.

On unix-based systems, have the system administrator ensure the correct access permissions are set for db2ckpw, and that there is enough swap/paging space allocated. On Windows, ensure that the account is not locked.

SQL1403N

The username and/or password supplied is incorrect.

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.

Supply the correct username and password combination.

Federated system users: ensure that the entry in SYSCAT.USEROPTIONS contains the correct username and password for the data source being accessed.

sqlcode: -1403

sqlstate: 08004

SQL1404N

Password expired.

Your password has expired.

Change your password, then retry the request using the new password. You can use the Command Line Processor to issue the CONNECT statement or the ATTACH command to change your password.

sqlcode: -1404

sqlstate: 08004

SQL1405N

Unable to communicate with local DB2 authentication server.

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

Ensure that the DB2 authentication server is started.

SQL1406N

Shared sort memory cannot be allocated for this utility.

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

Do any of the following:

Configure the value of the SHEAPTHRES_SHR configuration parameter to allow for sorts to occur in shared memory.
Enable intra-partition parallelism by setting the INTRA_PARALLEL configuration parameter to "YES".
Activate the connection concentrator.

SQL1407N

The option-name option is incompatible with feature.

The utility does not support the option_name option with feature.

Resubmit the command using compatible options.

SQL1408N

The audit policy audit-policy is already in use for the object object-name of type object-type.

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.

Use the REPLACE option of the AUDIT statement to replace the existing audit policy with the desired audit policy.

sqlcode: -1408

sqlstate: 5U041

SQL1409N

An audit policy is not associated with the object object-name of type object-type.

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.

Verify the correct object and type was used. If that is correct, then nothing needs to be done as the association does not exist.

sqlcode: -1409

sqlstate: 5U042

SQL1410N

The SQL statement cannot be issued within an XA transaction.

One of the following statements has been issued, but it cannot be issued within an XA transaction.

CREATE, ALTER, or DROP WORKLOAD
GRANT or REVOKE USAGE ON WORKLOAD
CREATE, ALTER, or DROP SERVICE CLASS
CREATE, ALTER, or DROP WORK CLASS SET
CREATE, ALTER, or DROP WORK ACTION SET
CREATE, ALTER, or DROP THRESHOLD
CREATE, ALTER, or DROP TRUSTED CONTEXT
CREATE, ALTER, or DROP AUDIT POLICY
SET TENANT

Reissue the statement from a non-XA connection or wait until the current XA transaction is complete before reissuing the statement.

sqlcode: -1410

sqlstate: 51041

SQL1411N

The specified clause, clause, is not supported for service superclasses.

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.

Remove the unsupported clause, or specify the UNDER clause to create or alter a service subclass.

sqlcode: -1411

sqlstate: 5U043

SQL1412N

The table named table-name could not be processed. Reason: reason-code.

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.

Take the action that corresponds to the reason-code.

31

Use the procedure SYSPROC.ADMIN_MOVE_TABLE to recreate the table. The new version of the table can be distributed.

You can verify that no other table in the database partition group has XML columns that were created prior to database server Version 9.7 by performing the following steps:

Use the ADMIN_GET_TAB_INFO table function or review the administrative view SYSIBMADM.ADMINTABINFO to retrieve the XML_RECORD_TYPE information for the table.
If the value of the returned column XML_RECORD_TYPE is 2 or greater, then the redistribute utility can process the table.
If the value of XML_RECORD_TYPE is 1, then the redistribute utility cannot process the table. Use the procedure SYSPROC.ADMIN_MOVE_TABLE to recreate the table.

sqlcode: -1412

sqlstate: 55019

SQL1413N

Invalid specification of a row change timestamp column for table table-name.

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.

Correct the syntax and resubmit the statement.

sqlcode: -1413

sqlstate: 429BV

SQL1414N

Table designator table-designator is not valid for the expression.

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.

Correct the syntax and resubmit the statement. Refer to the SQL Reference for rules for table designator of ROW CHANGE TIMESTAMP expression and ROW CHANGE TOKEN expression.

sqlcode: -1414

sqlstate: 42703

SQL1415N

The statement was compiled for diagnostic purposes only and has not been executed.

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.

This error is returned to prevent further processing by the system of statements prepared using service features and is expected.

SQL1416N

Wrapper library wrapper-library-name is not compatible with the release of database product installed at the federated server. The wrapper library is compatible with the following DB2 releases list-of-DB2-releases.

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.

To determine the release and fix pack level of DB2, issue the db2level command. If necessary, install the InfoSphere Federation Server fix pack that is equivalent to the current DB2 release and fix pack level. if the wrapper requires running a script to link the fenced wrapper library, then run the linking script. Wrappers that require this are the following:

Data Source	Default Wrapper Name	Linking Script
Informix	INFORMIX	djxlinkInformix
Microsoft SQL Server	DJXMSSQL3	djxlinkMssql
Oracle	NET8	djxlinkOracle
Sybase	CTLIB	djxlinkSybase
Teradata	TERADATA	djxlinkTeradata

For more information on the linking scripts, consult the InfoSphere Federation Server Installation Guide.

sqlcode: -1416

sqlstate: 560CN

SQL1417W

Wrapper wrapper-name supports data source server versions list-of-data-source-versions. Using the wrapper with later versions might result in errors or unexpected results.

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.

Contact the data source vendor to determine if the version of the data source server that you are using is compatible with applications written for earlier versions. if the version of the data source server that you are using is compatible, the wrapper should function correctly. However, IBM did not test the wrapper with the version of the data source server that you are using. If the version of the data source server that you are using is not compatible and you continue to use the wrapper to access that version of the data source server, then errors or unexpected results will probably occur.

sqlcode: +1417

sqlstate: 0168Q

SQL1418W

Changing the database configuration parameter DECFLT_ROUNDING may have unintended consequences. The value was not changed dynamically. All applications must disconnect from this database before the changes become effective.

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.

To rectify the MQT issue, refresh any MQTs potentially impacted by rounding mode. Evaluate and correct any issues related to triggers affected by rounding mode manually.

To rectify the presence of data in a table which now violate a constraint based on the new rounding mode, use SET INTEGRITY to check for rows that violate the constraint based on the new rounding mode. To rectify the generated column issue, use SET INTEGRITY with the FORCE GENERATED option on tables with generated columns which could be affected.

Alternatively, change the rounding mode database configuration parameter (DB config parameter) DECFLT_ROUNDING back to its prior value to avoid all of the potential consequences indicated in this message.

To have the new value for the configuration parameter come into effect, disconnect all applications from this database. If the database was activated, it must be deactivated.

sqlcode: +1418

sqlstate: 0168M

SQL1419N

The statement, clause, command, API, or function is not supported in a DB2 pureScale environment. Reason code = reason-code.

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.

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.

30

The ADMIN_GET_INVISIBILITY_LIST table function is not supported in a DB2 pureScale environment.

31

The control file recovery feature is not supported in a DB2 pureScale environment.

Respond to this message according to the reason code:

1

Execute the statement again, specifying the MANAGED BY AUTOMATIC STORAGE clause.

2

No user response is required. Automatic storage should already be enabled.

3

Execute the statement again without specifying the DROP STORAGE clause.

4

Execute the statement again without specifying ON DBPARTITIONNUMS and without specifying ON DBPARTITIONNUM with a database partition other than 0.

5

No response is required. You cannot alter database partition groups in a DB2 pureScale environment.

6

Execute the CREATE TABLE statement again without specifying any of the following clauses:

ORGANIZE BY DIMENSIONS
ORGANIZE BY INSERT TIME
ORGANIZE BY KEY SEQUENCE

7

Reissue the index reorganization command without specifying the ALLOW READ ACCESS or ALLOW WRITE ACCESS clause.

9

No response is required. You cannot create or drop a database on a specified database partition in a DB2 pureScale environment.

11

Execute the statement again without specifying the unsupported clauses.

13

No response is required. You cannot use the db2ReadLogNoConn API in a DB2 pureScale environment.

14

No response is required. You cannot add or drop database partitions in a DB2 pureScale environment.

16

No response is required. You cannot use the PRUNE LOGFILE command in a DB2 pureScale environment.

17

No user response is required. You cannot use the HEALTH_MON configuration parameter in a DB2 pureScale environment.

18

Block-based buffer pools are not supported in a DB2 pureScale environment. Execute the CREATE BUFFERPOOL or ALTER BUFFERPOOL statement again without specifying the NUMBLOCKPAGES or BLOCKSIZE clause.

19

Reissue the ROLLFORWARD or RECOVER command without specifying ON DBPARTITIONNUMS or specify a database partition value of 0.

20

Before you can add a CF or member on this host you will have to remove one. For instance, if you want to add a CF you will first have to remove a member.

23

Restart the restore operation without specifying the unsupported REBUILD option.

26

Do not specify the CATALOG_DBPARTITIONNUM clause with the SET CLIENT command.

27

Do not set the value of the logsecond database configuration parameter to -1. This value configures the database with infinite active log space, which is not supported in a DB2 pureScale environment.

28

Do not specify a raw device when updating the value of the newlogpath database configuration parameter. Specify a valid path name or, as an alternative to using raw logs, use either direct input/output (DIO) or concurrent input/output (CIO).

29

Quiesce the database using the QUIESCE DATABASE command, or quiesce the database manager instance using the QUIESCE INSTANCE command.

30

Do not use the ADMIN_GET_INVISIBILITY_LIST table function in a DB2 pureScale environment.

31

No response is required. You cannot use the CTRL_FILE_RECOV_PATH database configuration parameter in a DB2 pureScale environment.

sqlcode: -1419

sqlstate: 56038

SQL1420N

Too many concatenation operators.

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

Reduce the number of concatenations in the expression and try again.

sqlcode: -1420

sqlstate: 54001

SQL1421N

MBCS conversion error occurred when converting host variable or sqlvar number to or from wchar_t format. Reason code rc.

A C/C++ application with embedded SQL statements was precompiled with the WCHARTYPE CONVERT option. At runtime, the application received an error which occurred during conversion in either wcstombs(), for input host variables, or mbstowcs(), for output host variables. The host variable or sqlvar number indicates which data item experienced the problem. Valid reason codes are:

1: the problem occurred with input data
2: the problem occurred with output data

If application data is already in MBCS format, re-precompile the application with WCHARTYPE NOCONVERT and re-build. If application data is intended to be in wchar_t format, then input data failing in wcstombs() may be corrupt. Correct the data and re-execute the application.

sqlcode: -1421

sqlstate: 22504

SQL1422N

The size of the container is invalid.

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).

Check the administration notification log for details. Then correct the SQL statement.

sqlcode: -1422

sqlstate: 54039

SQL1423N

The query includes a column with a large object data type.

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.

Change the query to exclude any column that has a data type of BLOB, CLOB or DBCLOB. This is the only possible action if the query includes a column of type BLOB. If the column (say C1) is a CLOB, you could use CAST(C1 AS LONG VARCHAR) to get the first 32700 characters. Similarly for DBCLOB column (DC1) use CAST(DC1 AS LONG VARGRAPHIC) to get the first 16350 characters. If the application code can be changed, code can be added to change the SQLDA to use LONG VARCHAR or LONG VARGRAPHIC for CLOB and DBCLOB.

sqlcode: -1423

sqlstate: 56093

SQL1424N

Too many references to transition variables and transition table columns or the row length for these references is too long. Reason code=rc.

The trigger includes a REFERENCING clause that identifies one or more transition tables and transition variables. The triggered action of the trigger contains references to transition table columns or transition variables with one of the following conditions identified by the reason code:

1: references total more than the limit of the number of columns in a table
2: sum of the lengths of the references exceeds the maximum length of a row in a table.

Reduce the number of references to transition variables and transition table columns in the trigger action of the trigger so that the length is reduced or the total number of such references is less than the maximum number of columns in a table.

sqlcode: -1424

sqlstate: 54040

SQL1425N

A password has been supplied without a userid.

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

Resubmit the command/API and supply a userid if you are also supplying a password.

SQL1426N

A default instance cannot be determined.

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.

Set one of these environment variables to a valid instance name and resubmit the command.

SQL1427N

An instance attachment does not exist.

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

If the error occurred when detaching from an instance, continue processing. If the error occurred during the execution of any other command, attach to an instance and reissue the failed command.

SQL1428N

The application is already attached to nodename1 while the command issued requires an attachment to nodename2 for successful execution.

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.

Ensure that the application has no attachment before issuing the command or that the attachment that exists is to the correct node.

SQL1429N

A node directory entry cannot be created in which the node name matches the value of the DB2INSTANCE environment variable.

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

Choose another node name for the node being cataloged and try again.

SQL1430N

The database name database cannot be found in the system database directory on node nodename.

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.

Make sure the databases listed in the request all reside at the node to which you are attached or at the local node. Reissue the request.

SQL1431N

The relative path path is not allowed when executing remotely.

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

Specify a fully qualified path that is valid at the server and reissue the command.

SQL1432N

A request has been sent to a server using a database protocol which the server does not recognize.

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.

Do not attempt to attach to any of the servers listed in the Explanation.

SQL1433N

The application is already connected to database1 while the command issued requires a connection to database2 for successful execution.

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.

Ensure that the application has no connection before issuing the command or that the connection that exists is to the correct database.

SQL1434N

A CONNECT or ATTACH statement failed because of a client/server incompatibility between 32 bit and 64 bit platforms.

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

For scenario 1, you can issue a CONNECT or ATTACH statement in the following scenarios:

from a 32 bit client to a 32 bit server
from a 64 bit client to a 64 bit server

For scenario 2 listed above, reissue the statement from a supported client.

sqlcode: -1434

sqlstate: 08004

SQL1435N

Binding or rebinding the automated maintenance policy configuration stored procedures failed.

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.

To bind these automated maintenance policy configuration stored procedures perform the following steps:

Connect to the database on which you will use these stored procedures
Run the DB2 bind command with the bind file called db2policy.bnd in the SQLLIB/bnd directory:
```
DB2 bind db2policy.bnd blocking all grant public
```

sqlcode: -1435

sqlstate: 5U0ZZ

SQL1436N

Automated maintenance policy configuration file named file-name could not be opened.

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.

Confirm that the specified file satisfies the following conditions:
- the file exists
- the user id as which the stored procedure is running has permission to read the file
- the file is not empty
- the format of the file is UTF-8
Call the SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE procedure again specifying a file that satisfies the previously listed conditions.

sqlcode: -1436

sqlstate: 5U0ZZ

SQL1437N

The XML in the automatic maintenance policy file or LOB parameter passed to AUTOMAINT_SET_POLICY or AUTOMAINT_SET_POLICYFILE is not valid at line number line-number and column number coumn-number. Validation error message: error-message.

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.

Correct the contents of the XML configuration file and call the stored procedure again.

sqlcode: -1437

sqlstate: 5U0ZZ

SQL1438N

An internal error occurred while processing the XML automated maintenance policy configuration file or LOB parameter passed to AUTOMAINT_SET_POLICY or AUTOMAINT_SET_POLICYFILE.

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.

Confirm that the contents of the XML configuration file or the LOB parameter passed to SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE is valid and call the stored procedure again.

sqlcode: -1438

sqlstate: 5U0ZZ

SQL1439N

Could not retrieve automated maintenance policy configuration information.

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.

Default automated maintenance policies are created by the DB2 health monitor. If the health monitor has not yet created the default maintenance policies, then you can manually create them:

Connect to the database for which you wish to create default automated maintenance policies
Call the system stored procedure called SYSPROCS.SYSINSTALLOBJECTS with the following parameters:
```
SYSPROCS.SYSINSTALLOBJECTS( 'POLICY','C','','')
```

sqlcode: -1439

sqlstate: 5U0ZZ

SQL1440W

All privileges were granted but the WITH GRANT OPTION was ignored.

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.

No response is required.

sqlcode: +1440

sqlstate: 01516

SQL1441N

Invalid parameter. Reason code code.

The following is a list of valid reason codes:

1: A NULL was passed in for the context pointer.
3: The context pointer has been initialized, but not to a valid context area.
4.: Invalid option
5: reserved parameter was not NULL

Ensure that the application context pointer has been properly initialized and that any options used are valid and try again.

SQL1442N

The context is not in use or is not in use by the current thread. Reason code code.

The call failed because:

1: The context is not in use by any thread (no attach was done)
2: The context is not in use by the current thread.
3: The current thread is not using a context.

For a detach call, ensure that the context is the one in use by the current thread, and that a corresponding attach was done.

For a get current context call, ensure that the thread is currently using a context.

SQL1443N

Thread is already attached to a context.

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

Detach from the previous context before attaching to a new one.

SQL1444N

The application context cannot be destroyed because it is in use.

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.

Ensure that all calls to attach to a context have a corresponding detach, all CONNECTS have a corresponding CONNECT RESET, and all ATTACHES have a corresponding DETACH.

SQL1445N

Thread or process does not have a context to use.

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

Make sure the current thread or process is attached to a context before making any database calls.

SQL1446N

An internal error occurred while processing the XML automated maintenance policy configuration file or LOB parameter passed to AUTOMAINT_GET_POLICY or AUTOMAINT_GET_POLICYFILE.

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.

Confirm that the contents of the XML configuration file or the LOB parameter passed to SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE is valid and call the stored procedure again.

sqlcode: -1446

sqlstate: 5U0ZZ

SQL1447N

The XML in the automated maintenance policy file or LOB parameter passed to AUTOMAINT_SET_POLICY or AUTOMAINT_SET_POLICYFILE is not valid for reason: reason-code.

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: Either the FilterClause element or the FilterCondition element is too long.
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.

Respond according to the reason code:

1 and 4

Correct the contents of the XML configuration file or LOB parameter and call the stored procedure again.

2

Use the CREATE FUNCTION statement to create a function with the long filter clause and then use the new function in the FilterClause or FilterCondition element.

3

Without this schema document, you cannot use the SYSPROC.AUTOMAINT_SET_POLICY, SYSPROC.AUTOMAINT_SET_POLICYFILE, SYSPROC.AUTOMAINT_GET_POLICY, or SYSPROC.AUTOMAINT_GET_POLICYFILE procedures.

You cannot replace this schema document manually. Reinstall the database server to replace the missing file.

5

Ensure that the first line of the XML input specifies encoding="UTF-8". If the editor in which you created the XML input saved the file using different encoding, save the file again using UTF-8 encoding.

sqlcode: -1447

sqlstate: 5U0ZZ

SQL1448N

The path or file name full-file-name that was passed to AUTOMAINT_GET_POLICY or AUTOMAINT_GET_POLICYFILE does not exist.

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.

Confirm that the specified path and file satisfy the following conditions:
- the directory path and file exist
- the user id as which the stored procedures is running has permission to create or write to the file
Call the SYSPROC.AUTOMAINT_SET_POLICY or SYSPROC.AUTOMAINT_SET_POLICYFILE procedure again specifying a file that satisfies the previously listed conditions.

sqlcode: -1448

sqlstate: 5U0ZZ

SQL1449C

Tools catalog migrated successfully to the current level. The scheduler was not started successfully for the reason code reason-code.

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.

1: Correct the Tools Catalog Database configuration in the DB2 Administration Server configuration parameters. For instructions on configuring the Tools Catalog Database, refer to the section on the DB2 Administration Server in the DB2 Administration Guide.
2: Start the database manager containing the Tools Catalog Database.
3: Wait until the Tools Catalog Database is not being used by another scheduler.
4: Stop and Restart the DB2 Administration Server.

SQL1450N

Invalid registration information pointer.

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

Verify that a valid pointer was passed to the register/ deregister database server command/API.

SQL1451N

Reissue the register/deregister database server command/API from a server node.

SQL1452N

An invalid registration location was specified.

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

Verify that a valid registration location was passed to the register/deregister database server command/API.

SQL1453N

The entry in the database manager configuration file for file server name is missing or invalid.

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

Verify that a file server name was specified, that the name does not contain invalid characters, and is not longer than 48 characters in length. Update the file server name in the database manager configuration file and resubmit the command/API.

SQL1454N

The entry in the database manager configuration file for object name is missing or invalid.

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

Verify that an object name was specified, that the name does not contain invalid characters, and is not longer than 48 characters in length. Update the object name in the database manager configuration file and resubmit the command/API.

SQL1455N

The entry in the database manager configuration file for IPX socket number is missing or invalid.

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

Verify that an IPX socket number was specified, that the number does not contain invalid characters, and is not longer than 4 characters in length. Update the IPX socket number in the database manager configuration file and resubmit the command/API.

SQL1456N

The object name specified in the database manager configuration file already exists on the NetWare file server.

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

The object name specified in the database manager configuration file is already in use. Change the object name and then re-register the database server.

SQL1457N

Register/deregister failed to login to the NetWare file server specified because a NetWare directory services connection is already established to that file server.

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

Sever the directory services connection by logging out and detaching from Directory Services, and then reissue register/deregister.

SQL1458N

IPX/SPX has been configured in the database manager configuration file for direct addressing. It is not necessary to register/deregister the database server at/from a NetWare file server.

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 '*'.

Note that since the database server has been configured for direct addressing only, IPX/SPX clients using fileserver addressing will not be able to connect to this server. For the server to support both types of IPX/SPX client addressing, specify a fileserver and objectname in the database manager configuration file.

SQL1459I

Tools catalog migrated successfully to the current level.

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

No response is required.

SQL1460N

The environment variable variable required for SOCKS server name resolution is not defined or not valid.

The SOCKS environment variable SOCKS_NS or SOCKS_SERVER is not defined. SOCKS protocol support requires that both these environment variables be defined.

SOCKS_NS: This is the IP address of the domain name server where the SOCKS server is defined.
SOCKS_SERVER: This is the hostname of the SOCKS server.

Define the missing environment variable and resubmit the command.

SQL1461N

The security option security is not valid.

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.

Verify that SOCKS protocol support is required. If so, re-catalog the node with SECURITY SOCKS. If not, re-catalog the node, but omit the SECURITY option.

SQL1462N

Request is only valid for a syncpoint manager connection.

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

Connect to the syncpoint manager instance and reissue the request.

SQL1463N

The operation cannot be performed on the administration task because the administration task table table-name cannot be used.

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.

Make the administration task table usable for administration task operations. To re-create table table-name, explicitly drop the table and then call the SYSPROC.ADMIN_TASK_ADD procedure to schedule a task.

sqlcode: -1463

sqlstate: 55070

SQL1464W

Not all tasks were removed because some tasks were running.

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.

Wait until the running tasks complete and then use the SYSPROC.ADMIN_TASK_REMOVE procedure to remove the tasks. The SYSTOOLS.ADMIN_TASK_STATUS view can be used to check the execution status of tasks.

sqlcode: +1464

sqlstate: 0168S

SQL1465N

The result of the SQL statement specified for the administrative task is not valid as input to the procedure procedure-name specified for the administrative task.

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.

Modify the data in the database so that the SQL statement results in no more than one row, or modify the administrative task to change either the SQL statement or procedure specified for it. Ensure that the SQL statement will return no more than one row, and the number of arguments to the procedure specified for the administrative task matches the number of columns returned by the SQL statement. To modify the administrative task, use the SYSPROC.ADMIN_TASK_REMOVE procedure to remove the task, then call SYSPROC.ADMIN_TASK_ADD to recreate it.

sqlcode: -1465

sqlstate: 21507

SQL1467C

The database manager received an I/O error while trying to read a page from the system managed temporary table space with table space id table-space-id.

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.

SQL1468N

The database manager TCP/IP listener must be configured and running on the server instance instance (database partition number database-partition-number1) before attempting to CONNECT or ATTACH to node database-partition-number2.

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).

Note: This message may be returned by an implicit CONNECT or ATTACH.

Either:

Ensure that svcename has been specified in the database manager configuration on the instance instance, database partition number database-partition-number1, the DB2COMM environment variable has been set to use TCP/IP, and that TCP/IP listener was successfully started at DB2START time.
or
Explicitly catalog the node and database.

sqlcode: -1468

sqlstate: 08004

SQL1469N

Instance instance-name (database partition number database-partition-number1) does not have node database-partition-number2 specified in its db2nodes.cfg file.

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).

Note: This message may be returned by an implicit CONNECT or ATTACH.

Ensure that the node number specified by the SET CLIENT command or api or the DB2NODE environment variable exists in the db2nodes.cfg file of the intermediate instance instance-name, node database-partition-number1.

sqlcode: -1469

sqlstate: 08004

SQL1470N

Value of DB2NODE environment variable is not valid.

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.

Set the DB2NODE environment variable to one of the following values:

unset: causes the application to connect to the default node.
blank: causes the application to connect to the default node.
A number: causes the application to connect to the node with that node number. The node must be running on the same host as the application.

sqlcode: -1470

sqlstate: 08001

SQL1471N

Cannot connect to database database-name on node node-number because the database on this node is not synchronized with catalog node.

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.

If the database is restored without rolling forward on one node, ensure that the database is restored from consistent offline backups on all nodes without rolling forward.

sqlcode: -1471

sqlstate: 08004

SQL1472N

Cannot connect to database database-name on node node-number because the difference between the system time on the catalog node and the virtual timestamp on this node is greater than the max_time_diff database manager configuration parameter.

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.

Synchronize the system times on all machines, and ensure that the max_time_diff parameter is configured to allow for normal communication delays among the database machines.

sqlcode: -1472

sqlstate: 08004

SQL1473N

Cannot commit the transaction because the time difference between the system time on the local node and the virtual timestamps of node(s) node-list is greater than the max_time_diff database manager configuration parameter. The transaction is rolled back.

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.

Synchronize the system times on all machines, and ensure that the max_time_diff parameter is configured to allow for normal communication delays among the database machines.

sqlcode: -1473

sqlstate: 40504

SQL1474W

The transaction completed successfully, but the time difference between the system time on the local member and the virtual timestamps of member or members member-list is greater than the max_time_diff database manager configuration parameter.

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.

Synchronize the system times on all machines, and ensure that the max_time_diff parameter is configured to allow for normal communication delays among the database machines.

sqlcode: +1474

sqlstate: 01607

SQL1475W

A system error occurred during CONNECT RESET processing.

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

Check the administration notification log for details. The database at this node may need to be restarted.

sqlcode: +1475

sqlstate: 01622

SQL1476N

The current transaction was rolled back because of error sqlcode.

The transaction was rolled back because:

An implicit or explicit CLOSE CURSOR failed, or
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.
A rollback to savepoint failed or release savepoint failed.
A severe error occurred during an atomic array input operation.
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.

Correct the problem as indicated by the error sqlcode, then run the transaction again. Remove any ROLLBACK TO SAVEPOINT statement that is used in the same transaction in which a NOT LOGGED INITIALLY table is created or activated.

sqlcode: -1476

sqlstate: 40506

SQL1477N

For table table-name an object object-id in table space tbspace-id cannot be accessed.

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.

One of the following actions can be taken.

If the object is a table and it had NOT LOGGED INITIALLY activated, drop the table. If this table is required, re-create it.
If the object is a data partition, detach it from the table. If this data partition is required, add a new one.
If the object is a non-partitioned index, drop the index. If this index is required, create a new one.
If the table is a created temporary table, disconnect from the server and connect again to instantiate a new copy of the created temporary table.
If the table is a declared temporary table, drop the table. If this table is required, declare it again.
Otherwise, restore from a table space or database backup. The backup image must have been taken subsequent to the commit point following the completion of the non-recoverable operation (NOT LOGGED INITIALLY operation, or NONRECOVERABLE load).

The catalogs and administrative views can be used to determine what the object is. To determine if the object is a table, use the following query:


SELECT TABNAME
  FROM SYSCAT.TABLES
  WHERE TBSPACEID=tbspace-id AND
    TABLEID=object-id

If a table name does not appear as the result for this query you can determine if the object is a partition by using the following query:


SELECT DATAPARTITIONNAME, TABNAME
  FROM SYSCAT.DATAPARTITIONS
  WHERE TBSPACEID=tbspace-id AND
    PARTITIONOBJECTID=object-id

To determine if the object is an index, use the following query:


SELECT INDNAME
  FROM SYSCAT.INDEXES
  WHERE TBSPACEID=tbspace-id AND
    INDEX_OBJECTID=object-id

To determine if the object is a created temporary table or a declared temporary table, use the following query:


SELECT TABNAME
 FROM SYSIBMADM.ADMINTEMPTABLES
 WHERE TBSP_ID=tbspace-id AND
  INDEX_TAB_FILE_ID=object-id

sqlcode: -1477

sqlstate: 55019

SQL1478W

The defined buffer pools could not be started. Instead, one small buffer pool for each page size supported by the database manager has been started.

The defined buffer pools could not be started. Instead, one small buffer pool for each page size supported by the database manager has been started. The defined buffer pools could not be started for one or more of the following reasons:

Not enough memory could be allocated for the total size of the buffer pools specified for this database.
The buffer pool files in the database directory are missing or corrupt.

Check the administration notification log for the correct source of the problem. A possible solution includes:

Drop or alter the size of one or more of the buffer pools to allow the database to start properly.

After making the changes, disconnect from the database and start the database again.

sqlcode: +1478

sqlstate: 01626

SQL1479W

Attempt to fetch before the result set returned the first rowset.

The requested rowset overlapped the start of the result set and, depending on the fetch orientation specified:

SQL_FETCH_PRIOR

one of the following situations:

the current position was beyond the first row, and the number of the current row is less than or equal to the rowset size.
the current position was beyond the end of the result set, and the rowset size was greater than the result set size.

SQL_FETCH_RELATIVE

the absolute value of the fetch offset was less than or equal to the current rowset size.

SQL_FETCH_ABSOLUTE

the fetch offset was negative, and the absolute value of the fetch offset was greater than the result set size but less than or equal to the current rowset size.

No action needed.

SQL1480N

The discover type specified in the DISCOVER database manager configuration parameter is invalid.

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

Update the DISCOVER database manager configuration parameter with a type of DISABLE, KNOWN, or SEARCH.

SQL1481N

One or more of the communications protocols specified in the DISCOVER_COMM parameter is invalid.

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

Update the DISCOVER_COMM database manager configuration parameter with only valid values.

SQL1482W

The BUFFPAGE parameter will only be used if one of the buffer pools is defined with a size of -1.

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.

You can select from the SYSCAT.BUFFERPOOLS to review the buffer pool definitions. If none of the buffer pools are defined with size -1 (NPAGES), then setting the BUFFPAGE parameter will not change the size of the buffer pools for the database.

SQL1483N

Add database partition server processing for database partition server partitionnum failed. Information returned for the error includes SQLCODE sqlcode, SQLSTATE sqlstate, and message tokens token-list.

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.

Check the message associated with the SQLCODE of the SQL statement that failed. Follow the action suggested by that message.

sqlcode: -1483

sqlstate: 5UA02

SQL1484N

The request failed because of an ongoing add operation. Request: request. Member or dbpartitionnum: number.

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

Wait for the add operation to complete and resubmit the request.

sqlcode: -1484

sqlstate: 55071

SQL1485N

The database partition server or member cannot be added or dropped because of the state the database or instance name is in. State state.

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

Change the database or instance so that it is in a state that allows the adding or dropping of a database partition server or member and resubmit the request.

sqlcode: -1485

sqlstate: 55019

SQL1487W

The database partition server, DB2 member, or CF was added successfully.

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.

The new member or CF must be started manually using the db2start command.

SQL1488W

The add database partition server operation was successful, and the new database partition server partitionnum is active. The DB2 cluster manager is detected in the instance. You may want to run the cluster manager tool utility-name to configure the new database partition server for the cluster manager.

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.

Use the db2haicu tool to add the new database partition server to the cluster manager.

SQL1489I

The add database partition server operation was successful. The new database partition server dbpartitionnum is active.

No response is required.

SQL1490W

Activate database is successful, however, the database has already been activated on one or more nodes.

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

No action required.

SQL1491N

The database name was not deactivated because the database is still being used.

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

Ensure that all applications have done a CONNECT RESET, then try again.

SQL1492N

The database name was not deactivated because it was not activated.

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

No action is required.

SQL1493N

The command failed because the application is already connected to an active database.

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

Disconnect from the database, and then reissue the command.

SQL1494W

Activate database is successful, however, there is already a connection to the database.

There is already database connection on one or more nodes.

No action required.

SQL1495W

Deactivate database is successful, however, there is still a connection to the database.

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

No action required.

SQL1496W

Deactivate database is successful, but the database was not activated.

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

No action required.

SQL1497W

Activate/Deactivate database was successful, however, an error occurred on some nodes.

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

Refer to the diagnostic log to find out what error has occurred on which node, fix the problem if possible and then reissue the activate/deactivate database command.

SQL1498W

There are tables in the database that contain one or more type-1 indexes. To convert them to type-2 indexes, run the generated-file CLP script prior to database upgrade.

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.

To avoid the overhead of index rebuild on the first table access, run the generated-file CLP script generated by the db2ckupgrade command to convert type-1 indexes to type-2 indexes prior to database upgrade.

SQL1499W

Database upgrade was successful; however, additional user action may be required. See the administration notification log for more details.

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.

Refer to the administration notification log for additional information on the conditions detected to help you determine the action that might be required.

SQL1509N

The statement cannot be processed because all available transports are in use, and no more transports can be created. Reason code: reason-code.

A transport is a physical connection to a database.

The reason that no more transports can be created is indicated by the given reason code:

1: No memory is available for additional transports.
2: The value set for the configuration parameter maxTransports has been reached.

Respond to this error according to the reason code:

1

Resolve the memory shortage:

Make more memory available to the application. For example, terminate any unused connections.
Rerun the statement.

2

Change the database configuration to allow more transports:

Set the maxTransports configuration parameter to a higher value in the db2dsdriver.cfg configuration file.
Restart the application.

sqlcode: -1509

sqlstate: 57060

SQL1510N

The result set element list in a WITH RETURN TO CLIENT clause of a CREATE PROCEDURE statement is invalid. The following reason code indicates why the result set element list is invalid: reason-code

You can return multiple, interleaved result sets from stored procedures by using the WITH RETURN TO CLIENT clause in the CREATE PROCEDURE statement.

The given reason code indicates what is invalid about the specified result set elements:

1: The list of result set elements contained a value that is not a positive integer. Result set elements specified with WITH RETURN TO CLIENT must be positive integers. For example, the following are not valid result set elements: -2, 0, 2.3
2: The list of result set elements contained duplicate entries. You cannot include a result set element multiple times in the list. For example, the following list is not valid: (1, 2, 2).
3: The result set elements were not specified in ascending order. For example, the following list is valid: (1, 3). The following list is not valid: (3, 1).
4: An element in the result set list was greater than 32767. The largest valid result set list element is 32767.

The stored procedure was not created.

Call the CREATE PROCEDURE statement again specifying valid result set elements.

SQL1511N

The specified clause, clause, is not supported for service subclasses.

The clause, clause, that is specified is valid for a service superclass but is not valid for a service subclass.

Remove the unsupported clause, or specify a service superclass.

sqlcode: -1511

sqlstate: 5U044

SQL1512N

ddcstrc could not write to the specified file.

ddcstrc was not able to write the trace information to the filename that it has been instructed to write to.

Ensure that the filename specified is valid for your file system. If a filename is not specified, ensure that you have the necessary permission to write to the default file ddcstrc.tmp.

SQL1513W

ddcstrc has not been turned off.

Because of an error condition ddcstrc has not been turned off. This was done to ensure that the trace information will not be lost before being safely placed in a file.

Correct the ddcstrc error condition reported prior to this error and attempt to turn off the trace again.

SQL1514N

DB2START with the ADMIN MODE option cannot proceed because the specified member is part of a DB2 pureScale environment.

The db2start command is not compatible with the ADMIN MODE option in a DB2 pureScale environment.

If you need to restrict access to a certain member, use the QUIESCE option of the db2stop or STOP DATABASE MANAGER commands.

SQL1515N

The user mapping cannot be created for server server-name because of a conflict with an existing user mapping or federated server option. Reason code reason-code.

A user mapping defined for PUBLIC cannot coexist on a server with user mappings defined for individual users or on a server defined with the federated server option FED_PROXY_USER. The attempt to create the user mapping failed.

The reason code reason-code indicates the particular situation. The following actions can resolve the situation.

1: A user mapping for an individual user is being defined but server server-name already has a user mapping defined for PUBLIC. Drop the user mapping defined for PUBLIC from the server and create the user mapping again.
2: A user mapping for PUBLIC is being defined but server server-name already has a user mapping defined for an individual user. Drop all user mappings defined for individual users from the server and create the user mapping for PUBLIC again.
3: A user mapping for PUBLIC is being defined but server server-name is already defined with federated server option FED_PROXY_USER. Alter the server to remove the FED_PROXY_USER option and create the user mapping for PUBLIC again.

sqlcode: -1515

sqlstate: 428HE

SQL1516N

The ALTER SERVER statement cannot add the FED_PROXY_USER federated server option to server server-name because of a conflict with an existing user mapping.

The FED_PROXY_USER federated server option cannot be added to server server-name because it has an existing user mapping defined for PUBLIC. The ALTER SERVER statement failed.

Drop the user mapping defined for PUBLIC from the server and issue the ALTER SERVER statement again.

sqlcode: -1516

sqlstate: 428HE

SQL1517N

db2start failed because the cluster manager resource states are inconsistent.

The db2start command has failed to start the processes because there are inconsistencies between the cluster manager resource model and the db2nodes.cfg file. These inconsistencies occur when there is a modification (intentional or unintentional) to db2nodes.cfg that is not synchronized with the cluster manager.

A DB2 pureScale instance or new resources cannot be started until the inconsistencies have been resolved. DB2 resources that are already started are not affected by this error.

Restore the db2nodes.cfg file to an earlier configuration (one that was synchronized with the cluster manager). If this cannot be done, repair the cluster resource model. To do this, issue a global db2stop to stop the instance, and run the db2cluster tool with the -repair option.

SQL1520N

Buffersize must be a numeric value greater than or equal to 65536.

The user specified an invalid buffersize for the ddcstrc command.

Ensure that the buffersize used is numeric and greater than or equal to 65536 (64K). Note that the memory to be used will be a multiple of 64K. ddcstrc rounds down the buffersize specified to the nearest multiple of 64K.

SQL1522N

The deactivate command failed at one or more members where indoubt transactions were detected for the given database.

This message is returned when an attempt is made to explicitly deactivate a database using the DEACTIVATE DATABASE command or the sqle_deactivate_db API but the database could not be deactivated because indoubt transactions were detected for the given database at one or more members.

The database has been deactivated at members where no indoubt transactions were detected. At members where indoubts were detected, the database will be left activated or in the same state it was in, prior to the deactivate command being issued.

Respond to this error in one of the following ways:

Wait for the transaction manager to resolve the indoubt transactions:
1. Identify the indoubt transaction that involve the database using the LIST INDOUBT TRANSACTIONS command.
2. Monitor the indoubt transactions until the transaction manager automatically resolve the indoubt transactions.
3. Resubmit the DEACTIVATE DATABASE command or call the sqle_deactivate_db API again.
Resolve the transactions manually:
1. Identify the indoubt transaction that involve the database using the LIST INDOUBT TRANSACTIONS command.
2. Manually resolve the indoubt transactions. Resubmit the DEACTIVATE DATABASE command or call the sqle_deactivate_db API again.
Force the database deactivation by calling the DEACTIVATE DATABASE command with the FORCE option:
1. Determine on which members the deactivation operation failed by reviewing the db2diag log files.
2. On each member on which the deactivation operation failed, call the DEACTIVATE DATABASE command with the FORCE option.
  Any indoubt transactions will be left unresolved.

SQL1523N

An extent movement operation attempted to access the table space named tablespace-name while another process was already accessing that table space. Reason code = reason-code.

An extent movement operation attempted to reclaim unused storage to lower the high water mark but a utility or process is already accessing the table space. The extent movement operation resulted from an ALTER TABLESPACE statement specifying a REDUCE or LOWER HIGH WATER MARK clause.

The utility or process that is affecting the table space is indicated by one of the following reason codes:

1: The table space is in a backup pending state.
2: The table space is in a restore in progress state.
3: The table space is in a restore pending or a recovery pending state.
4: The table space is in a rebalance in progress state.
5: The table space is in a rollforward in progress state.
6: The table space is in a rollforward pending state.
7: The table space is in a redistribute in progress state.
8: The table space is in a quiesce shared state.
9: The table space is in a quiesce update state.
10: The table space is in a quiesce exclusive state.
11: The table space is in a pstat_deletion state.
12: The table space is in a pstat_creation state.
13: The table space is in a stordef pending state.
14: The table space is in a disable pending state.
15: The table space is in a move in progress state.

Refer to the documentation on the different states that a table space can be in. The documentation also tells you how to change the state to one that will allow the desired extent movement operation, or you can wait until the operation in process completes. For example, you can back up the table space to change the state from backup pending. Reissue the statement.

sqlcode: -1523

sqlstate: 55039

SQL1524N

The request cannot occur until all applications in the instance are aware of the new database partition server.

A new database partition server has been added online to the instance. When this event occurs, an existing application becomes aware of the new database partition server at its next transaction boundary (the exception occurs if the application has an open WITH HOLD cursor). A new database application becomes aware of the new database partition server at its first request. Until all applications in the instance are aware of the new database partition server, CREATE DATABASE PARTITION GROUP, ALTER DATABASE PARTITION GROUP, DROP DATABASE PARTITION GROUP, REDISTRIBUTE DATABASE PARTITION GROUP, and DROP DATABASE requests are not allowed.

One of the following, then try the request again.

Wait until all applications are aware of the new database partition server.
If waiting is not an option, terminate the application that is causing the request to fail. You can identify this application by using the db2pd -addnode oldviewapps command or the db2pd -addnode oldviewapps detail command.
If multiple database applications are preventing the request, you can force all the applications or quiesce the instance.

sqlcode: -1524

sqlstate: 55077

SQL1525N

An error occurred when starting the DB2 security daemon.

An unexpected error occurred when starting the DB2 security daemon.

Retry the DB2START command. If the problem persists, contact IBM Service.

SQL1526N

db2start failed because DB2VIA support was not started. Reason code reason-code.

DB2VIA support was not started successfully at db2start time. The reason code indicates the error:

The VIPL library specified in DB2_VI_VIPL registry variable could not be loaded.
The Device name specified in DB2_VI_DEVICE registry variable could not be opened.
DB2 does not support the VIA implementation installed.

Make sure the DB2 registry DB2_VI_VIPL is properly set and the name specified in DB2_VI_VIPL is in the %PATH% environment variable.
Make sure the DB2 registry DB2_VI_DEVICE is properly set.
DB2 only supports a VIA implementation that supports at least Reliable Delivery reliability level. It is also required that the VIA implementation complies with Intel Virtual Interface Architecture Implementation Guide and passes the conformance Suite. Make sure the VIA implementation you chose satisfies these requirements.

SQL1528W

An enabled workload is associated with a disabled service class.

Incoming connections will be assigned to the enabled workload workload-name, but the workload cannot map any new requests to the service class service-class-name, because the service class is disabled. Any new request mapped or remapped to the disabled service class will receive an SQL4714N error message.

If necessary, correct the issue by disabling the workload or by enabling the service class. Otherwise, no action is required.

sqlcode: +1528

sqlstate: 01HN0

SQL1529N

The last remaining CF cannot be dropped.

In a DB2 pureScale environment at least one cluster caching facility (CF) must exist. The last one cannot be dropped.

Add a new CF and activate the changes before dropping this one.

SQL1530W

The specified degree of parallelism will be ignored because the system is not enabled for intra-partition parallelism.

Either the DEGREE bind option was specified with a value greater than 1 or the SET CURRENT DEGREE statement was executed with a value greater than 1, but the database manager was not enabled for intra-partition parallelism.

The database manager must be started with the intra_parallel configuration parameter set to ON in order for the instance to be enabled for intra-partition parallelism.

The statement or command completed successfully, but the degree specification was ignored.

If you want to use intra-partition parallelism restart the database manager with the intra_parallel configuration parameter set to ON.

Otherwise use a value of 1 or ANY for the degree specification.

sqlcode: +1530

sqlstate: 01623

SQL1531N

The connection failed because the name specified with the DSN connection string keyword could not be found in either the db2dsdriver.cfg configuration file or the db2cli.ini configuration file. Data source name specified in the connection string: DSN.

The db2dsdriver.cfg configuration file contains database directory information and client configuration parameters for use by some IBM data server clients and drivers.

The CLI/ODBC initialization file (db2cli.ini) contains various keywords and values that can be used to configure the behavior of CLI and the applications using CLI.

This message is returned when a data source name is specified in a connection string with the "DSN" connection keyword but the specified data source name cannot be found in either of the following locations:

Specified with the "dsn alias" configuration keyword in the db2dsdriver.cfg configuration file
Specified as a section header in the db2cli.ini configuration file

Add the specified data source name to the db2dsdriver.cfg configuration file or the db2cli.ini configuration file.
Stop and restart the application process for the new configuration settings to take effect.
Resubmit the connection request to the specified data source name.

SQL1532N

The db2dsdriver.cfg configuration file contains multiple entries for the database alias database-alias.

The db2dsdriver.cfg configuration file contains database information, and is used by the following drivers and clients:

IBM Data Server Driver for ODBC and CLI
IBM Data Server Driver Package
For DB2 Version 9.7: for CLI and open source applications, the IBM Data Server Client and IBM Data Server Runtime Client

The information in the db2dsdriver.cfg file is similar to the information that is in the system database directory on an IBM Data Server Client or IBM Data Server Runtime Client.

The client driver configuration file cannot contain multiple identical database alias entries or multiple identical database entries.

Remove duplicate entries from the db2dsdriver.cfg configuration file.
Stop the application process and start it again for the new db2dsdriver.cfg file settings to take effect.

SQL1533N

The db2dsdriver.cfg configuration file contains multiple entries for a database with the following properties: database name database-name; server name server-name; and port number port-number.

The db2dsdriver.cfg configuration file contains database information, and is used by the following drivers and clients:

IBM Data Server Driver for ODBC and CLI
IBM Data Server Driver Package
For DB2 Version 9.7: for CLI and open source applications, the IBM Data Server Client and IBM Data Server Runtime Client

The information in the db2dsdriver.cfg file is similar to the information that is in the system database directory on an IBM Data Server Client or IBM Data Server Runtime Client.

The client driver configuration file cannot contain multiple identical database alias entries or multiple identical database entries.

Remove duplicate entries from the db2dsdriver.cfg configuration file.
Stop the application process and start it again for the new db2dsdriver.cfg file settings to take effect.

SQL1534N

The call to db2dsdcfgfill failed because invalid command options were specified.

You can use the db2dsdcfgfill command to create and populate a db2dsdriver.cfg configuration file based on the contents of the local database directory, node directory, and DCS directory.

This message is returned when an invalid parameter or parameter value is specified with the db2dsdcfgfill command.

Run db2dsdcfgfill again, specifying valid command options.

SQL1535I

The db2dsdcfgfill utility successfully created the db2dsdriver.cfg configuration file.

The configuration file db2dsdriver.cfg contains database directory information and client configuration parameters in a human-readable format. You can create and populate the configuration file db2dsdriver.cfg using the db2dsdcfgfill utility.

You do not need to respond to this message.

SQL1536N

The db2dsdcfgfill utility failed to create the db2dsdriver.cfg configuration file. Reason code: reason-code.

You can use the db2dsdcfgfill utility to create and populate a db2dsdriver.cfg configuration file based on the contents of the local database directory, node directory, and DCS directory.

The reason codes are as follows:

1: The db2dsdcfgfill utility could not create the db2dsdriver.cfg configuration file because there were insufficient system resources. For example, this error can happen if there is not enough room in the output directory to create the new file.
2: A non-severe, internal or system error occurred.

Run the db2dsdcfgfill utility again.

If the problem persists, respond to this error according to the given reason code:

1

Resolve the system resources problem:

Use operating system diagnostics tools to examine system resource data. For example, verify that there is enough space to create the new file.
Make more system resources available. For example, free disk space.
Run the db2dsdcfgfill utility again.

2

Work with IBM support to resolve the internal or system error:

Collect diagnostic information using db2trace while running the db2dsdcfgfill utility.
Contact IBM Support to investigate the collected db2trace diagnostic information.

SQL1537N

The db2dsdcfgfill utility failed because an invalid value was passed to the command. Reason-code: reason-code.

You can use the db2dsdcfgfill utility to create and populate a db2dsdriver.cfg configuration file based on the contents of the local database directory, node directory, and DCS directory.

The reason this message was returned is indicated by the given reason code:

1: The specified database manager instance does not exist on this client.
2: The specified database manager instance path is not valid. For example, the path might not exist, or the db2dsdcfgfill utilty might not have permission to access that directory.
3: The specified output directory is invalid. For example, the directory might not exist, or the db2dsdcfgfill utility does not have permission to create a file in that directory.
4: The specified db2cli.ini file path is invalid. For example, the directory might not exist, or the db2dsdcfgfill utility does not have permission to access that file or directory.

Respond to this message according to the given reason code:

1

Run db2dsdcfgfill again, specifying a valid database manager instance.

2

Resolve the problem with the database manager instance directory:

Determine why db2dsdcfgfill could not access the specified database manager instance directory. For example, determine if the permission settings of the directory prevent db2dsdcfgfill from accessing the directory.
Address the reason db2dsdcfgfill could not access the specified database manager instance directory. For example, change the permission settings of the directory to allow db2dsdcfgfill to access the directory.
Run db2dsdcfgfill again.

3

Resolve the problem with the output directory:

Determine why db2dsdcfgfill could not access the specified output directory. For example, determine if the permission settings of the directory prevent db2dsdcfgfill from creating a file in the directory.
Address the reason db2dsdcfgfill could not create the db2dsdriver.cfg configuration file in the specified directory. For example, change the permission settings of the directory to allow db2dsdcfgfill to create a file in the directory.
Run db2dsdcfgfill again.

4

Resolve the problem with the db2cli.ini file path:

Determine why db2dsdcfgfill could not access the specified file. For example, determine if the permission settings of the directory prevent db2dsdcfgfill from accessing a file in the directory.
Address the reason db2dsdcfgfill could not access the db2cli.ini file in the specified directory. For example, change the permission settings of the directory to allow db2dsdcfgfill to read a file in the directory.
Run db2dsdcfgfill again.

SQL1538N

The following keyword is not supported in the current environment: keyword.

The keyword you specified is not supported in a DB2 pureScale environment.

Rerun the command or execute the SQL statement again specifying only supported keywords.

sqlcode: -1538

sqlstate: 56038

SQL1539N

The load operation failed because the load target table is incompatible with exception tables in general or with the specific exception table in particular. Reason code: reason-code.

You can efficiently move large quantities of data into newly created tables, or into tables that already contain data using the load utility.

You can create a consolidated report of all of the rows that violated unique index rules, range constraints, and security policies during a load operation using a load exception table. You specify a load exception table by using the FOR EXCEPTION clause of the LOAD command.

The reason code indicates the specific reason this error was returned:

1

The load target table uses LBAC security and has at least one XML column.

2

The load target table is partitioned and has at least one XML column.

3

The partition map for the load target table is not the same as the partition map for the specified load exception table.

A partition map determines the distribution of the rows of a table among database partitions. The distribution of the rows of the load target table must be the same as the distribution of the rows of the load exception table.

4

The exception table is column organized. Column-organized tables are not supported as exception tables.

Re-issue the LOAD command without the FOR EXCEPTION option.

sqlcode: -1539

sqlstate: 5U049

SQL1540N

An SQL statement or a DB2 utility encountered an error because a storage group or table space object is not accessible on a member. Object identifier: object-id. Member: member-id. Object type keyword: object-type-keyword.

An SQL statement or a DB2 utility encountered an error because the storage group or table space where a database object resides is not accessible on this member. The SYSCAT.TABLESPACES catalog view can be used to identify the table space name given a table space identifier. The SYSCAT.STOGROUPS catalog view can be used to identify the storage group name given a storage group identifier. If the object identifier token value is "*N", a storage group file header is not accessible on this member.

Verify that all database storage paths are accessible on this member and reissue the SQL statement, or issue the SQL statement on a different member.

sqlcode: -1540

sqlstate: 57048

SQL1541N

Dropping the member failed because the specified member is the only member in this DB2 pureScale instance. The last member cannot be dropped.

In a DB2 pureScale environment at least one member must exist. The last one cannot be dropped.

Add a new member using the db2iupdt command with the -add option.
Drop the original member using the db2iupdt command with the -drop option.

SQL1542N

Adding the CF failed because the maximum number of CFs in the database manager instance has been reached.

A DB2 pureScale environment supports a maximum of 2 cluster caching facilities (CFs) for each database manager instance. This message is returned when an attempt is made to add more CFs than the maximum.

Drop one of the existing CFs using the db2iupdt command with the -drop option
Add the new CF using the db2iupdt command with the -add option

SQL1543N

The host specified for the CF is a duplicate.

In a DB2 pureScale environment only one cluster caching facility (CF) can exist on a given host.

Specify a different host that does not already have a CF.

SQL1544N

Backup of a database following a topology change in a DB2 pureScale environment cannot be performed from a newly added member.

Following a topology change in a DB2 pureScale environment, a backup of the database is required. This must be performed from one of the preexisting instance members.

Perform the backup from one of the preexisting members.

SQL1545N

Restore of a database image from a previous topology is not supported.

In a DB2 pureScale environment, restore of an image with a topology different than the current database topology (different setup or number of members) is not permitted.

Restore the image taken following the most recent topology change and proceed from there.

SQL1546N

The rollforward operation failed because the rollforward utility encountered an event in the database logs through which rolling forward cannot continue. Reason code: reason-code.

The reason code indicates what type of event was encountered in the logs:

1

A topology change that made transaction logs and table space backups that were created before the topology change incompatible with the database after the topology change:

A drop member operation
A restore of a pureScale database to a pureScale instance where the source member topology includes members that are not included in the target member topology
A restore of a Enterprise Server Edition database to a pureScale instance
A restore of a pureScale database to a Enterprise Server Edition instance

The rollforward utility cannot roll forward through these types of topology change. This message is returned when an attempt is made to roll forward through one of these types of topology change.

2

A non-recoverable upgrade operation. The rollforward utility cannot rollforward through this event.

3

A DB2 version change that made the transaction logs incompatible in the current DB2 version. The rollforward utility has stopped.

4

A DB2 version change that made a log record incompatible in the current DB2 version was encountered. The rollforward utility has stopped.

5

An invalid log record was encountered. The rollforward utility has stopped.

If the reason code refers to an invalid log record, see the db2diag.log and attempt to correct the problem before proceeding.

If the reason code and your recovery scenario refers to one of the following conditions:

a topology change event
a non-recoverable upgrade operation
a DB2 version change event and you wish to stay in the current DB2 version
an invalid log record

then run the ROLLFORWARD DATABASE command with the STOP option to accomplish the following outcomes:

Stop the rolling forward of log records and complete the rollforward recovery process. All committed transactions have been restored up to the event that has stopped the rollforward operation.
Roll back any incomplete transactions.
Turn off the rollforward pending state of the database.
Provide access to the database or table spaces that are being rolled forward.

If the reason code refers to a version change event and you would like to proceed with the roll forward, then issue the ROLLFORWARD DATABASE command from the later version of the product to complete the operation.

SQL1547N

The start or stop command failed because there was a previous incomplete add or drop operations.

An attempt to add or drop a DB2 member or cluster caching facility (CF) failed. As a result, the start or stop command cannot be processed until the incomplete add or drop operation is corrected.

Use response

Manually correct the failed add or drop operation using the db2stop command with the fixtopology parameter.
Note that using the db2stop command with the fixtopology parameter always performs a drop operation to complete an incomplete add or drop operation.
Resubmit the start or stop command.

SQL1548N

The REORG command failed because the ALLOW WRITE ACCESS and ALLOW READ ACCESS modes are not valid for a partitioned table.

You can reorganize indexes or tables by using the REORG command. You can control what access users have to the affected index or table by using the following clauses:

ALLOW NO ACCESS
ALLOW READ ACCESS
ALLOW WRITE ACCESS

There are restrictions and requirements for how these ALLOW clauses can be used. For example, when the REORG INDEXES ALL command is run on a data partitioned table, the ALLOW WRITE ACCESS clause is supported only when one or more of the following clauses is also specified: ON DATA PARTITION, CLEANUP, and RECLAIM EXTENTS.

This message is returned when a data partitioned table is being reorganized and one of the ALLOW clauses is specified in a way that is not supported.

Reissue the REORG command with the appropriate access mode for a partitioned table.

sqlcode: -1548

sqlstate: 5U047

SQL1549N

The ON DATA PARTITION clause is not allowed with the command.

A REORG TABLE command with the ON DATA PARTITION clause is not allowed on a table that meets both conditions:

It is in the reorg pending state.
One or more nonpartitioned indexes are defined on the table. A nonpartitioned index can be a user-defined index or a system-created index such as an XML PATH index that is created when the table contains an XML column.

Issue the REORG TABLE command without the ON DATA PARTITION clause.

sqlcode: -1549

sqlstate: 5U047

SQL1550N

The SET WRITE SUSPEND command failed because of the condition that is indicated by the reason code. Reason code = reason-code.

You cannot issue the SET WRITE SUSPEND command until the condition indicated by reason-code is resolved:

1

The database is not activated.

2

A backup database operation is currently in progress for the target database.

3

A restore database operation is currently in progress for the target database.

4

Write operations have already been suspended for the database.

5

One of the following conditions exists:

The current state of one or more table spaces does not permit the suspension of write operations.
Changes to the buffer pools that are associated with the table spaces are still pending and do not permit the suspension of write operations.

6

An error occurred during an attempt to suspend write operations for the database.

In a DB2 pureScale environment, SQL1550N can be returned with reason code 6 if the SET WRITE command failed on one or more members in the DB2 cluster.

7

The database is quiesced or in a temporary state that does not permit the suspension of write operations. This can be caused, for example, by a quiesced database or instance, or by a database deactivation in progress.

8

Set write suspend is not supported on an HADR standby.

Respond to this message according to the reason code:

1

Activate the database by issuing the ACTIVATE DATABASE command, and then reissue the SET WRITE SUSPEND command.

2

After the BACKUP procedure finishes, reissue the SET WRITE SUSPEND command.

3

After the RESTORE procedure finishes, reissue the SET WRITE SUSPEND command.

4

If you want to resume write operations for the database, issue the SET WRITE RESUME command.

5

View the table space states by using the MON_GET_TABLESPACE table function. If there are table spaces that are in a pending state, issue the appropriate command to bring them out of the pending state before reissuing the SET WRITE SUSPEND command.
If an operation is in progress for one or more table spaces, wait until the operation is complete before reissuing the SET WRITE SUSPEND command. For example, if the self-tuning memory manager is enabled, buffer pool changes might be in progress. When the changes are complete, the write suspend operations will be allowed.

6

Respond to reason code 6 by performing the following steps:

Investigate the cause of the failure by reviewing the administration notification log.
In a DB2 pureScale environment, review the administration notification log on each member in the DB2 cluster.
Correct the problem that is preventing the SET WRITE command from succeeding.
In a DB2 pureScale environment, if different members in the DB2 cluster are reporting different root causes for this problem, correct all of the causes reported by the members.
Reissue the SET WRITE SUSPEND command.

7

Unquiesce the database if quiesced, or wait a short period of time and reissue the SET WRITE command with the SUSPEND option.

8

Issue the SET WRITE command on the HADR primary.

SQL1551N

The SET WRITE RESUME command or the RESTART DATABASE command with the WRITE RESUME parameter failed because of the condition that is indicated by the reason code. Reason code = reason-code.

You cannot issue the SET WRITE RESUME command or the RESTART DATABASE command with the WRITE RESUME parameter until the condition indicated by reason-code is resolved:

1: A snapshot backup is in progress for the target database.
2: The database is not currently in the WRITE SUSPEND state.
3: An error occurred during an attempt to resume the write operations for the database.

Respond to this message according to the reason code:

1

Wait until the snapshot backup is complete.
Reissue the SET WRITE RESUME command.

2

If the command that failed is the SET WRITE RESUME command, no action is required because write operations are already enabled for this database. To suspend write operations for the database, issue the SET WRITE SUSPEND command.

If the command that failed is the RESTART DATABASE command with the WRITE RESUME parameter, issue the RESTART DATABASE command without the WRITE RESUME parameter. If this fails and the database is not in the WRITE SUSPEND state:

Wait until all SET WRITE SUSPEND operations are completed.
Reissue the RESTART DATABASE command with the WRITE RESUME parameter.

3

Investigate the cause of the failure by reviewing the diagnostic (db2diag) log files.
Correct the problem.
Reissue the SET WRITE RESUME command.

SQL1552N

The command failed because write operations for the database are suspended or are being suspended.

You can suspend write operations for a database using the db2SetWriteForDB API or the SET WRITE command with the SUSPEND clause. There are some operations that cannot be performed on a database when write operations for that database have been suspended, or while the database manager is in the process of suspending write operations for that database:

Backing up the database
Restoring the database
Restarting the database
Connecting to or activating the database
Updating or resetting database configuration files

This message is returned when an attempt is made to perform these kinds of operations against a database that is in WRITE SUSPEND state, or that is in the process of having write operations suspended.

First, if write operations for the database are in the process of being suspended, monitor the state of the database using the suspend_io configuration parameter, and wait until the SET WRITE SUSPEND operation completes before you continue.

Second, respond to this error according to the scenario in which the message was returned:

Backing up or restoring the database:

Resume write operations for the database by issuing the SET WRITE RESUME FOR DATABASE command.
Perform the backup or restore operation again.

Restarting the database without the WRITE RESUME clause:

Perform the restart again by performing one of the following actions:

Issue the RESTART DATABASE command with the WRITE RESUME clause.
Call the db2DatabaseRestart API specifying the DB2_RESUME_WRITE option

In a multiple database partition environment, reissue the restart command or API call on each database partition.

Restarting the database with the WRITE RESUME clause in DB2 pureScale environments:

If automatic restart is enabled, with the autorestart database configuration parameter set to ON, wait for several seconds and submit the restart again, specifying the WRITE RESUME clause or the DB2_RESUME_WRITE option.
If automatic restart is disabled, with the autorestart database configuration parameter set to OFF, perform the following two steps:
1. Restart the database without specifying the WRITE RESUME clause or the DB2_RESUME_WRITE option.
2. Restart the database again, specifying the WRITE RESUME clause or the DB2_RESUME_WRITE option.

Other scenarios (including connecting to the database, activating the database, or updating database configuration files):

Restart the database by performing one of the following actions:

Issue the RESTART command with the WRITE RESUME clause.
Call the db2DatabaseRestart API specifying the DB2_RESUME_WRITE option.

In DB2 pureScale environments, issuing the command or API on any one member will cause write operations to resume on all suspended members.

SQL1553N

The database manager cannot be stopped because one or more databases are in WRITE SUSPEND state.

You cannot shut down a database for which write operations are suspended. The database is in WRITE SUSPEND state.

Issue the SET WRITE RESUME command to resume write operations for the database, then re-issue the db2stop command.

sqlcode: -1553

SQL1554N

The command failed because LIST TABLESPACES and LIST TABLESPACE CONTAINERS commands have been deprecated and are not supported in a DB2 pureScale environment.

The commands and APIs that show information about table spaces and table space containers have been deprecated, are not supported in a DB2 pureScale environment, and might be removed in a future release. The LIST TABLESPACES and LIST TABLESPACE CONTAINERS commands are no longer being updated with new features.

Modify any of your existing scripts using the deprecated commands or APIs to call the MON_GET_TABLESPACE or the MON_GET_CONTAINER table functions instead. These table functions return more information than was provided by the deprecated commands and APIs.

sqlcode: -1554

sqlstate: 5U001

SQL1555N

The setting of SUSPEND_COS_DELETES did not complete successfully because of the condition that is indicated by the reason code. Reason code = reason-code.

You cannot issue the setting of SUSPEND_COS_DELETES until the condition indicated by reason-code is resolved:

1: Object storage deletes cannot be enabled or disabled while the database is suspended.
2: Object storage deletes have already been disabled for the database.
3: Object storage deletes dynamic update failed.

Respond to this message according to the reason code:

1

Call SET WRITE RESUME on the database.
Reissue the setting of SUSPEND_COS_DELETES command.

2

The SUSPEND_COS_DELETES setting must be 0 (OFF) to be disabled, or 1 (ON) to be enabled.

The SUSPEND_COS_DELETES setting must be 0 (OFF) to be disabled, or 1 (ON) to be enabled.
Reissue the setting of SUSPEND_COS_DELETES command.

3

The SUSPEND_COS_DELETES setting dynamic update failed.

Reissue the setting of SUSPEND_COS_DELETES command.

SQL1560N

Statistics profile does not exist for table table-name.

A statistics profile needs to be defined before use.

Register a statistics profile for the table using the SET PROFILE option of the RUNSTATS command and then reissue the operation.

SQL1561N

Statistics option not compatible with the database server level.

One or more of the options specified are not compatible with the database server level. This database server version does not support all of the statistics options available using the db2runstats API.

Use the sqlustat API to collect the statistics or use the db2runstats API and specify only those options that are available using the sqlustat API.

SQL1562N

Statistics node option is not compatible with the existed statistics for table table-name.

The statistics node option is different from the existing table and/or index statistics of the table.

Use consistent node option to collect the statistics for a table.

SQL1563N

The SYSINSTALLOBJECTS procedure failed to migrate the explain tables.

You can migrate explain tables using the SYSINSTALLOBJECTS procedure only if the explain tables were created in DB2 Version 9.5 or higher.

Migrate the explain tables using the db2exmig tool.

sqlcode: -1563

sqlstate: 5U048

SQL1564N

The restore or rollforward operation did not complete successfully because the specified operation is not supported. Reason code reason-code.

1

Restoring a database backup image when the image topology is a superset of the target member topology without specifying the WITHOUT ROLLING FORWARD clause.

2

An attempt was made to restore a table space from a backup image that was taken before one of the following events:

A DB2 member was dropped from a DB2 pureScale instance
A backup image from a DB2 Enterprise Server Edition (ESE) instance was restored to a DB2 pureScale instance

3

Restoring any backup image (database or tablespace) where the current member driving the restore does not exist in the backup image topology.

5

Restoring a backup image of an inconsistent database when the image topology is not a superset of the target member topology.

6

When restoring a backup image between a DB2 pureScale instance and a DB2 Enterprise Server Edition instance, either this is not a database restore or the backup image is not an offline database backup image.

7

Restoring a backup image of an inconsistent database between a DB2 Enterprise Server Edition instance and a DB2 pureScale Feature instance.

8

A down-level image can be restored only when both of the following conditions are satisfied:

The source topology matches the target topology.
The source instance type matches the target instance type.

9

Restoring a backup image between a DB2 pureScale instance and a DB2 Enterprise Server Edition instance without specifying the WITHOUT ROLLING FORWARD clause.

10

Restoring an offline backup image with reduced-redo logging enabled but without specifying the WITHOUT ROLLING FORWARD clause.

11

Restoring a backup image with reduced-redo logging enabled into an environment with reduced-redo logging disabled.

The action corresponding to the reason code:

1

Rerun the RESTORE command with WITHOUT ROLLING FORWARD clause.

2

Restore the closest full database backup taken before the tablespace backup, then rerun the RESTORE command.

3

Run the RESTORE command from a common member between the backup image topology and the current member topology.

5

Either perform an offline backup on the source instance or update the target instance to include at least all members in the source instance, then rerun the RESTORE command.

6

You must perform a full offline database backup on the source instance, then restore the full database backup by running the DATABASE RESTORE command with the WITHOUT ROLLING FORWARD clause.

7

Either perform an offline backup on the source instance or update the target instance to include the member identifier in the source instance, then rerun the RESTORE command.

8

To restore a down-level image, do one or both of the following:

Modify the target instance topology to add or drop members, or switch to another instance that matches the topology.
Run the RESTORE command on the same type of instance as the type of instance on which the BACKUP command was run. For example, if the BACKUP command was run on a DB2 pureScale instance, run the RESTORE command on a DB2 pureScale instance.

9

Rerun the RESTORE command with the WITHOUT ROLLING FORWARD clause.

10

Rerun the RESTORE command with the WITHOUT ROLLING FORWARD clause.

11

Enable reduced-redo logging and rerun the RESTORE command.

SQL1565N

The entry in the database manager configuration file for the CF diagnostic directory path (cf_diagpath) is invalid.

The entry in the database manager configuration file for the diagnostic directory path of the cluster caching facility (CF) is cf_diagpath.

This message is returned when you try to update the dbm config parameter cf_diagpath with specification of an invalid path. An invalid value for cf_diagpath is specified in the UPDATE DATABASE MANAGER CONFIGURATION command. For example, this message can be returned if a path is specified that does not exist, or if a path is specified for which the database manager does not have write access.

Run the command again, specifying a valid value for the cf_diagpath. Ensure that this is a valid and fully qualifed path.

sqlcode: -1565

sqlstate: 5U054

SQL1566N

The UPDATE DATABASE MANAGER CONFIGURATION command failed because the specified value for the cf_diaglevel configuration parameter is invalid.

You can specify the level of diagnostic errors that are recorded in the cfdiag.log file using the database manager configuration parameter cf_diaglevel.

This message is returned when an invalid value for cf_diaglevel is specified in the UPDATE DATABASE MANAGER CONFIGURATION command.

Run the command again, specifying a valid value for the cf_diaglevel.

sqlcode: -1566

sqlstate: 5U054

SQL1567N

An exclusive connection to a single database partition cannot be made in this environment

In a DB2 pureScale environment, connecting to a single database partition in exclusive mode is not supported.

Do not specify the ON SINGLE DBPARTITIONNUM clause on the CONNECT statement.

SQL1568N

The database manager configuration file is not accessible.

An error occurred while attempting to access the database manager configuration file. This file is created during instance creation and is critical for all database manager processing. An inaccessible database manager configuration file can be an indication of an incomplete instance setup or a damaged instance.

This message can also be returned when the file system on which the database manager configuration file resides is unavailable. For example, if the shared file system is IBM General Parallel File System (GPFS), this message can be returned if the GPFS cluster is offline.

The command cannot be processed.

Respond to this message be performing the following troubleshooting steps:

Confirm that the shared file system where the database manager configuration file is located is mounted.
If the shared file system is of type GPFS, confirm that the file system cluster is not stopped by performing the following steps:
1. Verify the status of the shared file system cluster using the following command:
```
db2cluster -cfs -list -host -state
```
2. If the shared file system cluster is stopped, restart the cluster using the following command:
```
db2cluster -cfs -start -host <hostname>
```
If the database manager instance was recently created, recreate the instance using db2icrt command.

SQL1569N

The operation failed because the command or API specified invalid database partitions.

If this message is being returned as a result of a backup operation, the specified database partitions are not currently defined in the database. If this message is being returned as a result of a rollforward or recover operation, either the ON DBPARTITIONNUMS or the ON DBPARTITIONNUM clause were specified and an invalid database partition number was specified. In non-DPF environments, only the current database partition can be specified.

For backup operations, reissue the command or API, specifying existing database partitions. For rollforward and recover operations, reissue the command or API without specifying ON DBPARTITIONNUMS or only specify the current database partition

sqlcode: -1569

sqlstate: 428A9

SQL1572N

The database rollforward or group crash recovery has failed because of a disk full situation.

If a log full situation occurs during a database rollforward or group crash recovery, more log files are automatically allocated as needed. However, in this case, new log files could not be allocated due to insufficient disk space. The recovery or rollforward operation has failed.

Make more disk space available to the group crash recovery or the database rollforward, and reissue the command.

Alternatively, the operation may succeed if reissued on a different member as follows:

If the operation that failed was a group crash recovery, DB2 cluster services will automatically reissue the group crash recovery on a different member. If the DB2 pureScale instance does not have automatic crash recovery enabled, the group crash recovery operation needs to be reissued manually on a different member.
If the operation that failed was a database rollforward, the rollforward operation needs to be restarted manually on another member.

SQL1573N

The database cannot be activated or connected to in the current instance environment.

This message is returned if

You are trying to activate or connect to a database that has not been verified for a DB2 pureScale environment, but are using a DB2 pureScale environment.
You are trying to activate or connect to a database that has been verified for a DB2 pureScale environment, but are not using a DB2 pureScale environment.

These two actions are not supported.

If you are using a DB2 pureScale environment you can use the db2checkSD utility to determine if the database can be used in that environment. If the db2checkSD utility does not report any errors, activate or connect to the database again.

sqlcode: -1573

sqlstate: 55001

SQL1575N

The most recent attempt to add or drop a DB2 member for database dbname in this DB2 pureScale environment failed.

Adding or dropping a DB2 member (a topology change) in this DB2 pureScale environment would leave database dbname in an unrecoverable state.

Backup or drop the database dbname then repeat the add or drop DB2 member operation.

SQL1576N

The database removal failed because of a cluster manager error.

A cluster manager error occurred that prevented successful processing of the drop command.

All data files associated with the database has been removed. However, the database location information might not have been removed.

Clean up the database resources that the cluster manager failed to remove by performing the following steps:

Collect as much of the following diagnostic information as possible:
- Error information from the SQLCA
- Related errors in the db2diag log files
Make the necessary corrective actions based on the cluster manager return code in the db2diag log files.
Manually remove or delete the related mount resources.
Remove the database location information from the system database directory using the UNCATALOG DATABASE command.

If you are unable to successfully remove the database resources using this procedure, contact IBM support with the following information:

Problem description
SQLCODE
SQLCA contents, if possible
Environment data on the client and server collected using the db2support command

sqlcode: -1576

sqlstate: 5U056

SQL1577N

The START command failed because the STANDALONE parameter was specified, and the current environment is a DB2 pureScale environment.

The STANDALONE parameter is not supported with the START command in a DB2 pureScale environment.

Call the command again without specifying the STANDALONE parameter.

SQL1578N

The START command failed because the RESTART parameter was specified, and the current environment is a DB2 pureScale environment.

The RESTART parameter is not supported with the START command in a DB2 pureScale environment.

Call the command again without specifying the RESTART parameter.

SQL1579N

Two or more log streams for database dbname on database partition dbpartitionnum are following different log chains. Log file file1 on log stream stream1 follows log chain chain1 and log file file2 on log stream stream2 follows log chain chain2.

When a database rollforward to a point-in-time operation completes, or a database restore operation without rolling forward is done, a new history of the database, called a log chain, is created. The database manager assigns log chain numbers to log extents and other database objects so that it can verify that the set of objects belongs to the same database history. The database manager has detected that two or more log streams are following different log chains, and has halted the current operation.

Check the log streams that are identified in this message and determine which log stream is following the correct log chain. Retrieve the required log files from the invalid log stream into an overflow log path, and attempt the operation again.

SQL1580W

Trailing blanks were truncated while performing conversion from codepage source-code-page to codepage target-code-page. The maximum size of the target area was max-len. The source string length was source-len and its hexadecimal representation was string.

During the execution of the SQL statement, a code page conversion operation has resulted in a string that is longer than the maximum size of the target object. Processing continued because only blank characters were truncated.

Ensure that the output is as expected and that the truncation has not caused any unexpected consequences.

sqlcode: +1580

sqlstate: 01004

SQL1581N

The table table-name cannot be in append mode and have a clustering index.

There are two situations where this error is issued.

A clustered index exists for a table and ALTER TABLE is used to attempt to place the table in append mode.
A table is in append mode and CREATE INDEX is used to attempt to create a clustering index.

If a clustering index is necessary then alter the table to set append mode off. If append mode is desired, drop the existing clustering index on the table.

sqlcode: -1581

sqlstate: 428CA

SQL1582N

The PAGESIZE of the table space tbspace-name does not match the PAGESIZE of the bufferpool bufferpool-name associated with the table space.

The PAGESIZE value specified in the CREATE TABLESPACE statement does not match the page size of the bufferpool specified for use with the table space. These values must match.

The statement cannot be processed.

Change the value specified for PAGESIZE to match the page size of the bufferpool or change the bufferpool to one that has a page size that matches.

sqlcode: -1582

sqlstate: 428CB

SQL1583N

PAGESIZE value pagesize is not supported.

The PAGESIZE that is specified is not a supported page size. The supported page sizes are 4096, 8192, 16384, and 32768, while a value of 4 K, 8 K, 16 K, or 32 K can also be specified.

The statement cannot be processed.

Specify one of the supported page sizes.

sqlcode: -1583

sqlstate: 428DE

SQL1584N

System temporary tablespace with page size of at least pagesize could not be found.

A system temporary table space was required to process the statement. There was no system temporary table space available that had a page size of pagesize or larger.

The statement cannot be processed.

Create a system temporary table space with a page size of at least pagesize.

sqlcode: -1584

sqlstate: 57055

SQL1585N

A temporary table could not be created because there is no available system temporary table space that has a compatible page size.

Temporary table spaces hold temporary data required by the database manager when performing operations such as sorts or joins, since these activities require extra space to process the results set. This message is returned when the database manager fails to create a temporary table because the database manager cannot find a table space with a compatible page size that is in a "normal" state.

This message can be returned when one of the following conditions occurs:

The row length of the system temporary table being generated is larger than can be accommodated by the system temporary table space with the largest page size that is currently in "normal" state.
The number of columns required in a system temporary table exceeded the limit that can be accommodated in the largest system temporary table space in the database.
A tablespace might be offline.
A query contains multiple references to the same view. The query also has a construct that has a join. This join can be pushed down through a UNION, where one or more participating tables contain large columns.

Perform the following troubleshooting steps:

Calculate what size of temporary table space is required.
Determine whether a temporary table space exists that has the required page size and is in "normal" state by using the MON_GET_TABLESPACE table function.

If a table space with the required page size does not exist, create a system temporary table space with the required page size.
If a table space with the required page size exists:
- If the table space is not in "normal" state, move the table space to a "normal" state. For example, drop and recreate the table space.
- If the table space is in "normal" state, perform one of the following steps:
  - Eliminate one or more columns from the system temporary table.
  - Create separate tables or views, as required, to hold additional information beyond the limit.

If your query is referencing a view multiple times, either rewrite the query or redefine separate views.

sqlcode: -1585

sqlstate: 54048

SQL1586N

The statement was not executed because the query compiler was unable to successfully resolve the text search function in the statement.

There are some rare situations in which text search functions cannot successfully be resolved by the query compiler. One example of such a situation is the application of a text search function to a column from the null-producer of an OUTER JOIN.

This message is returned when the query compiler is unable to successfully resolve text search functions.

The statement was not executed.

No user response is required. The specified statement cannot be executed.

SQL1587N

The command or statement failed because there is currently a CF on the host on which the command was run or the statement executed. Command or statement type: command-statement-code. Host name: host.

There are some DB2 commands, such as "ATTACH", and SQL statements, such as "CONNECT", that cannot be performed on a host where a DB2 cluster caching facility (CF) is located. This message can be returned when these commands or statements have been issued explicitly or implicitly.

The token command-statement-code indicates which type of command or SQL statement was attempted:

1: Explicit or implicit CONNECT TO <database-alias>
2: Explicit or implicit ATTACH TO <instance-alias>

Respond to this message in one of the following ways:

Run the command or execute the statement again on a host that does not have a CF on it by performing the following steps:
1. Find a host that does not currently have a CF on it using the following command:
```
db2instance -list
```
2. Log in to a host that does not currently have a CF on it.
3. Run the DB2 command or execute the SQL statement again.
Specify a host that does not currently have a CF on it by using one of the following methods:
- Use the environment variable DB2NODE to specify the member and run the DB2 command or execute the SQL statement again.
- Use the Set Client command's CONNECT_MEMBER or ATTACH_MEMBER option with the DB2 command or SQL statement.

sqlcode: -1587

sqlstate: 560CW

SQL1588N

Error sqlcode on member member-ID prevents processing of the current statement.

The current member cannot process data change statements until the condition causing error sqlcode on member member-ID is corrected. The statement cannot be processed.

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

Retry the operation. If the error persists, correct the problem and try again.

sqlcode: -1588

sqlstate: 57063

SQL1589N

The database connection failed because an operating system resource limit was reached.

This message can be returned when there are more than 1024 simultaneous local database connections, and as a result, an operating system limit is reached. On AIX operating systems, no more than 1024 local database connections established by a single process or application can exist simultaneously.

This message can also be returned when the database manager encounters an internal error while making operating system calls.

Terminate any unneeded local database connections.

If terminating local database connections resolves the problem, prevent reoccurrences of this error by modifying your applications to use fewer simultaneous local connections. If your applications require many database connections, use remote connections (or loopback connections when the database server and client are on the same host machine) using TCP/IP instead of local connections.

If reducing the number of local connections does not resolve this problem, contact IBM software support for help with investigating the cause of the problem.

sqlcode: -1589

sqlstate: 54067

SQL1590N

LONG VARCHAR and LONG VARGRAPHIC fields are not permitted in TABLESPACEs which are built on DEVICEs.

Devices (raw i/o) on HP require i/o to be aligned on 1024 byte boundaries. LONG VARCHAR and LONG VARGRAPHIC fields are handled in 512 byte pieces, and thus can only be used in SYSTEM MANAGED TABLESPACEs or in DATABASE MANAGED TABLESPACEs with only FILE containers.

Alternatives:

Choose one of the LOB columns types (BLOB,CLOB,DBCLOB) instead of LONG.
Use a table space with the correct attributes.

sqlcode: -1590

sqlstate: 56097

SQL1592N

The INCREMENTAL option is not valid with reason code reason-code since the table table-name cannot be incrementally processed.

The cause is based on the reason code reason-code:

32

The table is not a REFRESH IMMEDIATE materialized query table, nor a REFRESH DEFERRED materialized query table with a supporting staging table, nor a PROPAGATE IMMEDIATE staging table.

33

A LOAD REPLACE or LOAD INSERT has occurred to the table if it is a materialized query table or staging table.

34

A LOAD REPLACE has occurred to the table after the last integrity check.

35

One of the following:

The materialized query or staging table was newly created. Full processing is required for the first time the table is checked for integrity after it has been created.
New constraint has been added to the table itself or its parents (or its underlying table if it is a materialized query table or staging table) while in the Set Integrity Pending state.
If it is a materialized query table or staging table, a LOAD REPLACE has occurred to any underlying table of the table after the last refresh.
If it is a materialized query table, at least one underlying table was forced to full access (using the FULL ACCESS option) before the materialized query table was refreshed.
If it is a staging table, at least one underlying table was forced to full access (USING the FULL ACCESS option) before the staging table was propagated.
If it is a deferred materialized query table and its corresponding staging table is in incomplete state.
Some of its parents (or underlying tables for materialized query tables or staging tables) have been non-incrementally checked for integrity.
The table was in the Set Integrity Pending state before database upgrade. Full processing is required for the first time the table is checked for integrity after database upgrade.
The table was placed in the Set Integrity Pending state during a point in time roll-forward operation.

Do not specify the INCREMENTAL option. The system will check the entire table for constraint violations (or if it is a materialized query table, recompute the materialized query table definition query).

sqlcode: -1592

sqlstate: 55019

SQL1594W

Integrity of non-incremental data remains unverified by the database manager.

The table was previously unchecked. When the option NOT INCREMENTAL is not specified, incremental processing of the table is done. The previously unchecked portion of the table remains unchecked and the corresponding values in the CONST_CHECKED column remains marked as 'U'.

No action is required. To verify the integrity of previously unchecked data and have the system maintain the integrity of the data in the table, issue the SET INTEGRITY statement with the OFF option to place the table in the Set Integrity Pending state and then re-execute the SET INTEGRITY statement with the IMMEDIATE CHECKED and NOT INCREMENTAL options.

sqlcode: +1594

sqlstate: 01636

SQL1596N

WITH EMPTY TABLE cannot be specified for table-name.

The WITH EMPTY TABLE clause cannot be specified for table table-name because the table meets one of the following conditions:

It is a materialized query table or is a staging table.
It has a dependent refresh immediate materialized query table or has a dependent propagate immediate staging table.
It is the parent in a referential constraint.
It has attached data partitions that have not been checked for constraint violations.
The ALTER TABLE statement was previously executed against this table, specifying the DETACH PARTITION clause, and that asynchronous detach operation is not complete. There are data partitions in this table that are still in the logically detached state (SYSCAT.DATAPARTITIONS.STATUS = 'L').

The WITH EMPTY TABLE clause cannot be specified when altering such a table to ACTIVATE NOT LOGGED INITIALLY.

The statement cannot be processed.

If the table does not have a logically detached partition, issue the ALTER TABLE statement without the WITH EMPTY TABLE clause.

If the table does have a logically detached partition, perform the following steps:

Wait for the asynchronous partition detach task to complete.
You can monitor the progress of the detach task in the following ways:
- Monitor the progress of the detach task by using the LIST UTILITIES command and look for the description containing source table table-name.
- Confirm that there are no data partitions in the logically detached state by using the SYSCAT.DATAPARTITIONS catalog view. Any data partitions that are still logically detached will have an 'L' in the column named STATUS.
Execute the ALTER TABLE statement again.

sqlcode: -1596

sqlstate: 42928

SQL1597N

Configuring the DB2 environment failed because the specified DB2 configuration parameter is discontinued.

The LOGRETAIN and USEREXIT database configuration parameters have been discontinued.

Log retention and the use of user exit programs to archive and retrieve the files are still supported. To configure a database to use log retention and user exit programs, you should use the LOGARCHMETH1 database configuration parameter.

To enable log retention, set the LOGARCHMETH1 database configuration parameter to LOGRETAIN.

To enable log retention and identify that a user exit program should be used to archive and retrieve the log files, set the LOGARCHMETH1 database configuration parameter to USEREXIT.

SQL1598N

An attempt to connect to the database server failed because of a licensing problem.

This message can be returned in the following situations:

Connecting directly to the database server using IBM DB2 Connect Unlimited Edition for System z: If you use IBM DB2 Connect Unlimited Edition for System z to connect directly to the database server, this message is returned when a valid license has not been activated on the DB2 for z/OS subsystem.
Connecting directly to the database server using an edition of IBM DB2 Connect other than IBM DB2 Connect Unlimited Edition for System z: If you use an edition other than IBM DB2 Connect Unlimited Edition for System z to connect directly to a database server, this message is returned when a valid license is not present on the client computer.
Connecting to a database server through a DB2 Connect gateway server: If you connect to a database server through a DB2 Connect gateway server, this message is returned when a valid license is not present on the DB2 Connect gateway server.

Respond to this message according to which scenario applies to your situation:

Connecting directly to the database server using IBM DB2 Connect Unlimited Edition for System z: If you use IBM DB2 Connect Unlimited Edition for System z to connect directly to the database server, activate the license by running the activation program in the activation kit.
Connecting directly to the database server using an edition of IBM DB2 Connect other than IBM DB2 Connect Unlimited Edition for System z: If you use an edition other than IBM DB2 Connect Unlimited Edition for System z to connect directly to a database server, ensure that a DB2 Connect product and valid license key are installed on your client computer.
Connecting to a database server through a DB2 Connect gateway server: If you connect to a database server through a DB2 Connect gateway server, ensure that a valid license key is installed on the gateway server.

sqlcode: -1598

sqlstate: 42968

SQL1599N

Creating the public alias failed because the environment is configured for SAP.

You can configure the DB2 environment for SAP by setting the system environment variable named DB2_WORKLOAD to the value SAP.

You can reference objects outside the local schema using public aliases, also known as public synonyms. You can create public aliases using the CREATE PUBLIC ALIAS statement.

Public aliases are not supported in a DB2 environment that is configured for SAP. This message is returned when an attempt is made to create a public alias when the system environment variable named DB2_WORKLOAD is set to the value SAP.

There are several ways to refer to objects outside of the local schema without creating public aliases, including: using full-qualified names, or creating local aliases. In the following examples, the local schema is called "schemaA" and there is a table called "tableX" in a different schema, called "schemaB".

Example 1: Using fully-qualified names

You could refer to tableX using a fully-qualified name:


select * from schemaB.tableX

Example 2: Creating a local alias

You could refer to tableX by first creating a local alias:


create alias AX for table schemaB.tableX
select * from AX

Instead of creating public aliases, refer to database objects outside of the local schema by using fully-qualified names, or by creating local aliases.

sqlcode: -1599

sqlstate: 42612

SQL1600N

The storage group storage-group cannot be dropped because it is the default storage group.

DROP STOGROUP cannot be processed because storage-group-name is the current default storage group.

The statement cannot be processed.

Before dropping the current default storage group, designate a new default storage group by using the ALTER STOGROUP statement.

sqlcode: -1600

sqlstate: 42893

SQL1601N

The Database System Monitor input parameter parameter is a null pointer.

The user called one of the Database System Monitor APIs and provided a null pointer instead of a required parameter.

The command can not be processed.

The user should reissue the command with a valid parameter value.

SQL1602N

An object type supplied in the input data structure (sqlma) is not supported.

An object type specified in the variable data area of the input data structure (sqlma) for Database System Monitor Snapshot API is not supported.

The command can not be processed.

Reissue the command using a valid object type.

SQL1603N

The parameter parameter is not specified in the input data structure (sqlma).

A required parameter is not specified in the input data structure (sqlma) of the Database System Monitor Snapshot or Estimate Buffer Size API.

The command cannot be processed.

The user should reissue the command specifying a valid parameter value.

SQL1604N

The parameter parameter is not null terminated.

A null character is expected at the end of the character string parameter.

The command can not be processed.

Add a null character at the end of the character string parameter and reissue the command.

SQL1605W

The database db-alias is not active.

The Database System Monitor Reset API was called for a specific database, but the database was not active.

The command completed successfully but no action was taken.

Verify that the database alias is correct and the database has been started.

SQL1606W

The Database System Monitor output buffer is full.

The Database System Monitor output buffer area is not large enough to accommodate the returned data. Likely causes are intense system activity when the call was made, or in the case of a Database Monitor API call within a user application, the user allocated a buffer too small to contain the returned data.

The command completed successfully and data collected prior to the buffer overflow is returned in the user's buffer.

The user should reissue the command, or in the case of a Database Monitor API call within a user application, allocate a larger buffer or reduce the amount of information requested.

SQL1607N

There is not enough working memory to execute the requested Database Monitor function.

The database manager is out of working memory to process the Database System Monitor command.

The command can not be processed.

Reduce the buffer size in the input parameter and reissue the command.

SQL1608W

Two or more database aliases specified as input refer to the same database.

A Database System Monitor Snapshot or Estimate Buffer Size API call was issued specifying the same request for two or more database aliases in the sqlma input data structure, and they point to the same database.

Database System Monitor executes successfully, but returns only one copy of the information in the output buffer.

No action is required. However, the user should verify that the database aliases specified on input are correct if information on different databases was expected.

SQL1609N

The database alias db-alias is a remote database and cannot be monitored.

A Database System Monitor API call was issued specifying the database alias of a remote database. Database System Monitor does not support monitoring of remote databases.

The command cannot be processed.

The user should verify that the database alias specified on input is correct, and reissue the command with the correct database alias.

SQL1610N

The Database System Monitor input parameter parameter is invalid.

The user called one of the Database System Monitor APIs and specified an invalid value for the specified parameter.

The command can not be processed.

The user should reissue the command with a valid parameter value.

SQL1611W

No data was returned by Database System Monitor.

None of the monitoring information requested by the users was available at the time the Database System Monitor API call was issued. This can occur when a requested database or application is inactive, or when a monitoring group such as the Table group is turned OFF, and Table information is requested.

The command completed successfully, but no data is returned to the user.

The user should make sure that the databases or applications for which monitoring is desired are active at the time the Database System Monitor API is called, or that the desired monitoring groups are active.

SQL1612N

The specified event monitor target path is invalid.

The target path specified in the CREATE EVENT MONITOR statement is not a valid path name. The command could not be processed.

Resubmit the statement with the correct event monitor target path.

sqlcode: -1612

sqlstate: 428A3

SQL1613N

The specified event monitor option is invalid.

The option specified in the CREATE EVENT MONITOR statement is not valid. Possible causes include:

The specified MAXFILES, MAXFILESIZE, or BUFFERSIZE is too low.
MAXFILESIZE is smaller than BUFFERSIZE.
MAXFILESIZE NONE was specified with MAXFILES not equal to 1.

The command could not be processed.

Resubmit the statement with the corrected event monitor options.

sqlcode: -1613

sqlstate: 428A4

SQL1614N

An I/O error occurred when activating an event monitor. Reason code = reason-code.

An I/O error was detected when an event monitor was activated. <reason-code> is one of the following:

1: Encountered an unknown event monitor target type.
2: The Event monitor target path was not found.
3: Access to event monitor target path was denied.
4: Event monitor target path is not the name of a pipe.
5: No process has opened the event monitor target pipe for reading.
6: Encountered an unexpected I/O error.

Where possible, fix the problem described by the reason code, and resubmit the SET EVENT MONITOR statement.

sqlcode: -1614

sqlstate: 58030

SQL1615W

The specified event monitor or usage list is already in the requested state.

An attempt was made to either activate an already active event monitor or usage list, or to deactivate an already inactive event monitor or usage list. The SET EVENT MONITOR or SET USAGE LIST statement was ignored.

In a partitioned database environment or a DB2 pureScale environment, the usage list on one or more members was already in the requested state. Any usage lists that were not in the requested state when the statement was issued were changed to the requested state.

If the statement was issued for a usage list for a partitioned table or index, the usage list for one or more data partitions was already in the requested state. Any usage lists that were not in the requested state when the statement was issued were changed to the requested state.

No user response is required.

sqlcode: +1615

sqlstate: 01598

SQL1616N

The limit on the maximum number of active event monitors has already been reached.

A maximum of 128 event monitors can be active simultaneously on each database partition.

In a multiple partition database environment, a maximum of 32 GLOBAL event monitors can be active simultaneously on each database.

One of these limits has already been reached. The specified event monitor cannot be activated.

If possible, deactivate one of the active event monitors and resubmit the SET EVENT MONITOR statement. Use the following query to determine all the active event monitors and whether or not they are global:

SELECT EVMONNAME, MONSCOPE FROM SYSCAT.EVENTMONITORS WHERE EVENT_MON_STATE(EVMONNAME) = 1

sqlcode: -1616

sqlstate: 54030

SQL1617N

The specified event monitor has already reached its MAXFILES and MAXFILESIZE limit.

The specified event monitor was created with a limit on the amount of data that would be allowed in the event monitor target directory. This limit has already been reached. The specified event monitor cannot be activated.

If possible, delete some of the event monitor data files from the target directory, and resubmit the SET EVENT MONITOR statement.

sqlcode: -1617

sqlstate: 54031

SQL1618N

The target path of the specified event monitor is in use by another event monitor.

The specified event monitor was created with the same target path as another event monitor. This other event monitor was activated at least once, and has left .evt and/or .ctl files in the target path. These files may be in use by application(s) that are reading the event information they contain.

If the other event monitor is currently active, deactivate it. After ensuring no application(s) are using the files it created in the target path, remove the files. Then resubmit the SET EVENT MONITOR statement.

Alternatively, recreate the required event monitor, specifying a different target path, and resubmit the SET EVENT MONITOR statement.

sqlcode: -1618

sqlstate: 51026

SQL1619N

Cannot DROP an active event monitor.

The specified event monitor is currently active, and therefore cannot be dropped.

Deactivate the event monitor and resubmit the DROP EVENT MONITOR statement.

sqlcode: -1619

sqlstate: 55034

SQL1620N

Unable to flush event monitor. Reason code rc.

The event monitor could not be flushed. Possible reasons are indicated by the following reason codes:

1: The event monitor is not active.
2: The event monitor is running at a pre-version 6 level of output, for which flush is not available.
3: The flush succeeded on some database partitions, but failed on at least one database partition.
4: The database partition is in write-suspended state.

Actions, according to reason code, are provided as follows:

1

Ensure that the event monitor is active and, if necessary, issue a SET EVENT MONITOR evmonname STATE 1 statement to activate the event monitor.

2

If the event monitor is running at a pre-version 6 level of output, do not attempt to flush it.

3

If the flush failed on at least one database partition, check the db2diag log file for any probes from routines sqlm_bds_flush_monitor or sqlm_bds_flush_monitor_hdl which would indicate the partition experiencing the issue with the event monitor being flushed, take any required corrective actions (for example, make sure there is enough monitor heap on that partition, and for a write-to-table event monitor, ensure the table space has enough space on that partition), and then deactivate and reactivate the event monitor by issuing the following statements:


SET EVENT MONITOR evmonname STATE 0
SET EVENT MONITOR evmonname STATE 1

4

Enable the resumption of write operations on the database partition by issuing the SET WRITE command with the RESUME parameter.

sqlcode: -1620

sqlstate: 55034

SQL1621N

The transaction in which the specified event monitor or usage list was created has not yet been committed. The event monitor or usage list cannot be activated.

An event monitor or usage list cannot be activated until the transaction in which it was created has been committed.

Commit the transaction in which the event monitor or usage list was created and then reissue the SET EVENT MONITOR or SET USAGE LIST statement.

sqlcode: -1621

sqlstate: 55033

SQL1622N

The STATE value specified in the SET EVENT MONITOR STATE or the SET USAGE LIST STATE statement is not valid.

The STATE value specified in the SET EVENT MONITOR STATE or the SET USAGE LIST STATE statement is not within the range of valid values, or the value is NULL as a result of an indicator variable.

Valid values for the event monitor state are:

0: to deactivate the event monitor
1: to activate the event monitor

Valid values for the usage list state are:

ACTIVE: to activate the usage list
INACTIVE: to deactivate the usage list
RELEASED: to release the memory associated with the usage list

The statement cannot be executed.

Correct the event monitor or usage list state value and/or any indicator variable and reissue the statement.

sqlcode: -1622

sqlstate: 42815

SQL1623N

The sqlmonsz or sqlmonss API was called with too many objects specified in the sqlma input structure.

The limit imposed on the number of objects that are permitted in the sqlma input structure has been exceeded.

Reduce the number of objects in the sqlma parameter and try the call again.

SQL1624N

All databases referenced by the sqlmonsz or sqlmonss API must be located at the same node.

The sqlma parameter contained references to databases that reside on different nodes.

Modify the sqlma parameter so that all database objects reference the same node and then try the call again.

SQL1625W

The monitor is not able to convert from the code page source to the code page target. This conversion was attempted for data pertaining to type type.

Possible types are as follows:

statement text
dcs application
application
table
locks
table space

Conversion of data from the source code page to the target code page is not supported. This condition can occur under the following conditions:

source and target code page combination is not supported by the database manager.
source and target code page combination is not supported by the operating system character conversion utility on the server node.

This situation can occur when the monitor tries to convert data pertaining to a database whose code page is incompatible to that of the monitor application.

Check your operating system documentation for a list of supported conversions and ensure that the appropriate ones are installed and accessible to the database manager.

If possible ensure that the database being monitored and the monitoring application are in the same codepage.

SQL1626W

Overflow occurred while performing conversion from codepage source to codepage target. The size of the target area was max-len, the data pertained to type type, and the first eight characters are data.

Possible types are as follows:

statement text
dcs application
application
table
locks
table space

The monitor is unable to convert the data due to space constraints. The data is retained in its original form.

If possible ensure that the database being monitored and the monitoring application are in the same codepage.

SQL1627W

A snapshot api request was made at the self-describing datastream level, but the server was only able to return a snapshot of the fixed size structure format.

Although the application issuing the snapshot request made it at the SQLM_DBMON_VERSION6 or later level, the server returning the snapshot returned a downlevel view of the data.

In the self describing data format for snapshot (DB2 version 6 and later), collected information, including the server level, is returned as part of the snapshot datastream. In the pre-version 6 levels of DB2, the snapshot collected information is returned in an sqlm_collected structure. You must use the sqlm_collected structure, and the old data stream processing method to parse this snapshot datastream.

SQL1628W

A remote get switches operation returned partial results because the output buffer is full. To retrieve the full results, use a minimum buffer size of size bytes.

The output buffer provided was not large enough to return all the switch data available. The monitor returned as much data as possible using the given output buffer.

Allocate a larger data buffer and re-issue the switch request.

SQL1629W

A remote snapshot operation failed on node or nodes node-list, with reason code or codes reason-list.

Some type of failure occurred during an operation on a remote node for reason <reason-code>, which is one of the following:

1: FCM was unable to communicate with the target node, due to a node failure or communications error.
2: The snapshot operation failed to complete on the target node. Please see the administration notification log for the specific sqlca.

If the cause of the error was a node failure, or communication error, you will need to resolve the communication error, or restart the node that failed to correct the error.

If the error was due to a snapshot operation failure on a remote node, see the administration notification log for the sqlca from the failed operation, and refer to the instructions for that code to correct the problem.

SQL1630N

The specified event monitor has already reached its PCTDEACTIVATE limit.

The specified Write to Table event monitor was created with a PCTDEACTIVATE limit, specifying how full a DMS table space must be before the event monitor automatically deactivates, and this limit has already been reached. The specified event monitor cannot be activated.

Reduce the space used in the table space, and resubmit the SET EVENT MONITOR statement. Alternatively, drop the event monitor and recreate it with a higher PCTDEACTIVATE limit value.

sqlcode: -1630

sqlstate: 54063

SQL1631N

Event monitor event-monitor-name of type event-monitor-type is already active. Event monitor was not activated.

Only one event monitor of type ACTIVITIES, STATISTICS or THRESHOLD VIOLATIONS may be active at any one time. Event monitor activation failed because an event monitor of the same type is already active.

Deactivate event monitor event-monitor-name before attempting to activate this event monitor.

sqlcode: -1631

sqlstate: 5U024

SQL1632W

The collect and reset statistics request was ignored because another collect and reset statistics request is already in progress.

The collect and reset statistics request was ignored because a previous collect and reset statistics request is already in progress. Only one collect and reset statistics request may be processed at one time on this database.

No action required.

sqlcode: +1632

sqlstate: 01H53

SQL1633W

The activity identified by application handle application-handle, unit of work ID unit-of-work-id, and activity ID activity-id could not be captured because there is no active activity event monitor.

An attempt was made to capture an activity identified by an application handle, a unit of work identifier, and an activity identifier. This requires that an activity event monitor be created and its state set to active. There currently is no activity event monitor in the active state.

If there already is an activity event monitor but it is not in active state, set its state to active. If there are no activity event monitors in this database, create one, set its state to active. Reinvoke this procedure.

sqlcode: +1633

sqlstate: 01H53

SQL1634N

Statistics could not be collected because there is no active statistics event monitor.

An attempt was made to collect workload management statistics. This requires that a statistics event monitor be created and its state set to active. There currently is no statistics event monitor in the active state.

If there already is a statistics event monitor but it is not in active state, set its state to active. If there are no statistics event monitors in this database, create one, set its state to active. Reinvoke this procedure.

sqlcode: -1634

sqlstate: 51042

SQL1635N

The snapshot operation failed because the size of the snapshot is snapshot-size bytes, which exceeds the maximum allowable size of max-size bytes.

You can collect DB2 database and related operating system information by using the snapshot monitor. In multiple database partition environments, you can take a snapshot of the current database partition, a specified database partition, or all database partitions. Taking a snapshot of all database partitions at once is referred to as a taking global snapshot.

In general, the size of the data buffer that the snapshot operation allocates is restricted by system resource constraints. For global snapshots, you can optionally specify the maximum allowed size of the data buffer by setting the DB2_MAX_GLOBAL_SNAPSHOT_SIZE registry variable.

This message can be returned in two types of scenarios:

In general, this message is returned when the requested snapshot size exceeds the maximum possible snapshot size.
For global snapshot operations, this message can also be returned when the requested snapshot size exceeds the value that is set in the DB2_MAX_GLOBAL_SNAPSHOT_SIZE registry variable.

Respond to this message by performing one or more of the following actions.

General:

Create a smaller snapshot by reducing the amount of information that is collected.
Two examples of ways to collect smaller snapshots by changing the parameters that are specified with the GET SNAPSHOT command:
- Collect information for only one database by using the DATABASE parameter instead of using the ALL DATABASES parameter.
- Collect information for only the applications that are connected to a particular database by using the APPLICATIONS ON parameter instead of using the ALL APPLICATIONS parameter.

Global snapshots only:

Collect multiple, smaller snapshots by running the GET SNAPSHOT command separately on each database partition instead of creating a global snapshot.
If the DB2_MAX_GLOBAL_SNAPSHOT_SIZE registry variable is set, increase DB2_MAX_GLOBAL_SNAPSHOT_SIZE to a value that is at least as large as the actual size given in this message in the snapshot-size runtime variable, and then run the GET SNAPSHOT command again.

SQL1636N

The event monitor encountered errors during activation. Reason code reason-code.

During the activation of the event monitor, errors were encountered as indicated by the following reason code:

1: The event monitor was successfully activated. However this is a DB2 pureScale environment and an error has occurred leading to limited or no restart capability for this global or write-to-table event monitor. If the monitoring member is no longer able to run the event monitor, the system may not be able to restart it on another member.
2: The event monitor failed to activate on the current member. However this is a DB2 pureScale environment and this global or write-to-table event monitor may have been successfully activated on another member.

The action corresponding to the reason code is:

1: Examine the administration notification log and the db2diag.log for details. Correct the problem affecting the member and deactivate and reactivate the event monitor to ensure full restart capability is enabled.
2: Examine the administration notification log and the db2diag.log for details. Correct the problem affecting the member. Check to see if the event monitor is active, deactivate the event monitor if required and reactivate the event monitor to ensure full restart capability is enabled.

sqlcode: -1636

sqlstate: 560CS

SQL1637N

The statement failed because a clause was specified that is not supported with transparent DDL. Specified clause: clause.

You can create, alter, and drop remote tables in a federated environment using familiar SQL statements such as CREATE TABLE, ALTER TABLE, and DROP TABLE by using transparent DDL. The ability to work with both local and remote tables using the same, familiar SQL statements simplifies the administration of federated database environments. You can enable using transparent DDL with a remote table by creating the table using the CREATE TABLE statement with the OPTIONS clause.

This message is returned when the CREATE TABLE statement or the ALTER TABLE statement is called, specifying a clause that is not supported with transparent DDL.

Execute the statement again, without specifying the unsupported clause.

sqlcode: -1637

sqlstate: 428I2

SQL1638N

Redirecting storage group paths is not possible.

A process attempted to modify storage group paths using the SET STOGROUP PATHS command or the db2SetStogroupPaths API at a time when this is not possible. For example, this message can be returned when an attempt is made to redirect a storage group path during a table space restore. Storage group paths can only be redirected during a redirected database restore.

Possible actions include: To modify storage group paths of an active database, use the ALTER STOGROUP statement. To perform a redirected restore, issue a RESTORE DATABASE command using the REDIRECT option. During the redirected restore it is possible to use the SET STOGROUP PATHS command or the db2SetStogroupPaths API to redirect storage group paths.

sqlcode: -1638

sqlstate: 5U057

SQL1639N

The database server was unable to perform authentication because security-related database manager files on the server do not have the required operating system permissions.

The DB2 database system requires that your instance and database directories, and the files in those directories, have a minimum level of operating system permissions. When the instance and database directories are created by the database manager the permissions are accurate, and changing those permissions could cause database manager functions to fail. The complexity of DB2 file permissions is increased in the case of non-root installed instances and operating system-based authentication.

This message is returned when security-related database manager executable files do not have necessary permissions for the database manager to perform remote connection authentication-related tasks.

There are several reasons why these security-related files might not have the necessary permissions, including the following reasons:

The database manager instance is a non-root installed instance and operating system-based authentication has not been enabled using the db2rfe command
Operating system permissions of database manager files were accidentally changed

Respond to this message in one of the following ways:

If the instance is a non-root installed instance, enable operating system-based authentication using the db2rfe command.
Reset all of the operating system permissions for the database manager binary files for this instance by running the following command as a superuser:
```
db2iupdt -k <instance-name>
```
where <instance-name> is the name of the affected instance.

Note that both the db2rfe command and the db2iupdt command require that the database manager instance be stopped and restarted.

sqlcode: -1639

sqlstate: 08001

SQL1640N

A usage list cannot be created for the object object-name.

Usage lists can be created only for regular tables and indexes. For more information about the types of objects for which usage lists can be created, refer to the Related topics section.

Use the name of a valid table or index object.

sqlcode: -1640

sqlstate: 42809

SQL1641N

The db2start command failed because one or more database manager program files was prevented from executing with root privileges by file system mount settings.

With a root-installed instance in UNIX and Linux environments, several database manager executable programs are what is known as "set user ID upon execution" (setuid) programs. A setuid program executes with the privileges of the owner of the program, instead of the privileges of the user than ran the program. For example, database manager programs such as the db2start program are owned by root, and therefore executes with root privileges regardless of what the privileges are of the user who runs the db2start command.

The ability of programs to run with setuid privileges on a mounted file system is configured using the nosuid option when the file system is mounted. Mounting a file system with the nosuid option prevents programs from running with setuid privileges.

This message is returned in UNIX and Linux environments when database manager programs that are needed to start a database instance were not able to execute as root because the file system on which the the database manager programs are located was mounted with the nosuid option.

Remount the file system on which the database product files, including the sqllib directory and the db2start program, are located without the nosuid option.
Re-run the db2start command.

SQL1642N

The database manager failed to connect to an internet socket on a remote computer because the connection request was refused by the remote computer.

To interact with a remote database across a network, the database manager must use a communication protocol, such as TCP/IP, and use operating system interfaces, such as an internet socket, to connect to database-related operating system services on the computer on which the remote database is located.

This message is returned when the database manager attempts to connect to a remote computer using the TCP/IP communication protocol and receives the error code ECONNREFUSED or WSAECONNREFUSED from the TCP/IP function called CONNECT. Usually, the connection is refused because the database-related operating system service to which the database manager is attempting to connect on the remote computer is inactive.

There are multiple scenarios that can lead to this error being returned, including the following scenarios:

The database manager on the remote computer is stopped
There is a problem with the way the remote database is cataloged
There is a problem with the way the remote database server is configured
The DB2COMM registry variable at the remote database server is not set to the communication protocol that is being used by the client
Firewall software on the remote computer is blocking the database manager connection attempt
There are more TCP/IP connection requests than the remote computer can handle

Respond to this error by systematically eliminating the possible causes:

Ensure that the database manager on the remote computer has been started successfully.
Ensure that the database is cataloged correctly.
Ensure that the entries in the database manager configuration file for the remote database are valid and consistent.
Ensure that the DB2COMM environment variable at the remote database server is set to the communication protocol that is being used by the client.
Ensure that firewall software is not blocking the TCP/IP connection to the remote computer.
Ensure the number of connection requests being sent to the remote computer by all applications is less than the number of request that can be handled by the computer.

If you have eliminated the possible causes listed here, collect diagnostic information using the db2support command and then contact IBM software support.

SQL1643C

The database manager failed to allocate shared memory because the database manager instance memory limit has been reached.

The maximum amount of memory that can be allocated for each database partition is controlled by the instance_memory database manager parameter. DB2 memory consumption varies depending on workload and configuration. In addition to this, self-tuning of database_memory becomes a factor if it is enabled. There are many factors that contribute to the calculation of instance_memory and the affect that parameter has on the instance memory limit, including the following factors:

You can specify the maximum amount of memory that can be allocated for a database partition using the instance_memory database manager parameter.
Setting the instance_memory database manager parameter to AUTOMATIC allows the database manager instance memory to grow as needed, up to a limit calculated based on physical RAM on the computer and on the maximum allowed by the database product license.

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 the instance memory limit has been reached.

Determine the total instance memory consumption by a database manager instance for a specific database partition, or for all database partitions using the ADMIN_GET_DBP_MEM_USAGE table function or the db2pd command with the -dbptnmem parameter.
Increase the value to which the instance_memory database manager parameter is set or set instance_memory to AUTOMATIC.
If this error continues to happen after you have set instance_memory as large as possible, or have set instance_memory to AUTOMATIC, collect diagnostic information using the db2support utility and contact IBM software support.

sqlcode: -1643

sqlstate: 57019

SQL1644N

The database manager failed to send data to an internet socket on a remote computer because the connection request was reset by the remote computer.

This message is returned when the database manager attempts to send data to a remote computer using the TCP/IP communication protocol and receives the error code ECONNRESET or WSAECONNRESET from the TCP/IP function called RECV.

There are multiple scenarios that can lead to this error being returned, including the following scenarios:

Client-side connection pooling is enabled and a database application has not been retrying after database connection failures.
A database agent was forced off of the remote computer.
A database agent on the remote computer was terminated.
A database-related operating system thread on the remote computer has timed out.
The connection was closed by the remote gateway or server at the TCP/IP level.

Systematically investigate and resolve the possible causes:

Client-side connection pool problems

If client-side connection pooling is enabled, ensure that the database application retries database connections after receiving database connection failures.

Database agent forced off

Investigate whether any events might have forced a database agent off of the remote computer, such as an administrator forcing all users and agents off the remote computer to perform maintenance.
If database agents have been forced off the remote computer, work with a database or system administrator to bring the database server back online and ready to process requests, and then retry the unit of work.

Database agent terminated

Investigate whether any failures on the remote computer might have terminated a database agent. For example, the termination of a key database manager process might cause the termination of a database agent.
If failures on the remote computer have terminated a key database manager process, work with a database or system administrator to bring the database server back online and ready to process requests, and then retry the unit of work.

Thread timed out

Review diagnostic logs on the remote computer for error messages that indicate an operating system thread timed out.
If database-related operating system threads ran longer than the idle thread timeout (IDTHTOIN) operating system parameter, take one or more of the following corrective actions:
- Increase the value of the IDTHTOIN parameter.
- If connection pooling is enabled at the gateway, disable that connection pooling.
- Ensure that the database application is not holding resources open longer than necessary. For example, ensure the database application closes with-hold cursors after the cursors are no longer needed.

Connection closed by the remote gateway or server

Resolve any problems external to the database product that might have caused a TCP/IP connection to be closed on the remote gateway or server. Some examples of problems that could cause the connection to be closed include the following problems:

Firewall software errors or failure
Power failure
Network failure

If you have eliminated the possible causes listed here, collect diagnostic information using the db2support command and then contact IBM software support.

sqlcode: -1644

sqlstate: 08001

SQL1645N

The database manager failed to connect to or send data to an internet socket on a remote computer because the connection was terminated by the remote computer.

There are multiple scenarios that can lead to this error being returned, including the following scenarios:

A database agent could not be started at the remote computer because of a memory allocation failure.
A database agent was forced off of the remote computer.
A database agent on the remote computer was terminated.
The connection was closed by the remote gateway or server at the TCP/IP level.

Systematically investigate and resolve the possible causes:

Failure to start a new database agent

Investigate diagnostic logs at the remote computer to determine whether any memory limits have been exceeded and memory allocation failures happened as a result.
If any memory limits have been reached at the remote computer, or if there were memory allocation failures at the remote computer, work with a database or system administrator to resolve the cause of the memory allocation problems, and then retry the unit of work.

Database agent forced off

Investigate whether any events might have forced a database agent off of the remote computer, such as an administrator forcing all users and agents off the remote computer to perform maintenance.
If database agents have been forced off the remote computer, work with you database or system administrator to bring the database server back online and ready to process requests, and then retry the unit of work.

Database agent terminated

Investigate whether any failures on the remote computer might have terminated a database agent. For example, the termination of a key database manager process might cause the termination of a database agent.
If failures on the remote computer have terminated a key database manager process, work with you database or system administrator to bring the database server back online and ready to process requests, and then retry the unit of work.

Connection closed by the remote gateway or server

Firewall software errors or failure
Power failure
Network failure

If you have eliminated the possible causes listed here, collect diagnostic information using the db2support command and then contact IBM software support.

sqlcode: -1645

sqlstate: 08001

SQL1646N

A routine failed because the fenced user ID cannot access required files in the sqllib directory or other instance or database directories.

The database manager runs user defined functions and stored procedures outside of the DB2 database address space by running those routines as the DB2 fenced user. The default fenced user ID is "db2fenc1" and the default group is "db2fadm1".

The fenced user ID needs to be able to access DB2 database-related files, such as executable and library files, in the sqllib directory and other instance and database directories. When the instance and database directories are created by the database manager, the file and directory operating system permissions are set correctly and should not be changed.

This message can be returned when you are working with fenced stored procedures or routines directly, or when a DB2 utility, such as the health monitor, runs as a fenced mode process.

The most common cause of this error is that the operating system file permissions for DB2 database-related files or directories were accidentally changed after the database manager created the instance and database directories.

Respond to this error by performing the following troubleshooting steps:

If possible, determine which file or directory the database manager or the db2fmp process itself was unable to access by reviewing available database diagnostic information (such as the db2diag log files) or operating system diagnostic information.
Compare the operating system permissions on DB2 database-related files and directories, including the sqllib directory and the db2fmp executable itself, with the documented default permissions that the database manager would have set when the instance and database directories were initially created.

sqlcode: -1646

sqlstate: 58004

SQL1648N

The SQL statement or command cannot be processed because of the state of a DB2 member or CF in a DB2 pureScale environment. Member = member-id. Reason code = reason-code.

The state of a DB2 member or CF prevents the SQL statement or command from being processed. This could be a result of one of the following reasons:

1: The database manager is being stopped or started on a member.
2: Member crash recovery is being performed for a failed member.
3: The statement or command cannot be issued from a DB2 member that has a code level higher than the current effective code level (CECL). When there is a fix pack update in progress on a DB2 pureScale instance, you can have DB2 members with a higher code level than the CECL. Some statements and commands can only be issued from DB2 member that have the same code level as the CECL.
4: The statement or command is not supported because there is a fix pack update in progress and at least one DB2 member or cluster caching facility (CF) have a different code level than the CECL. Some statements and commands are only supported when all DB2 members and CFs have the same code level as the CECL. The value of "*N" as the member-id indicates that the condition is not specific to a particular member or CF.
5: A connection to or activation of the database cannot be made because one or more commands, statements, or operations that are not compatible is in progress.
6: After an add member operation, the first use of the database failed because no members have been started.
7: After an add member operation, the first use of the database failed because the database is not active on any previously existing member (a member that was in the database manager instance the last time the database was usable, before the new member was added.) The use of the database was blocked because some actions of the add member operation have not yet completed.
8: A connection to the database for the first time after the member was added failed because of an error while processing it on another member.
9: The operation cannot be initiated from a member that was not on the source member topology.
10: An add member operation was attempted from a different code level than the CECL, or an add member operation was attempted while the database manager instance is in a heterogeneous state.
11: The command failed because after a drop member operation, an explicit connection to the database must be made.

Respond this message by performing the corresponding action for each reason code:

1

Wait until the DB2 member is available. Then re-issue the statement or command.

2

Wait until crash recovery is completed and the DB2 member is available. Then re-issue the statement or command.

3

Perform one of the following actions:

Re-issue the statement from a member that has a code level equal to the CECL.
Complete the fix pack update so that all members are at the same code level as the CECL, then re-issue the statement from any DB2 member.

4

Complete and commit the fix pack update operation. After all the DB2 members and CFs are at the same code level, retry the operation.

5

Wait until the restricted operation is completed, then rerun the command.

6

Respond to reason code 6 by performing the following actions:

Start a previously existing member (a member that was in the database manager instance the last time the database was usable.)
Connect to or activate the database on that previously existing member.
Re-attempt to connect to the database on the newly added member.

7

Respond to reason code 7 by performing the following actions:

Cause any uncompleted actions of the add member operation to finish by connecting to or activating the database on a previously existing member (a member that was in the database manager instance the last time the database was usable.)
Perform the failed operation again.

8

Make necessary configuration changes to avoid exceeding database or operating system limits and re-issue the command.

9

Connect to the database from a member that was in the source member topology.

10

To add a member, move the database manager instance to a homogeneous state (in other words, bring all DB2 members and CFs to the same code level) and then issue the add member request from a member that is part of the instance.

11

Connect to the database from an existing member, then rerun the command.

sqlcode: -1648

sqlstate: 57061

SQL1649W

Deactivate database is successful, however, the database remains available in suspended I/O write operations mode.

The database cannot be shutdown while it is in suspended I/O write operations mode. The database will be shut down when I/O write operations are resumed.

No action required. Issue a 'SET WRITE RESUME' command to resume I/O write operations and deactivate the database completely.

SQL1650N

The function invoked is no longer supported.

The user has attempted to call an API that is no longer supported in this version of the database manager.

The function required may be supported by a different API call.

If your Windows application calls the sqledgne API or the db2DbDirGetNextEntry API with a pre-V9 version number, it must be updated to call the db2DbDirGetNextEntry API with the current version number.

SQL1651N

The request cannot be executed because the database server version does not support this functionality.

Some new functionality is not supported against older database server versions. Another possible cause of this error could be the request referenced objects with qualifiers of length that exceeds the support of the server version.

Execute the request against a database server where the latest database server version has been installed, or upgrade the server to the latest database server version.

SQL1652N

File I/O error occurred.

Error occurred either opening, reading, writing, or closing a file.

Check the db2diag log file for details. Also, check for disk full conditions, file permissions, and operating system errors.

SQL1653N

An invalid profile path was specified.

A full path to a file where server information should be generated must be specified.

Ensure that the profile path specified is correct and not null.

SQL1654N

An instance path error was encountered.

The instance path could not be returned.

Check that the DB2INSTANCE path was specified correctly. Check that the complete path length specified is not approaching the maximum supported by the operating system.

SQL1655C

The operation could not be completed due to an error accessing data on disk.

The failure to complete the operation is due to a problem in accessing data on a disk. The SQL statement has been rolled back or the operation has been aborted. The database remains accessible.

The application can retry the operation, although it may continue to fail. If the operation continues to fail, it may be necessary to contact the DB2 system administrator to investigate further.

Check the administration notification log for details that may help to diagnose the problem. Investigate the errors and determine the cause, possibly involving IBM Software Support.

If DB2 data is determined to be in error, then restore and rollforward the table space or database.

If hardware or other software is determined to be the cause, repair the systems involved (possibly requiring a DB2 outage).

sqlcode: -1655

sqlstate: 58030

SQL1656C

An error occurred while processing data. The operation could not be completed, but the database remains accessible. Contact IBM Software Support.

The failure to complete the operation is due to a detected DB2 page inconsistency. The SQL statement has failed or the operation has been aborted. The database remains accessible.

Contact IBM Software Support for instructions on what diagnostic data to collect to assist in resolving this issue. The application can retry the operation, although it may continue to fail.

sqlcode: -1656

sqlstate: 58004

SQL1657W

The database was successfully deactivated. Because the database is an HADR primary database and because the database was in disconnected peer state when it was deactivated, crash recovery will automatically be performed on the database when it is restarted.

In general, you can deactivate an HADR primary database using one of the following methods:

DEACTIVATE DATABASE command or the sqle_deactivate API
db2stop command with the FORCE option

If an HADR primary database is deactivated while it is in disconnected peer state, the database will be deactivated in an inconsistent state, and crash recovery will automatically be performed when the database is restarted.

Attempts to perform offline backup operations on this database will fail until the database is successfully restarted.

No response is required.

When the database is restarted, the database manager will automatically perform crash recovery for this database.

SQL1658N

The quiesce operation failed for the object named name. Reason code: reason-code.

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

The specific reason this message was returned is indicated by the reason-code:

1: An attempt was made to quiesce a database that is in WRITE SUSPEND state.
2: An attempt was made to quiesce a database manager instance in which at least one databases is in WRITE SUSPEND state.

Respond to this error according to the reason code:

Reason code 1

To quiesce a database that is in WRITE SUSPEND state perform the following steps:

Resume writes on the database using the SET WRITE command with the RESUME option or using the db2SetWriteForDB API with the DB2_RESUME_WRITE option.
Re-issue the quiesce operation.

Reason code 2

To quiesce an instance in which there are one or more databases in WRITE SUSPEND state perform the following steps:

Determine which databases are in WRITE SUSPEND state by reefrring to the suspend_io configuration parameter for each database in the instance.
For each database that is in WRITE SUSPEND state, resume writes on the database using the SET WRITE command with the RESUME option or using the db2SetWriteForDB API with the DB2_RESUME_WRITE option.
Re-issue the quiesce operation.

SQL1659N

The database manager started with fewer Host Channel Adapters (HCAs) than configured for the cluster caching facilities (CFs) or members.

The database manager encountered a non-critical error when starting. Communication could not be established with one or more HCAs on a cluster caching facility (CF) or member, however each CF or member is connected by at least one HCA. With fewer HCAs the CF or member has less throughput capacity. There is also a greater risk of downtime due to the reduced redundancy.

Review cluster alerts by running 'db2cluster -cm -list -alert' to see which HCAs are not responding. Follow the corrective actions given by the alerts to rectify any reported problem.

SQL1660N

The Generator at the server, which is used by Discovery to gather server information, has failed.

A server system failure has occurred.

Report the failure to your database server administrator. More details of the failure can be found in the server's db2diag log file.

SQL1661N

The query failed because the information you are trying to retrieve could not be found on the HADR standby database.

The statement or command is trying to retrieve an XML value that is not available on the HADR standby database. This might be because that value has not yet been replayed on the standby.

Retry your query on the read-enabled HADR standby later, or submit the query against the HADR primary database.

sqlcode: -1661

sqlstate: 58004

SQL1662N

Log archive compression failed while archiving or retrieving log file log-file for log-archive-method for database database on member member-number. Reason code: reason-code.

While archive log file compression is enabled, an error occurred when archiving or retrieving an archived log file.

Check the db2diag.log file for more details.

Contact IBM Support.

SQL1663W

Log archive compression is not fully enabled for log-archive-method.

Log archive compression is not fully enabled for log-archive-method until log-archive-method is set to DISK, TSM, VENDOR or DB2REMOTE.

You can change log-archive-method to DISK, TSM, VENDOR or DB2REMOTE with the UPDATE DATABASE CONFIGURATION command.

SQL1664W

A warning code was received from an in-database analytics provider. Warning code: warning-code. Provider name: provider-name. Associated text and tokens: tokens.

You can perform in-database analytics using an embedded analytics provider.

While referencing an in-database analytics provider, an unexpected warning code was received from the specified provider.

Respond to this error by performing the following troubleshooting steps:

Identify and correct the root cause of the warning by locating the appropriate message text and corrective action for the specified error at the provider.
Check any appropriate diagnostic logs that are generated by the provider.

sqlcode: +1664

sqlstate: 01699

SQL1665N

The command failed because log archive compression is not supported when raw devices are used for database logging.

Log archive compression is not supported when log files, yet to be archived, are on raw devices. You receive this error when:

A command to enable log archive compression was issued and the LOGPATH or NEWLOGPATH database configuration parameters already point to raw devices.
A command to set the NEWLOGPATH database configuration parameter to a raw device was issued and log archive compression is already active.
A command to enable log archive compression and set the NEWLOGPATH database configuration parameter to a raw device was issued.

If you want to use log archive compression, ensure that both LOGPATH and NEWLOGPATH do not point to raw devices.

If you must set NEWLOGPATH to point to a raw device, first disable log archive compression, then retry setting the NEWLOGPATH configuration parameter.

SQL1666N

The table definition statement failed because some functionality was specified in the table definition that is not supported with the table type. Unsupported functionality: functionality-keyword.

This message is returned when an attempt is made to create or alter a table with functionality that is not supported with that type of table.

The functionality-keyword runtime token lists the clause or keyword that indicates the unsupported functionality.

Review the supported functionality and restrictions of the type of table. Then submit the statement again, specifying only functionality that is supported with the table type.

sqlcode: -1666

sqlstate: 42613

SQL1667N

The operation failed because the operation is not supported with the type of the specified table. Specified table: table-name. Table type: table-type. Operation: operation-keyword.

This message is returned when an attempt is made to perform an operation against a table that is not supported with that type of table.

Review the supported functionality and restrictions of the type of table. Then submit the statement again, specifying only functionality that is supported with the table type.

sqlcode: -1667

sqlstate: 42858

SQL1668N

The operation failed because the operation is not supported with this environment. Reason code: reason-code.

This message is returned when an attempt is made to perform an operation that is not supported in a specific environment. The reason code indicates why the operation failed:

1

The database includes one or more column-organized tables and the operation tried to enable or use functionality that is not supported with column-organized tables.

4

An attempt was made to create a column-organized table in an operating system environment that is not supported with column-organized tables.

5

An attempt was made to use column-organized tables in an environment in which intrapartition parallelism is disabled.

6

An attempt was made to use column-organized tables in a partitioned database environment.

7

An attempt was made to use column-organized tables in a DB2 pureScale environment.

8

An attempt was made to create or access a column-organized table in an XA transaction.

9

This message is returned with reason code 9 when an attempt is made to use self-tuning for sort memory with column-organized table functionality:

An attempt is made to set one or both of the following configuration parameters to "AUTOMATIC" when there are one or more column-organized tables in the database: SORTHEAP, SHEAPTHRES_SHR.
An attempt is made to create a column-organized table while one or both of the following configuration parameters was set to "AUTOMATIC": SORTHEAP, SHEAPTHRES_SHR.
An attempt is made to have the SHEAPTHRES_SHR configuration parameter set "AUTOMATIC" and the WLM_ADMISSION_CTRL configuration parameter to "YES" at the same time.

10

An attempt was made to create a shadow table by specifying the MAINTAINED BY REPLICATION clause in a partitioned database environment or in a DB2 pureScale environment.

11

An attempt was made to perform an external table operation in DB2 environment on windows operating system.

12

An attempt was made to enable the adaptive workload manager in an environment where it is not supported. The adaptive workload manager can only be enabled when the SHEAPTHRES_SHR and SORTHEAP configuration parameters are not set to AUTOMATIC.

14

An attempt was made to create or drop a remote table space that is not supported.

15

An attempt was made to create a row-organized table or data partition of the table in a remote table space.

16

An attempt was made to create or alter a table to use a remote table space for the index table space, or create an index on a remote table space.

17

An attempt was made to either create or drop a storage group that is using remote storage in an environment where this operation is not supported.

18

An attempt was made to create a 'remote user' temporary table space that is not supported.

19

An attempt was made to create, drop or alter a remote table space storage group that is not supported.

20

An attempt was made to alter a storage group that is using remote storage in an environment where this operation is not supported.

22

An attempt was made to create a 'remote system' temporary table space that is not supported.

23

An attempt was made to use the following options on a remote table space: The ALTER TABLESPACE options REBALANCE, CONVERT TO LARGE, AUTORESIZE NO, INCREASESIZE, FILE SYSTEM CACHING, LOWER HIGH WATER MARK, or REDUCE; The CREATE TABLESPACE options AUTORESIZE NO, INITIALSIZE, INCREASESIZE, or FILE SYSTEM CACHING.

24

An attempt was made to create, drop, or restore table space when COS deletes are suspended.

26

An attempt was made to backup or restore a database or table space using remote storage in an environment where this operation is not supported.

27

An attempt was made to start a pureScale instance in an environment that does not support remote storage table spaces.

28

An attempt was made to issue an HADR command in an environment that does not support remote storage table spaces.

29

An attempt was made to issue a command that is not supported in strict FIPS mode.

Respond to this error according to the reason code:

1

To enable functionality that is not supported with column-organized tables, drop and recreate existing column-organized tables as row-organized tables.

5

Enable intrapartition parallelism and then execute the operation again. Ensure that enough shared sort heap is available by setting the DB2_WORKLOAD registry variable to ANALYTICS or setting the sheapthres database manager configuration parameter to 0.

4, 6, and 7

Create the table as a row-organized table.

8

Respond to reason code 8 in the following ways:

Create or access column-organized tables in only non-XA transactions.
In XA transactions, create or access only row-organized tables.

9

Respond to reason code 9 in the following ways:

To use column-organized tables, or to create a column-organized table), disable self-tuning for sort memory by setting the SORTHEAP and SHEAPTHRES_SHR configuration parameters to appropriate, numerical values instead of "AUTOMATIC".
To use self-tuning for sort memory, use row-organized tables instead of column-organized tables.

10

Shadow tables cannot be created in a partitioned database environment or in a DB2 pureScale environment. However, to create a materialized query table that is not a shadow table, create the table without specifying the MAINTAINED BY REPLICATION clause.

11

External table operation cannot be performed in DB2 environment on windows operating system.

12

Ensure that the SHEAPTHRES_SHR and SORTHEAP configuration parameters are not set to AUTOMATIC.

14

Create a non-remote table space.

15

Create the row-organized table or data partition in a non-remote table space.

16

If the INDEX IN clause for the create table, alter table, or create index specifies a remote table space then use a non-remote table space instead. Else, if this was an attempt to create an index or enforced constraint where the index table space is remote, this is not supported. If the index is necessary, then you'll need to recreate the table to use a non-remote table space for the index table space.

17

Create a storage group that uses local storage. Note that you cannot drop a storage group that uses remote storage.

18

Create a user temporary table space on a non-remote storage group.

19

Not supported.

20

A storage group that is using remote storage does not support the SET AS DEFAULT, ADD or DROP storage path alter operations.

22

Create a system temporary table space on a non-remote storage group.

23

A remote table space does not support the following command options: The ALTER TABLESPACE options REBALANCE, CONVERT TO LARGE, AUTORESIZE NO, INCREASESIZE, FILE SYSTEM CACHING, LOWER HIGH WATER MARK, and REDUCE; The CREATE TABLESPACE options AUTORESIZE NO, INITIALSIZE, and INCREASESIZE, FILE SYSTEM CACHING.

24

Disable 'suspend_cos_deletes' configuration and then execute the operation again.

26

A backup or restore operation involving a database or table space using remote storage is not supported.

27

Update the environment to not allow the creation of remote storage table spaces and re-try starting the instance.

28

The use of HADR involving a database or table space using remote storage is not supported.

29

Check whether you are in strict FIPS mode. Certain functionality might be disabled for FIPS compliance. To verify that you are in strict FIPS mode on a server or instance-based client, check whether the DB2AUTH registry variable is set to STRICT_FIPS. If you are on an instance-less client, check the DB2AUTH environment variable for the same value. If you are on a client, use the ENV_GET_REG_VARIABLES table function to check the registry variable on the server.

sqlcode: -1668

sqlstate: 56038

SQL1669W

The operation operation-keyword succeeded. However the following option was ignored: SQL-keyword.

This message is returned when an attempt is made to perform an operation that is neither supported with column-oriented tables nor blocked with column-oriented tables.

For example, this message can be returned when an attempt is made to use the ALTER TABLE statement to turn off append mode for a column-organized table. Column-organized tables are always in append mode, so turning append mode off is not supported and attempts to turn append mode off are ignored.

No response is required.

SQL1670N

The discover type specified in the DISCOVER database manager configuration parameter indicates discovery is disabled.

DISCOVER = DISABLE is configured in the database manager configuration file.

If DISCOVER functionality is required, change the discover type to KNOWN or SEARCH.

SQL1671N

The search discovery request failed. Check the administration notification log for further details.

The search discovery request failed for one of the following reasons:

Initialization failed (sqleCommonInitializationForAPIs)
Failed to retrieve the client instance path (sqloinstancepath)
Failed to open the output file (sqlofopn)
Failed to write to output file (sqlofprt)
Failed to get memory (sqlogmblk)
Failed to retrieve database manager configuration (sqlfcsys)
DB2 internal system function failed (sqlogpid, sqlogmt)

Check the db2diag log file for details.

If initialization fails, try re-booting the machine or re-installing the product.
If there was an instance path failure, check the DB2INSTANCE value to ensure it is correctly set.
If the open or write to file failed, check that you have access to open and write a file to the <sqllib path>\<instance>\tmp directory on Windows machines, or the <instance path>/sqllib/tmp directory on UNIX machines.
If get memory failed, check the available memory on your machine.
If retrieving the DBM configuration failed, try re-booting the machine or re-installing the product.
If a DB2 internal system function failed, check that the operating system functions on your machine are functioning correctly.

DB2 Service can provide details about the error codes returned by these functions and written to the db2diag log file.

SQL1673N

The address list specified as input to the discover interface is invalid.

The application program used an invalid input address list pointer. The address list points to nothing.

Ensure that a valid input address list pointer is specified in the application program, and that it is not null.

SQL1674N

The server address specified as input to the discover interface is invalid.

The application program used an invalid input server address pointer. The server address points to nothing.

Ensure that a valid input server address is specified in the application program, and that it is not null.

SQL1675N

Discovery is only allowed against DB2 administration servers. The communications information provided does not access an administration server.

A KNOWN discovery request was issued against a database server that is not a DB2 administration server. The communications information specified is not correct.

Verify that DB2ADMINSERVER is set on the database server instance you are accessing. This indicates that the server instance is a DB2 administration server. Retry the KNOWN discovery request with the correct communications information.

SQL1676N

The CREATE TABLE STATEMENT failed because functionality that is not compatible with the specified type of table is currently enabled for the database. Incompatible functionality keyword: functionality-keyword.

You can create column-organized tables by using one of two different methods:

Specifying the ORGANIZE BY COLUMN clause with the CREATE TABLE statement
Setting the DFT_TABLE_ORG database configuration parameter to COLUMN and then calling the CREATE TABLE statement without the ORGANIZE BY ROW clause

This message is returned when an attempt is made to create a column-organized table while functionality that is not supported with column-organized tables is enabled in the database. The run-time token functionality-keyword indicates the nature of the functionality that is incompatible.

Respond to this message in one of the following ways:

To be able to create a column-organized table, disable the functionality identified in the run-time token functionality-keyword.
To create a table with the functionality identified in the run-time token functionality-keyword still enabled, create a row-organized table instead of a column-organized table.

SQL1677N

DB2START or DB2STOP processing failed due to a DB2 cluster services error.

DB2 cluster services failed to perform the required operation.

Troubleshoot the DB2 cluster services status using the db2cluster command and the db2instance command.

In an environment with multiple members and cluster caching facilities (CFs), collect diagnostic details from the host machine where the members and CFs reside.

SQL1678W

DB2START of CF with identifier identifier was not possible on host host-name because the instance was previously stopped using the "db2stop INSTANCE ON" command. CF duplexing is not available on this instance.

While multiple cluster caching facilities (CFs) are configured in this database manager instance, the CF has been temporarily disabled by the user from participation in the instance through the use of "db2stop INSTANCE ON" command.

Typical reasons for this are to allow for rolling upgrades of the CF or, to allow the instance to start without CF duplexing. If the CF server failed to start with an error this allows the instance to be started up while the source of the error is resolved by the user.

Once the CF becomes available, issue a "db2start INSTANCE ON" command followed by "db2start CF" command to start the CF and to make it available for the instance. CF duplexing will automatically be re-established by the database manager once the CF is started.

SQL1679N

DB2START was unable to start a CF with identifier identifier on host host-name. Reason code reason-code.

The reason code indicates why this error was returned:

1

This message can be returned with reason code 1 for multiple reasons, including the following reasons:

The host on which the cluster caching facility (CF) is located is unavailable.
A TCP/IP communication error occurred while trying to establish a connection with the host on which the CF is located.
DB2 cluster services was unable to allocate memory for the CF because the CF memory database manager configuration parameter CF_MEM_SZ is set to a value that is larger than the amount of memory that is available.

Respond to this message according to the reason code:

1

Perform the following troubleshooting activities:
- Ensure that the host has the proper authorization defined in the .rhosts or the host.equiv files to execute remote commands.
- Ensure that the application is not using more than the maximum allowed file descriptors at the same time: 500 + (1995 - 2* total_number_of_nodes)
- Ensure all the Enterprise Server Edition environment variables are defined in the profile file.
- Ensure the profile file is written in valid Korn Shell script format.
- Ensure that all the host names defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
- Ensure that the DB2FCMCOMM registry variable specifies the correct IP format to use (TCPIP4 or TCPIP6).
- Ensure that the CF_MEM_SZ database manager configuration parameter is set to a valid value.
Then, rerun the DB2START command.

SQL1680W

An error occurred during DB2START processing of DB2 member with identifier identifier on host host-name. Reason code reason-code. The database manager will asynchronously attempt to start the member in recovery mode on another available host.

An error was encountered while attempting to start the member on the host. The DB2START command has failed as a result of this error.

The reason code indicates why this error was returned:

1: Host is not reachable because the host is unavailable or a TCP/IP communication error occurred while trying to establish a connection with the host.

Respond to this message according to the reason code:

1

For reason code 1, perform the following troubleshooting activities:

Ensure that the host has the proper authorization defined in the .rhosts or the host.equiv files
Ensure that the application is not using more than (500 + (1995 - 2* total_number_of_nodes)) file descriptors at the same time.
Ensure all the Enterprise Server Edition environment variables are defined in the profile file.
Ensure the profile file is written in the Korn Shell script format.
Ensure that all the host name defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
Ensure that the DB2FCMCOMM registry variable is set correctly.
Rerun the DB2START command.

SQL1681W

DB2START of DB2 member with identifier identifier was not possible on host host-name as the instance was previously stopped using the "db2stop INSTANCE ON" command. The database manager will asynchronously attempt to start the DB2 member in light mode on another available host. While in recovery mode, the DB2 member will not accept any client connections.

The instance on the host was previously stopped by "db2stop INSTANCE ON" command. One of the reasons for doing so is to bring down the host for maintenance or software rolling upgrade. The member could not be started on this host. However, the database manager will attempt to start it in light mode on another available host.

The user can issue DB2 LIST command to find out if and on which host the member has been started. Once the software upgrade or maintenance work has been completed on the host, the user should issue "db2start INSTANCE ON" command to start up the instance on the host and then reissue "db2start MEMBER" command to relocate the member to this host.

SQL1682W

DB2START processing was successful on host host-name. Due to a previous DB2START failure of a DB2 member or host failure, the DB2 member has been relocated by the database manager to this host.

When the member was previously stopped, it was running in restart light mode. It will continue to run in restart light mode until its home host becomes active and database manager relocates it to its home host.

No user response is required.

SQL1683N

An error was encountered during DB2START processing. The database manager failed to restart the DB2 member with identifier identifier as a light member on host host-name.

The member failed to start as a light member on the host either because there was no DB2 idle processes running on the host or the animation of one of the DB2 idle processes failed.

Investigate the problems on the host.

SQL1684N

An error was encountered during DB2START processing. The database manager failed to start a component of the DB2 pureScale environment.

A component of the DB2 pureScale environment failed to start due to insufficient memory, CPU resources, or a problem with the DB2 cluster file system.

Run the db2cluster command to check the health of the DB2 cluster file system. Also ensure that the hosts in the DB2 pureScale instance have sufficient memory and CPU resources.

SQL1685N

An error was encountered during DB2START processing of DB2 member with identifier identifier because the database manager failed to start one or more CFs.

The database manager failed to start the cluster caching facilities (CFs), therefore the DB2 member could not be started.

There are multiple reasons for which this message can be returned. For example, this message can be returned because the CF_MEM_SZ memory configuration parameter was set to a value that is larger than the physical memory limit of the system. When this message is returned because CF_MEM_SZ is set too large, there will be messages in the db2diag log files indicating that there are not enough system resources to process requests.

Ensure that the instance is configured with functioning CFs by performing the following steps:
1. Identify problems with any CFs using the following db2cluster command:
```
db2cluster -cm -list -alert
```
2. Resolve the identified problems using the db2cluster command with the -clear parameter:
```
db2cluster -cm -clear -alert
```
If the CF is under maintenance, run the "db2start INSTANCE ON" command after the maintenance has completed.
To force the database manager instance to start without a redundant CF, manually start one CF by issuing the command "db2start 129", then start the instance by issuing the db2start command again.

SQL1686N

An error was encountered during DB2START processing on host host-name as the database manager failed to activate the host.

The database manager tried to start up the instance on the host while the DB2 cluster services failed to make the host active and rejoin the DB2 pureScale cluster.

Determine why the DB2 cluster services failed to make the host active and rejoin the DB2 cluster.

SQL1687N

An error was encountered during DB2STOP processing. The DB2 member with identifier identifier is performing restart recovery, or has unresolved indoubt transactions.

The member cannot be stopped when it is still performing restart recovery or has unresolved indoubt transactions.

Determine the status of this member using the db2instance command with the -list parameter. You can also use the DB2_MEMBER administrative view or the DB2_GET_INSTANCE_INFO table function.
Resolve the indoubt transactions, if they exist.

SQL1688N

DB2STOP failed to stop the CF with identifier identifier. Reason code reason.

The reason code indicates why this error was returned:

1: The cluster caching facility (CF) still contains dirty pages or holds locks.
2: The named CF is the only running CF in the instance.
3: The primary CF cannot be stopped until the secondary CF is in PEER state and ready to take over. The secondary CF has not yet completed the transition from the initial CATCHUP state to a PEER state.
4: The instance is in the process of failing over the CF primary role, no CF can be stopped.

Respond to this message according to the reason code:

1

Ensure that no active member is running. The user should also wait for the CF to flush out dirty pages before issuing the "db2stop CF" command again.

2

Perform the following steps:

If there are active members, stop each of the members using the "db2stop MEMBER" command.
After the members have been stopped, stop the CF with a global call to db2stop.

3

Wait for the secondary CF to transition to a PEER state before re-running this command. Refer to the STATE column in the DB2_CF administrative view for this information.

4

Stop the instance by running a global "db2stop FORCE" command.

SQL1689W

DB2STOP processing was successful. However, the DB2 member with identifier identifier was running in recovery mode on a host other than its home host host-name.

The member was successfully stopped, however the host it was running on was not its home host. It was running in light mode on another DB2 member's host. Typically it is not advisable to stop DB2 members that are running in light mode.

No user response is required.

It is recommended that if the member is running in light mode on a host other than its home host, the user performs the necessary actions so that the member is to be relocated by the database manager to its home host before stopping it.

SQL1690N

An error occurred during DB2STOP processing of a DB2 member or CF with identifier identifier on host host-name. Reason code reason-code.

The reason code indicates why this error was returned:

1: The host is not reachable because the host is unavailable or a TCP/IP communication error occurred while trying to establish a connection with the host.
2: The cluster manager successfully stopped the DB2 member or cluster caching facility (CF) even though there was a communication error.

This message can also be returned when a password has expired.

Respond to this message according to the reason code:

1

Perform the following troubleshooting activities for reason code 1:

Ensure that the host has the proper authorization defined in the .rhosts or the host.equiv files
Ensure that the application is not using more than (500 + (1995 - 2* total_number_of_nodes)) file descriptors at the same time.
Ensure all the Enterprise Server Edition environment variables are defined in the profile file.
Ensure the profile file is written in the Korn Shell script format.
Ensure that all the host name defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
Ensure that the DB2FCMCOMM registry variable is set correctly.
Verify whether the member or CF has been stopped by running the command "db2instance -list".

Then, rerun the DB2STOP command.

2

Verify whether the member or CF has been stopped by running the command "db2instance -list".

Review the db2diag log files for more information.

SQL1691N

An error was encountered during DB2STOP processing on host host-name. Reason code reason-code. The database manager failed to bring down the host for maintenance.

The reason code indicates why this error was returned:

1: One or more DB2 members or cluster caching facilities (CFs) were still active on the host and could not be stopped.
2: The instance was still active and the CF running on this host is not stoppable.

The instance on the host could not be stopped due to active DB2 members or CFs were running.

Respond to this message according to the reason code:

1: Run "db2stop MEMBER" or "db2stop CF" command to stop the member or CF prior to stop the instance on the host. To force the instance on the host to shut down, run "db2stop INSTANCE ON" command with FORCE option.
2: Ensure all members are stopped and retry "db2stop INSTANCE ON" command

SQL1692N

An error was encountered during DB2STOP processing. The database manager failed to stop a component of the DB2 pureScale environment.

A component of the DB2 pureScale environment failed to respond to the DB2 cluster services and did not shut down.

Determine which components of the database manager instance failed to stop using the following command:
```
db2instance -list
```
Stop the components that failed to stop by performing the following steps:
1. Collect more information about the reasons why these components failed to stop from the diagnostic information collected in the db2diag log files.
2. Resolve the problems that caused the components to fail to stop.
3. Stop the components manually.
[Optional] Clean up interprocess communications for the instance by running the following command as the instance owner at each physical partition:
```
$HOME/sqllib/bin/ipclean
```

SQL1693N

An error was encountered during DB2STOP processing on host host-name as the database manager failed to deactivate the host. The database manager failed to bring down the host for maintenance.

The database manager tried to stop the instance on the host while the DB2 cluster services failed to temporarily take the host out of the DB2 pureScale cluster.

Determine why the DB2 cluster services failed to temporarily take the host out of the DB2 pureScale cluster

SQL1694N

The command option option is not valid for a DB2 pureScale instance.

Some options are only supported on certain instance types. The option that was specified is not available with a DB2 pureScale instance.

Use the supported command options for DB2 pureScale instance.

sqlcode: -1694

sqlstate: 56038

SQL1695N

The command option option is not valid for an instance that is not a DB2 pureScale instance.

Some options are only supported on certain instance types. The option that was specified is not available with an instance that is not a DB2 pureScale instance.

Use the supported command options for instances that are not DB2 pureScale instances.

sqlcode: -1695

sqlstate: 56038

SQL1696N

Statement precompilation failed because the option COMPATIBILITY_MODE ORA was not specified. Reason Code: reason-code.

You can process an application program source file containing embedded SQL statements to produce a modified source file that contains host language calls for the SQL statements and to produce a package in the database by using the PRECOMPILE command or the PREP command.

You can configure the way the application source file is compiled by specifying precompile options with the PRECOMPILE command. For example, you can enable features that facilitate the migration of embedded SQL C applications from other database systems by specifying the precompiler option COMPATIBILITY_MODE ORA with the PRECOMPILE command.

This message is returned when an attempt is made to use a feature that requires the precompiler option COMPATIBILITY_MODE to be set to ORA, but the COMPATIBILITY_MODE ORA option was not specified.

The reason code, reason-code, indicates the reasons for the precompilation failure:

1: The UNSAFENULL precompile option was specified without the required COMPATIBILITY_MODE ORA option.
2: The "EXEC SQL COMMIT WORK RELEASE" or "EXEC SQL ROLLBACK WORK RELEASE", "EXEC SQL COMMIT RELEASE", or "EXEC SQL ROLLBACK RELEASE" statement was found in the embedded SQL code and PRECOMPILE command was issued without the required COMPATIBILITY_MODE ORA option.

Call the PRECOMPILE command again, specifying the required COMPATIBILITY_MODE ORA option.

SQL1697N

The statement cannot be precompiled because an indicator variable structure was specified that contains fewer members than the corresponding host variable structure. Indicator variable structure name: variable-name. Number of members in the host variable structure: number-of-members.

In embedded SQL applications, information about the contents of host variable structures can be stored in corresponding indicator variable structures. When an indicator variable structure is specified, the number of members in the indicator variable structure must be equal to the corresponding host variable structure.

This message is returned when the number of members in an indicator variable structure does not equal the number of members in the corresponding host variable structure.

Modify the embedded SQL application to declare equal number of members in the indicator variable structure as that of the host variable structure.
Recompile and rerun the embedded SQL application.

SQL1698N

The START DATABASE MANAGER command failed on a DB2 pureScale instance where fix pack updates are being applied or have been applied. Reason code: reason-code.

The reason code indicates why the START DATABASE MANAGER command failed:

1: The fix pack update installation on the member or cluster caching facility (CF) is corrupted.
2: During an online fix pack update, an attempt was made to start a member or CF with a code level lower than the current effective code level (CECL). To start a member or CF, their code level must be equal or higher to the CECL.
3: During an offline fix pack update, an attempt was made to start a member or CF with a code level that is not equal to the CECL. To start a member or CF, their code level must be equal to the CECL.
4: The fix pack update installation on a member or CF is incomplete.
5: The information about the CEAL and CECL is corrupted.
6: The CEAL or CECL database manager configuration parameter has an invalid value.
7: The instance information is missing from the configuration file for fix pack updates.

Respond this message by performing the corresponding action to the reason code:

1: Retry the fix pack update operation.
2: Update the member or CF to a code level equal or higher than the CECL. Then restart the member or CF.
3: Ensure that all members and CFs are at a code level equal to CECL. Then restart the member or CF.
4: Retry the fix pack update operation.
6: Recreate the instance.
7: Contact IBM support to assist you in the repair of the configuration file.

SQL1699N

The specified member subset attribute is not valid. Reason code = reason-code Attribute name: attribute-name Value: value

The statement cannot be processed because of the following reason code:

The specified value is only valid in a data sharing environment.

You cannot change a member subsets catalogDatabaseAlias attribute without also changing the databaseAlias attribute.

The database name cannot be used for the database alias attribute in a member subset.

The action corresponding to the reason code is as follows:

Reissue the member subset management routine with a different attribute value.

Specify a new databaseAlias attribute value or do not change the catalogDatabaseAlias attribute value.

Specify another name for the databaseAlias attribute value.

sqlcode: -1699

sqlstate: 530AA

SQL1700N

The reserved schema name name was found in the database during database upgrade.

The database contains one or more database objects using the schema name name which is a reserved schema name in the DB2 copy version to which you want to upgrade the database.

The command cannot be processed.

Ensure that all the database objects that use the reserved schema name are dropped and recreate the objects using a different schema name.

Reverse the database upgrade and make the corrections using the DB2 copy version where the database resided prior to the database upgrade.

Ensure that no reserved schema names are in use before attempting the database upgrade again.

Then, re-issue the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade the database.

SQL1701N

The database cannot be upgraded because the database terminated abnormally.

The database terminated abnormally (for example, due to a power failure) before attempting to upgrade the database. You must restart the database before you can upgrade the database successfully.

The command cannot be processed.

You must issue the RESTART DATABASE command using the DB2 copy where the database resided prior to attempting to upgrade the database. Then, re-issue the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade.

SQL1702W

The protocol connection managers have started successfully.

No action required.

SQL1703W

The db2event directory could not be created during database upgrade.

The database was upgraded successfully but the db2event directory could not be created.

This is a warning only.

The db2event directory must be created to use the event monitor. The db2event directory must be created in the database directory where the upgraded database resides. The database directory of the upgraded database can be determined by issuing the LIST DATABASE DIRECTORY command.

SQL1704N

Database upgrade or update request failed. Reason code reason-code.

Database upgrade or update request failed. The reason codes are as follows:

2

database cannot be upgraded because it could be in one of the following states:

backup pending state
restore pending state
roll-forward pending state
transaction inconsistent state
HADR has marked the database inconsistent

3

database logs are full.

4

insufficient disk space.

5

cannot update database configuration file.

7

failed to access the database subdirectory or one of the database files.

8

failed to update database container tag.

9

table space access is not allowed.

17

Failure to allocate new page from the system catalog table space.

21

Database upgrade is complete on the catalog partition but not on all the other database partitions. There are database partitions that cannot be upgraded due to system errors, such as node failure or connection failure.

22

Database upgrade failed because the catalog partition cannot be upgraded due to system errors, such as database partition failure or connection failure.

24

Error creating the dbpath/db2event/db2detaildeadlock event monitor directory where dbpath is the file path used to create the database.

25

Database upgrade failed because the HADR primary's log shipping position does not match the HADR standby's log replay position.

26

Database update is already in progress.

Possible solutions based on the reason code are:

2: Reverse the database upgrade and correct the database state by performing any necessary corrective action in the DB2 copy version where the database resided prior to the upgrade. For HADR systems, stop HADR should be issued prior to attempting to upgrade the HADR primary database. Resubmit the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade the database.
3: Increase the database configuration parameters logfilsiz or logprimary to a larger value. Resubmit the UPGRADE DATABASE command.
4: Ensure that there is sufficient disk space and resubmit the UPGRADE DATABASE command.
5: There was a problem in updating the database configuration file. Ensure that the database configuration file is not being held exclusively by any users and is updatable. Resubmit the UPGRADE DATABASE command. If the problem persists, inform your IBM service representatives.
7: Restore the database from the database backup.
8: Resubmit the UPGRADE DATABASE command. If the problem persists, contact your IBM service representative.
9: Reverse the database upgrade and correct the table space access. Resubmit the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade the database. Refer to message SQL0290N for the suggested actions to take to correct the table space.
17: If the system catalog table space is an Automatic Storage DMS table space or SMS table space, ensure that there is at least 50% free disk space available for the system catalog table space, then upgrade the database. If the system catalog table space is a DMS table space. Reverse the database upgrade and add more containers to the system catalog table space from the DB2 copy version where the database resided prior to upgrade. You should allocate 50% free space for database upgrade. Resubmit the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade the database.
21: Check the administration notification log to determine the database partitions that cannot be upgraded. Correct the situation and resubmit the UPGRADE DATABASE command. As database upgrade only takes place on database partitions that require upgrade, you can submit the UPGRADE DATABASE command from any database partition.
22: Correct the database partition failure situation on the catalog partition. Resubmit the UPGRADE DATABASE command.
24: Remove the dbpath/db2event/db2detaildeadlock event monitor directory where dbpath is the file path used to create the database. Resubmit the UPGRADE DATABASE command.
25: Issue the STOP HADR command on the primary database followed by reissuing the UPGRADE DATABASE command. The standby database will have to be re-initialized.
26: The database update is already in progress and must be completed before any further actions can be taken against the database.

SQL1705W

Unable to update a database directory entry to the current release level.

One or more database aliases could not be updated in the database directory for a database which has just been upgraded from a previous release.

Uncatalog database aliases for the upgraded database and re-catalog them using the same information.

SQL1706W

At least one non local database was detected in the node directory for this instance during word size instance update.

While performing word size instance update, at least one database not created under this instance was encountered. Such databases must have the same word size as this instance for instance update to complete successfully.

Ensure that all databases cataloged at the instance have the same word size.

SQL1707N

Unable to update the instance word size.

There was an error while attempting to update the word size of the instance. Please contact your IBM service representative.

Contact your IBM service representative.

SQL1708W

Database upgrade is completed with the warning-code warning code.

Database upgrade is completed with a warning. The warning codes are as follows:

1: One or more database partitions were not upgraded.

Possible solution based on the warning codes:

1: Re-issue the UPGRADE DATABASE command.

SQL1709N

The CREATE INDEX statement failed because the RANDOM keyword was specified and functionality that is not supported with the RANDOM keyword was included in the index definition. Reason code: reason-code.

You can reduce some types of index page contention in DB2 pureScale environments by randomizing the keys of indexes. Specifying the RANDOM keyword for a column will cause the index keys for that column to be randomized.

There are some restrictions on functionality that is supported with the RANDOM keyword. This message is returned when a CREATE INDEX statement includes the RANDOM keyword, but some other functionality that is included in the index definition is not supported with the RANDOM keyword.

The reason code indicates more specifically why this message was returned:

1: The RANDOM keyword was specified for a column that is a of type CHAR or VARCHAR, the database was using UCA collation and the column was not defined as FOR BIT DATA.
2: The RANDOM keyword was specified for a column that is a of type GRAPHIC or VARGRAPHIC and the database was using UCA collation.
3: The index definition included one or more expression-based keys.

Respond to this error according to the reason code:

1

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

Resubmit the CREATE INDEX statement, specifying the RANDOM keyword with a column that is a data type that is supported with the RANDOM keyword.
Alter the column so that the column is identified as FOR BIT DATA by issuing the ALTER TABLE statement, reorganize the table, and then resubmit the CREATE INDEX statement.

2

Resubmit the CREATE INDEX statement, specifying the RANDOM keyword with a column that is a data type that is supported with the RANDOM keyword.

3

Resubmit the CREATE INDEX statement using either the RANDOM keyword or an expression-based key but not both.

sqlcode: -1709

sqlstate: 42997

SQL1710N

The operation cannot be performed because the source member topology and the target member topology have no common member.

The target member topology does not contain a common member with the source member topology. The source and target members must have at least one common member.

Rerun the command against an instance with at least one common member with those in the source member topology.

SQL1712N

The command failed. The source and target member topologies are different, and the source and target instances are not at the same database product level. Command: command-token

The specified command failed because both conditions are true:

The source and target member topologies are different, and
The source and target instances are not at the same database product level.

For the specified command to run successfully, you must fix one of these conditions.

You can either:

Upgrade the down-level source database to the higher level, then rerun the command, or
Match the topologies by either adding or dropping a member to the source member topology or the target member topology.

SQL1713N

CATALOG DATABASE command failed. One or more files in the member database directories do not belong to the same database.

The command failed because an inconsistency was found in at least one of the files.

Cleanup the member database directories for the members that do not belong to this database, and rerun the command.

SQL1714N

The ROLLFORWARD command failed because it was run on a member that did not exist in the source member topology.

Following a backup and restore, if the target member topology contains all the member identifiers contained in the source member topology, you can roll forward through one or more add member events in the transaction logs. However, the ROLLFORWARD command must be run from a member that existed in the source member topology at the time of the backup operation.

Rerun the ROLLFORWARD command from a member that existed in the original source member topology.

SQL1715N

The rollforward operation encountered an add member event for a member that does not exist in the current member topology.

During a roll forward operation, if the ROLLFORWARD command encounters an add member log record for a member, that member must exist in the member topology.

Add the member that was on the source member topology and is not in the current member topology. Rerun the ROLLFORWARD command.

SQL1716N

Alter or drop the member failed because the resulting subset does not have a primary member.

A member subset must contain at least one primary member.

Before dropping or altering the specified member, add another primary member to the subset. To add another member to the subset, run the SYSPROC.WLM_ALTER_MEMBER_SUBSET routine. If you no longer need the member subset, drop the member subset by running WLM_DROP_MEMBER_SUBSET statement.

sqlcode: -1716

sqlstate: 530AB

SQL1717N

Connection to the database alias rejected because the application was assigned to a member subset that is disabled. Database alias: database-alias-token Member subset: member-subset-token

The connection request was rejected because the application was assigned to a disabled member subset.

You can either connect to a different database alias or enable the member subset. To enable the subset, use the alter member subset management routine WLM_ALTER_MEMBER_SUBSET.

sqlcode: -1717

sqlstate: 08001

SQL1718N

The database alias database_alias cannot be uncatalogued.

If a database alias was cataloged using member subset routine WLM_CREATE_MEMBER_SUBSET, the database alias must be uncataloged using a member subset routine. Neither the UNCATALOG DB command nor the sqleuncd() API can be used to uncatalog this database alias.

Uncatalog the database alias using member subset routine WLM_DROP_MEMBER_SUBSET.

SQL1719N

The SQL statement failed because column-organized tables are not supported. Reason code: reason-code

Column-organized tables are not supported when certain conditions are true. The conditions are indicated by the following reason codes:

1: Intra-partition parallelism is disabled.
2: Database partitioning feature is enabled.
3: DB2 pureScale feature is enabled.

Perform the action corresponding to the reason code to enable support of column-organized tables:

1: Enable Intra-partition parallelism and re-issue the SQL statement.
2: Re-create the table as row-organized table and re-issue the SQL statement.
3: Re-create the table as row-organized table and re-issue the SQL statement.

sqlcode: -1719

sqlstate: 56038

SQL1720N

Could not drop the only member.

You cannot drop the only member that the database could be connected to because dropping the member, results in dropping the database. The database must be dropped first.

First drop the database, then drop the member.

SQL1721N

Starting the database manager failed because of a problem with a configuration file that is needed by RDMA.

In DB2 pureScale environments, you can specify that communication between the cluster caching facility (CF) and DB2 members uses Remote Direct Memory Access (RDMA) by setting the database manager configuration parameter CF_TRANSPORT_METHOD to "RDMA".

This message is returned when the CF_TRANSPORT_METHOD configuration parameter is set to "RDMA" and there is a problem with configuration files related to RDMA functionality.

Examples of problems that could cause this message to be returned:

The direct access transport (DAT) configuration file, dat.conf, is missing or contains invalid entries
Files are missing from the OpenFabrics Enterprise Distribution (OFED) package

Respond to this error in one of the following ways:

If using RDMA is not needed, unset the CF_TRANSPORT_METHOD database manager configuration parameter.
To use RDMA, verify files associated with DAT configuration, such as the dat.conf file, and file associated with the OFED software.

SQL1722N

The configuration parameter was not updated because the keyword MEMBER was used and the configuration parameter cannot be set to the specified value on a per-member basis. Configuration parameter: configuration-parameter. Specified value: specified-value.

You can configure aspects of your database manager instance by calling the UPDATE DATABASE MANAGER CONFIGURATION command to set database manager configuration parameters. You can configure aspects of individual databases by calling the UPDATE DATABASE CONFIGURATION command to set database configuration parameters.

In a DB2 pureScale environment, some configuration parameters can be set on a local, per-member basis. When you set a local value for a specific DB2 member the local value overrides the global (instance-wide or database-wide) value. To set a configuration parameter locally to a particular member, you would specify the MEMBER keyword with the UPDATE DATABASE MANAGER CONFIGURATION command or the UPDATE DATABASE CONFIGURATION command.

Some configuration settings are valid as global settings, but are not supported as per-member settings. This message is returned when an attempt is made to set a configuration parameter locally for a DB2 member to a value that is not supported as a per-member setting.

Respond to this message in one of the following ways:

To set the configuration parameter to the specified value globally, call the command again without the MEMBER keyword.
To set the configuration parameter on a per-member basis, review the supported values for the configuration parameter and then call the command again specifying only supported values.

SQL1723N

The CREATE TABLESPACE statement or ALTER TABLESPACE statement failed because a file system caching option was specified that is not supported in the current environment.

File caching allows you to save recently used data on the disk for quick access in subsequent calls to the same data. Enabling file system caching can improve your database performance if you often use the same set of data.

There are restrictions on and requirements for using file caching. There are also restrictions on and requirements for bypassing file caching in some environments. This message is returned when an attempt is made to use file system caching or bypass file system caching in an unsupported environment, such as a disk sector size that is not supported.

Review supported file system caching configurations.
Make changes to resolve the restriction that was encountered or satisfy the requirement that was missed by performing one or more of the following kinds of troubleshooting actions:
- Change the environment: format the target disk to have the required sector size.
- Change the statement: enable file system caching using the FILE SYSTEM CACHING option.
Reissue the statement.

SQL1724W

The table table-name was successfully created as a column-organized table. However, one or both of the SORTHEAP and SHEAPTHRES_SHR configuration parameters is currently set to a value that cannot be used with column-organized tables.

You can enable self-tuning for sort memory by setting the database configuration parameters SORTHEAP and SHEAPTHRES_SHR to "AUTOMATIC".

Self-tuning for sort memory is not supported with column-organized tables.

This message is returned when a column-organized table is created while either of the following configuration parameters is set to "AUTOMATIC": SORTHEAP and SHEAPTHRES_SHR.

To use column-organized tables, set both of the configuration parameters SORTHEAP and SHEAPTHRES_SHR to a fixed value.

SQL1725N

Could not perform the specified action because the status of the indoubt transaction changed after you issued the LIST INDOUBT TRANSACTIONS command.

When you run the LIST INDOUBT TRANSACTIONS command on the client, it returns the current state of the indoubt transactions. However, the output is not refreshed on the client if the status changes on the server. If the status of an indoubt transaction is not synchronized between the server and the client, you might not be able to perform all of the actions that are listed as valid options in the LIST INDOUBT TRANSACTIONS command output.

Quit the interactive window and reissue the LIST INDOUBT TRANSACTIONS command to obtain the most recent status of the indoubt transactions from the server.

SQL1726N

The database manager was not started because the CF_TRANSPORT_METHOD database manager configuration parameter is set to "TCP" but the Ethernet card is not at least 10GE.

In DB2 pureScale environments, you can specify that communication between the cluster caching facility (CF) and DB2 members be done using sockets by setting the database manager configuration parameter CF_TRANSPORT_METHOD to "TCP". To use the sockets communication method, you must be using at least a 10GE Ethernet card.

This message is returned when the CF_TRANSPORT_METHOD configuration parameter is set to "TCP" but an Ethernet card of at least 10GE has not been configured.

Respond to this message in one of the following ways:

To use the sockets communication method, perform one of the following tasks:
- Configure a 10GE network.
- To use a Ethernet that is not at least 10GE, set the DB2_SD_ALLOW_SLOW_NETWORK registry variable to ON.
To use a different communication method set the CF_TRANSPORT_METHOD configuration parameter to a different value, such as "RDMA".

SQL1727N

The statement was not precompiled because the following host variable array or structure array contains an unsupported data type: variable_name

The COMPATIBILITY_MODE ORA precompile option allows the use of host variable arrays, structure arrays, and indicator arrays in an embedded SQL statement. A host variable array or structure array declared for an INSERT, UPDATE, or DELETE statement must contain supported data types.

Remove the unsupported data types in the declared host variable arrays, or structure arrays.
Precompile the modified embedded SQL application.

SQL1728N

The command or operation failed because the keystore could not be accessed. Reason code reason-code.

DB2 native encryption stores encryption keys in a keystore file. To use this functionality, you must perform the following set-up and configuration tasks:

Create a keystore file (also known as a key database) for storing encryption objects, such as private keys.
Configure the database manager to use the keystore file by setting encryption configuration parameters, such as KEYSTORE_TYPE and KEYSTORE_LOCATION.
Manage passwords for accessing the keystore file (save the password in a stash file, for example.)

This message is returned when the database manager fails to retrieve or update information in the keystore file while performing one of several different types of operations:

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

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

1

The following database manager configuration parameters are not set to valid and compatible values: KEYSTORE_LOCATION, KEYSTORE_TYPE.

2

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

3

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

4

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

5

Reason code 5 can be returned for three general reasons:

The database manager process ran as the instance owner ID, and the instance owner ID does not have read permission and write permission for the keystore file.
A DB2 utility was invoked by a user other than the instance owner.
The disk containing the keystore file is out of space.

6

The database manager failed to process the contents of the keystore file.

Example: If the database manager is configured to use a keystore file that is compliant with the PKCS#12 standard, but the format of the keystore file is not compliant with the PKCS#12 standard, then the database manager will be unable to use the keystore file.

7

An error was returned from an IBM Global Security Kit (GSKit) command. The IBM Global Security Kit (GSKit) error details were printed in the db2diag diagnostic log file.

Resolve the problem according to the reason code, and then retry reissue the command:

1

Set both of the database manager configuration parameters KEYSTORE_LOCATION and KEYSTORE_TYPE to valid and compatible values.

2

Set the KEYSTORE_LOCATION database manager configuration parameter to a valid file name.

3, 4

Provide the database server with a valid password for accessing the keystore file in one of the following ways:

Recreate the stash file
Provide the keystore password as an argument to the command

5

Respond to reason code 5 in the following ways:

Set the keystore file permissions so that the file can be read and written to by only the instance owner ID.
Invoke encryption-related DB2 utilities, such as dbckbkup, as the instance owner.
If this message is returned because the disk containing the keystore file is out of space, increase the amount of space that is available on that disk.

6

Recover the current keystore file from a backup copy.

7

Review the IBM Global Security Kit (GSKit) error that is printed in the db2diag diagnostic log file, correct the problem that is causing the IBM Global Security Kit (GSKit) error, and then reissue the command. If the IBM Global Security Kit (GSKit) errors continue, contact IBM Software Support for assistance.

SQL1729N

The command failed because the label label does not exist in the keystore.

DB2 native encryption stores encryption keys in a keystore file. Keys are accessed by a master key label, which is also stored in the keystore file. When you issue DB2 commands against databases that are configured to use this functionality, the database manager must look up the appropriate key using a label:

You can specify the label as a parameter to the command.
If you do not specify a label, the database manager will use the label that is configured for the database.

This error is returned when a label is specified with a command parameter but the specified label could not be found in the keystore file.

Respond to this error in one of the following ways:

Reissue the command, specifying a label that exists in the keystore file.
Reissue the command without specifying a label to cause the label that is configured for the database to be used automatically.

SQL1730N

The command or operation failed because the master key label does not exist in the keystore file. Label being used: label. File type number: file-type-number. File name: file-name.

DB2 native encryption stores encryption keys in a keystore file. When you issue DB2 commands against databases that are configured to use this functionality, the database manager must look up the appropriate key using a label:

You can specify the label as a parameter to the command.
If you do not specify a label, the database manager will use the label that is configured for the database. Sometimes the database manager will save a label in a log file, a configuration file, or a backup image and then retrieve that saved label as appropriate.

This message is returned when the database manager retrieves a label that was successfully used in past operations (saved in a log file, for example) but the label cannot be found in the current keystore file. This error scenario can arise in multiple ways, including the following examples:

A label was deleted from the keystore file.
An older copy of the keystore file was restored and the restored copy does not contain the label.
An attempt is made to restore a backup image which references a label, but that label is not in the keystore file on the host machine where the restore operation is happening.
An attempt is made to roll forward through transactions in archived log files that reference a label, but that label is not in the keystore file where the transactions are being replayed.
The contents of the keystore file where a high availability disaster recovery (HADR) primary database resides do not match the keystore file contents where the corresponding standby database resides.

The runtime token file-name indicates the name of the file in which the reused label appeared. The file-type-number runtime token indicates the type of file in which the reused label appeared:

1: Database log file
2: Configuration file
3: Backup image

Respond to this error in one of the following ways:

If the keystore file has become out of date (because a label has been deleted, for example) restore a backed-up version of the keystore file that contains the label that is missing from the current keystore file.
If the keystore files are not synchronized on two host machines involved in an operation (such as an HADR primary-standby pair, or when a backup image taken on one host machine is restored to a different host machine) synchronize the two keystore files and then reissue the command.

SQL1731C

An encryption operation failed. Database name: database-name. Log file name: log-file-name. Database partition number: db-partition-number. Log stream ID: log-stream-ID.

You can encrypt data in databases using the IBM DB2 Encryption Offering.

This message is returned when an encryption-related operation fails because of a critical, internal error.

Collect diagnostic information, including the log file given in the runtime token log-file-name and db2diag diagnostic log files, and then contact IBM Software Support for assistance.

SQL1732N

The command failed because the specified encryption options are not supported together or not supported in this environment.

To use DB2 native encryption, encryption options must be specified in the ENCROPTS database configuration parameter or with the ENCROPTS command parameter.

The value of the ENCROPTS database configuration parameter and the ENCROPTS command parameter must be a string, in a specific format, indicating a combination of encryption-related configuration details.

This message is returned when an incompatible or unsupported combination of configuration details is specified.

Correct the configuration details specified in the ENCROPTS configuration parameter or the ENCROPTS command parameter and then reissue the command.

SQL1733N

The command was not executed because the specified label is too long.

DB2 native encryption stores encryption keys in a keystore file. Keys are accessed by a master key label, which is also stored in the keystore file. The label is created in one of two ways:

You create the label when you create a key manually.
The database manager generates a label when creating a key.

This message is returned when a manually created label is specified with a command, and the label is longer than the supported label size.

Reissue the command, specifying a label that is a supported length.

SQL1734N

The command or operation failed because the master key does not match a supported key length.

DB2 native encryption uses a master key to manage encryption for data in databases. The master key for a given database can be created in two ways:

You can create a master key manually, and specify the label for that key (with the CREATE DATABASE statement, for example.)
You can allow the database manager to generate a master key for a database.

This message is returned when the label of a manually created master key is specified with a command or statement, but the length of the manually created key is not supported with DB2 native encryption.

Reissue the command, specifying the label of a master key that is a supported length.

SQL1735N

The RESTORE command failed because the encryption key label specified in the command does not match the label used to encrypt the backup image.

You can specify the label as a parameter to the command.
If you do not specify a label, the database manager will use the label that is configured for the database.

When you create an encrypted backup image, you can specify multiple master key labels. When you restore an encrypted backup image, you must specify one of the master key labels that were used when the backup image was created.

This message is returned when an attempt is made to restore a backup image, specifying a master key label that was not used to create the backup image.

Respond to this error in one of the following ways:

Allow the restore utility to look up the correct master key label by issuing the RESTORE command without specifying any label.
Manually determine what master key labels were used to create the backup image by issuing the RESTORE command specifying "show master key details" with the ENCROPTS parameter, and then perform the restore operation specifying one of the labels that were used to create the backup image.

SQL1736N

The command failed to retrieve the keystore password. Reason code reason-code.

DB2 native encryption stores encryption keys in a keystore file. When you issue DB2 commands (the START DATABASE MANAGER command, for example) in an environment configured to use this functionality, the database manager looks up keys in the keystore file.

The keystore file is protected with a password. In order for the database manager to look up an encryption key, the keystore file password must be provided to the database manager in one of two ways:

The password can be stored in a stash file.
The password can be specified with a parameter to DB2 commands.

This message is returned when keystore file password information is specified with a parameter to a DB2 command, but the database manager is unable to use the password information that was specified with the parameter.

The reason code indicates more specifically what error the database manager encountered while processing the specified password information:

1: The password information could not be processed because the format of the argument was not recognized.
2: The argument was processed by the command, but the specified password information could not be used successfully (the file name specified does not exist, for example.)

Reissue the command, with a password argument corrected according to the reason code:

1: Specify the password information using a valid string format.
2: Specify the correct password, an open, readable file handle, or the name of an existing file.

SQL1737N

The command or operation failed because the database is not encrypted.

You can encrypt data in databases using DB2 native encryption. You can perform encryption operations on encrypted databases by specifying encryption-related parameters with commands or by using the ADMIN_ROTATE_MASTER_KEY built-in stored procedure.

This message is returned when an attempt is made to perform DB2 native encryption operations with a database that is not encrypted.

Respond to this error in one of the following ways:

Reissue the command without specifying parameters that are specific to DB2 native encryption.
Reissue the command against a database that is encrypted.

SQL1738N

The command was not executed because a label was not provided.

DB2 native encryption stores encryption keys in a keystore file. Keys are accessed by a master key label, which is also stored in the keystore file. In general, the label is provided in one of two ways:

You can specify a label with a command parameter.
You can allow the database manager to generate a new label or use the existing label configured for the database.

There are some cases where a master key label must always be specified. This message is returned when a label must be specified, but no label is specified:

The ADMIN_ROTATE_MASTER_KEY stored procedure is issued in an HADR environment.
The BACKUP command is issued with the ENCRYPT clause to create an encrypted backup image of a database that is not encrypted.

Reissue the command, specifying a master key label.

SQL1739N

The command or operation failed because the value specified with the ENCROPTS parameter is invalid.

To use DB2 native encryption, encryption options must be specified in the ENCROPTS database configuration parameter or with the ENCROPTS command parameter.

The value of the ENCROPTS database configuration parameter and the ENCROPTS command parameter must be a string, in a specific format, listing a combination of encryption-related configuration details.

This message is returned when the database manager is unable to parse the configuration information specified in the ENCROPTS configuration parameter or the ENCROPTS command parameter because the format of the specified string is unexpected.

Correct the configuration details specified in the ENCROPTS configuration parameter or the ENCROPTS command parameter and then reissue the command.

SQL1740N

The key rotation operation failed. Reason code: reason-code.

DB2 native encryption uses a master key to manage encryption for data in databases. You can rotate the master key for a database by using the ADMIN_ROTATE_MASTER_KEY built-in stored procedure.

This message is returned when rotating the master key fails because of an internal error. The reason code, which is useful for IBM support personnel only, indicates more specifically the nature of the underlying problem:

1: Memory management errors, other than out-of-memory conditions, were encountered.
2: Internal latch errors were encountered.
3: Key rotation was attempted on a partitioned system where not all database partitions are active.

For reason codes 1 and 2, perform the operation again.

For reason code 3, wait until all database partitions are active and then reissue the command.

If this error continues, collect diagnostic information, including the db2diag diagnostic log files, and then contact IBM Software Support for further assistance.

SQL1741N

The command or operation failed because the master key for master key label label has changed.

DB2 native encryption stores encryption keys in a keystore file. Keys are accessed by a master key label, which is also stored in the keystore file. The label is created in one of two ways:

You create the label when you create a key manually.
The database manager generates a label when creating a key.

Once a key is created with a given label, the key for that label cannot change. This message is returned when the key has changed for a given master key label.

The key for a master key label can appear to have changed for different reasons, including the following examples:

The same label is used for different keys in different keystore files, and those keystore files have been moved to different host machines.
The key was accidentally changed manually.

Perform the following troubleshooting steps:

Verify that the keystore file contains the correct master key and master key label.
If required, restore the keystore file from the most recent backup image and retry the command or operation.

SQL1742N

Creating the primary key failed because the columns of the primary key definition do not correspond to the columns of a unique constraint or primary key constraint on the base table.

You can create a primary key on a shadow table. However there are some requirements and restrictions related to creating a primary key on shadow tables. This message is returned when an attempt is made to create a primary key on a shadow table, but there is no corresponding primary key or unique constraint for the base table of the shadow table.

To create a primary key on a shadow table, include a set of columns in the definition of the new primary key that corresponds to the set of columns from a primary key or a unique constraint of the base table.

sqlcode: -1742

sqlstate: 428I7

SQL1743N

The RESTORE command failed because the backup image is of an encrypted database but the target database is not encrypted.

You can encrypt data in databases by using DB2 native encryption. For example, you can create an encrypted database by specifying encryption parameters with the CREATE DATABASE command.

When an encrypted database is backed up, that backup image cannot be restored into an existing, target database that is not encrypted, unless the NO ENCRYPT parameter is specified with the RESTORE command.

This message is returned when an attempt is made to restore the image of an encrypted database to a target database that is not encrypted and the NO ENCRYPT parameter is not specified with the RESTORE command.

To restore the backup image into a non-encrypted target database, issue the RESTORE command with the NO ENCRYPT parameter.

SQL1744N

The RESTORE command failed because the target database already exists and encryption options were specified.

You can encrypt data in databases by using DB2 native encryption. For example, you can create an encrypted database in two ways:

Specifying encryption-related parameters with the CREATE DATABASE command
Restoring from a backup image into a new, encrypted database by specifying encryption-related parameters with the RESTORE command

What is not supported, however, is specifying encryption-related parameters with the RESTORE command when restoring into an existing database that is not encrypted.

To restore into an existing database that is not encrypted, perform one of the following actions:

To restore a backup image of an encrypted database into an existing database that is not encrypted, issue the RESTORE command without specifying any encryption-related parameters other than the NO ENCRYPT parameter.
To restore a backup image of a non-encrypted database into an existing database that is not encrypted, issue the RESTORE command without specifying any encryption-related parameters.

SQL1745N

The API_name API failed because the API attempted to read encrypted logs.

You can encrypt data in databases by using DB2 native encryption. With databases that are configured to use this functionality, database log files are also encrypted. You can work with encrypted log files by using the db2ReadLogNoConn API.

This message is returned when an attempt is made to work with encrypted database log files using a utility that is not supported with encrypted log files.

To work with log files that have been encrypted by DB2 native encryption functionality, use only utilities that are supported with encrypted log files.

SQL1746W

The database, database-name, was successfully created. However, database configuration was not automatically tuned for your system resources.

When the sqlecrea API is invoked or the CREATE DATABASE command is issued, by default the Configuration Advisor tunes the database configuration according to your system resources. (You can disable the Configuration Advisor from running at database creation by using the DB2_ENABLE_AUTOCONFIG_DEFAULT registry variable.)

This message is returned when the Configuration Advisor is enabled to run at database creation time, but the Configuration Advisor encounters an error and is unable to optimize the database configuration for your system resources.

To tune the database configuration, manually run the AUTOCONFIGURE command.

sqlcode: +1746

sqlstate: 5U061

SQL1747N

The statement was not processed because of an error specifying the ENVIRONMENT clause. Reason code: reason-code. Substring: substring.

You can specify multiple named routine environment variables with associated values in the ENVIRONMENT clause of the CREATE FUNCTION statement. The ENVIRONMENT clause is specified as a comma-separated list of name-value pairs.

This message is returned when there is a problem with one or more of the names or values specified with the ENVIRONMENT clause.

The reason code identifies the problem more specifically:

1: More routine environment variables were specified than the maximum supported number of routine environment variables.
2: A value string that is longer than the maximum supported length was specified with a routine environment variable.
3: A routine environment variable name was specified that is longer than the maximum supported length for a name.
4: A routine environment variable name was specified more than once.

Depending on the nature of the problem, the token substring might be empty, or might contain a substring showing where the problem occurs in the ENVIRONMENT clause.

Reissue the SQL statement, specifying a valid ENVIRONMENT clause.

sqlcode: -1747

sqlstate: 428I8

SQL1748N

A user-defined function has encountered a deadlock with a CPad. Function name: function-name. Specific name: specific-name.

A deadlock is created when two applications both lock data that is needed by the other, such that neither application can continue executing.

You can use a CPad to allocate a named, unique area of memory as a temporary storage area and work pad for user-defined functions.

This message is returned when two user-defined functions encounter a deadlock scenario accessing the same CPad.

Rewrite the user-defined function to avoid deadlock scenarios.

sqlcode: -1748

sqlstate: 57068

SQL1749N

The statement failed because it references a type type-name which was generated for an array or row column definition.

The use of a ROW type or ARRAY type as the data type for columns in a CREATE HADOOP TABLE statement generates a user-defined data type using a system-generated name.

The data types that are generated for this purpose cannot be referenced in other statements or expressions, with the exception of the COMMENT statement.

Replace or remove the reference to the generated data type and resubmit the statement.

sqlcode: -1749

sqlstate: 429CC

SQL1750C

A failure occurred that terminated the operation operation-name on table table-name, of type table-type, which might result in invalid or inconsistent data. log-entry-ID.

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

These are the runtime tokens:

operation-name

The type of processing, such as INSERT.

table-name

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

table-type

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

log-entry-ID

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

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

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

Locate the diagnostic details in the appropriate log file by using the information in the log-entry-ID. You can retrieve the text of the error from the logs with the following statement:


SELECT * FROM Table
(SYSHADOOP.LOG_ENTRY('log-entry-id'));

Determine which data were not cleanly inserted, if for an INSERT operation, and insert the data again, or drop the table and start the INSERT operation again.

sqlcode: -1750

sqlstate: 58041

SQL1751N

The resulting database partition group would not contain any nodes that can be used in a partition map.

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

Do not drop all the nodes in the database partition group without adding at least one node. If tablespaces are already defined on the database partition group but there are no tables, ensure that at least one node has containers for all the table spaces.

sqlcode: -1751

sqlstate: 428C0

SQL1752N

The table space cannot be created in the database partition group db-partition-group.

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

For system temporary table spaces, specify database partition group IBMTEMPGROUP. For other table space types, specify a database partition group other than IBMTEMPGROUP.

sqlcode: -1752

sqlstate: 429A1

SQL1753N

Database partition database-partition-number does not have containers for all the system temporary table spaces defined in the database partition group IBMTEMPGROUP.

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

Issue the ALTER TABLESPACE statement to add containers on every database partition for every system temporary table space in the database.

sqlcode: -1753

sqlstate: 57052

SQL1754N

The index table space or long table space is not in the same database partition group as the primary table space.

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

Make sure all the table spaces specified in the CREATE TABLE statement belong to the same database partition group.

sqlcode: -1754

sqlstate: 42838

SQL1755N

Database partition dbpartnum does not have containers for all the table spaces defined in the database partition group dbpartgrpname.

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

Issue the ALTER TABLESPACE statement to add containers to all the table spaces on this database partition.

SQL1756N

More than one clause specifies containers without the ON DBPARTITIONNUMS clause.

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

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

The statement was not processed.

Correct the statement and reissue it.

sqlcode: -1756

sqlstate: 428B1

SQL1757N

A USING clause without an ON DATABASE PARTITION clause is missing.

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

The statement is not processed.

Ensure that the USING clause without the ON DATABASE PARTITION clause is specified or that each database partition in the database partition group is included once in an ON DATABASE PARTITION clause.

sqlcode: -1757

sqlstate: 428B1

SQL1758W

The containers not designated for specific nodes are not used by the table space on any node.

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

The statement has been processed.

If the containers are needed on some of the nodes, issue an ALTER TABLESPACE statement to add the necessary containers.

sqlcode: +1758

sqlstate: 01589

SQL1759W

Redistribute database partition group is required to change database partitioning for objects in database partition group database-partition-group-name to include some added database partitions or exclude some dropped database partitions.

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

This warning is issued in the following cases:

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

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

If you want the database partition included or excluded for database partitioning then issue the REDISTRIBUTE DATABASE PARTITION command or API. Another alternative is to drop all tables that use table spaces in the database partition group.

sqlcode: +1759

sqlstate: 01618

SQL1760N

The CREATE PROCEDURE or ALTER MODULE statement used to define stored procedure procedure-name must have a valid LANGUAGE clause, EXTERNAL clause, and PARAMETER STYLE clause, or include an SQL procedure body.

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

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

Add the missing clause, then try again.

sqlcode: -1760

sqlstate: 42601

SQL1761N

The database partition group db-partition-group is not defined for the buffer pool bpname.

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

The statement cannot be processed.

The possible actions are:

Specify a buffer pool that has defined the database partition group for the table space.
Alter the buffer pool to add the database partition group of the table space.
If CREATE TABLESPACE, specify a database partition group that is defined for the buffer pool.

sqlcode: -1761

sqlstate: 42735

SQL1762N

Unable to connect to database because there is not enough space to allocate active log files.

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

There is insufficient space available on the device used to store the recovery logs.
If userexits are enabled, the userexit program may be failing due to an incorrect path, incorrect install directory, sharing violation, or other problem.
If log archiving is enabled, the log archiving method may not be functioning or the target might be inaccessible.
Database configuration parameter log_disk_cap is set and either there is insufficient space available on the device to store the minimum number of two log files required for database activation, or log_disk_cap is set to a value lower than the size of two log files.

Based on the cause:

Ensure that there is sufficient space on the device for the primary logs, as DB2 may require extra space to allocate new logs so that the database will start with at least LOGPRIMARY log files. Do NOT delete recovery logs to free space, even if they appear inactive.
Ensure the userexit program is operating correctly by manually invoking it. Review the instructions provided in the sample userexit source code for compiling and installing the userexit program. Ensure that the archive destination path exists.
Ensure that the log archiving method is working correctly. If errors are being encountered then further information can be found in the db2diag.log file.
Ensure that there is sufficient space on the device for the minimum number of two log files required for database activation and that log_disk_cap is set to a value larger than the size of two log files.

As a last resort, try reducing the values for LOGPRIMARY and/or LOGFILSIZ database configuration parameters so that a smaller set of active log files are used. This will reduce the requirement for disk space.

Reissue the connect statement after determining and correcting the problem.

SQL1763N

Invalid ALTER TABLESPACE statement for table space table-space-name due to reason reason-code

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

1

The CONVERT TO LARGE clause must be specified by itself.

2

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

3

When adding or removing space from the table space:

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

4

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

5

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

6

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

7

There are no storage groups in the database.

8

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

9

The REBALANCE clause must be specified by itself.

10

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

11

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

12

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

13

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

14

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

1

Issue the CONVERT TO LARGE clause in its own ALTER TABLESPACE statement.

2

If using the BEGIN NEW STRIPE SET container operation and other operations in the same statement, move the BEGIN NEW STRIPE SET operation into its own ALTER TABLESPACE statement.

3

If both adding pages to and removing pages from a table space, use two ALTER TABLESPACE statements.

4

Remove the container clause from the ALTER statement and re-issue the statement.

5

Specify a container clause including the list of containers to reduce and re-issue the statement.

6

To convert temporary table spaces using automatic storage, create a new automatic storage-managed temporary table space and drop the old temporary table space. To convert from system-managed to automatic storage-managed table spaces, all data must be moved manually.

7

Create a storage group using the CREATE STOGROUP statement. A table space can only be managed by automatic storage if there is a storage group created.

8

To convert database-managed table spaces that use DEVICE containers to be managed by automatic storage, perform the following steps:

Perform a table space or database level redirected restore operation.
Issue the SET TABLESPACE CONTAINERS command with the USING AUTOMATIC STORAGE option.

9

Issue the REBALANCE clause in its own ALTER TABLESPACE statement.

10

Convert the table space to be managed by automatic storage and ensure the table space has the Reclaimable Storage attribute before using the REDUCE MAX clause or the REDUCE with a specified size clause.

11

Table spaces must have the Reclaimable Storage attribute before you can use clauses to reduce or lower the high water mark.

12

Only use a single clause to reduce or lower the high water mark in each ALTER TABLESPACE statement.

13

Remove the ADD, DROP, RESIZE, EXTEND, REDUCE, LOWER HIGH WATER MARK, or BEGIN_STRIPE_SET clause from the ALTER statement and re-issue the statement.

14

Issue the REBALANCE clause so the table space contains only automatic storage containers. After the rebalance operation completes, issue the ALTER TABLESPACE with the USING STOGROUP clause.

sqlcode: -1763

sqlstate: 429BC

SQL1764N

Specified size for a RESIZE action in an ALTER TABLESPACE statement is smaller than the current size of the table space container.

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

Specify a size that is larger than the current size value of the table space container.

sqlcode: -1764

sqlstate: 560B0

SQL1765W

The update completed successfully. However, index creation, recreation, or reorganization may not be recovered on the secondary database server.

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

To enable full logging, update the database configuration parameter LOGINDEXBUILD or issue the SQL statement ALTER TABLE LOG INDEX BUILD ON. To enable redo of any logged index build operations, update the configuration parameter INDEXREC to either RESTART or ACCESS.

SQL1766W

The command completed successfully. However, LOGINDEXBUILD was not enabled before HADR was started.

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

To enable full logging, set the database configuration parameter LOGINDEXBUILD to ON.

SQL1767N

Start HADR cannot complete. Reason code = reason-code.

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

1: The database was not in roll forward-pending or roll forward-in-progress state when the START HADR AS STANDBY command was issued.
2: START HADR AS PRIMARY cannot be issued on an HADR standby database.
3: START HADR AS STANDBY cannot be issued on an active database.
9: Database upgrade is in progress on an active HADR standby.
98: A valid HADR license is not installed. The command did not complete successfully.
99: The command was issued in a multi-partition instance environment.

The user response corresponding to the reason code is:

1: Initialize the standby database from a backup image or a split mirror of the primary database, then reissue the START HADR AS STANDBY command.
2: If you intend to change the standby database to a primary database, issue the TAKEOVER command.
3: If you intend to change a primary database to a standby database, issue the TAKEOVER command from the current standby. If you intend to change a standard database to a standby, the database must be deactivated first.
9: Upgrade processing must complete on the primary and standby database and the standby database must be deactivated before the command can be reissued.
98: Obtain and install a valid HADR license and resubmit the command.
99: The HADR feature is not supported in a multi-partition instance environment.

SQL1768N

Unable to start HADR. Reason code = reason-code.

The explanation corresponding to the reason code is:

1

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

2

The database has infinite active logging enabled.

3

The database has DATALINKS enabled.

4

Invalid entry for the hadr_local_host configuration parameter.

5

Invalid service name for the hadr_local_svc configuration parameter.

6

Invalid service name for the hadr_remote_svc configuration parameter.

7

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

8

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

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

9

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

10

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

11

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

12

Invalid entry for the hadr_remote_host configuration parameter.

13

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

14

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

15

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

16

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

17

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

18

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

19

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

20

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

21

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

22

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

23

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

24

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

25

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

26

A table space is not available.

27

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

28

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

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

29

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

97

The database failed checks when attempting to start HADR. Refer to db2diag.log for details.

98

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

99

An internal error occurred during HADR startup.

The user response corresponding to the reason code is:

1

The database must be a recoverable database. Activate log archiving by setting database configuration parameter logarchmeth1 or logarchmeth2 to a value other than OFF. Take an offline database backup to make the database recoverable and reissue the command.

2

Disable infinite active logging and reissue the command.

3

Update the database manager configuration file so that DATALINKS is set to NO and reissue the command.

4

Ensure that the hadr_local_host configuration parameter can be mapped to an IPv4 or IPv6 address associated with the local host.

5

Ensure that the hadr_local_svc configuration parameter is set to a valid service name. For Unix platforms, edit the /etc/services file. For Windows, edit %SystemRoot%\system32\drivers\etc\services. Alternatively, a literal port number can be specified for this parameter.

6

Ensure that the hadr_remote_svc configuration parameter is a valid service name. For Unix platforms, edit the /etc/services file. For Windows, edit %SystemRoot%\system32\drivers\etc\services. Alternatively, a literal port number can be specified for this parameter.

7

Perform the following troubleshooting steps:

Check if the old standby database is already running as a primary or standalone database. To avoid a potential split-brain scenario, the primary database will not be started if it cannot establish a connection to the standby database. If the old standby database is already running as a primary, consider starting the old primary database as a new standby database.
1. Issue START HADR DATABASE ON dbname AS STANDBY to convert the old primary database into a new standby database.
2. Or alternatively, reinitialize the old primary database into a new standby database via a backup image of the new primary database.
If there was no forced takeover (aka failover) operation on the standby database and the standby database is not running as a primary or standalone database, then check the hadr status and configuration.
1. Ensure that the standby database is online and started as a standby database (use 'db2pd -db dbname -hadr' or MON_GET_HADR).
2. Confirm that the hadr_target_list, hadr_local_host, hadr_local_svc, hadr_remote_inst, hadr_remote_host, hadr_remote_svc database configuration parameters are set correctly on both the primary and standby database.
3. Ensure that the network is functioning, and the primary and standby host can reach each other via TCP/IP (consider using the system 'ping' utility to ping the remote host and svc/port).
4. Examine the db2diag.log files for other error messages that indicate there are incompatible configuration settings on the primary database and the standby database.
5. Ensure that the value of the hadr_timeout configuration parameter is the same on both the primary database and the standby database.
6. Ensure that the value of the hadr_peer_window configuration parameter is the same on both the primary database and the standby database.
7. Ensure the hadr_timeout configuration parameter is set to a value for sufficient time for a connection and handshake to be established between the primary and standby database.
If the standby database is offline and cannot be started (due to a standby system failure or other disaster), then force start the primary database.
1. Issue START HADR DATABASE ON dbname AS PRIMARY BY FORCE on the primary database.
2. Or alternatively, issue STOP HADR command on the primary database.

8

Ensure that the following HADR database configuration parameters have a non-NULL value where required:

hadr_local_host
hadr_local_svc
hadr_remote_host
hadr_remote_svc
hadr_remote_inst
hadr_target_list

You can determine the current value of these HADR configuration parameters by using the GET DATABASE CONFIGURATION command.

9

Reconfigure the database to use only file system storage for the log files, instead of using raw I/O (direct disk access) devices.

10

Address the cause of the HADR shutdown, and if desired, reissue the START HADR command.

11

Ensure that the hadr_local_host, hadr_remote_host, and hadr_target_list configuration parameters are in the same IP format (IPv4 or IPv6) or can be resolved to the same format.

12

Ensure that the hadr_remote_host configuration parameter can be mapped to an IPv4 or IPv6 address.

13

Ensure that the dbheap configuration parameter is configured properly and that the system has sufficient memory available for the size of the buffer pool defined. Then retry the operation. If you need to change the size of a buffer pool on the HADR standby, you need to perform a new database restore operation using a backup image from the primary database that includes the new buffer pool size.

14

Ensure that the hadr_target_list configuration parameter has an entry for the pair specified by the hadr_remote_host and hadr_remote_svc configuration parameters.

15

Ensure that all of the entries specified by the hadr_target_list configuration parameter are valid host:service pairs.

16

Ensure that the entries for the hadr_target_list configuration parameter are in the correct format.

17

Either set the hadr_replay_delay configuration parameter to 0 or change the hadr_syncmode configuration parameter to SUPERASYNC.

18

Ensure the hadr_replay_delay configuration parameter is set to 0 on the HADR primary database.

19

Determine which database should be the primary. Drop the other primary database or try converting it to a standby. If both should be primary, they should be removed from each other's hadr_target_list, so that they are independent.

20

Set the hadr_syncmode database configuration parameter to either ASYNC or SUPERASYNC.

21

Update the value specified by either the hadr_local_svc or the svcename configuration parameter so that the TCP port used by hadr_local_svc is not in the port range (inclusively) of svcename and svcename + 1.

22

Update the hadr_local_svc database configuration parameter or the system service names so that the TCP port used by hadr_local_svc is not between (inclusively) the ports defined by service name DB2_instance and DB2_instance_END, where 'instance' is the name of the database manager instance. To update system service names, on Unix platforms, edit the /etc/services file; on Windows, edit %SystemRoot%\system32\drivers\etc\services.

23

DB2CA_instance_CMD and DB2CA_instance_CMD_END
DB2CA_instance_NOTIFY and DB2CA_instance_NOTIFY_END
DB2CA_instance_MGMT and DB2CA_instance_MGMT_END

In these service names, 'instance' represents the name of the database manager instance. To update system service names, on Unix platforms, edit the /etc/services file; on Windows, edit %SystemRoot%\system32\drivers\etc\services.

24

Check that DB2 registry variable DB2_HADR_SOSNDBUF is set properly. It should not exceed available memory or system level socket buffer size limit.

25

Check that DB2 registry variable DB2_HADR_SORCVBUF is set properly. It should not exceed available memory or system level socket buffer size limit.

26

Refer to db2diag.log to identify the table space that is not available. Resolve the root cause and ensure the storage for the table space is available. If required, recover the affected table space using the RESTORE DATABASE or ROLLFORWARD DATABASE command. Otherwise, you can drop the table space if it is no longer needed.

27

Set the hadr_peer_window database configuration parameter to 0 in a DB2 pureScale environment.

28

Ensure that the database configuration parameter HADR_SSL_LABEL and the database manager configuration parameters SSL_SVR_KEYDB, SSL_SVR_STASH, and SSL_CIPHERSPECS are set to valid values. After updating the SSL_SVR_KEYDB, SSL_SVR_STASH, or SSL_CIPHERSPECS configuration parameter, stop and restart the database manager.

29

Either change hadr_syncmode database configuration to SYNC or NEARSYNC, or disable automated failover via db2haicu if TSA is used as cluster manager.

97

Check the db2diag.log message and follow the instructions to fix any issues.

98

Obtain and install a valid HADR license and resubmit the command.

99

If the problem persists, contact IBM Support.

SQL1769N

Stop HADR cannot complete. Reason code = reason-code.

The explanation corresponding to the reason code is:

1: The command was issued on a standard database.
2: The command was issued on an active HADR standby database.
3: The command was interrupted by HADR shutdown due to a STOP HADR command, deactivation of the database, or an internal error.
98: A valid HADR license is not installed. The command did not complete successfully.
99: The command was issued in a multi-partition instance environment.

The user response corresponding to the reason code is:

1: No action is required as HADR is not running on this database. Verify that the specified database alias is correct.
2: The user should deactivate the database and then reissue the command.
3: If the command was interrupted due to another STOP HADR command, no further action is necessary. Otherwise, ensure that the database instance is started and reissue the STOP HADR command.
98: Obtain and install a valid HADR license and resubmit the command.
99: The HADR feature is not supported in a multi-partition instance environment.

SQL1770N

Takeover HADR cannot complete. Reason code = reason-code.

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

1

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

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

2

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

3

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

4

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

5

The command was issued against an inactive standby database.

6

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

7

A communication error occurred during takeover.

8

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

9

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

10

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

11

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

12

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

15

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

16

Suspended agents exist on standby during takeover.

98

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

99

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

The user response corresponding to the reason code is:

1

Wait for the log streams to reach the allowed condition, and then retry the takeover operation. An alternative is to use the BY FORCE option of the TAKEOVER HADR command to perform a failover. The BY FORCE option will allow takeover in broader conditions, but may result in data loss and will not change the primary into a standby.

2

Wait for the log streams to finish local catchup, and then retry the takeover operation.

3

Allow the standby more time to reach the end of the online backup and reissue the command.

4

This command is not supported on a standard or HADR primary database. Issue the command on an HADR standby database only.

5

Activate the standby database, then issue the takeover command.

6

Refer to the database logs on both HADR database partitions for possible causes of this message. The roles of the database partitions may not have changed. Check the value of the hadr_db_role database configuration parameter on both database partitions.

7

Refer to the database logs on both HADR databases for possible causes of this message. You can determine this by checking the value of the hadr_db_role configuration parameter.

It is possible that there was a problem executing the role switch.

If the roles of the databases have not changed, reissue the TAKEOVER HADR command on the standby.
If the roles of both databases are STANDBY, issue the TAKEOVER HADR command with the BY FORCE option on the database that you want to become the primary.

8

Wait for the conflicting command to complete, or for the database to shut down in the case of an internal error. Check the HADR role of the primary and standby databases. Start the databases and retry the takeover if you still want to perform that operation.

9

To force the standby database to takeover outside a peer window, reissue the TAKEOVER HADR command without the PEER WINDOW ONLY parameter. Although forcing the standby database to takeover outside a peer window is supported, the risk of transaction loss is greater when the takeover happens outside a peer window.

If your primary database failed and you do not want to force the standby database to take over outside a peer window because of the risk of data or transaction loss, consider alternative responses to the failure of the primary database than a forced takeover.

In a high availability solution with a primary database and a standby database, a common strategy for responding to the failure of the primary database is to have the standby database take over database operations for the failed primary database. However, there are other strategies for responding to a failure of the primary database, including repairing and restarting the failed primary database instead of failing over to a standby database. Although this repair and restart strategy would have a larger negative impact on the availability of the database solution for user applications than the failover strategy, it has other strengths such as less risk of data or transaction loss.

10

Review the cluster manager diagnostic information to determine the error that the cluster manager returned. If possible, repair the cause of the cluster manager error and run the TAKEOVER command again.

11

Disable replay delay by setting the hadr_replay_delay configuration parameter to 0, and reissue the TAKEOVER HADR command.

12

Wait for the members to finish member crash recovery, and then retry the takeover operation.

15

If there is no immediate need to connect to this database, wait for the UPGRADE DATABASE command to complete on the primary database, allow the standby database time to replay all upgrade log records sent from the primary database, and then reissue the command.
If you need to connect to this database immediately, issue the STOP HADR command to turn the HADR role to STANDARD.

16

Restart the instance to resolve the suspended agents, and then reissue the TAKEOVER HADR command.

98

Obtain and install a valid HADR license and resubmit the command.

99

HADR is not supported in a multi-partition instance environment.

SQL1771N

Non-recoverable databases cannot be used as either HADR primary or HADR standby database.

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

Either convert the database to standard role or do not use circular logging.

SQL1772N

Infinite active logging cannot be enabled on either HADR primary or HADR standby databases.

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

Either convert the database to standard role or do not use infinite logging.

SQL1773N

The statement or command failed because it requires functionality that is not supported on a read-enabled HADR standby database. Reason code = reason-code.

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

1

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

2

The query attempted to access an invalid index.

3

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

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

4

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

5

A write operation was attempted on an HADR standby database.

6

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

7

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

8

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

The user response corresponding to the reason code is:

1: Only the UR isolation level is supported on an HADR standby database. Change the isolation level to UR or set the DB2_STANDBY_ISO registry variable to UR to enable automatic isolation coercion.
2: Invalid indexes are not automatically rebuilt on the HADR standby database. Set the LOGINDEXBUILD database configuration parameter to ON on the HADR primary database so the indexes on the HADR standby database will be kept in sync with the indexes on the primary database.
3: Change the query so that it does not use any data types that cannot be read on an HADR standby database, and does not query for XML and LOB values that are not inline.
4: Change the query so that it does not access a created or declared temporary table.
5: Change the statement or command so that no write operation is required, or connect to the HADR primary database to perform the write operation.
6: Connect to the HADR primary database to rebind the package.
7: Issue the query against the column-organized table on the primary.
8: Issue the SET INTEGRITY statement on the HADR primary database.

sqlcode: -1773

sqlstate: 51045

SQL1774N

Table space restore or rollforward cannot be issued on an HADR primary or HADR standby database.

Table-space-level restore and Table-space-level rollforward operations are not allowed on an HADR primary database.

A table-space-level restore operation on an HADR standby database is only allowed on a table space that is in an abnormal state. The restore operation is not allowed when the table space state is normal (value 0).

A table-space-level rollforward operation on an HADR standby database is not allowed.

Convert the database to standard role and then issue the restore command or rollforward on the database.

If the goal is to recover lost data on a primary and the data to be restored is available on the standby, consider running the TAKEOVER command to convert the standby database to a primary database rather than restoring the table space on the primary.

SQL1775N

The HBase table was not created because a TERMINATED BY character separator-char was invalid.

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

Specify a valid value for the option.

sqlcode: -1775

sqlstate: 530AE

SQL1776N

The command cannot be issued on an HADR database. Reason code = reason-code.

The explanation corresponding to the reason code is:

1: The command is not supported on an HADR standby database.
2: Connection requests are not allowed while an HADR database is switching roles on takeover.
3: The UPGRADE DATABASE command is not supported on an HADR standby database.
4: Connection requests to an HADR standby database are not allowed while the replay-only window is active. The replay-only window is active when DDL or maintenance operations are being replayed on the standby.
5: Connection requests to an HADR standby are not allowed until the standby reaches the highest replay log position of a previous standby activation.
6: This database is an old primary database. It cannot be started because the standby has become the new primary through forced takeover.
7: The command cannot be processed while the standby replay is being restarted on the DB2 pureScale cluster.
9: Connection requests to an HADR standby are not allowed while database upgrade is in progress.

The user response corresponding to the reason code is:

1

Consider enabling reads on standby to allow client connections, or connect to the primary for the operation.

2

Retry the connection to the intended database after the takeover operation completes. Note that since the takeover operation relocates the primary database role, your intended database may now be active on a different server than where it was prior to the takeover.

3

Issue the UPGRADE DATABASE command on the primary database and then re-create your standby after the database upgrade is successful.

4

Connect to the HADR primary database, or wait until the replay-only window is inactive on the standby database.

5

Reissue the command when replay reaches the highest replay log position of a previous activation of the standby database. Check db2diag.log for this position. Use "db2pd -hadr" command to get current replay position.

6

Consider the following scenarios when deciding on a suitable response:

6.1) If the HADR primary database is running on a different server, then the database on this server should be started as an HADR standby database. Perform the following steps:

Issue the START HADR AS STANDBY command on the database on this server.
Verify that this new HADR standby database has established a connection with the HADR primary database by examining the HADR_CONNECT_STATUS field of the db2pd -hadr command or the MON_GET_HADR() table function on the HADR primary database. Note, an ADM12513E message will also be reported in the administration notification log on the HADR primary database if a connection cannot be established.
If this new HADR standby database cannot establish a connection to the HADR primary database, then this new HADR standby database will need to be fully reinitialized based on a backup image of the HADR primary database. Please see IBM Db2 Knowledge Center article titled "Initializing high availability disaster recovery (HADR)".

6.2) If the HADR primary database is not running on a different server (or cannot be made to run), then the database on this server should be started as an HADR primary database. Perform the following steps:

Issue the STOP HADR command on the database on this server.
If you wish to establish an HADR standby database on a different server before starting the database on this server as an HADR primary database, then please see IBM Db2 Knowledge Center article titled "Initializing high availability disaster recovery (HADR)".
Issue the START HADR AS PRIMARY command on the database on this server (or the START HADR AS PRIMARY BY FORCE command if there is no HADR standby database running yet).

7

Reissue the command after the restart of the replay completes.

9

Make sure the UPGRADE DATABASE command is issued on the primary database and wait until the standby database is no longer in upgrade in progress state before reissuing the command.

sqlcode: -1776

sqlstate: 08004

SQL1777N

HADR is already started.

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

No action required.

SQL1778N

The HBase table was not created or altered because the column mapping is not valid. Reason code: reason-code. Column or mapping name: name.

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

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

1: The SQL column ''<name>'' is not mapped to an HBase column. All SQL columns must be specified in the HBase COLUMN MAPPING clause.
2: The SQL column ''<name>'' is mapped in multiple HBase COLUMN MAPPING clauses. You cannot specify the same SQL column in more than one HBase COLUMN MAPPING clause.
3: The HBase key or column qualifier name was provided multiple times in the COLUMN MAPPING clause
4: The KEY column mapping was not specified in the CREATE TABLE(HBASE) statement. You cannot create an HBase table without specifying a row key.

Correct the error in the HBase column mapping, and reissue the statement.

sqlcode: -1778

sqlstate: 530AF

SQL1779N

Java class class-name of type class-type could not be loaded. log-entry-id

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

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

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

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

Check the spelling of the specified class name and ensure that the JAR file that contains the class can be accessed by Big SQL.

Locate the diagnostic details in the appropriate log file by using the information in the log-entry-id runtime token. You can retrieve the text of the error from the logs with the following statement:


SELECT * FROM
Table
(SYSHADOOP.LOG_ENTRY('log-entry-id'));

sqlcode: -1779

sqlstate: 46503

SQL1780N

The table was not created because some specified functionality is not supported with the database with code page and collation. Clause specifying the unsupported functionality: clause. Database code page: code-page. Database collation: collation.

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

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

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

Respond to this error in one of the following ways:

Remove the specified functionality and reissue the SQL statement.
To use the specified functionality, drop and recreate the database with a code page and collation that is supported with the functionality

sqlcode: -1780

sqlstate: 560DB

SQL1781N

An error occurred while parsing the configuration file. Configuration type: config-type. Reason code: reason-code.

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

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

1: A line in the configuration file is invalid.
2: A line in the configuration file is too long.
3: An EOF condition was encountered in the configuration file.
4: The configuration file could not be opened.
5: The configuration file could not be read.
6: A parameter in the configuration file is missing or not set.
7: A parameter in the configuration file has an invalid value. When this message is returned with reason code 7, the name of the parameter is included in the runtime token value.

Correct any errors in the external keystore configuration file and rerun the command.

SQL1782N

The command or operation failed because an error was encountered accessing the centralized key manager. Reason code reason-code.

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

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

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

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

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

1: Automatic creation of a new master key and master key label is not allowed.
2: The centralized key manager configuration file specified in the KEYSTORE_LOCATION database manager configuration parameter does not exist.
3: No password was given (the password required to open the SSL keystore is not stashed and no password was provided with the command.)
4: The given password (the password that is stashed or that was provided with the command) is not valid to access the SSL keystore file.
5: SSL error ssl-error was encountered.
6: An authentication error was encountered from the centralized key manager.
7: An authorization error was encountered from the centralized key manager.
8: A KMIP error was encountered from the centralized key manager.
9: The connection is configured to use TLS hostname validation. When connecting to the specified centralized key manager, hostname validation failed because the TLS certificate of the key manager does not contain a hostname or IP address that matches the value configured in the centralized key manager configuration file.

Resolve the problem according to the reason code, and then reissue the command:

1

The ALLOW_KEY_INSERT_WITHOUT_KEYSTORE_BACKUP parameter in the centralized key manager configuration file is set to false. You can either create a new master key and master key label in the centralized kay manager and specify that master key label on the command, or set the ALLOW_KEY_INSERT_WITHOUT_KEYSTORE_BACKUP to true.

2

Set the KEYSTORE_LOCATION database manager configuration parameter to a valid file name.

3, 4

Provide the DB2 server with a valid password for accessing the SSL keystore file in one of the following ways:

Recreate the stash file
Provide the keystore password as an argument to the command

5

Review the SSL error from this list of SSL errors: http://www-01.ibm.com/support/knowledgecenter/SSAL2T_8.1.0/com.ibm.cics.tx.doc/reference/r_gskit_error_codes.html. Correct the problem that is causing the SSL error, and then reissue the command. If the SSL errors continue, contact IBM Software Support for assistance.

6

Review the authentication error that is printed in the db2diag diagnostic log file, correct the problem that is causing the authentication error, and then reissue the command.

7

Review the authorization error that is printed in the db2diag diagnostic log file, correct the problem that is causing the authorization error, and then reissue the command.

8

Review the KMIP error that is printed in the db2diag diagnostic log file, correct the problem that is causing the KMIP error, and then reissue the command. If the DEVICE_GROUP configuration parameter is set and the keystore being used is not IBM Security Key Lifecycle Manager (ISKLM), remove the parameter from the configuration file.

9

Open the db2diag.log file and examine the common name and subject alternate name (SAN) fields of the certificate of the centralized key manager. These fields contain the hostnames or IP addresses for which the certificate is issued. Make sure that the system administrator has set up the correct certificate on the key manager. Consult the vendor-specific KMIP documentation for information about how to create the correct certificate.

If the centralized key manager is using the correct certificate and the correct hostname is also specified in the centralized key manager configuration file, this error would suggest that there is a security risk. The communication might have been intercepted by a malicious host.

SQL1783N

The command or operation failed because an error was encountered accessing the PKCS #11 key manager. Reason code reason-code.

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

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

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

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

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

1: The PKCS #11 key manager configuration file specified in the KEYSTORE_LOCATION database manager configuration parameter does not exist.
2: No password was given (the password required to access the PKCS #11 key manager is not stashed and no password was provided with the command.)
3: The given password (the password that is stashed or that was provided with the command) is not valid to access the PKCS #11 key manager.
4: The given password (the password that is stashed or that was provided with the command) is locked.
5: The given password (the password that is stashed or that was provided with the command) is expired.
6: The given password (the password that is stashed or that was provided with the command) is not initialized.
7: An unexpected error was encountered from the PKCS #11 key manager. The error is included in the runtime token value.
8: The PKCS #11 vendor library specified in the PKCS #11 configuraiton file can not be loaded.
9: The provided master key label already exists in the PKCS #11 keystore.
10: Multiple objects with the same label exist in the PKCS #11 keystore.
11: The PKCS #11 keystore is write-protected.
12: There are no slots available in the PKCS #11 keystore.
13: The PKCS #11 slot specified by slot label or slot ID was not found.
14: The user is not authorized to perform the command or operation in the PKCS #11 keystore.

Resolve the problem according to the reason code, and then reissue the command:

1

Set the KEYSTORE_LOCATION database manager configuration parameter to a valid file name.

2, 3

Provide the database server with a valid password for accessing the PKCS #11 key manager in one of the following ways:

Recreate the stash file
Provide the PKCS #11 key manager password as an argument to the command

4, 5, 6

Correct the status of the password within the PKCS #11 key manager, and then reissue the command.

7

Review the PKCS #11 key manager error that is printed in the db2diag diagnostic log file, correct the problem that is causing the error, and then reissue the command.

8

Review the error that is printed in the db2diag diagnostic log file, correct the problem that is causing the error, and then reissue the command.

9

If a master key label was not specified, then reissue the command. Otherwise, take appropriate object management actions using available vendor utilities, and then reissue the command.

10

You can either take appropriate object management actions using available vendor utilities, and then reissue the command, or you can reissue the command and specify a different master key label.

11

Certain actions may not be allowed on a write-protected PKCS #11 keystore. Review those actions using available vendor utilities.

12

Check configuration and ability to connect to the PKCS #11 keystore using available vendor utilities.

13

Verify the provided slot label or slot ID is correct, and then reissue the command.

14

Review the authorization error that is printed in the db2diag diagnostic log file, correct the problem that is causing the authorization error, and then reissue the command.

SQL1784N

The operation failed because a database object has been modified in a later code level and cannot be accessed from the current code level. Database object name: object-name. Object code level marker: marker1. Current code level marker: marker2.

This message is returned in the following scenario:

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

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

Apply the higher fix pack code level again ("code level B" described in the explanation).
If the fall back operation is necessary, drop the object named in the runtime token object-name, fall back to the earlier fix pack code level ("code level A" described in the explanation), and recreate the object.

SQL1786N

DB2START processing failed due to an invalid netmon.cf file.

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

Review the diagnostic (db2diag) log files to determine the misconfiguration found within the /var/ct/cfg/netmon.cf file.

Correct the misconfiguration. Stop and restart the peer domain before re-issuing the db2start command.

SQL1790W

A default table space could not be found with a page size of at least page size that authorization ID authorization-id is authorized to use.

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

Ensure that a table space with a page size of at least pagesize exists.

sqlcode: +1790

sqlstate: 01670

SQL1791N

The specified server definition, schema, or nickname does not exist.

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

Specify an existing server definition, schema, or nickname and resubmit the statement.

sqlcode: -1791

sqlstate: 42704

SQL1792W

The statistics for the specified nicknames were not updated completely because of schema inconsistencies between the remote and local catalogs.

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

Create a new nickname and resubmit the statement.

sqlcode: +1792

sqlstate: 01669

SQL1793N

The model schema-name.model-name could not be reverted. Reason code: reason-code.

The model reversion operation could not be completed successfully. Any existing model versions associated with the model remain unchanged. The possible reason codes are as follows:

1: The model has no versions to revert to.

Respond according to the reason code provided:

1: No response is necessary.

sqlcode: -1793

sqlstate: 5507B

SQL1794N

There are no models defined for the associated object schema-name.object-name.

An operation cannot be completed successfully because there are no models defined for the associated object.

Verify that the associated object name is spelled correctly.

sqlcode: -1794

sqlstate: 4274O

SQL1795W

The database configuration parameter was enabled successfully, but another feature that it depends on is not enabled. Reason code: reason-code.

A database configuration parameter was enabled successfully, but another feature that it depends on is not enabled. The possible reason codes are as follows:

3: The AUTO_AI_OPTIMIZER database configuration parameter hierarchy depends on the AUTO_RUNSTATS database configuration parameter.

Respond according to the reason code provided:

3: Ensure that the AUTO_RUNSTATS database configuration parameter and its parent hierarchy are both enabled for the database when enabling the AI Optimizer.

sqlcode: +1795

sqlstate: 01694

SQL1796I

The logical backup utility completed successfully. The timestamp for the backup image is timestamp.

The logical backup utility produced a backup image successfully. Refer to the timestamp to use that image in the future.

No action is required. Processing can continue.

sqlcode: +1796

sqlstate: 01541

SQL1797N

The utility-name utility has failed with error error-text.

The utility identified by utility-name has encountered an error and is terminated.

Refer to the error text and any relevant log files for details. Correct the error and run the utility again.

sqlcode: -1797

sqlstate: 5UA0Q

SQL1798N

The maximum number of columns that can be added to the table has been reached. Recreate the table if you want to add more columns.

The maximum number of columns that can be added to the table has been reached.

Recreate the table if you want to add more columns.

sqlcode: -1798

sqlstate: 54011

SQL1800N

An invalid pointer to structure sqle_request_info was passed to the catalog admin command/api.

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

Specify a valid pointer to sqle_request_info and re-submit the command.

SQL1801N

Invalid request type.

The specified request type is not supported for this command.

Ensure that the request type is one of the following supported request types:

SQLE_CCA_REQUEST - CCA catalog node request for catalog and open scan command
SQLE_DAS_REQUEST - DAS catalog node request for catalog and open scan command
SQLE_CND_REQUEST - Open scan command for CCA and DAS catalog entries

SQL1802N

No entry belongs to the request type.

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

Catalog an entry with the same request type and re-submit the command.

SQL1803N

The requested operation cannot be executed on a CLI dynamic SQL package that is in use, or on any package if in "No Package Lock" mode. An affected package is pkgschema.pkgname_0Xcontoken.

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

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

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

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

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

If the package is a CLI dynamic SQL package, then only attempt this operation when there are no other active connections that are using the CLI packages.
If "No Package Lock" mode is active, do not attempt disallowed operations in "No Package Lock" mode. In order to execute the requested operation, "No Package Lock" mode must be exited. This is accomplished by unsetting the DB2_APM_PERFORMANCE environment registry variable. In order for the variable change to take effect, that database manager must be stopped and restarted.

sqlcode: -1803

sqlstate: 57056

SQL1804N

The statement could not be executed on the current connection because there is already an active statement on that connection, and the data source has not been enabled for multiple active statements on a single connection. Federated data source name: data-source-name.

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

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

Respond to this error in one of the following ways:

Execute only one statement at once on any connection.
Enable simultaneous execution of multiple statements on one connection by setting the DB2_ONE_REQUEST_PER_CONNECTION server option to 'N' using the ALTER SERVER statement:
```
ALTER SERVER <server-name> OPTIONS(
     ADD DB2_ONE_REQUEST_PER_CONNECTION 'N')
```

sqlcode: -1804

sqlstate: 57064

SQL1805N

The insert, update, or delete operation was not processed because the operation uses a nickname in a way that is not supported.

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

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

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

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

Respond to this message in one of the following ways:

To update a data source object that is in a federated system but not in the federated database itself, use methods other than compound SQL statements, SQL procedures, or triggers.
Remove any insert, update, or delete operations against a nickname or federated three-part name from compound SQL statements, SQL procedures, or triggers.

sqlcode: -1805

sqlstate: 429A9

SQL1806N

A two-phase commit transaction failed because the transaction is being distributed across a federated server topology that is not valid for two-phase commit transactions.

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

Transaction identifiers
Transaction managers
Resource managers

In federated systems there is an additional component:

The federated server becomes a federated transaction manager

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

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

Review the transaction that failed as well as the topology of the federated server and remote data sources involved in the failed transaction.
Modify the topology of the federated server and the remote data sources so that no federated server must both receive federated two-phase commit requests and send federated two-phase commit requests to a data source as part of the same transaction.

sqlcode: -1806

sqlstate: 25503

SQL1807N

Execution of an SQL statement against a federated data source failed because some part of the SQL statement is not supported by the specified data source. Federated data source name: data-source-name. Unsupported clause: clause.

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

This message can be returned for the following reasons:

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

Respond to this message according to the reason the message was returned:

If the statement includes the DEFAULT keyword, rewrite the statement without the DEFAULT keyword and execute the statement again.
If you are attempting to open a cursor, respond in one of the following ways:
- If the statement for which the cursor is being created does not insert, update, or delete data, recreate the cursor as read-only.
- Enable insert, update, and delete operations by setting the DB2_IUD_ENABLE to 'Y' using the following command:
```
ALTER SERVER <server-name> OPTIONS(
     ADD DB2_IUD_ENABLE 'Y')
```
  After the data source has been configured to allow insert, update, and delete operation, recreate the cursor.

SQL1808N

The execution of an SQL statement failed because the query optimizer produced an access plan that is invalid for a federated environment. Reason code: reason-code.

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

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

1: A part of the predicate cannot be found.
2: The statement includes a positioned update operation or a positioned delete operation. A positioned update or delete operation is an update or delete operation that modifies the data of a result set. Positioned update and delete operations require cursors to be used.
3: An element cannot be found in the columns of a nickname.

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

Respond to this error by performing the following steps:

Rewrite the statement to cause the optimizer to create a different access plan.
Execute the statement again.
If the statement continues to fail after it has been rewritten, collect the diagnostic information and contact IBM support for assistance.

sqlcode: -1808

sqlstate: 58004

SQL1809N

An insert, update, or delete operation in a trusted wrapper failed because part of the query in the body of the wrapper must be evaluated locally. Wrapper name: wrapper-name.

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

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

Respond to this error in one of the following ways:

If no insert, update, or delete operations are required, reopen the cursor as read-only.
Alter the wrapper so that it is no longer trusted using the ALTER WRAPPER statement with the DB2_FENCED wrapper option set to 'Y', and then reopen the cursor.

SQL1810N

The insert or update statement was not executed or the cursor could not be opened because the statement contains some elements that must be evaluated locally and some elements that must be evaluated remotely.

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

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

This message is returned in the following cases:

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

Respond to this error in one of the following ways:

Alter the statement to use neither the INSERT statement with the VALUES clause nor the UPDATE statement with the SET clause, and then execute the statement again.
If this message is returned when an attempt is made to open a cursor on a result set and update, or delete operations are not required, reopen the cursor as read-only.
Cause the federated database to send the statement to the federated data source without evaluating the statement locally by alter the statement so that the statement contains no elements that are not supported by the data source.

SQL1811N

The statement failed because some aspect of the federated server or data source is not supported with federated two-phase commit transactions. Reason code: reason-code.

The reason code indicates the configuration or feature that is unsupported in this context:

1: The federated data source is not supported with federated two-phase commit transactions.
2: The federated server is part of a DB2 cluster and is using the High availability disaster recovery (HADR) feature.
3: The federated server is part of a DB2 cluster and is a partitioned database.
4: The federated server is part of a DB2 cluster and is in the process of an online update.

Respond to this message according to the reason code:

1

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

To access data in the specified data source, do not use two-phase commit transactions.
To use two-phase commit transactions, do not include the specified data source in the transactions.

1, 2

To use two-phase commit transactions, do not include the specified data source in the transactions.

3

Wait for the online update to complete and then perform the transaction again.

sqlcode: -1811

sqlstate: 560D7

SQL1812W

Length of column column-name was reduced from remote-column-length to column-length.

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

Examine the remote table and identify the column that use large-scale types such as STRING or BINARY. In the local column specification for the nickname, using ALTER NICKNAME statement change the data type of the column that correspond to the column identified in the previous step. Ensure that the column size is large enough to accommodate the data in the remote data source.

sqlcode: +1812

sqlstate: 0169E

SQL1815N

Federation is not supported for XML data when the Database Partitioning Feature is enabled.

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

To use federation with XML data, create a new database instance without the Database Partitioning Feature enabled.

sqlcode: -1815

sqlstate: 55076

SQL1816N

Wrapper wrapper-name cannot be used to access the type-or-version of data source (server-type server-version) that you are trying to define to the federated database.

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

Consult the documentation to find out which wrapper supports the type and version of data source that you want to define. Make sure that the wrapper has been registered to the federated database by the CREATE WRAPPER statement. Then recode the CREATE SERVER statement so that it specifies this wrapper, and run the CREATE SERVER statement again.

sqlcode: -1816

sqlstate: 560AC

SQL1817N

The CREATE SERVER statement does not identify the type-or-version of data source that you want defined to the federated database.

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

In the CREATE SERVER statement, code the type-or-version option so that it designates the type-or-version of data source being defined. Then run the CREATE SERVER statement again.

sqlcode: -1817

sqlstate: 428EU

SQL1818N

The ALTER SERVER statement that you submitted could not be processed.

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

Let the unit of work finish; then resubmit the ALTER SERVER statement.

sqlcode: -1818

sqlstate: 55007

SQL1819N

The DROP SERVER statement that you submitted could not be processed.

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

Let the unit of work finish; then resubmit the DROP SERVER statement.

sqlcode: -1819

sqlstate: 55006

SQL1820N

Action on the LOB value failed. Reason code=reason-code.

The possible reasons codes are:

Not enough buffer space to store the LOB value.
The remote data source does not support the current action on LOB data type.
Some internal programming limitation exceeded.

Reduce the size of the LOB or replace the function which is being applied on the LOB data type. As a last resort, remove the LOB data type from the statement.

sqlcode: -1820

sqlstate: 560A0

SQL1821W

The LOB value retrieved may have changed.

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

Set the "deferred_lob_retrieval" to "N" in SYSSERVEROPTIONS, resubmit your query, or ignore the warning.

sqlcode: +1821

sqlstate: 01621

SQL1822N

Unexpected error code error-code received from data source data-source-name. Associated text and tokens are tokens.

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

Possible error codes include:

4901 Trying to open more than 15 cursors
4902 Row size exceeds 32K limit

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

Ensure the data source is available, then identify and correct the root cause of the problem by locating the appropriate message text and corrective action for the specified error at the data source.

sqlcode: -1822

sqlstate: 560BD

SQL1823N

No data type mapping exists for data type data-type-name from server server-name.

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

Create a mapping for the specified type name on the specified server using the CREATE TYPE MAPPING statement.

sqlcode: -1823

sqlstate: 428C5

SQL1824W

Some base tables in the operands of this UNION ALL may be the same table.

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

Verify if all operands point to different remote tables. If two operands point to the same remote base table, consider issuing a rollback to reverse the update/delete operation.

sqlcode: +1824

sqlstate: 01620

SQL1825N

Execution of an SQL statement against a federated data source failed because some part of the SQL statement is not supported in a federated environment. Federated data source name: data-source-name. Reason code: reason-code.

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

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

1: An attempt was made to insert, update, or delete LOB data through a federated database.
2: An attempt was made to execute an insert, update, or delete operation against a view, which was created with the UNION ALL clause.

Respond to this message according to the reason code:

1: Perform the insert, update, or delete LOB data for the specified data source through native interfaces at the data source.
2: Rewrite the statement so that the insert, update, or delete operation is not using a UNION ALL view, and execute the statement again.

sqlcode: -1825

sqlstate: 429A9

SQL1826N

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

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

The statement cannot be processed.

Refer to the SQL Reference for valid values for the specified column in the specified system catalog object. Correct the statement and reissue it.

sqlcode: -1826

sqlstate: 23521

SQL1827N

No user mapping is defined from local authorization ID auth-ID to server server-name.

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

If it is an ALTER USER MAPPING statement, first create a user mapping using the CREATE USER MAPPING statement. Then, alter the user mapping. If it is a DROP USER MAPPING statement, no extra action is needed because the user mapping does not exist.

sqlcode: -1827

sqlstate: 42704

SQL1828N

No server option option-name is defined for remote server server-name or for a group of remote servers: server type server-type, version server-version, and protocol server-protocol.

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

If it is an ALTER SERVER statement, first create a server option using the CREATE SERVER statement. Then, alter the server option. If it is a DROP SERVER statement, no extra action is needed because the server option for the servers does not exist.

sqlcode: -1828

sqlstate: 42704

SQL1829W

The federated server received the warning message warning-code from the data source server-name. The associated text and tokens are tokens.

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

Use the diagnostic information for the data source to determine what, if any, corrective action to take.

sqlcode: +1829

sqlstate: 0168O

SQL1830N

RETURNS clause must be specified prior to a predicate specification using the EXPRESSION AS clause.

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

The statement cannot be processed.

Specify the CREATE FUNCTION statement with the RESULTS clause prior to the PREDICATE clause.

sqlcode: -1830

sqlstate: 42627

SQL1831N

Table statistics for a subtable subtable-name cannot be updated.

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

The statement cannot be processed.

Update the catalog statistics for the root table of the table hierarchy instead of the subtable.

sqlcode: -1831

sqlstate: 428DY

SQL1832N

The routine routine-name cannot be used to define a filter because it is defined as an SQL function.

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

The statement cannot be processed.

Specify a routine that is not defined with LANGUAGE SQL.

sqlcode: -1832

sqlstate: 429B4

SQL1833N

Connection to remote Extended Search Server host_name on port port_number could not be established or was terminated.

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

Verify the Host name and Port number of the remote Extended Search server. Also, check that the Extended Search Server is up and running

SQL1834N

User-defined column column_name is identical to a fixed column for wrapper Wrapper_name but uses a different data type.

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

Do not specify the fixed columns for Wrapper Wrapper_name in the column definition of an CREATE NICKNAME statement. However, if the fixed columns are specified, then the fixed column name and the data type/data type length must match the fixed column definition. It is not allowed to alter a fixed column name or data type.

SQL1835N

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

Verify that the object name is defined on this server and is of type object_type.

SQL1836N

No column mapping exists between user-defined column column_name and a field name on the remote Extended Search Server es_host_name.

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

Verify that the column name is defined as a field in one of the following:

any of the data sources specified in option DATASOURCE
in a data source in a category specified in option CATEGORY.

SQL1837N

The required option option_name for the option_type object object_name cannot be dropped.

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

See the federation documentation for this data source to determine if the option can be set to another value. It might be necessary to drop the associated object.

sqlcode: -1837

sqlstate: 428GA

SQL1838N

The search statement statement is not a valid Extended Search query.

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

Correct the search statement and submit the request again. Consult the documentation for information about creating valid SQL search statements when using Extended Search Nicknames.

SQL1839N

One or more search parameters are not valid.

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

Consult the IBM DB2 Life Sciences Data Connect Planning, Installation, and Configuration Guide (Part: Extended Search Wrapper) for information about how to write valid SQL statements.

SQL1840N

The option-type option option-name cannot be added to the object-name object.

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

See the federation documentation for this data source. Determine the actions that are valid for the options that are associated with this object.

sqlcode: -1840

sqlstate: 428GA

SQL1841N

The value of the option-type option option-name cannot be changed for the object-name object.

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

See the federation documentation for this data source. Determine the actions that are valid for the options that are associated with this object. It might be necessary to drop the associated object and create it again with a new option value. If this message is produced in response to a SET SERVER OPTION statement, it might be necessary to use an ALTER SERVER statement.

sqlcode: -1841

sqlstate: 428GA

SQL1842N

Option option-name of type option-type for object object-name found near text is not valid. Reason code= reason-code.

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

01: Unexpected character.
02: Element or attribute name expected but not found.
03: Min/max occurrence expected after reference.
04: More than one colon found in an attribute name.
05: Min/max occurrence is not an integer value.
06: Min/max occurrence out of range.
07: Min occurrence greater than max occurrence.
08: Reference in column template option was not "column".
09: '=' delimiter missing from namespace specification.
10: Opening or closing quotation mark missing from namespace specification.
11: Duplicate reference in template.
12: The wrapper option option-name is not allowed when the database manager instance is 32-bit.
13: The two wrapper options or option values are not compatible. The wrapper option option-name is only valid when "DB2_FENCED" is set to "Y".
14: The wrapper option option-name is not supported on this particular platform.
15: The wrapper cannot be loaded into the DB2 threaded engine on this particular platform as it is not threadsafe.
16: The minimum valid value for the wait-time parameter is 1000 microseconds.

See the federation documentation for this data source. Determine the correct option syntax and recode the statement. The reason codes are:

01: Examine the option value near the specified position and change or remove the invalid character.
02: Examine the option value near the specified position and correct the syntax.
03: Ensure that a range specification "[min,max]" follows each reference in the template option value.
04: Templates support only one level of name qualification. Remove the extra qualifications.
05: Ensure that the min occurrence and max occurrence values of a range specification are integers.
06: Ensure that the values for the range specification "[min,max]" are within the allowed ranges for this data source.
07: Correct the range specification. Ensure that the first number is less than or equal to the second.
08: Replace the reference in the column template option value with the token 'column'.
09,10: Recode the namespace option value in the form 'name="specification"'.
11: Recode the template. Ensure that no references are repeated.
12: Do not specify the option-name wrapper option for a 32-bit database manager instance.
13: Examine the option value for the "DB2_FENCED" wrapper option.
14: Consult the SQL Reference to verify the wrapper option that you want. Install and use the 64-bit client for this data source.
15: Specify the value "Y" for the "DB2_FENCED" wrapper option.
16: Issue the statement again with a valid value for wait-time.

sqlcode: -1842

sqlstate: 42616

SQL1843N

The operator-name operator is not supported for the nickname-name.column-name nickname column.

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

See the federation documentation for this data source. Recode the statement and remove or change the invalid expression. Then submit the statement again.

sqlcode: -1843

sqlstate: 429BP

SQL1844W

Data for column column-name were truncated between the remote data source and the federated server.

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

To correct this problem, examine the statement for any type-cast or conversion functions that might be restricting the size of data returned from the remote data source. If the statement contains these functions, recode the statement to allow larger data to be returned from the data source. Then submit the statement again. If the statement does not contain these functions, or if correcting the functions does not correct the problem, examine the local column specification in the nickname in the DB2 catalog. Using the ALTER NICKNAME statement or DROP NICKNAME and CREATE NICKNAME statements, change the column specification to ensure that the column size is larege enough to accomodate the data returned by the remote data source.

sqlcode: +1844

sqlstate: 01004

SQL1846N

The option-type-1 option option-name-1 for the object-name-1 object conflicts with option-type-2 option option-name-2 for the object-name-2 object.

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

See the federation documentation for this data source. Determine the valid options that can be specified with this object. Then recode and submit the statement again.

sqlcode: -1846

sqlstate: 42867

SQL1847N

Template substitution error for the object-name object-type. Reason code = reason-code. Additional text and tokens text.

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

01: Reference name not found in template. The additional text identifies the missing reference.
02: Cannot substitute an attribute reference with element content. The additional text identifies the reference in error.

See the federation documentation for this data source. Further diagnostic information may be logged to the db2diag log file. Correct the template syntax if necessary, using the ALTER NICKNAME statemet. Then submit the original statement again.

sqlcode: -1847

sqlstate: 428G9

SQL1860N

Table space tablespace-name is not compatible with table space tablespace-name. Reason code = reason-code.

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

1: All table spaces (data, long, index) for a partitioned table must be in the same database partition group.
2: The data table spaces for a partitioned table must be either all SMS, all regular DMS, or all large DMS. The index table spaces for a partitioned index must be all regular DMS or all large DMS.
3: The page size for all data table spaces must be the same. The page size for all index table spaces must be the same. The page size for all long table spaces must be the same. However, the page sizes of data table spaces, index table spaces, and long table spaces can be different from each other.
4: The extent size for each data table space must be the same as the extent sizes of other data table spaces. The extent size for each index table spaces must be the same as the extent sizes of other index table spaces. The extent sizes for all table space used storing long data must also be the same. However, the extent sizes of table spaces used for different purposes do not need to match.
5: Long data for a partitioned table must be stored in the same table space as the data for all data partitions or it must be stored in large table spaces, each of which is distinct from the table space of the corresponding data partition. This error will occur if a LONG IN clause is used that specifies a table space that is different from the data table space but is not a large table space. LONG IN can only be used to specify regular table spaces if they are identical to the data table spaces (i.e. in the case where the LONG IN clause is redundant because it merely specifies the data table spaces, which is the same as the default behavior if LONG IN were omitted entirely).

Specify a table space that matches the other table spaces for the table.

sqlcode: -1860

sqlstate: 42838

SQL1865W

Query result might not be consistent with remote semantics and follows local semantics. Reason code: reason-code.

For Federation/DV, server option ignore_semantic_difference identifies if the server is in ignore_semantic_difference mode.

N means it is in maximal_consistency mode: query results will follow local query semantics.

Y means it is in ignore_semantic_difference mode: query results will follow remote datasource semantics.

This message is returned when a query's result might not be consistent with remote datasource semantics even though it was run in ignore_semantic_difference mode.

The reason code indicates in more detail why this is the case:

1: Query execution is not fully pushed down to the remote datasource; its processing reverts to maximal_consistency mode.
2: MQT table which has been populated follows local semantics; its result is consistent with local semantics.

The statement will be processed.

1

Evaluate whether the semantic difference affects the correctness of the application using the results.

If so, either check why the query is not fully pushed down and then modify it to fully push down to avoid the difference or account for the difference in the application.

2

MQTs are always populated using local semantics.

sqlcode: 1865

sqlstate: 0169J

SQL1870N

A row could not be inserted into a range-clustered table because a key sequence column is out of range.

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

To see the range defined by the range-clustered table query the constraints defined on this table, and find the constraint named "RCT". For example: SELECT * FROM SYSIBM.SYSCHECKS WHERE NAME='RCT' AND TABLE=<rct table-name>

you can drop and recreate the range-clustered table with the WITH OVERFLOW option enabled. This will create a range-clustered table which can handle out-of-range records, but does not guarantee ordering and has higher locking implications.
you can drop and recreate the range-clustered table with a new range definition which will include this record.
you can define a view which is a UNION ALL of the range-clustered table records and create a separate table which contains the out-of-range records. Inserts, updates, deletes, merges, and queries should then be directed at the view.

sqlcode: -1870

sqlstate: 23513

SQL1871N

This function is not supported on range-clustered tables. Reason code = reason-code.

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

1

VALUE COMPRESSION and COMPRESS SYSTEM DEFAULT are not available.

2

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

3

Adding a column is not supported.

4

SET DATA TYPE is not supported.

5

Changing PCTFREE is not supported.

6

Changing APPEND mode is not supported.

7

Column attributes cannot be changed.

8

Typed tables are not supported.

10

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

11

The LOAD utility is not supported.

12

Table Reorganization is not supported.

13

Table Truncate is not supported.

14

Columns of type XML cannot be used.

15

COMPRESS YES is not supported.

17

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

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

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


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

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


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

18

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

19

Random distribution tables are not supported.

If the unavailable function is required on this table, consider creating the table without the ORGANIZE BY KEY SEQUENCE clause. If the table already exists, you will need to drop and then create the table again. Reason codes:

1

Remove the VALUE COMPRESSION clause or the COMPRESS SYSTEM DEFAULT clause.

2

Remove the CLUSTER keyword from the CREATE INDEX statement.

3

To add a column you must drop and create the table again with the additional column.

4

Remove SET DATA TYPE clause from the ALTER TABLE statement.

5

Remove PCTFREE clause from the ALTER TABLE statement.

6

Remove the APPEND clause from the ALTER TABLE statement.

7

To change column attributes you must drop and create the table again with the new column attributes.

8

Do not use a typed table definition together with the ORGANIZE BY KEY SEQUENCE clause.

10

To alter or redistribute a database partition group that was used to define a tablespace containing a range-clustered table, perform the following steps:

Drop and recreate the range-clustered table in a table space that does not belong to the database partition group that you want to alter or redistribute.
Call the ALTER TABLESPACE command or the REDISTRIBUTE DATABASE PARTITION GROUP command again.

11

Consider using the IMPORT utility instead of the LOAD utility. Multiple IMPORT commands can be issued concurrently using subsets of the data to improve performance. Also consider using parallel insert applications which populate different regions of the key sequence range.

12

Table reorganization is not required for Range Clustered Tables.

13

Drop the table and recreate.

14

Remove the column defined with data type XML or use another supported data type.

15

Remove the COMPRESS YES clause.

17

To create a range-clustered table in a partitioned database environment, make one of the following changes to the CREATE TABLE statement and execute the statement again:

Use the DISTRIBUTE BY REPLICATION clause instead of the DISTRIBUTE BY HASH clause.
Specify a single column as the distribution key with the DISTRIBUTE BY HASH clause that is one of the columns specified in the sequence key with the ORGANIZE BY KEY SEQUENCE clause.

18

Execute the CREATE TABLE statement again, without specifying the DISALLOW OVERFLOW clause.

19

Remove the DISTRIBUTE BY RANDOM clause.

sqlcode: -1871

sqlstate: 429BG

SQL1880N

option-name is not a supported option-type option for cursor object-name by either the wrapper wrapper-name, or the federated data source server-name, or both.

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

The cursor cannot be opened.

Do not open the cursor with this option.

sqlcode: -1880

sqlstate: 428EE

SQL1881N

The server option was not set because the option is invalid in the context in which it is being used. Option: option-name. Type of option: option-type. Object to which the option is being applied: object-name.

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

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

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

Review the server options that are appropriate for the data source, and then execute the statement again, specifying valid options.

sqlcode: -1881

sqlstate: 428EE

SQL1882N

The option-type option option-name cannot be set to option-value for object-name.

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

Consult the SQL Reference to verify the value that you want. Then revise and resubmit the statement that you want to run. Be sure to delimit the value in single quotes.

sqlcode: -1882

sqlstate: 428EF

SQL1883N

option-name is a required option-type option for object-name.

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

Consult the documentation to find out the options that are required for the statement that you want to run. Then revise and resubmit this statement.

sqlcode: -1883

sqlstate: 428EG

SQL1884N

The option_name option was specified more than once for the object_type object object_name.

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

Recode the statement so that the statement references the option that you want only once. Then submit the statement again.

sqlcode: -1884

sqlstate: 42853

SQL1885N

The option_type option option_name is already defined for object_name.

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

Query the appropriate catalog view to determine what value the option is currently set to. If the option value differs from the one that you want, recode the statement so that the SET keyword follows the OPTIONS keyword. Determine which catalog view contains the options for this option.

sqlcode: -1885

sqlstate: 428EH

SQL1886N

The operation-type operation is not valid because the option-type option option-name has not been defined for object-name.

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

If you specified SET in the statement that you want to run, recode the statement, either omitting SET or replacing it with ADD (ADD is the default); remove any incorrect DROP clause. Then submit the statement again.

sqlcode: -1886

sqlstate: 428EJ

SQL1887N

SPECIFICATION ONLY clause required.

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

Add the SPECIFICATION ONLY clause and then resubmit the statement.

sqlcode: -1887

sqlstate: 42601

SQL1888N

The port number port-number is not valid.

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

Verify that the port number is specified as a numeric value and that it is no more than 14 characters in length.

Resubmit the command with a valid port number.

SQL1889W

The update alternate server request was ignored.

The request can only be applied to a database server.

Issue the request in a database server.

SQL1890N

The host name host-name is not valid.

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

Verify that the host name is no longer than 255 characters in length.

Resubmit the command with a valid host name.

SQL1891N

The address of the host name parameter is not valid.

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

The command cannot be processed.

Correct the application program so a correct address is used and the input string is null terminated.

SQL1892N

The address of the port number parameter is not valid.

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

The command cannot be processed.

Correct the application program so a correct address is used and the input string is null terminated.

SQL1900N

The command completed successfully.

The command line utility successfully completed the command.

No action is required.

SQL1901N

The syntax of the command is not correct.

The command line utility could not process the command.

Correct and resubmit the command.

SQL1902W

An even number of hosts has been detected. It is recommended to have an odd number of hosts in the cluster for majority quorum, to avoid a split brain scenario. You have the option of adding an additional cluster host to use majority quorum or a Qdevice host as quorum arbitrator. Number of hosts : number-hosts.

An even number of hosts were detected in the IBM Db2 High Availability ( HA ) Database Partition Feature ( DPF ) environment. In DPF, without a Qdevice and an even number of hosts, a split brain scenario can occur.

Add a host to make the total number of quorum hosts an odd value, or add a Qdevice host as a quorum arbitrator.