SQL21000-29999

SQL Message ID	Message	Explanation	User Response
SQL21000N	A text search option is not installed or not properly configured.	DB2 Text Search or DB2 Net Search Extender is not installed or not correctly configured on this server. One of the text search features must be correctly configured and started on your system if you want to use a text search function such as CONTAINS, SCORE, or NUMBEROFMATCHES, or the DESCRIBE TEXT SEARCH INDEXES command. DB2 Text Search is not supported in a DB2 pureScale environment.	Ensure that either DB2 Text Search or DB2 Net Search Extender is correctly installed and configured and that the database is enabled for text search. Disable the DB2 pureScale Feature to use DB2 Text Search. sqlcode: -21000 sqlstate: 42724
SQL21002N	A snapshot backup failed. The database being backed up is configured to use raw logs, but raw logs are not supported with snapshot backups.	You cannot perform a snapshot backup on a database that uses a raw device for database logging. The snapshot backup failed.	You have two choices: Even though you cannot perform a snapshot backup on a database that uses a raw device for database logging, you can perform a traditional backup on a database that uses a raw device for database logging. You can reconfigure the database log path to be a file path instead of a raw device and then run a snapshot backup.
SQL22000W	Cannot find the requested configuration for object `object-name`. Returning default configuration for `object-type`.	The object does not have a specific configuration of its own so the default configuration for that object type will be returned.	If the behavior of the default configuration is correct, no action has to be taken.
SQL22001W	Cannot find the default configuration for object `object-name`. Returning install configuration for `object-type`.	The object does not have a specific configuration of its own so the install configuration for that object type will be returned.	If the behavior of the install configuration is correct, no action has to be taken.
SQL22004N	Cannot find the requested configuration for the given object. Returning default configuration for `object-name`.	The object does not have a specific configuration of its own so the default configuration for that object type will be returned.	If the behavior of the default configuration is correct, no action has to be taken.
SQL22005N	Cannot find the default configuration for the given object, returning install configuration for `object-name`.	The object does not have a specific configuration of its own so the install configuration for that object type will be returned.	If the behavior of the install configuration is correct, no action has to be taken.
SQL22006N	Cannot update `object-action-or-contact-name` because it does not exist.	The API was requested to update the configuration of an element which does not exist.	Create the element and then re-issue the API call.
SQL22007N	The specified Health Indicator identifier or name, `Health-Indicator-name`, is invalid.	The requested action can only be performed against a valid Health Indicator. The supplied Health Indicator does not exist.	Determine the correct the identifier or name, and resubmit the request.
SQL22008N	The value `parameter-value` of parameter `parameter-name` is not of the correct format, type, or value.	The requested action can not be taken because the supplied value for this parameter is not of an acceptable format, type, or value.	Determine the correct format and type of, or value for, this parameter, and resubmit the request.
SQL22009N	There is no health contact information for this instance.	There is no health contact information for this instance.	If the current contact information is correct, no action has to be taken.
SQL22010N	The value `parameter-value` of parameter `parameter-name` is not within the acceptable range of values for this parameter, which is greater than `parameter-max-value` and/or less than `parameter-min-value`.	The requested action can not be taken because the supplied value for this parameter is not within the acceptable range of values.	Resubmit the request with an acceptable value for this parameter.
SQL22011W	Cannot find the configuration for `object-name-or-type`.	The object or object type does not have a specific or default configuration of its own.	No action required.
SQL22012W	Implicit instance attach failed.	An explicit instance attachment does not exist and an implicit attachment to the default instance failed. The command cannot be executed.	Make sure that the database manager is started and that environment variables are set properly.
SQL22013N	Cannot add `obj-act-contact` because it already exists.	The API was requested to add an action or notification which already exists.	Modify or delete the existing actions and notifications.
SQL22014W	The health monitor returned no health related data.	There is no health data for this instance or the health monitor is off.	Verify that the health monitor is running on this instance.
SQL22015N	The specified Health Indicator identifier or name, `Health-Indicator-name`, is invalid for this object type.	The supplied Health Indicator does not exist for this object type.	Verify the object type and identifier or name, and resubmit the request.
SQL22016N	The health monitor returned no recommendations for health indicator `Health-Indicator-name`. Reason code = `reason-code`.	The health monitor was unable to return any recommendations. The explanation corresponding to the reason code is: The health indicator is not in an alert state. The health indicator has not yet been evaluated. The health indicator is disabled.	The action corresponding to the reason code is: Verify that the health indicator is in an alert state. The problem may have already been resolved. It is also possible that the health indicator is fluctuating between alert and normal states. If the indicator is fluctuating, the sensitivity for the health indicator may be set too low and the health indicator may be reacting to changes in system usage. If this is the case, consider increasing the sensitivity using the UPDATE ALERT CONFIGURATION command. Wait for at least one full refresh interval for the health indicator, to ensure that the health indicator has been evaluated. Resubmit the request. Enable the health indicator using the UPDATE ALERT CONFIGURATION command. Wait until the health indicator has been evaluated, then resubmit the request. If the problem persists, contact IBM Support.
SQL22017N	A non-severe error occurred while generating recommendations at the health monitor. SQLCODE = `sqlcode`.	The health monitor encountered a non-severe error while trying to retrieve recommendations for the specified health indicator.	Correct the error as indicated in the SQLCODE. Resubmit the recommendation request. If the problem persists, contact IBM Support.
SQL22018W	The collection data for this health indicator could not be retrieved.	Collection data is stored in tables in the database. The table data could not be retrieved either because the table could not be accessed or the table has been altered from its original definition and the correct columns no longer exist.	If the problem persists, contact IBM Support.
SQL22019N	Health monitor processing was halted due to an unexpected error. Reason code = `reason-code`.		If the problem persists, contact IBM Support.
SQL22020N	Health monitor processing was halted because its shared memory segment upper limit was reached. The current size is `size`.		If the problem persists, contact IBM Support.
SQL22021N	Automation is turned off.	The required utility cannot be performed because the automation switch is turned off currently.	Attempt one of the following: Resolve the problem according to the recommendation provided by the health monitor. Turn on the corresponding automation switch.
SQL22022N	The duration of the maintenance window is not long enough to run the maintenance activity.	The required utility cannot be performed because the maintenance window defined in the automatic maintenance configuration does not have an adequate duration.	Attempt one of the following: Resolve the problem according to the recommendation provided by the health monitor. Increase the duration of the maintenance window for the corresponding automatic maintenance activity.
SQL22025N	An invalid input argument was specified for the reorgchk stored procedure.	Only 'T' and 'S' are supported for the first argument of the stored procedure. If 'T' is specified as the first argument, the second argument to the stored procedure must be a fully qualified table name as <schema.table-name>.	Resubmit with valid input arguments.
SQL22200N	The DB2 Administration Server cannot be stopped.	The DB2 Administration Server cannot be stopped because it is currently handling at least one request from a client.	Issue the DB2ADMIN STOP command with the /FORCE option to cancel all current requests being handled by the DB2 Administration Server and force the DB2 Administration Server to stop.
SQL22201N	The DB2 Administration Server failed to authenticate the user `authorization-ID` on the host `hostname`. Reason code `reason-code`.	The DB2 Administration Server was unable to authenticate the user `authorization-ID` for the following reason: Invalid user ID or password. Password expired. User account is disabled. User account is restricted. The DB2 Administration Server is unable to process requests submitted as the root user. Authorization failed.	Depending on the reason code, try the following: Verify that a valid user ID and password were specified for the host `hostname`. Change the password on host `hostname` for user `authorization-ID`. Contact your system administrator for assistance. Attempt the request again once the password has been changed. Contact your system administrator to unlock the account. Contact your system administrator to find out the restrictions placed on the account. Resubmit the request as a user other than root. An internal authentication error has occurred. If you continue to receive this message after attempting the suggested solutions, contact IBM Support.
SQL22202W	The DB2 Administration Server cannot be quiesced. Reason code `reason-code`.	The DB2 Administration Server quiesce operation failed for one of the following reasons: The DB2 Administration Server is already quiesced. The DB2 Administration Server is currently processing requests on behalf of DB2 clients.	Depending on the reason for the failure, attempt one of the following: No action required. Wait until the DB2 Administration Server is not processing any requests, or resubmit the quiesce request and specify the force option. Forcing a quiesce will terminate any requests that are currently being processed.
SQL22203W	The DB2 Administration Server cannot be unquiesced. Reason code `reason-code`.	The DB2 Administration Server unquiesce operation failed for one of the following reasons: The DB2 Administration Server is not quiesced. There is at least one administration request in progress.	Depending on the reason for the failure, attempt one of the following: No action required. Wait until the DB2 Administration Server has completed processing all administration requests, or resubmit the unquiesce request and specify the force option. Forcing the unquiesce operation will allow normal requests to be handled concurrently with the administration requests, which may prevent the administration requests from completing successfully.
SQL22204N	The DB2 Administration Server encountered a non-severe error while executing a request.	A non-severe error occurred in the DB2 Administration Server while it was processing a request.	Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information. If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Contact IBM Support with the following required information: Problem description SQLCODE or message number SQLCA contents if possible Trace file if possible
SQL22205C	The DB2 Administration Server encountered an unexpected error while executing a request.	An unexpected error occurred in the DB2 Administration Server while it was processing a request.	Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information. If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Contact IBM Support with the following required information: Problem description SQLCODE or message number SQLCA contents if possible Trace file if possible
SQL22206N	An error occurred while accessing a message queue. Reason code `reason-code`.	An unexpected error or bad message was received on a message queue. The following is a list of reason codes: Unable to create a message queue. The number of message queues allowed may have been exceeded. An error was encountered while reading from a message queue. An error was encountered while writing to a message queue. An invalid message was received from a message queue. An error was encountered while opening a message queue. An error was encountered while closing a message queue. An error was encountered while querying a message queue. An error was encountered while deleting a message queue.	Ensure the number of message queues allowed is not reached. Reduce the number of message queues in use if necessary and resubmit the request. If you continue to receive this error message after attempting the suggested solutions, please contact IBM Support.
SQL22207N	The DB2 Administration server cannot execute the script at host `hostname`. Reason code `reason-code`.	The DB2 Administration Server failed to execute the script for one of the following reasons: The user specified an existing script and the script does not exist. The script working directory is invalid. The last line of the script failed to run because a statement termination character could not be found. A system error occurred while attempting to execute the script.	Depending on the reason for the failure, attempt one of the following: Verify that the script specified exists on host `hostname` at the path provided. Verify that the working directory is valid on host `hostname`. Verify the script contents and resubmit the request. Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information. If you continue to receive this error message after attempting the suggested response, refer to the DB2 Administration Server's First Failure Data Capture Log for additional information or contact IBM Support.
SQL22208N	The DB2 Administration Server failed to execute function/method `function-name` in library/class `library-name` at host `hostname`. Reason code `reason-code`.	The DB2 Administration server encountered an error while trying to execute a function/method in a library/class for one of the following reasons: The library/class `library-name` could not be found. The function/method `function-name` could not be found in the library/class `library-name`. The version of the function/method invoked at the DB2 Administration Server is not supported.	Depending on the reason for the failure, attempt one of the following: Verify that the library `library-name` exists on host `hostname`. Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information. If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Contact IBM Support with the following required information: Problem description SQLCODE or message number SQLCA contents if possible Trace file if possible See response for reason code 2.
SQL22209N	The DB2 Administration Server encountered an unexpected Java error on host `hostname`.	An error occurred while the DB2 Administration Server was attempting to start or communicate with a Java Interpreter. The following could be the cause of the problem: Java has been improperly installed or configured on host `hostname`. The DB2 Administration Server jdk_path configuration parameter has been set incorrectly.	Attempt the following: Contact the system administrator for host `hostname` to verify that Java is properly installed and configured. Verify that the DB2 Administration Server jdk_path configuration parameter has been set correctly. The jdk_path configuration parameter can be viewed using CLP. The parameter should point to the location where Java is installed on the host `hostname`. If you continue to receive this error message after attempting the suggested response, please contact IBM Support.
SQL22210N	The DB2 Administration server cannot execute the specified request while quiesced.	The DB2 Administration Server failed to execute the request because the DB2 Administration Server is currently quiesced. Only administrative requests can be executed while the DB2 Administration Server is quiesced.	Try the request again when the DB2 Administration Server is no longer quiesced. Contact your database administrator to determine when the DB2 Administration Server will be unquiesced.
SQL22211N	An error occurred setting or retrieving the DB2 Administration Server configuration parameter `parameter-token`. Reason code `reason-code`.	The following error occurred while updating or reading the DB2 Administration Server configuration: Configuration parameter is unknown. Configuration parameter value is not in the correct range. A system error occurred while updating the DB2 Administration Server configuration parameters.	Depending on the reason code, verify the following: The configuration parameter exists. The value specified for the configuration parameter is in the correct range. See the description of the configuration parameter in the DB2 Administration Guide: Performance volume for the range of allowable values. Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information or contact IBM Support.
SQL22212N	A DB2 Administration Server communication error has been detected. Client system: `client-ip-address`. Server system `server-ip-address`.	A DB2 Administration Server communication error has been detected. Possible causes include the following: The DB2 Administration Server at the server system was shut down by the system administrator. The DB2 Administration Server at the server system was terminated due to an internal or system error. The DB2 Administration Server is not installed at the server system. The DB2 Administration Server has not been cataloged correctly at the client system. The communication subsystem at the client system or server system has not been configured correctly, or has not been started successfully. A network error has caused the connection to go down. An internal error in the DB2 Administration Server caused the connection to go down.	Verify the following: The DB2 Administration Server has not been shut down. The DB2 Administration Server has not been terminated. The DB2 Administration Server has been installed at the server system. The remote DB2 Administration Server is cataloged properly on the client system. The communication subsystems on both client and server systems are configured and started up properly. The network is operating properly. Nothing to verify. If the problem persists, consult with your network administrator or contact IBM Support.
SQL22213N	DB2ADMIN processing was successful. The scheduler was not started successfully.	The DB2ADMIN command successfully started the DB2 Administration Server, but the DB2 Administration Server was unable to start the scheduler.	Perform the following actions: Ensure that the tools catalog database configuration parameters are set to the correct values. For instructions on configuring the Tools Catalog Database, refer to the section on the DB2 Administration Server in the DB2 Administration Guide. Ensure the database manager containing the tools catalog database has been started. If the tools catalog database is remote to the tools catalog database instance, ensure the scheduler user ID and password are set correctly. The scheduler user ID must have SYSADM authority on the tools catalog database. You can change the scheduler user ID and password by using the db2admin setschedid command. Ensure the tools catalog database is not being used by another scheduler. After performing the suggested actions, try stopping and then restarting the DB2 Administration Server. If you continue to receive the error message after performing the suggested actions, contact IBM Support.
SQL22214N	The admin node `node-name` does not exist in the DB2 node directory.	The admin node `node-name` is invalid. The node name does not exist in the DB2 node directory.	Verify that the node name `node-name` is cataloged in the admin node directory using the LIST ADMIN NODE DIRECTORY command. If the admin node is not listed in the admin node directory, submit a CATALOG ADMIN ... NODE command to catalog the admin node. If you continue to receive this error message after attempting the suggested response, please contact IBM Support.
SQL22215W	The DB2 Administration Server configuration parameters were updated successfully.	The configuration parameters were updated successfully, however, you must restart the DB2 Administration Server to have the changes become effective.	Restart the DB2 Administration Server to have the changes become effective.
SQL22216N	An error occurred while performing an extended console operation. Reason code = `reason-code`.	While performing the operation, an unexpected error occurred. The possible reason codes are as follows: 1 The console name used to active the console has more than 8 characters. 2 The operator command that was issued is longer than the allowed 126 characters. 3 For an activate request, the issuer does not have read authority to resource name, MVS.MCSOPER., where is the name of the console. 4 For an activate request, the console was already active.	The action corresponding to the reason code is: 1 Check if the user name supplied as the console name has more than 8 characters. 2 Check if the operator command is more than 126 characters in length. 3 Provide the required read authority to the resource MVS.MCSOPER., where is the name of the console. 4 Ensure that the extended console you want to activate is not active.
SQL22220N	The DB2 Administration Server encountered a script error. Script error code `error-code`.	A script error was encountered while the DB2 Administration server was executing the script. The script exited with error code `error-code`.	Verify that the script is correct. If you continue to receive this error message after attempting the suggested response, refer to the DB2 Administration Server's First Failure Data Capture Log for additional information or contact IBM Support.
SQL22221N	The scheduler is not active. Reason code `reason-code`.	The scheduler was unable to handle the request because the scheduler is not active for one of the following reasons: The scheduler is not enabled. The scheduler is not configured properly.	Check the following: Verify that the scheduler has been enabled. The scheduler is enabled using the SCHED_ENABLE DB2 Administration Server configuration parameter. Verify the current setting of the SCHED_ENABLE parameter by viewing the DB2 Administration Server configuration parameters using the GET ADMIN CONFIGURATION command. To modify the value of any configuration parameter, use the UPDATE ADMIN CONFIGURATION command. Verify that the scheduler is properly configured. To configure the scheduler, refer to the section on the DB2 administration server in the DB2 Administration Guide. If you continue to receive this error message after attempting the suggested response, refer to the DB2 Administration Server's First Failure Data Capture Log for additional information or contact IBM Support.
SQL22222N	The logon user account for the Scheduler is invalid.	The scheduler requires a valid logon account to connect to the tools catalog database if the tools catalog database is remote to the DB2 Administration Server. This error is caused by the account not being setup, or the logon user account does not contain a valid DB2 user ID.	If a logon user account has been set up, then ensure that the account uses a valid DB2 user ID. You can set up the logon user account for the Scheduler by using the following command: `DB2ADMIN SETSCHEDID <userid> <password>`
SQL22223N	The instance `instance-name` does not exist on host `hostname`.	The DB2 Administration Server on host `hostname` failed to execute a request because the instance `instance-name` provided in the request does not exist on the host.	Verify the following: The remote instance field of the node entry in the local node directory corresponding to the instance `instance-name` is correct. The instance `instance-name` exists on host `hostname`. If you continue to receive this error message after attempting the suggested response, refer to the DB2 Administration Server's First Failure Data Capture Log for additional information or contact IBM Support.
SQL22230N	The data set `dataset` could not be located on the system.	One of the following reasons may apply: The data set has not been cataloged. The volume on which the data set is located is not mounted. The data set does not exist on the volume specified in the catalog. A data set or PDS/E member name required for this operation was not specified. The data set or PDS/E member name contains invalid characters or is longer than the maximum length allowed by the system. For more information on the first three of these reasons refer to the MVS system messages IGW01021T, IGW01508T and IGW01511E.	Ensure that the name of the data set is entered correctly, that the data set has been cataloged and that the volume on which it is located is mounted on the system.
SQL22231N	The requested operation is not supported for the data set `dataset`.	Certain properties of the specified data set prevent it from being used in conjunction with the requested operation, which may include an inapplicable record format or data set type. For example, a member name cannot be specified for a PS data set.	Ensure that the data set has properties that are appropriate for the selected operation. Refer to the DB2 Administration Server's (DAS) First Failure Data Capture Log for additional information.
SQL22232N	The job ID `jobid` was not found on the Job Entry Subsystem (JES).	Possible reasons include: The job with the specified job ID has not been submitted to the JES. The job with the specified job ID has been purged from the JES.	Ensure that the job ID belongs to a job that has been submitted to the JES and that has not been purged yet.
SQL22236N	A file I/O error occurred. Reason code `reason-code`.	An error occurred while accessing the file system. The reasons codes are as follows: An invalid directory was specified. An attempt was made to open a non-existent file. An attempt was made to create an existing file.	The action is based on the reason code as follows. Specify a valid directory. Specify a file that exists. Specify a file that does not already exist.
SQL22237N	A file system error occurred when performing an operation on path `path`. Reason code = `reason-code`.	An error occurred while accessing the file system. The explanation corresponding to the reason code is: 1 The specified path already exists. 2 The specified path does not exist. 3 An attempt was made to modify the specified file or directory which is currently read-only. 4 An attempt was made to modify or delete the specified file or directory which is currently in use by another application. 5 The specified file or directory is not accessible. 6 The specified path or device is not available. 7 The specified non-empty directory was mentioned in an inappropriate context. For example trying to non-recursively delete a non-empty directory. 8 The specified path does not refer to a directory. 9 The specified path is invalid. 10 The specified path name is too long. 11 There is no more space available on the file-system. 12 The maximum number of files that can be open has been reached. 13 The end of the specified file has been reached. 14 A physical I/O error occurred. 15 An unidentified error occurred. 16 A directory with the new directory name already exists.	The user response corresponding to the reason code is: 1 Specify a path that does not exist. 2 Specify a path that does exist. 3 Verify the specified file or directory is not read-only. 4 Verify the specified file or directory is not in use by any other applications. 5 Verify the specified file or directory is accessible to the current user. 6 Verify the specified path or device is still available. 7 Verify the specified directory is empty. 8 Verify the specified path refers to a directory. 9 Verify the specified path is valid. 10 Verify the specified path is within the maximum limit for path names on the specific operating system. 11 Verify there is space available on the file-system. 12 Close one or more files and re-try the operation. 13 Verify the operation is not trying to read or seek beyond the end of file. 14 Retry the operation. If the problem persists, contact IBM Support. 15 Retry the operation. If the problem persists, contact IBM Support. 16 Specify a directory name that does not exist.
SQL22245N	JCL generation failed. Reason (code[, token]) = `reason-code`.	JCL generation failed as indicated by the following reason code: 01 A card with the reserved JCL skeleton parameter &JOB is not found or is misplaced in the main JCL skeleton. This card should be the first non-comment card in the main JCL skeleton after the TEMPLATE card. 02 Incorrect use of a reserved JCL skeleton parameter. The token in this message contains the name of the parameter that caused the problem. 03 There are more occurrences of the reserved JCL skeleton parameter &CTLSTMT in the main JCL skeleton than expected. The token in this message is set to the expected number of the &CTLSTMT parameters. 04 There are more occurrences of the reserved JCL skeleton parameter &STEPLIB in the main JCL skeleton than expected. The token in this message is set to the expected number of the &STEPLIB parameters. 05 The main JCL skeleton does not begin with the TEMPLATE statement. This statement should be the first non-comment statement in the main JCL skeleton. 06 The jobname or stepname in the JCL skeleton does not contain the JCL skeleton built-in function &SEQ required for job or step sequencing. The JCL skeleton built-in function &SEQ should be specified in the jobname or stepname of the JCL skeleton. The token in this message contains a fragment of the incorrect JCL statement. 07 The keyword JOB is not found in the first non-comment statement in the JCL skeleton for //JOB-statement. It might be commented out, mistyped, or missed delimiting spaces, especially after the keyword. 08 The main JCL skeleton is incomplete or has incorrect structure. The required standard JCL statements may be commented out, missed or misplaced, especially if in-stream JCL procedures are being used in this JCL skeleton. 09 The syntax of jobname, stepname, or ddname in the JCL skeleton is invalid. Possible reasons for this: incorrect length of the name field, or the field includes some non-alphanumerical characters. The token in this message contains a fragment of the incorrect JCL statement. 10 An incorrect use of ampersand in the JCL skeleton. The JCL skeleton contains one or more stand-alone ampersand characters. An ampersand is the first symbol of any JCL skeleton parameter and should not be used without an accompanying identifier. The token in this message contains a fragment of the incorrect JCL statement. 11 The reserved JCL skeleton parameter &OBJECT was not found in the JCL skeleton. 12 A user-defined JCL skeleton parameter should not appear in the JCL skeleton. The token in this message contains the name of the JCL skeleton parameter that caused the problem. 13 A reserved JCL skeleton parameter should not appear in the JCL skeleton. The token in this message contains the name of the reserved JCL skeleton parameter that caused the problem. 14 The generated JCL is too long and the buffer for it cannot be allocated. The token in this message contains requested size that caused the problem. To avoid this problem, decrease the number of database objects selected for processing.	Correct the problem according to the given explanation. If the problem persists, contact your Database Administrator or IBM Support.
SQL22247N	The known discovery operation failed.	Discovery is disabled on the target DB2 Administration Server.	Enable discovery by modifying the value of the DISCOVER configuration parameter on the DB2 Administration Server. Change the value to KNOWN if you only want known discovery enabled. Change the value to SEARCH if you want both known and search discovery enabled. To modify the value of the configuration parameter, use the UPDATE ADMIN CONFIGURATION command.
SQL22250N	Usage: DASMIGR is a utility to migrate the DB2 Administration Server to run under the DB2 Copy from which the utility was invoked.	The DASMIGR command syntax is: `DASMIGR [-h \| -p [DAS Profile Path]]` The command options are: -h Prints this message. -p Moves the DAS working directory under the install directory of the current DB2 Copy. DAS Profile Path Overrides the default location where the DAS working directory is to be moved. This option takes affect only if "-p" option is specified. Example: `dasmigr -p "C:\DB2 PROFILES"`	Issue the DASMIGR command with one of the valid command options.
SQL22251N	Migration of the DB2 Administration Server from `source-dasname` to `target-dasname` failed. Reason code `reason-code`.	The DB2 Administration Server `source-dasname` could not be migrated for one of the following reasons: The Tools Catalog Database has not been created at the target DB2 Administration Server. The Tools Catalog Database has been configured improperly at the target DB2 Administration Server.	Attempt the following at the target DB2 Administration Server `target-dasname`: Verify that the Tools Catalog Database exists. Verify the TOOLSCAT_DB and TOOLSCAT_SCHEMA DB2 Administration Server configuration parameters are correct. They should be set to the name and schema of the Tools Catalog Database. View the current settings of TOOLSCAT_DB and TOOLSCAT_SCHEMA using the GET ADMIN CONFIGURATION command. To modify the value of any DB2 Administration Server configuration parameter, use the UPDATE ADMIN CONFIGURATION command If you continue to receive this error message after attempting the suggested response, please contact IBM Support.
SQL22252N	DAS migration failed with reason code `reason-code`.	An error has occurred while migrating the DB2 Administration Server. The reason codes are as follows: The system resources available were insufficient to complete the migration. The DB2 Administration Server's configuration parameters do not identify a valid tools catalog. A non-severe error occurred during migration.	Verify that enough system resources are available for DAS migration. Verify that a tools catalog is created and is identified correctly by the DB2 Administration Server's configuration parameters. Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information.
SQL22255W	Usage: dasauto [-h\|-?] -on\|-off	An incorrect argument was entered. Valid arguments for this command are: -h\|-? display the usage information -on\|-off enables or disables autostarting of the DB2 Administration Server	Enter the command again as follows: dasauto [-h\|-?] -on\|-off
SQL22256W	The dasauto command was successful.	All processing completed normally.	No further action is required.
SQL22260I	The DB2 Administration Server has been updated successfully.
SQL22261N	The DB2 Administration Server update command has encountered an unexpected error.	An unexpected error occurred while attempting to update the DB2 Administration Server.	Contact IBM Support and, if possible supply a trace file.
SQL22262N	Update of the DB2 Administration Server between major releases is not supported.	You can only update the DB2 Administration Server between minor releases of DB2.	Please Use DB2 Administration Server migrate command (dasmigr) to update between major releases.
SQL22263I	The DB2 Administration Server has been migrated successfully.
SQL22264N	The DB2 Administration Server migrate command has encountered an unexpected error.	An unexpected error occurred while attempting to migrate the DB2 Administration Server.	Contact IBM Support and, if possible supply a trace file.
SQL22265N	Migration of the DB2 Administration Server between minor releases is not supported.	You can only migrate the DB2 Administration Server between major releases of DB2.	Use DB2 Administration Server update command (dasupdt) to update between minor releases.
SQL22266N	The DB2 Administration Server is already installed under the current DB2 Copy.	The DB2 Administration Server is already installed under the DB2 Copy from which the DB2 Administration Server update command was run.	Run the DB2 Administration Server update command from the DB2 Copy to which you would like the DB2 Administration Server to be moved.
SQL22267W	Usage: DASUPDT is a utility to update the DB2 Administration Server to run under the DB2 Copy from which the utility was invoked.	The DASUPDT command syntax is: `DASUPDT [-h \| -p [DAS Profile Path]]` The command options are: -h Prints this message. -p Moves the DAS working directory under the install directory of the current DB2 Copy. DAS Profile Path Overrides the default location where the DAS working directory is to be moved. This option takes affect only if "-p" option is specified. Example: `dasupdt -p "C:\DB2 PROFILES"`	Issue the DASUPDAT command with one of the valid command options.
SQL22270N	The contact, or contact group, with name `name` cannot be added to the contact list.	The contact, or contact group, already exists in the contact list.	Create a new contact, or contact group, with a unique name.
SQL22271N	The contact, or contact group, information with name `name` could not be found.	The contact, or contact group, could not be found in the contact list.	Check and correct the name, and try again.
SQL22272N	The record with key `key` cannot be inserted.	The system tried to insert a record and the new record's key `key` already exists in the system.	Remove the duplicate from the system; or, insert a new record with another key.
SQL22273N	The record with key `key` could not be found.	The record with key `key` could not be found because the record does not exist.	Check and correct the key, and try again.
SQL22280N	This action cannot be performed because the scheduler is quiesced.	No action can be performed until the scheduler is activated again.	Activate the scheduler.
SQL22281N	The scheduler is already active.	The scheduler cannot be made active because it is already active.	No further action is required.
SQL22282N	The scheduler is unable to access the Tools Catalog Database. Reason code = `reason-code` and SQLCODE `sqlcode`.	The scheduler function cannot be processed because the scheduler is unable to access the Tools Catalog Database for the reason specified by the `reason-code` as follows: The given user ID, or password, is incorrect. Incorrect Tools Catalog Database configuration in the DB2 Administration Server configuration parameters. One or more of the following DB2 Administration Server configuration parameters is incorrect: TOOLSCAT_DB TOOLSCAT_SCHEMA The Tools Catalog Database is already being used by another scheduler on the same system. The Tools Catalog Database is only supported through TCP/IP as a communication protocol. Unexpected errors. Refer to SQLCODE `sqlcode` for more details.	The action corresponding to the reason code is: Check your user ID and password and try again. Verify that the DB2 Administration Server TOOLSCAT_DB and TOOLSCAT_SCHEMA configuration parameters have been set correctly. View the current settings of TOOLSCAT_DB and TOOLSCAT_SCHEMA using the GET ADMIN CONFIGURATION command. To modify the value of any DB2 Administration Server configuration parameter, use the UPDATE ADMIN CONFIGURATION command. If you continue to receive this error message after attempting the suggested response, please contact IBM Support. Contact your system administrator. Attempt the following: If the tools catalog database is local to the scheduler, then set up the instance specified by the DB2 Administration Server configuration parameter toolscat_inst to use TCP/IP communications. If the tools catalog database is remote to the scheduler, then ensure that the node used by the toolscat_db admin configuration parameter supports TCP/IP as the communication protocol. Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information. Contact IBM Support if you continue to receive this message after attempting the suggested solutions.
SQL22283N	Task `taskid`.`suffix` does not exist in the Tools Catalog Database.	The scheduler cannot retrieve the task from the Tools Catalog Database. The task might have been removed from the Tools Catalog Database or never existed.	Check for the existence of the task using the Task Center.
SQL22284N	Task `taskid`.`suffix` is not scheduled.	The requested action, Run a scheduled task now, cannot be performed because the task is not currently scheduled to run.	Attempt one of the following: Perform a Run now instead Activate all of the task's schedules and perform Run a scheduled task now again.
SQL22285N	The scheduler is unable to get the corresponding hostname from the partitioned database on partition number `partition-number`.	The requested partition number does not exist in the partitioned database.	Verify that the partition number exists by displaying the list of nodes using the LIST DBPARTITIONNUMS command.
SQL22286N	Unable to execute the required task.	The scheduler failed to run the task because an unexpected error occurred.	Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information. If trace was active, invoke the Independent Trace Facility at the operating system command prompt.
SQL22287N	User `userid` does not have permission to execute Task `taskid`.`suffix`.	The task failed to execute because the user does not have sufficient authority to run the task.	Users must be granted run permission by the owner of the task before they can run the task.
SQL22295N	Unable to communicate successfully with the SMTP server at host `host-name` using port `port-number`. Reason code = `reason-code`.	The SMTP server at host `host-name` using port `port-number` failed to successfully negotiate the protocol to send mail. An explanation of the error is indicated by the following reason code: There is no SMTP server running at `host-name` on port `port-number`. An unexpected error was encountered while communicating with the SMTP server.	Verify that the SMTP server name is specified correctly and that the SMTP port specified in the services file corresponds to the port number being used by the SMTP server. Invoke the Independent Trace Facility at the operating system command prompt. Contact IBM Support if the problem persists. sqlcode: -22295 sqlstate: 08001
SQL22296N	Unable to send mail using the SMTP protocol due to invalid recipient addresses.	The SMTP server failed to successfully negotiate the send mail protocol for all the specified recipients.	Verify that the recipient addresses are specified correctly. This error might also be returned if the SMTP server is unable to reach the recipient addresses. This can be independently verified by using any other mail client to send mail to the recipients using the same SMTP server. If this is successful, invoke the Independent Trace Facility at the operating system command prompt. Contact IBM Support if the problem persists.
SQL22297I	Configuration changes will not be effective until the DB2 Administration Server is restarted.	The DB2 Administration Server has been successfully configured, but the changes will not take effect immediately. The changes will take effect when the DB2 Administration Server is restarted.	To have the change take effect at the next DB2 Administration Server restart, no further action is required.
SQL22400N	The function or feature name `function-or-feature-name` is not valid.	The function or feature name `function-or-feature-name` is not valid. For valid function and feature names, search the documentation.	Specify a valid function or feature name, then try the request again. sqlcode: -22400 sqlstate: 5U001
SQL22401N	The application with agent ID `agent-ID` does not exist.	The application with agent ID `agent-ID` does not currently exist. To see all active database applications, use LIST APPLICATIONS command.	Specify an agent ID for an active application, then try the request again. sqlcode: -22401 sqlstate: 5U002
SQL22402N	No activity monitor reports can be found.	No activity monitor reports can be found because either the report ID or the report type specified is invalid.	Specify a valid report ID or a valid report type, then try the request again. sqlcode: -22402 sqlstate: 5U003
SQL22403N	One or more values provided when saving or dropping the monitoring task `monitoring-task-name` are invalid. Reason code: `code`.	One or more values provided when saving the monitoring task `monitoring-task-name` are invalid for the reason given by reason code `code`. The possible reason codes are as follows: The action mode `action-mode` is invalid. The request to create the monitoring task failed because the specified monitoring task name `monitoring-task-name` is not valid. The request to create the monitoring task failed because another monitoring task with the same name `monitoring-task-name` was found. The request to save the monitoring task failed because the value specified for the availability of application lock chains is not valid. The request to save the monitoring task failed. One or more report IDs in `report-IDs` are invalid because there are no associated reports. The request to modify or drop the monitoring task failed because the specified monitoring task ID `monitoring-task-ID` is not valid. The associated monitoring task either does not exist or is a built-in monitoring task. A built-in monitoring task cannot be modified or dropped.	The action corresponding to the reason code is: To create a new monitoring task, specify action mode C. To modify an existing monitoring task, specify action mode M. Try the request again. A monitoring task name cannot be null, blank, or exceed 128 characters in length. Specify a valid monitoring task name, then try the request again. Monitoring tasks must have unique names. Specify a unique name for the new monitoring task, then try the request again. To make application lock chains available for this monitoring task, specify 'Y'; otherwise, specify 'N'. Try the request again. Specify one or more IDs for activity monitor reports that exist, then try the request again. Specify an existing user-defined monitoring task ID, then try the request again. sqlcode: -22403 sqlstate: 5U004
SQL22404N	The action mode `action-mode` specified when creating or dropping the database objects for function or feature `function-or-feature-name` is not valid.	The action mode `action-mode` is invalid. To create the database objects for `function-or-feature-name`, specify action mode C. To drop the database objects for `function-or-feature-name`, specify action mode D.	Specify a valid action mode, then try the request again. sqlcode: -22404 sqlstate: 5U005
SQL22405N	The Activity Monitor is unable to collect the required snapshot data because the monitor switch `monitor-switch` is not turned on at the database manager level.	The Activity Monitor is unable to collect the required snapshot data because the monitor switch `monitor-switch` is not turned on at the database manager level.	Turn on the specified monitor switch using the monitor switch database manager configuration parameter, then try the request again. sqlcode: -22405 sqlstate: 5U006
SQL27902N	LOAD RESTART/TERMINATE is not allowed on a table that is not in LOAD PENDING state.	No RESTART or TERMINATE is necessary. The RESTART and TERMINATE modes of the LOAD utility should be used to resume or cancel a previously failed/interrupted LOAD operation. They are only supported on tables where a previous load operation failed and the table is in LOAD PENDING state. For tables that are not in LOAD PENDING state, only the INSERT and REPLACE modes of the LOAD utility are supported.	To populate the table with the contents of the input source re-issue your LOAD command using the INSERT or REPLACE mode. You can use the LOAD QUERY utility to find out the current state of the table.
SQL27903I	`agenttype` has started on partition `partitionnumber` at time `timestamp`.	This is an informational message indicating that a DB2 agent is about to begin on a given partition.	No action is required.
SQL27904I	The input file was not found. Using standard input as the input.	This is an informational message indicating that an DB2 agent is about to begin on a given partition.	No action is required.
SQL27905W	The column compression dictionary was built. However, the dictionary might not be optimal due to insufficient utility heap memory.	The load utility analyzes the input data to determine the best encoding schemes for building column compression dictionaries. To build the best dictionaries and get the maximum possible compression, the entire set of data should be loaded at one time and enough utility heap memory should be available. These message is return when the LOAD operation completed successfully but the compression dictionary that was built is not optimal for compression because of insufficient utility heap memory.	Increase the utility heap size before invoking the Load utility.
SQL27906N	The load operation was not performed because the specified parameters are not supported with the type of the target table.	You can efficiently move a large amount of data into a table by using the load utility. In a partitioned database environment, you can perform a load operation on only a subset of the database partitions on which the table is defined by specifying the PARTITIONED DB CONFIG parameter with the LOAD command. You can cause the load utility to build a new dictionary for the table by specifying one of the following parameters with the LOAD command: RESETDICTIONARY, RESETDICTIONARYONLY. This message is returned when an attempt is made to load data into a column-organized table with the following unsupported combination of parameters passed to the LOAD command: The PARTITIONED DB CONFIG parameter is specified with a value of OUTPUT_DBPARTNUMS And either the RESETDICTIONARY parameter or the RESETDICTIONARYONLY parameter is specified	To load data into a column-organized table, using only a subset of database partitions, issue the LOAD command specifying the KEEPDICTIONARY parameter. To load data into a column-organized table and create a new dictionary, issue the LOAD command without specifying OUTPUT_DBPARTNUMS with the PARTITIONED DB CONFIG parameter.
SQL27907I	Maximum input record length `record-length`.	This is an informational message indicating the record length used for the Load operation.	No action is required.
SQL27908I	The utility is running with check level: `check-level`.	This is an informational message indicating whether truncation checking is enabled or not.	No action is required.
SQL27909I	Tracing `numberofrecords` non-delimited record(s).	This is an informational message indicating that tracing is enabled for the first `numofrecords` record(s).	No action is required.
SQL27910I	The string delimiter is `chardel`, the column delimiter is `coldel`, and the decimal point is `decept`. Tracing `numofrecords` delimited record(s).	This is an informational message indicating what delimiters are used for string, column and decimal point. In addition, this message also shows tracing is enabled for the first `numofrecords` record(s).	No action is required.
SQL27911I	The input partition map file `filename` was opened successfully for reading.	This informational message indicates the input partition map file was opened successfully for reading.	No action is required.
SQL27912I	Reading of input partitioning map is in progress.	This informational message indicates that reading of the input partition map file is in progress.	No action is required.
SQL27913I	Input partitioning map was successfully read.	This informational message indicates that the input partition map file was successfully read.	No action is required.
SQL27914I	The mode of operation is `mode`.	This informational message indicates the mode of operation for the partitioning agent. There are two different modes of operation: Partition Analyze	No action is required.
SQL27915I	Output partitioning map file not used.	This is an informational message indicating that the output partitioning map file is not used.	No action is required.
SQL27916I	The output partitioning map file `filename` was opened successfully.	This is an informational message indicating that the output partitioning map file was opened successfully.	No action is required.
SQL27917N	The LOAD command was not executed because a previous load operation on the table failed and the parameters that were specified with the LOAD command are not supported after a failed load operation on this type of table.	You can cause the load utility to build a new dictionary for a table by specifying one of the following parameters with the LOAD command: RESETDICTIONARY, RESETDICTIONARYONLY. If no dictionary exist, then any LOAD command with either the INSERT parameter or the REPLACE parameter will build one. This message is returned when the following sequence of events occurs: The LOAD command is issued against a column-organized table that causes a new dictionary to be built. The load operation fails. The LOAD command is reissued for the same table, with one of the following parameter combinations specified: The KEEPDICTIONARY parameter The TERMINATE parameter in combination with the DBPARTNUM parameter If the LOAD command is issued against a column-organized table, that causes a new dictionary to be built, and the operation fails, then the LOAD command may be reissued for the same table, but with the following restrictions: The KEEPDICTIONARY parameter may not be specified The TERMINATE parameter may not be specified in combination with the DBPARTNUM parameter	Reissue the LOAD command without specifying either of the following parameter combinations: The KEEPDICTIONARY parameter The TERMINATE parameter in combination with the DBPARTNUM parameter
SQL27918I	Distribution file name: `filename`.	This is an informational message indicating the name of the distribution file used in the utility.	No action is required.
SQL27919I	The distribution file `filename` was opened successfully for writing.	This informational message indicates the distribution file was opened successfully for writing.	No action is required.
SQL27920I	This utility is using `numkeys` partitioning keys.	This informational message indicates the number of partitioning keys used in the utility.	No action is required.
SQL27921I	`keyname` Start:`index` Len:`length` Position:`position` Type:`type`.	This informational message describes attributes of a partitioning key.	No action is required.
SQL27922I	Output data files are not created because the run type is ANALYZE.	This is an informational message indicating that the output data files are not created because the mode of operation is ANALYZE.	No action is required.
SQL27923W	The value in row `row-number` and column `column-number` could not be converted to a Boolean value, so a null value was loaded instead.	The inability to convert the value might be due to a data type mismatch, such as trying to load a date into a Boolean column. If the source of the value that could not be converted is: A delimited ASCII (DEL) file, the indicated column number identifies the ordinal position of the field that contains that value An ASCII file, the indicated column number identifies the byte location of the beginning of the field that contains that value	Examine the input data. If necessary, take one of the following actions: Correct the input data and resubmit the command. In the output table, manually replace the null with the correct value.
SQL27924W	The value in row `row-number` and column `column-number` could not be converted to a Boolean value, and the target column is not nullable, so the row was not loaded.	The inability to convert the value might be due to a data type mismatch, such as trying to load a date into a Boolean column. If the source of the value that could not be converted is: A delimited ASCII (DEL) file, the indicated column number identifies the ordinal position of the field that contains that value An ASCII file, the indicated column number identifies the byte location of the beginning of the field that contains that value	Examine the input data. If necessary, take one of the following actions: Correct the input data and resubmit the command. In the output table, manually insert a row containing the correct values.
SQL27926I	Output data for partition `partitionnum` will be sent to standard output.	This is an informational message indicating that the output data on partition `partitionnum` will be sent to standard output.	No action is required.
SQL27927I	Processed `numofrecords` records (or lines).	This is an informational message indicating that `numofrecords` records (or lines) were processed.	No action is required.
SQL27928I	Processing record number `num`.	This informational message indicates which record is being processed. This message will only be reported when the TRACE option is specified.	No action is required.
SQL27929I	Partitioning number returned from hash function: `hexvalue` (hex) `decvalue` (decimal).	This informational message reports the result of the hashing function in both hex and decimal format.	No action is required.
SQL27930N	A record was rejected during partitioning with reason code `reason-code` and partition-relative record number `rec-num`.	A record was rejected during load while attempting to determine what partition the record belongs to. If the 'dumpfile' load modifier was specified, the rejected record can be found in the partition-relative dumpfile at the partition-relative record number `rec-num` listed in this message. An explanation of the error specified by the `reason-code` is as follows: The string representation of the data type of a partitioning column is invalid. Either the syntax is invalid or the value is out of range. The column values corresponding to the partitioning keys are not contained within the first 32K of the record. The record is empty (all space characters). The record length does not match the expected length. The record is incomplete. An error occurred while processing a generated column value.	The action corresponding to the `reason-code` is: Ensure that the string representation or the datatype is correct. The column values comprising the partitioning keys must be contained within the first 32KB of the record. If you are concerned that the record is empty, check your data for correctness. Ensure the record length is not larger or smaller than the expected length. Ensure the input data file is complete. Ensure the generated column value is correct and compliant.
SQL27931I	Writing output partition map to file `filename`.	This is an informational message indicating that the output partition map is written to `filename`.	No action is required.
SQL27932I	Writing distribution map to `filename`.	This is an informational message indicating that the distribution map is written to `filename`.	No action is required.
SQL27935I	`agenttype` has ended on partition `partitionnumber` at time `timestamp`.	This is an informational message indicating that an DB2 agent has just completed operation on a given partition.	No action is required.
SQL27936I	Elapsed time: `hr` hours, `min` minutes, `sec` seconds.	This informational message reports the total time elapsed.	No action is required.
SQL27937I	Throughput: `throughput` records/sec.	This is an informational message indicating the throughput of a given DB2 agent.	No action is required.
SQL27939I	Record counts for output partitions: partition number `partitionnum`. Record count: `numofrecords`.	This informational message indicates the number of records processed for a given partition.	No action is required.
SQL27941I	Program terminated abnormally.	This informational message indicates the utility program has terminated abnormally.	No action is required.
SQL27942I	There are `number-of-warnings` warning message(s) and `number-of-rejected-records` rejected records.	This informational message reports there are `number-of-warnings` warning message(s) and `number-of-rejected-records` rejected record(s) encountered during the operation.	No action is required.
SQL27945I	Key Index: `index`. Data: `data1` `data2` `data3` `data4` `data5`.	This informational message reports the attributes of a given partition key.	No action is required.
SQL27947I	The input data file specified at line `linenum` of the configuration file is ignored.	The input data file specified at line `linenum` of the configuration file is ignored. The command line option will be used if it is specified; otherwise, the first specification of input data file in the configuration file will be used.	No action is required.
SQL27948I	The output data file specified at line `linenum` of the configuration file is ignored.	The output data file specified at line `linenum` of the configuration file is ignored. The command line option will be used if it is specified; otherwise, the first specification of output data in the configuration file will be used.	No action is required.
SQL27949I	The distribution data file specified at line `linenum` of the configuration file is ignored.	The distribution file specified at line `linenum` of the configuration file is ignored. The command line option will be used if it is specified; otherwise, the first specification of distribution file in the configuration file will be used.	No action is required.
SQL27950I	The type of the input data file is `filetype`.	This is an informational message indicating that the format of the input data is `filetype`. 0-ASC 1-DEL 2-BIN 3-CUR	No action is required.
SQL27951I	The NEWLINE flag is ignored in case of binary or delimited input data files.	This informational message reports that the NEWLINE flag is ignored for binary or delimited input data files.	No action is required.
SQL27952I	The NEWLINE flag is turned on.	This informational message reports that the NEWLINE flag is in effect.	No action is required.
SQL27953I	Usage: db2split [-c configuration-file-name] [-d distribution-file-name] [-i input-file-name] [-o output-file-name] [-h help message]	-c option will run this program using a user specified configuration file -d option specifies the distribution file -i option specifies the input file -o option specifies the output file -h option will generate the help message
SQL27959N	The partitioned database configuration option `option-name` is invalid. Reason code = `reason-code`.	The partitioned database configuration option named in the error message is incorrectly specified or is incompatible with one of the other load options specified. The possible reason codes are as follows: 1 Partitioned database configuration options cannot be specified in a non-partitioned database environment or when the DB2_PARTITIONEDLOAD_DEFAULT registry variable is set to OFF. 2 Partitioned database configuration options may not be specified more than once. 3 Invalid pointer detected in the piPartLoadInfoIn input structure passed to the db2Load API. 4 Invalid pointer detected in the poPartLoadInfoOut output structure passed to the db2Load API. 5 The argument supplied to the MODE option must be one of the following: PARTITION_AND_LOAD PARTITION_ONLY LOAD_ONLY LOAD_ONLY_VERIFY_PART ANALYZE 6 The maximum number of partitioning agents must be less than or equal to the maximum number of partitions allowable in a cluster. 7 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. 8 The arguments supplied to the ISOLATE_PART_ERRS option must be one of the following: SETUP_ERRS_ONLY LOAD_ERRS_ONLY SETUP_AND_LOAD_ERRS NO_ISOLATION 9 The value supplied to the STATUS_INTERVAL option must be in the range 1-4000. 10 The maximum port number must be greater than or equal to the minimum port number. 11 The only legal arguments for the CHECK_TRUNCATION, NEWLINE and OMIT_HEADER options are TRUE and FALSE. 12 The argument supplied to RUN_STAT_DBPARTNUM must be a legal partition number. 13 If the mode is ANALYZE, the MAP_FILE_OUTPUT option must be specified. 14 If the mode is PARTITION_ONLY or LOAD_ONLY and a remote client is being used, then the PART_FILE_LOCATION option must be specified. If the mode is PARTITION_ONLY or LOAD_ONLY then if the file type is CURSOR, the PART_FILE_LOCATION option must be used and must specify a file name. 15 The load actions RESTART and TERMINATE can only be used when the mode is PARTITION_AND_LOAD, LOAD_ONLY or LOAD_ONLY_VERIFY_PART. 16 The HOSTNAME option cannot be specified unless the FILE_TRANSFER_CMD option is also specified. 17 The partition isolation error modes LOAD_ERRS_ONLY and SETUP_AND_LOAD_ERRS cannot be used when both the ALLOW READ ACCESS or COPY YES options of the load command are used. 18 The LOAD_ONLY and LOAD_ONLY_VERIFY_PART modes are not compatible with the CLIENT option of the load command. 18 The partitioned database configuration option is not allowed on a random distribution table using the random by generation method.	Resubmit the LOAD command with the correct partitioned database configuration options.
SQL27960N	PART_FILE_LOCATION must specify a fully qualified base filename when the file type is CURSOR.	When loading from an input file of type CURSOR, the PART_FILE_LOCATION option must specify a fully qualified base filename instead of a directory.	Resubmit the LOAD command with a proper argument for the PART_FILE_LOCATION partitioned database configuration option.
SQL27961N	ROWCOUNT cannot be specified in a partitioned database environment unless the mode is ANALYZE.	The ROWCOUNT option of the load command is not supported except when the mode is ANALYZE.	Resubmit the load command without the ROWCOUNT option.
SQL27965N	The DB2_LOAD_COPY_NO_OVERRIDE registry variable value `value` is not valid.	A Load was issued with the COPY NO parameter, but the value of the DB2_LOAD_COPY_NO_OVERRIDE registry variable was not valid.	Set the DB2_LOAD_COPY_NO_OVERRIDE registry variable to a valid value, or unset the registry variable to stop overriding Loads which have the COPY NO parameter.
SQL27966W	The DB2_LOAD_COPY_NO_OVERRIDE registry variable value `value` overrides the COPY NO parameter specified in the Load.	A Load command was issued with the COPY NO parameter, however the DB2_LOAD_COPY_NO_OVERRIDE registry variable overrides the parameter.	Set the DB2_LOAD_COPY_NO_OVERRIDE registry variable to a valid value or unset the registry variable to stop overriding Loads which have the COPY NO parameter.
SQL27967W	The COPY NO recoverability parameter of the Load has been converted to NONRECOVERABLE within the HADR environment.	The COPY NO recoverability parameter of the Load has been converted to NONRECOVERABLE. This occurred because the Load was issued within an HADR environment and the DB2_LOAD_COPY_NO_OVERRIDE registry variable was not set.	The COPY NO Load parameter is not valid within an HADR environment. The DB2_LOAD_COPY_NO_OVERRIDE registry variable can be set to override the COPY NO parameter or you can accept that the COPY NO parameter will be converted to NONRECOVERABLE.
SQL27970N	An incompatible combination of import options is specified. Reason code = `reason-code`.	An incompatible combination of import options is specified by the user. The command cannot be processed. An explanation of the error specified by the `reason-code` is as follows: The SKIPCOUNT and RESTARTCOUNT options are mutually exclusive. Online import mode (ALLOW WRITE ACCESS) is not compatible with the REPLACE, CREATE and REPLACE_CREATE import options. Online import mode (ALLOW WRITE ACCESS) was specified for the import command using buffered inserts. Online import mode (ALLOW WRITE ACCESS) was specified for the import command inserting into a view. Online import mode (ALLOW WRITE ACCESS) was specified for the target table using table lock size. Commitcount AUTOMATIC was specified for the import command using buffered inserts. Commitcount AUTOMATIC was specified for the import command, but the server does not support this option. The servers supporting automatic commitcount are DB2 UDB on Linux, Unix and Windows V8.1 FixPak 4 and higher DB2 versions. Online import mode (ALLOW WRITE ACCESS) was specified for the import command, but the server does not support this option. The servers supporting online import are Linux, Unix and Windows, zSeries and iSeries.	The action corresponds to the following reason codes: Reissue the command using either the SKIPCOUNT or RESTARTCOUNT option. Reissue the command without specifying ALLOW WRITE ACCESS, or use INSERT or INSERT_UPDATE import option. Reissue the command without specifying ALLOW WRITE ACCESS, or rebind the import packages (bind files db2uimtb.bnd and db2uimpm.bnd) without using the INSERT BUF option. Reissue the command without specifying ALLOW WRITE ACCESS. Reissue the command without specifying ALLOW WRITE ACCESS, or alter the table using LOCKSIZE ROW. Reissue the command without specifying automatic commitcount, or rebind the import packages (bind files db2uimtb.bnd and db2uimpm.bnd) without using the INSERT BUF option. Do not attempt to use this command option against an incompatible server. Do not attempt to use this command option against an incompatible server.
SQL27971N	The target table has changed since the start of the import utility.	This message can be returned for several reasons. For example, this message could be returned if application dropped the target table and created a new table with the same name while an online import was running. The utility stops processing.	If desired, rerun the operation.
SQL27972N	A range of rows from the input file, starting at `first-failed-row` and ending at `last-failed-row`, was not inserted into the table. SQLCODE = `sqlcode`.	The atomic compound database operation failed to insert a sequence of rows of data read from the input file. One or more of the fields in the input file is not compatible with the database field where the field is being inserted. Processing continues with the next row of input data.	Examine the input file and the database contents. If desired, modify the database or modify the input file and rerun the operation.
SQL27980W	The utility encountered attached or detached data partitions in the target table or the source table.	Some of the data partitions are in the attached or detached state. The utility treats these data partitions as invisible. Any input source records belonging to those data partitions will be rejected by the import utility or the load utility. The rows rejected by the load utility can be recovered from the exception table, if one was specified. The export utility will not process any data that might exist in those data partitions.	No action is required.
SQL27981W	The utility could not verify presence of attached or detached data partitions in the target table or the source table.	Some of the data partitions might be in the attached or detached state, but the utility was unable to confirm this. The utility treats these data partitions as invisible. Any input source records belonging to those data partitions will be rejected by the import utility or the load utility. The rows rejected by the load utility can be recovered from the exception table, if one was specified. The export utility will not process any data that might exist in those data partitions.	No action is required.
SQL27982N	Vendor Load API (sqluvtld) is no longer supported.	Vendor Load API (sqluvtld) is no longer supported. DB2 Load utility is the only supported bulk loader. DB2 Load utility can be executed via db2Load API.	Do not use the sqluvtld API or any applications that invoke it.
SQL27983N	The LOAD utility is unable to rebuild the index.	The LOAD target table has detached data partitions and has dependent materialized query tables or dependent staging tables that have not been incrementally refreshed with respect to the detached data partition. This condition prevents the LOAD utility running in insert mode or restart mode from rebuilding a unique index.	Do not specify indexing mode REBUILD with LOAD insert until the dependent materialized query tables or dependent staging tables are refreshed. Use a different LOAD indexing mode, or execute the SET INTEGRITY statement with the IMMEDIATE CHECKED option to maintain the dependent materialized query tables or dependent staging tables with respect to the detached data partition. If a LOAD restart cannot incrementally maintain indexes, the previously failed LOAD operation must be terminated before dependent materialized query tables or dependent staging tables can be refreshed.
SQL27984W	The export command completed successfully. However, some information that would be required to recreate one or more tables has not been saved to the output file. The file will not be able to be used by the IMPORT command to create or replace tables. Reason code: `reason-code`.	You can export data from a database to a file by using the export utility. You can then import the data from that file to recreate those tables by using the import utility. This message is returned when the export utility is unable to export all of the information for one or more tables, which means that the output file that the export utility created would not be able to be used by the import utility to create or recreate the tables. The reason code indicates the type of information that was not exported: 1 Index information has not been saved because the index column names contain hexadecimal values of 0x2B or 0x2D. 2 XML column definitions have not been saved. 3 Multidimensional clustered table (MDC) key definitions have not been saved. 4 Table partitioning key definitions have not been saved. 5 Index names have been truncated due to code page conversion. 6 Information about protected tables has not been saved. 7 Action strings other than 'SELECT * FROM <TABLE-NAME>' have not been saved. 8 Column names specified with the METHOD N parameter were not used because the METHOD N parameter is not supported when hierarchical data is being exported. 9 A column name that was too long for the Integration Exchange Format (IXF) format has been truncated. 10 A user-defined type name that was too long for the IXF format has been truncated. 11 Typed table information has been truncated due to codepage conversion. 12 The name of a schema that is associated with a user-defined type was too long for the IXF format. The schema name has been truncated. 13 Decimal floating-point column definitions have not been saved. 14 Hidden columns information has not been saved. 15 Information about indexes with random ordering was not saved. 16 Table column orientation in column-organized tables has not been saved. 17 Information about expression-based indexes 18 Indexes created with the BUSINESS_TIME WITHOUT OVERLAPS clause have not been saved. 19 Information about columns where STRINGUNITS has been specified as CODEUNITS32 has not been saved. 20 BINARY or VARBINARY column definitions have not been saved. 21 Information that the table was created as a random distribution table was not saved. 22 Information that the table was created with row modification tracking enabled was not saved.	For reason codes 1, 3, 4, 5, 7, 8, 9, 11, 14, 17, and 18: To force the import utility to create the tables despite the fact that some information is missing, specify the FORCECREATE parameter when you issue the IMPORT command with the CREATE parameter or the REPLACE_CREATE parameter. For reason codes 2, 6, 10, 12, 13, 15, 16, 19, 20, 21 and 22, perform the following steps: Use the db2look command to extract table information and create the table. Issue the IMPORT command with the INSERT or REPLACE parameter with the exported file. sqlcode: +27984 sqlstate: 5U059
SQL27985N	Autoloader executable (db2atld) is no longer supported.	Autoloader executable (db2atld) is no longer supported. The Load utility is the only supported bulk loader. The Load utility is executed via a db2Load API, LOAD CLP command, or SYSPROC.ADMIN_CMD stored procedure.	Do not use the db2atld executable.
SQL27986W	A column name has been truncated in the PC/IXF file during Export. This file will not be supported in Import using Method N.	Data has not been affected during Export but the file cannot be used in Import with Method N because some column information is missing.	If Method N will not be used in Import, then no action is necessary. If Method N will be used, then export using Method N again, but explicitly specify shorter column names. Even though the PC/IXF file will contain the shorter column names, this will not affect the import of the data into an existing table. Alternatively, rename the columns in the original table to be shorter and export the data again. sqlcode: +27986 sqlstate: 5U036
SQL27987N	This PC/IXF file is not supported in Import using Method N.	Data has not been affected during Export but the file cannot be used in Import using Method N since some column information is missing.	Import using another Method other than N. Alternatively, export using Method N again, but explicitly specify shorter column names. Even though the PC/IXF file will contain the shorter column names, this will not affect the import of the data into an existing table. Alternatively, rename the columns in the original table to be shorter and export the data again. sqlcode: -27987 sqlstate: 5U015
SQL27990W	During loading, at least one row was found to be on the wrong partition.	When loading a partitioned database using the load utility with LOAD_ONLY_VERIFY_PART mode, any rows in the input file that are found to be on the wrong partition will be discarded. If the "dumpfile" modifier is specified, the discarded rows will be saved to the dump file. This message will appear only once per partition per load job, even when there are multiple partition violations present.	If the discarded rows are saved to a dump file, they can be loaded to the correct partition by simply issuing another load command with the MODE option set to PARTITION_AND_LOAD.
SQL27991W	Too many partitioning agents specified in the load command.	Too many partitioning agents have been specified in the PARTITIONING_DBPARTNUMS partitioned database configuration option of the load command. The maximum number of partitioning agents is specified by the MAX_NUM_PART_AGENTS load option, which defaults to 25 if not specified.	Resubmit the command with the correct number of partitioning agents. Alternatively, the PARTITIONING_DBPARTNUMS option can be omitted and the load utility will automatically select an appropriate number of partitioning agents.
SQL27992N	The data file contains a valid partitioning map, but the load mode is not LOAD_ONLY.	Load has detected a valid partitioning map at the beginning of the file. The Load mode specified would cause the utility to treat this as user data, possibly causing undesired results.	If the reason the data file begins with a partitioning map header is that the data in the file has already been partitioned, then use LOAD_ONLY mode to load the file. In this case it will also be necessary to use the OUTPUT_DBPARTNUMS option to specify the single partition to which the data should be loaded. If the partitioning map detected by load at the beginning of the file is actually user data, then use the IGNOREHEADER modifier to disable the partition map detection and load the entire data file.
SQL27993W	The STATISTICS USE PROFILE option of the Load utility was specified, however, a statistics profile does not exist.	The statistics profile does not exist in the catalog table SYSIBM.SYSTABLES. The statistics profile must be created before the load is executed. The load utility continues processing.	To create a statistics profile, use the SET PROFILE or SET PROFILE ONLY options of the RUNSTATS utility. Refer to the RUNSTATS documentation for a detailed description of the utility options.
SQL27994W	The length of a special register default column is smaller than the target column length. Load may truncate the values corresponding to this column (`column-num`).	The clause SESSION_USER, CURRENT_USER, SYSTEM_USER, or CURRENT_SCHEMA has been specified for column `column-num`, but this column was either defined with a length that is less than 128 bytes (SESSION_USER only) or the column-value inserted into this column may exceed the target length after codepage conversion. Load may truncate the column-value.	If your system standards would not allow a user ID (SESSION_USER) to exceed the length of the column, then this warning may be ignored. To prevent this warning from occurring, the length of the column must be at least 128 bytes. If codepage conversion resulted in the growth of this register default column, increase the length of the column to accommodate the growth.
SQL27999N	The requested IMPORT operation into a remote target (nickname) cannot be performed. Reason code = `reason-code`.	The target of the requested IMPORT operation resides in a remote database and is referenced locally by a nickname. The options specified for the IMPORT command do not meet the constraints required to allow the operation. The operation was rejected. The explanation corresponding to the reason code is: 1 The federated wrapper which manages the operations on the nickname is non-relational. Only nicknames managed by relational wrappers are supported. The ODBC wrapper is also not supported. 2 The DATALINK SPECIFICATION clause was specified, but is not supported. 3 One of the following unsupported filetype modifiers was specified: indexixf or indexschema. 4 The dldelfiletype modifier, which is unsupported, was specified. 5 One of the following unsupported filetype modifiers was specified: nodefaults or usedefaults. 6 The no_type_idfiletype modifier, which is unsupported, was specified. 7 One of the following unsupported filetype modifiers was specified: generatedignore, generatedmissing, identityignore, identitymissing, periodignore, periodmissing, transactioidignore, or transactionidmissing. 8 The COMMITCOUNT clause was not specified or was specified with the value AUTOMATIC. If the COMMITCOUNT clause is used, a non zero number must be specified. 9 The ALLOW WRITE ACCESS clause, which is required, was not specified. 10 An unsupported filetype was specified. Only files of type IXF, ASC, or DEL are supported. 11 An unsupported import action was specified. Only the INSERT INTO or INSERT_UPDATE INTO actions are supported. 12 Target table contains one of unsupported column types: LOB columns, XML columns, generated columns, datalink columns, or target table is a hierarchy table (typed table). 13 The lobsinfile filetype modifier, which is unsupported, was specified. 14 Either the remote target is not a table, or insufficient privileges prevent the utility from accessing the nickname. Import operation is only permitted when nickname is defined on a table, and PASSTHRU privilege is granted on the user. 15 The necessary stored procedures do not exist against the target database. Update the the database system catalog and cause built-in SQL routines and views to be recreated by calling the version of the db2updv* command that is appropriate for the recently installed fix pack. 16 The target table is a random distribution table using the random by generation method, which is unsupported.	Correct the options specified and retry the IMPORT command.
SQL29006N	A Java exception `exception-string` was encountered.	Java exception `exception-string` was thrown.	If the problem persists contact your technical service representative.
SQL29007N	Unable to communicate with the Query Controller.	The Query Controller may not be running or the communication has timed out.	Request that the database administrator start the Query Controller.
SQL29008N	Error encountered during job sequence number generation.	An error was encountered during job sequence number generation.	If the problem persists contact your technical service representative.
SQL29009N	The query has been rejected. Reason code `reason-code`.	The query has been rejected. The reason codes are as follows: DB2 does not allow the query to generate result set, or the query contains host variables, parameter markers, special registers, created temporary tables, declared temporary tables, session variables, IDENTITY_VAL_LOCAL function, NEXT VALUE expression, and/or PREVIOUS VALUE expression. Therefore the query cannot be put on hold or run in the background, as the state might not be valid at the time the query is actually executed. The query would update a DB2 table, therefore it cannot be put on hold or run in background, as the state might no longer be valid at the time the query is actually executed. The query cannot be queued because it contains nested routines. The query cannot be put on hold or run in the background because it contains nested routines. DB2 does not allow this query to be queued. This may occur when the query contains array inserts. DB2 does not allow a query to be queued when the concentrator is turned on. DB2 does not allow a query to be queued when the REOPT ALWAYS option is enabled for the query.	Contact the database administrator to examine the reason code and increase the appropriate cost threshold accordingly.
SQL29010N	The query submission has been cancelled.	The user has cancelled the query submission. No query was submitted.
SQL29011I	Query `query-ID` will be run in the background.	The user has chosen to run the query in the background.
SQL29013I	Query `query-ID` has been held.	The query has been put in held state by Query Patroller.	Contact the database administrator to have the query released.
SQL29014N	The value specified for DB2 registry variable `registry-variable` is invalid.	The value specified for `registry-variable` is invalid because of the following restrictions by `registry-variable`: DQP_NTIER The value must be one of OFF, RUN[:timeout], or CHECK[:timeout]. DQP_LAST_RESULT_DEST The length must not exceed 32 characters. DQP_TRACEFILE The length must not exceed 256 characters.	Correct the value of the DB2 registry variable `registry-variable` with the db2set command and resubmit the query.
SQL29015N	Error encountered during job cancellation. Reason code = `reason-code`.	An error was encountered while trying to cancel a job. The reason code maps to an SQL or DB2 message.	Examine the reason code, correct the error, and retry the action again.
SQL29017N	Query `query-id` has been cancelled.	The user has cancelled the query.
SQL29020N	An internal error has occurred. Error = `error`.	An error has occurred during internal processing.	Contact IBM Support and provide the db2diag log file and the qpdiag.log file.
SQL29021N	User `user-ID` is suspended.	The user `user-ID` is suspended from submitting a query to the database.	Contact the database administrator to have the user's submitter profile reactivated.