Each message has a message identifier that consists of a prefix (DB2) and a message number. Messages are listed in numeric sequence based on the message number. These messages are generated by the command line processor to alert you when a warning or error condition occurs. Messages are displayed directly on the screen interface. The command line processor returns DB2 and SQL messages.
For more information about SQL messages, see "SQL Messages".
| DB20000r | The "<command>" command completed successfully. |
Explanation: No errors were encountered during the execution of this command.
User Response: No action required.
| DB21001E | The option "<option-letter>" specified after the 'db2' command or in the DB2OPTIONS variable is incorrect. |
Explanation: The option specified is not supported. The supported options are:
Option Description ------ ------------------------------ -a Display SQLCA -c Auto-commit -e Display SQLCODE/SQLSTATE -f Read from input file -l Log commands in history file -n Remove new line character -o Display output -p Display interactive prompt -r Save output report to file -s Stop execution on cmd error -t Set stmt termination character -v Echo current command -w Display FETCH/SELECT warnings -x Suppress printing of column headings -z Save all output to file
The command cannot be processed.
User Response: Resubmit the command with a valid option.
| DB21002E | The parameter for option "<option-letter>" specified after the 'db2' command or in the DB2OPTIONS variable is missing or incorrect. |
Explanation: The following lists the options with parameters:
Option Description ------ -------------------------- -ec Display SQLCODE -es Display SQLSTATE -f<filename> Read from input file <filename> -l<filename> Log commands in history file <filename> -r<filename> Save output report to file <filename> -td<x> Set termination char. to 'x' -z<filename> Save all output to file <filename>
User Response: Resubmit the command with the valid option and parameter.
| DB21003E | The value "<value>" in "<environment-variable>" is not valid. |
Explanation: The value for DB2BQTRY must be between 0 and 4294967295. The value for DB2BQTIME, DB2RQTIME or DB2IQTIME must be between 1 and 4294967295.
User Response: Set the environment variable with the correct value and resubmit the command.
| DB21004E | You cannot specify both an input file and a command when invoking the command line processor. |
Explanation: You cannot specify both the -f option and a command line command when invoking the command line processor.
User Response: Correct the error and issue the command again.
| DB21005E | An error occurred while accessing the file "<filename>". |
Explanation: The following could have caused the error:
User Response: Correct the error and try again.
| DB21006E | The input command is too long. The maximum length is "<length>". |
Explanation: The input command cannot exceed the length specified.
User Response: Correct the error and resubmit the command.
| DB21007E | End of file reached while reading the command. |
Explanation: The last command was not executed because end of file was reached. Terminate the last command with a ';' (or your defined termination character) if the -t option was used. Remove the '\' from the last line in the command if the +t option was used.
User Response: Correct the error and resubmit the command.
| DB21008E | Commands can only be entered from the command line processor interactive mode or file input mode. |
Explanation: The user attempted to enter a command line processor command from the DOS prompt.
User Response: Use command line processor interactive mode or file input mode.
| DB21010I | Help given for "<help-command-phrase>". |
Explanation: This message only appears in the history file specified with the -l option.
User Response: No action required.
| DB21011I | In a partitioned database server environment, only the table spaces on the current node are listed. |
Explanation: Only the table spaces on the current node are visible to the LIST TABLESPACES command.
User Response: To list the table spaces on another node, you must issue the LIST TABLESPACES command on that node.
| DB21015E | The command line processor back-end process request queue or input queue was not created within the timeout period. |
Explanation: Either the values for the DB2BQTRY and DB2BQTIME environment variables need to be increased or the command line processor back-end program "db2bp" cannot be started. The "db2bp" program must reside in the correct database manager install path and users must have execute permission on the file.
User Response: Correct the error and resubmit the command.
| DB21016E | The command line processor encountered a system error while sending the command to the back-end process. |
Explanation: One of the following could have happened:
User Response: Resubmit the command. If the error occurs again, get help from your system administrator.
| DB21017E | The command line processor encountered a system error with the front-end process output queue. Reason code = <reason code>. |
Explanation: A system error occurred while creating or reading from the front-end process output queue.
If the reason code is -2499, the command line processor output queue conflicts with an existing queue.
User Response: Resubmit the command. If the error occurs again, record the message number and reason code, and get help from your system administrator.
| DB21018E | A system error occurred. The command line processor could not continue processing. |
Explanation: One of the following caused the system error:
User Response: Retry the command. If the problem persists, record the DB2 message number. If the trace was active, save the trace information and contact your technical support with the following information:
| DB21019E | An error occurred while accessing the directory "<directory>". |
Explanation: The following could have caused the error:
User Response: Correct the error and resubmit the command.
| DB21020E | Unable to create the default message file "<file>". |
Explanation: To properly process this command, CLP needs a file where the messages issued during processing are saved before they are displayed on the console. It attempted to create such a file in a directory normally used for that purpose (such as /tmp on UNIX platforms or ...\TMP on OS/2), but the attempt failed because the directory does not exist.
User Response: Correct the error and resubmit the command.
| DB21021E | No Administration Server instance is defined. The command failed. |
Explanation: You issued a command that needs to use an Administration Server instance, but no such instance is defined.
User Response: Define an Administration Server instance and resubmit the command.
| DB21022E | Unable to switch to Administration Server instance "<instance-name>". |
Explanation: You issued a command that needs to use an Administration Server instance. Command line processor tried to switch to Administration Server instance "<instance-name>" but failed. The possible reasons may be:
User Response: Check that a valid Administration Server instance is set up before using this command. Also, you may need to issue the DETACH, or CONNECT RESET, or TERMINATE command before trying your request again.
| DB21023E | The command is not valid when executed from Administration Server. |
Explanation: You issued one of the following commands: GET DBM CONFIGURATION, RESET DBM CONFIGURATION, or UPDATE DBM CONFIGURATION, but these commands cannot be executed from Administration Server.
User Response: Issue one of the following commands that are valid on Administration Server: GET ADMIN CONFIGURATION, RESET ADMIN CONFIGURATION, or UPDATE ADMIN CONFIGURATION.
| DB21024I | This command is asynchronous and may not be effective immediately. |
Explanation: This message is displayed after a FORCE command with the ASYNC clause.
User Response: No action required.
| DB21025I | 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. |
Explanation: Changes to the database manager configuration parameters become effective only after they are loaded into memory. This typically occurs after a DB2START on a server and after the application restarts on a client.
User Response: For the new database manager configuration parameters to become effective, do one or more of the following:
| DB21026I | For most configuration parameters, all applications must disconnect from this database before the changes become effective. |
Explanation: The database configuration command has been successfully processed. However, except for some configuration parameters such as MINCOMMIT, the active database configuration cannot be changed until all applications have disconnected from the database. After the applications disconnect from the database, the first connection to the database will cause the changes to become effective.
User Response: Ensure that all applications disconnect from the database and issue a db2 connect to command. Also, you may want to rebind your packages after the new configuration parameters take effect so that the new values will be used during the bind.
| DB21027E | Isolation level may not be changed while connected to a database. |
Explanation: The user attempted to change the isolation level while connected to a database. The command is ignored.
User Response: If a change in isolation level is necessary, disconnect from the current database, then set the isolation level and re-connect to the database.
| DB21028E | The cursor "<cursor-name>" has not been declared. |
Explanation: The specified cursor needs to be declared before issuing an OPEN, FETCH, or CLOSE SQL statement.
User Response: Declare the cursor and resubmit the command.
| DB21029E | The cursor "<cursor-name>" has already been declared and opened. |
Explanation: The user attempted to declare a cursor that is open.
User Response: Close the cursor and resubmit the open command.
| DB21030E | The cursor "<cursor-name>" has not been opened. |
Explanation: The specified cursor needs to be opened.
User Response: Open the cursor and resubmit the command.
| DB21031E | The SQL statement using the cursor "<cursor-name>" ("<internal-cursor>") returned: |
Explanation: This message shows the internal cursor name for the user defined cursor. Some SQL error messages may show the internal cursor name. This message is displayed before the SQL message.
User Response: Correct the SQL error and resubmit the command.
| DB21032E | You have already declared the maximum number of cursors. |
Explanation: Command line processor supports 100 cursors declared with the WITH HOLD attribute and 100 cursors declared without the WITH HOLD attribute.
User Response: Re-declare one of the existing cursors and resubmit the command.
| DB21033E | The command is not valid for databases that reside on DRDA hosts. |
Explanation: The following commands are not supported for databases that reside on DRDA host servers:
User Response: Do not issue the command for this database.
| DB21034E | The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: |
Explanation: This message is displayed before the SQL error message. The error may be caused by a syntax error in a non-SQL command.
User Response: Correct the error and resubmit the command.
| DB21035E | The maximum number of items in the "<list-name>" list has been exceeded. The maximum number is "<number>". |
Explanation: The number of items in the list cannot exceed the maximum specified. This error may be caused by an invalid range specification.
User Response: Correct the error and resubmit the command.
| DB21036E | The "<command>" command failed. |
User Response: Retry the command with the trace active. If the problem persists, save the trace information and contact your technical support with the following information:
| DB21037W | No data sources found. |
User Response: There were no ODBC data sources found of the type (USER or SYSTEM) that you specified. Retry the command by specifying the other type (SYSTEM or USER).
| DB21040E | "<number>" is not a valid in-doubt transaction number. |
Explanation: "<number>" is not one of the listed in-doubt transaction numbers.
User Response: Select one of the listed transaction numbers and resubmit the command.
| DB21041W | <number> indoubt transaction(s) not shown. |
Explanation: Command line processor could not display all the in-doubt transactions. The number of transactions not displayed is "<number>".
User Response: Finish processing the current list of indoubt transactions in order to reduce the total number of indoubt transactions in the system. Next, reissue the list indoubt transactions command.
| DB21042E | You must specify a transaction number. |
Explanation: A transaction number must be specified with the commit (c), rollback (r), or forget (f) in-doubt transaction subcommands.
User Response: Reissue the command with the appropriate transaction number.
| DB21043E | "<subcommand>" is not a valid request. |
Explanation: The in-doubt transaction subcommand specified is not valid. Valid subcommands are:
Subcommand Description
---------- -----------------------------
c <number> Heuristically commit the
in-doubt transaction <number>.
r <number> Heuristically rollback the
in-doubt transaction <number>.
f <number> Heuristically forget the
in-doubt transaction <number>.
l <number> List all in-doubt transactions
or the in-doubt transaction
<number>.
q Exit LIST INDOUBT TRANSACTION
prompting.
NOTE: The "f <number>" command is not available in DB2 Extended Enterprise Edition.
User Response: Correct the error and resubmit the command.
| DB21044E | Cannot COMMIT transaction number "<number>". |
Explanation: The transaction must be in a prepared state (i) when you issue the commit (c) subcommand.
User Response: Issue another command.
| DB21045E | Cannot ROLLBACK transaction number "<number>". |
Explanation: The transaction must be in a prepared (i) or idle (e) state. when you issue the rollback (r) subcommand.
User Response: Issue another command.
| DB21046E | Cannot FORGET transaction number "<number>". |
Explanation: The transaction must be in a heuristically committed (c) or heuristically rolled-back (r) state when you issue the forget (f) command.
User Response: Issue another command.
| DB21050E | "<state>" is not a valid SQLSTATE. |
Explanation: The sqlstate specified is not valid or could not be found. Valid states are numerical and two or five digits in length.
User Response: Resubmit the command using a different state.
| DB21051E | The command is not supported for this environment. |
Explanation: The command requested is currently not supported by the command line processor in the environment being used.
User Response: Resubmit the command on a different platform or within a different environment.
| DB21052I | "<command>" has been submitted for execution. |
Explanation: The command line processor is attempting to execute the indicated command. It will be unable to determine whether the command has completed successfully.
User Response: If the command appears unsuccessful, submit it from outside the command line processor.
| DB21053W | Automatic escalation will occur when you connect to a database that does not support <isolation-level>. |
Explanation: Isolation levels are database dependent. Some, like NC, are only supported by specific databases. If you select an isolation level that is not supported by the database you are connecting to, it will automatically escalate to a supported level.
User Response: Connect to a database that supports the isolation level you have selected, or select a different isolation level.
| DB21054E | The command line processor encountered a system error with the <command> command. Reason code = <reason code>. |
Explanation: The command line processor was unable to get enough memory to process your command. A system error occurred while processing it.
Reason
code Description Syntax
---- -------------- -------------------
1 Data file LOAD FROM
file/pipe/dev...
2 Lob data LOBS FROM
lob-path...
3 Directory USING directory...
4 Source FROM dir/dev...
5 Target TO dir/dev...
6 Tablespace TABLESPACE
tblspace-name...
7 Tblspace-def MANAGED BY...
8 Container data USING (PATH...,
PATH...)
or
USING (
{FILE|DEVICE}...,
{FILE|DEVICE}...)
9 Log path log-directory ...,
log-directory ...
10 Node list node-number ...,
node-number ...
User Response: Correct the error and resubmit the command.
| DB21055W | Command not valid for type 2 connections. |
Explanation: The information returned by the GET CONNECTION STATE command does not apply to type 2 connections.
User Response: Issue QUERY CLIENT to verify CONNECT = 1.
| DB21056W | Directory changes may not be effective until the directory cache is refreshed. |
Explanation: If directory caching (DBM CFG dir_cache) is enabled, database, node, and DCS directory files are cached in memory. Directory changes may not become effective until the directory cache is refreshed. Refer to the dir_cache configuration parameter in the ADMIN guide for a description on directory caching.
User Response: To refresh CLP's directory cache, issue a db2 TERMINATE. To refresh the directory information for another application, stop and restart that application. To refresh the directory information for the database, stop (db2stop) and restart (db2start) the database.
| DB21057E | Invalid tape device specified. |
Explanation: The tape device passed to the operating system was not accepted. On Windows NT it must be of the form "\\.\TAPEx" where x represents the drive number (0 is the first).
User Response: Reissue the command specifying a valid tape device.
| DB21058E | Invalid tape position specified. |
Explanation: The tape mark position specified is not valid. On Windows NT the first tape position to which a backup is record is 1. Subsequent backup images begin at tape mark 2 and so on.
User Response: Reissue the command specifying a valid tape position.
| DB21059E | Invalid tape blocksize specified. |
Explanation: The tape mark blocksize specified is not in the range supported by the tape device. In addition, for backup/restore to work it must also be a factor of or multiple of 4096.
User Response: Reissue the command specifying a valid tape size.
| DB21060E | General tape failure. |
Explanation: An unexpected return code was returned from the tape operation.
User Response: Resubmit the command. If the error occurs again, get help from your system administrator.
| DB21061E | Command line environment not initialized. |
Explanation: You have tried to invoke the command line processor from a command window that was not started by db2cmd.exe.
User Response: Issue DB2CMD to start a command window that has the command line processor environment initialized.
| DB21080E | No previous RESTORE DATABASE command with REDIRECT option was issued for this database alias, or the information about that command is lost. |
Explanation: You have tried to run the RESTORE DATABASE command with the CONTINUE or ABORT option. However, either you didn't previously issue a RESTORE DATABASE command with the REDIRECT option, or you did issue such a command but for a different database alias than the one specified on the failing command. Another possible cause for this message could be that the information about a correctly issued previous RESTORE DATABASE ... REDIRECT command was lost. This can happen if the CLP back-end process terminates abnormally, or if you issue the TERMINATE command.
User Response: Restart the whole redirected restore process by issuing the RESTORE DATABASE ... REDIRECT command and SET TABLESPACE CONTAINERS commands again. Then issue the RESTORE DATABASE ... CONTINUE command.
| DB21081E | No sections were found in the db2cli.ini file. |
Explanation: You have tried to list CLI parameters in the db2cli.ini file by using the GET CLI CONFIGURATION command, but the file is empty. There are no sections in that file.
User Response: To update the db2cli.ini file, use the UPDATE CLI CONFIGURATION command.
| DB21082E | You don't have enough authority to run the UPDATE CLI CONFIGURATION command. |
Explanation: You need to have SYSADM authority to run this command.
User Response: Obtain the necessary authority from your database administrator, then issue the command again.
| DB21083E | Section <section> not found. |
Explanation: Section <section> was not found in the db2cli.ini file.
User Response: Specify an existing section and issue the command again.
| DB21084E | NEW and CONFIRM passwords not the same. |
Explanation: You were using the ATTACH or CONNECT command and specified that you wanted to change your password. The new password needs to be specified twice, by using the NEW and CONFIRM clauses, or by responding to the prompts. The two passwords you specified as your new password were different.
User Response: Specify the same password twice.
| DB21085I | Instance "<instance_name>" uses DB2 code release "<rel_ver_mod>" with level identifier "<level_id>" and informational tokens "<build_id1>", "<build_id2>" and "<build_id3>". |
Explanation: This message is the output of the db2level command and provides detailed information about the code level of a given DB2 instance. The information may be request by DB2 service personnel to aid in resolving problems.
User Response: Record all displayed information to provide to DB2 service personnel.
The db2level executable should not be copied from one machine to another. Only DB2 installation and service maintenance programs should manipulate this file.
The db2level executable will not display information about private test fixes that the customer has received from DB2 service personnel and installed on top of an officially supported service level.
| DB21100E | Stored procedure "<procedure-name>" exists in multiple schemas. |
Explanation: The specified procedure name was found in more than one schema.
User Response: Re-issue the CALL command with a fully qualified procedure name ("<schema>"."<procedure-name>").
| DB21101E | Too few command line parameters specified for the stored procedure. |
Explanation: More command line parameters are required for the stored procedure definition.
User Response: Verify the command line parameters and re-issue the command.
| DB21102E | Error occurred while allocating the environment handle. sqlrc = "<rc>" |
Explanation: DB2 failed to allocated the enviroment handle.
User Response: Retry the command. If the problem persists, contact your technical support representative.
| DB21103W | Too many input parameters specified (expected "<quantity>"). |
Explanation: There are too many command line parameters specified for the stored procedure. The parameters after the expected quantity are ignored.
User Response: Verify the stored procedure parameters.
| DB21600N | The "<command>" command did not complete successfully. |
Explanation: Errors were encountered during the execution of this command.
User Response: Contact your technical service representative. Information in the db2diag.log file will enable your service representative to determine the cause of the failure.
| DB29320W | Output has been truncated. |
Explanation: The full query result cannot be fetched as supplied. Command line processor output can be a maximum of MAX_STATETMENT_SIZE characters. However the output of any particular column cannot exceed MAX_COLUMN_SIZE characters in length.
User Response: The CLP query can be rewritten to fetch a shorter string. Use of another interface to DB2 can also help in overcoming the CLP's limitation.
| DB29501E | DB2 has detected an inconsistent environment. Please investigate the following : "<error>" |
Explanation: An error in the operating environment has been detected.
User Response: This error may arise due to an inconsistent DB2 or operating system environment. Attempt to correct the problem identified in the error message and re-issue the command.
| DB29502E | An incompatible Java Runtime Environment has been detected. Please verify that the required level of the Java Runtime Environment has been installed. The Java application may be launched using the Java runtime installed with DB2. |
Explanation: The installed Java runtime is not supported by the DB2 Java application.
User Response: The installed DB2 Java runtime will be used to launch the DB2 Java application. Other Java applications using the installed Java runtime should be terminated prior to executing the DB2 Java application to ensure correct behaviour.
| DB29503E | Connections to multiple databases is not supported. |
Explanation: You cannot connect to more than one database.
User Response: Connect to only one database.
| DB29504E | Connections to multiple users is not supported. |
Explanation: You cannot connect to more than one user.
User Response: Connect to only one user.
| DB29526E | You cannot drop this table; it does not exist. Please select a job that has results, and try again, or select a recurring job that is scheduled and try again. |
Explanation: A request was made to drop a result table for a job which did not have an associated result table.
User Response: Select a job that has a results or select a recurring job that is scheduled and try again.
| DB29543E | Resource DLL rqsres.dll not found. |
Explanation: Resource DLL rqsres.dll could not be loaded succesfully.
User Response: During initialization of DB2 Query Patroller Recurring Query Scheduler the resource DLL rqsres.dll could not be loaded as it was either damaged or deleted. Please reinstall DB2 Query Patroller QueryEnabler.
| DB29544E | Resource DLL qeres.dll not found. |
Explanation: Resource DLL qeres.dll could not be loaded succesfully.
User Response: During initialization of DB2 Query Patroller QueryEnabler the resource DLL qeres.dll could not be loaded as it was either damaged or deleted. Please reinstall DB2 Query Patroller QueryEnabler.
| DB29545E | Name invalid: Query Name can only be 20 characters or less in length. Please change the name accordingly and retry. |
Explanation: A name for a query was specified which was longer than 20 characters.
User Response: Specify a query name that has at most 20 characters.
| DB29546E | Name invalid: Query Name can only contain alphanumeric characters and spaces...( "a..z", "A..Z", "0..9" ). Please change the name accordingly and retry. |
Explanation: A name for a query was specified which contained non-alphanumeric charcters.
User Response: Specify a query name composed of only alphanumeric charcaters.
| DB29608E | Script Load Failed. |
Explanation: Script files required by DB2 Query Patroller Tracker could not be found.
User Response: Please reinstall DB2 Query Patroller Tracker.
| DB29610E | Could not load the ODBC Driver Manager. |
Explanation: The ODBC driver dll ODBC32.DLL could not be loaded.
User Response: The ODBC driver dll ODBC32.DLL could not be loaded as it was damaged or destroyed. Please reinstall ODBC.
| DB29611E | Three login attempts failed! Exiting Tracker! |
Explanation: DB2 Query Patroller Tracker requires to connect to the ODBC Data Source specified on the login dialog. The userid, password combination specified on the login dialog was not authorized to connect to the specified database.
User Response: Please relaunch DB2 Query Patroller Tracker and provide a valid userid password combination for the ODBC Data source specified on the login dialog.
| DB29613E | Resource DLL tkres.dll not found. |
Explanation: DB2 Query Patroller Tracker requires the resource dll tkres.dll for successful operation. The dll could not be loaded.
User Response: During initialization of DB2 Query Patroller Tracker the resource DLL tkres.dll could not be loaded as it was either damaged or deleted. Please reinstall DB2 Query Patroller Tracker.
| DB29700E | The application programming interface "<program>" did not complete successfully for object "<name>" with reason code "<name>". Try again or contact your local support. |
Explanation: An application programming interface call did not complete.
User Response: Try the operation again or contact your system administrator.
| DB29701E | Class "<class name>" not found. Please check you classpath. |
Explanation: The "<class_name>" cannot be located in the specified classpath.
User Response: Verify the classpath is correct. If you are using QueryAdmin.bat or QueryMonitor.bat please check the classpath setting in the batch file.
| DB29702E | User "<userID>" does not have administrative authority to use QueryAdministrator. |
Explanation: User "<userID>" does not have Administrative authority defined in the DB2 Query Patroller User Profile table.
User Response: Have a DB2 Query Patroller administrator ensure that "<userID>" has the authorization necessary to perform the operation.
| DB29703E | User "<userID>" is not defined in User Profile. |
Explanation: User "<userID>" is not defined in the DB2 Query Patroller user profile table.
User Response: Have a DB2 Query Patroller administrator ensure that "<userID>" is defined in the User Profile table.
| DB29704E | User iwm cannot be removed. |
Explanation: User iwm is the mandatory userid needed for DB2 Query Patroller so it cannot be removed.
User Response:
| DB29705W | Invalid value entered for "<column-name>". Valid ranges are from "<minimum_value>" to "<maximum_value>". |
Explanation: The value entered for "<column-name>" is invalid.
User Response: Reenter a value that is specified with the range.
| DB29706E | Job Queue "<queue_id>" cannot be removed. There are one or more incomplete jobs in this queue. |
Explanation: This job queue "<queue_id>" cannot be removed since there are still jobs running on the queue.
User Response: Wait until all jobs that are on the queue are completed before deleting it.
| DB29707E | Result Destination "<destination-name>" is already defined. |
Explanation: The "<destination-name>" specified is already defined. "<destination-name>" must be unique.
User Response: Specify an unique "<destination-name>".
| DB29708E | User "<userID>" is already defined. |
Explanation: The "<userID>" specified is already defined. "<userID>" must be unique.
User Response: Specify an unique "<userID>".
| DB29709E | Group "<group_id>" is already defined. |
Explanation: The "<group_id>" specified is already defined. "<group_id>" must be unique.
User Response: Specify an unique "<group_id>".
| DB29710E | Job queue "<queue_id>" is already defined. |
Explanation: The "<queue_id>" specified is already defined. "<queue_id>" must be unique.
User Response: Specify an unique "<queue_id>".
| DB29720E | User "<userID>" does not have the necessary authority to use QueryMonitor. |
Explanation: User "<userID>" is defined in the DB2 Query Patroller User Profile table but has no authority.
User Response: Have a DB2 Query Patroller administrator ensure that "<userID>" has the authorization necessary to perform the operation.
| DB29721E | Error encountered when submitting a new job. Reason code : "<reason-code>". |
Explanation: An error was encountered when submitting a new query. Check the reason code returned.
Reason codes map to a valid SQL message. Check the help for the corresponding SQL message.
User Response: Correct the problem and retry this operation.
| DB29722E | Error encountered during job sequence number generation. Reason code : "<reason-code>". Job will not be submitted. |
Explanation: An error was encountered during job sequence number generation. Check the reason code returned.
Reason codes map to a valid SQL message. Check the help for the corresponding SQL message.
User Response: Correct the problem and retry this operation.
| DB29723E | Error encountered during purging of a result set for job "<job-id>". Reason code : "<reason-code>". |
Explanation: An error was encountered when purging the specified result set. Check the reason code returned.
Reason codes map to a valid SQL message. Check the help for the corresponding SQL message.
User Response: Correct the problem and retry this operation. The table may have been dropped manually outside of the system environment.
| DB29724E | Error encountered when attempting to change status for job "<job-id>". Reason code : "<reason-code>". |
Explanation: An error was encountered when changing the status for the specified job. Check the reason code returned.
Reason codes map to a valid SQL message. Check the help for the corresponding SQL message.
User Response: Correct the problem and retry this operation.
| DB29725E | Error encountered during resubmit of job "<job-id>" with SQL statement "<SQL_stmt>". Reason code : "<reason-code>". |
Explanation: An error was encountered when resubmiiting the specified job. Check the reason code returned.
Reason codes map to a valid SQL message. Check the help for the corresponding SQL message.
User Response: Correct the problem and retry this operation.
| DB29726E | Request completed successfully. |
Explanation: The request was successful.
User Response:
| DB29727N | DB2 Query Patroller server is not installed. |
Explanation: DB2 Query Patroller server is not installed on the DB2 server.
User Response: Install the DB2 Query Patroller server.
| DB29801E | Invalid command line parameters. |
Explanation: The parameter for command line specified is missing or incorrect.
User Response: Correct the problem and retry this operation.
| DB29802E | Completed with Error. |
Explanation: The program terminiated due to an error. Please see the associated error messages for the reason.
User Response: Correct the problem and retry this operation.
| DB29803E | DB2 registry variable "<registry-variable>" is not set or is invalid. |
Explanation: The required DB2 registry variable "<registry-variable>" is not set or has been set with an invalid format.
User Response: If the DB2 registry variable is DQP_RUNTIME then set DQP_RUNTIME to the fully qualified path where DB2 Query Patroller is installed.
If the DB2 registry variable is DQP_SERVER then set DQP_SERVER to [host]:[port], where [host] represents the IP address of the machine where DB2 Query Patroller server is installed, and [port] represents the TCP port used by DB2 Query Patroller server.
If the DB2 registry variable is DQP_SERVER or DQP_NET then set DQP_SERVER or DQP_NET to [host]:[port], where [host] represents the IP address of the machine where DB2 Query Patroller server is installed, and [port] represents the TCP port used by DB2 Query Patroller server.
For any other DB2 registry variable, please refer to the DB2 Query Patroller documentation.
| DB29804E | A memory allocation error has occurred. |
Explanation: During processing, there was not enough memory to continue processing.
User Response: Ensure that your system has sufficient real and virtual memory.
| DB29805E | User ID "<userID>" is undefined. |
Explanation: "<userID>" is not defined on the operating system.
User Response: Create an operating system user account or use a correct user ID.
| DB29806E | Cannot change effective user ID to "<userID>". Operating system error : "<OS-error>". |
Explanation:
User Response:
| DB29807E | An I/O error (reason = "<code>") occurred while reading the file "<file>". |
Explanation: The read operation against "<file>" failed.
User Response: Determine if the I/O error can be corrected and resubmit the command.
| DB29808E | An I/O error (reason = "<code>") occurred while writing the file "<file>". |
Explanation: The write operation against "<file>" failed.
User Response: Determine if the I/O error can be corrected and resubmit the command.
| DB29809E | An I/O error (reason = "<code>") occurred during a read operation. |
Explanation: Incomplete data was read during an I/O operation.
User Response: Determine if the I/O error can be corrected and resubmit the command.
| DB29810E | An I/O error (reason = "<code>") occurred during a write operation. |
Explanation: An I/O error occurred during a write operation. The data may be incomplete.
User Response: Determine if the I/O error can be corrected and resubmit the command.
| DB29811E | File "<file-name>" could not be opened (reason = "<code>"). |
Explanation: Error encountered while trying to open file "<file-name>".
User Response: Ensure that the "<file-name>" is correct and exists in the file system, and that the file permissions are correct.
| DB29812E | Error occurred while terminating process "<process-ID>". |
Explanation: Error encountered while trying to kill process "<process-ID>".
User Response: Ensure the terminating process has sufficient authority and the process exists.
| DB29813E | There is not enough memory available to process the command. |
Explanation: Not enough random access memory (RAM) is available to process the command.
User Response: Check if the system has sufficient paging space. Free up some memory by stopping unused applications.
| DB29814E | The request failed because an operating system process, thread, or swap space limit was reached. |
Explanation: An operating system process, thread, or swap space limit was reached.
User Response: Increase the limit which was reached (or have your system administrator increase it).
| DB29815E | Execution of "<program-name>" failed (reason = "<reason-code>"). |
Explanation: Error encountered while executing "<program-name>".
User Response: Determine if the problem can be fixed and retry the operation.
| DB29816I | Completed successfully. |
Explanation: The request was successful.
User Response: No action necessary.
| DB29820E | Unknown job type "<type>" for job "<job-id>". |
Explanation: The iwm_nodemgr process encountered a job with an unrecognized type.
User Response: Resubmit the query. If problem presists contact an IBM Service representative.
| DB29821E | Another node manager is running. |
Explanation: Only one iwm_nodemgr process can run on each node.
User Response:
| DB29822E | Node manager could not recover jobs. |
Explanation: The iwm_nodemgr failed to recover jobs that were running when it last failed.
User Response:
| DB29823W | sysinfo statistics are not being collected. |
Explanation: CPU utilization cannot be collected for this node because sysinfo facility is disabled.
User Response:
| DB29824E | Job "<job-id>" not found. |
Explanation: The job "<job-id>" was not found in the job table.
User Response:
| DB29825I | Completion message for job "<job-id>" saved to file "<file-name>". |
Explanation: The agent process has lost contact with the Server component, and was unable to notify it of job completion. When the Node Manager process successfully restarts on this node, the Server component receveies notification of the job's completion.
User Response:
| DB29826N | Error encountered when executing SQL statement "<SQL-statement>". Error : "<sqlcode>". |
Explanation: The "<SQL-statement>" failed.
User Response: Correct the "<SQL-statement>" and resubmit the job.
| DB29827I | Too many columns selected. |
Explanation: The job's SQL statement selected too many columns.
User Response: Correct the SQL statement and resubmit the job.
| DB29828E | Cannot create result table "<result-table>". |
Explanation: The "<result-table>" could not be created.
User Response: Make sure system has sufficient free disk space and the table does not aleady exist.
| DB29829E | SQLDA type "<type>" is not supported for column "<column-name>". |
Explanation: DB2 Query Patroller does not recognize the database column type.
User Response:
| DB29830E | Job "<job-id>" cannot be updated. |
Explanation: The request to update this job cannot be performed because the request change is not valid for the current state of the job.
User Response:
| DB29831W | Job "<job-id>" (process ID "<process-ID>") is no longer running. |
Explanation: The job terminated without notifying the Server component.
User Response:
| DB29832E | Node "<node-name>" not found. |
Explanation: The RequestHandler Node Manager process is not active on the requested node.
User Response:
| DB29835W | Node "<node-name>" has not responded for 5 minutes, attempting recovery. |
Explanation: The iwm_nodemgr process has not updated the node information for five minutes. The iwm_sched process assumes that the node has crashed and will recover jobs scheduled for the node.
User Response:
| DB29836E | Scheduler could not recover jobs for node "<node-name>". |
Explanation: An error occurred during node recovery.
User Response:
| DB29837W | No active nodes available to assign jobs. |
Explanation: There are no nodes with an active node manager process.
User Response:
| DB29838I | "<number>" result tables over "<number>" days old have been purged. |
Explanation: Purging of result tables has been activated through the DB2 Query Patroller system parameters. This message indicates how many result tables have been purged.
User Response: No action necessary.
| DB29839I | "<number>" jobs over "<number>" days old have been purged. |
Explanation: Purging of DB2 Query Patroller jobs has been activated through the DB2 Query Patroller system parameters. This message indicates how many jobs have been purged.
User Response:
| DB29840I | PREPARE SQL statement "<SQL-statement>" failed for user "<userID>" with SQLCODE "<sqlcode>" |
Explanation: The SQL statement could not be PREPARED.
User Response:
| DB29841E | SQL statement "<SQL-statement>" failed. Exit code "<code>". |
Explanation:
User Response:
| DB29842E | Error "<sqlcode>" encountered during execution of the following SQL statement: "<SQL-statement>". |
Explanation: The SQL statement failed.
User Response: Correct the SQL statement and resubmit request.
| DB29843E | Failed to connect to database "<database-alias>" with user ID "<userID>". Error code: "<sqlcode>". |
Explanation: The SQL CONNECT statement failed.
User Response:
| DB29844E | User "<userID>" is not defined in the User Profile table. |
Explanation: There is no row in the User Profile table for the user.
User Response: Correct the user ID or have an Administrator add a user to the User Profile table.
| DB29845E | Error opening socket. Error : "<error-code>". |
Explanation: The socket specified cannot be open.
User Response: Determine if the problem can be corrected by examining the "<error-code>".
| DB29846E | Error closing socket. Error : "<error-code>". |
Explanation: The socket specified cannot be closed.
User Response: Determine if the problem can be corrected by examining the "<error-code>".
| DB29847E | Error occurred while sending or receiving data. Error : "<error-code>". |
Explanation: Error happened while sending / receiving data.
User Response: Determine if the problem can be corrected by examining the "<error-code>".
| DB29848E | Error encountered on TCP/IP protocol support. TCP/IP function "<function>". Socket was "<socket>". Error : "<error-code>". |
Explanation: The TCP/IP function failed.
User Response: Determine if the problem can be corrected by examining the "<error-code>".
| DB29849E | The specified listener port "<listener_port>" is not valid. |
Explanation: The specified listener port is not valid.
User Response: Verify the DB2 Query Patroller configuration parameters are correctly set.
| DB29850E | The specified connect port "<connector_port>" is not valid. |
Explanation: The specified connect port is not valid.
User Response: Verify the DB2 Query Patroller configuration parameters are correctly set.
| DB29851E | Invalid internet address "<internet_addr>". |
Explanation: The specified internet address is not valid.
User Response: Verify the DB2 Query Patroller configuration parameters are correctly set.
| DB29852E | TCP/IP could not find host name "<host_name>" in the local Hosts file. |
Explanation: The "<host_name>" specified cannot not be resolved.
User Response: Verify the DB2 Query Patroller configuration parameters are correctly set.
| DB29853E | Service "<service_name>" is not defined in the TCP/IP services file. |
Explanation: The "<service_name>" specified cannot not be resolved in the TCP/IP service file.
User Response: Verify the DB2 Query Patroller configuration parameters are correctly set.
| DB29854E | Invalid network identifier "<network_string>". |
Explanation: The network identifier must be in the form host-id:port-id where host-id represents either a resolvalbe host name or the dotted internet address and port-id represents either a resolvable service name or a port number.
User Response: Verify the DB2 Query Patroller configuration parameters are correctly set.
| DB29855E | DB2 Query Patroller server is not available. |
Explanation: The Server component cannot be contacted.
User Response: Verify the DB2 Query Patroller configuration parameters are correctly set.
| DB29856E | A severe internal processing error has occurred. Error "<error-code>". |
Explanation: An internal DB2 Query Patroller failure occurred.
User Response: Please contact an IBM Service representative.
| DB29857E | "<name>" value is missing. |
Explanation: An internal DB2 Query Patroller failure occurred.
User Response: Please contact an IBM Service representative.
| DB29858E | "<name>" value is invalid. |
Explanation: An internal DB2 Query Patroller failure occurred.
User Response: Please contact an IBM Service representative.
| DB29859E | Destination "<name>" is no longer valid. |
Explanation: An destination name is no longer active.
User Response:
| DB29860E | Expected response message not received. |
Explanation: An internal DB2 Query Patroller failure occurred.
User Response: Please contact an IBM Service representative.
| DB29861E | Connection to iwm_net lost. |
Explanation: The iwm_net program is no longer active.
User Response: Restart the Server component or agent on this node.
| DB29862E | Not connected. |
Explanation: An internal DB2 Query Patroller failure occurred.
User Response: Please contact an IBM Service representative.
| DB29863E | Message not understood. |
Explanation: An internal DB2 Query Patroller failure occurred.
User Response: Please contact an IBM Service representative.
| DB29864E | iwm_local database access is not available. |
Explanation: The iwm_local program failed or was not started successdully.
User Response: Restart the DB2 Query Patroller and all agents.
| DB29865E | iwm_remote database access is not available. |
Explanation: The iwm_remote program failed or was not started successdully.
User Response: Restart the Server component.
| DB29866E | iwm_local database access failed. |
Explanation: The iwm_local program failed or was not started successdully.
User Response: Please contact an IBM Service representative.
| DB29867E | iwm_remote database access failed. |
Explanation: The iwm_remote program failed or was not started successdully.
User Response: Please contact an IBM Service representative.
| DB29868E | Invalid ticket. |
Explanation: An internal DB2 Query Patroller failure occurred.
User Response: Please contact an IBM Service representative.
| DB29869E | Logon has expired. |
Explanation: Your logon to DB2 Query Patroller has expired.
User Response: Log on again.
| DB29870E | Not authorized. |
Explanation: You are not authorized to perform the requested funcion.
User Response: Contact your System Administrator to obtain the necessary authorization.
| DB29871N | Mail for job "<job-id>" "<job-status>" could not be sent to "<email-address>". Reason : "<reason-code>". |
Explanation: Error encountered during sending of user notification for job "<job-id>".
User Response:
| DB29991E | DB2 Query Patroller Server is not correctly installedy. |
Explanation: DB2 Query Patroller Server was not installed correctly.
User Response: Please reinstall DB2 Query Patroller server.
| DB210016E | Cannot initialize TCP/IP (reason = "<reason-code>"). |
Explanation: Cannot initialize TCP/IP. The TCP/IP return code is invalid.
User Response: Check the WINSOCK version supported by the WINSOCK DLL. DB2 Query Patroller supports the following versions: 0.0, 1.0, 1.1.
| DB210017E | Unsupported WINSOCK.DLL level. |
Explanation: This version of the file WINSOCK.DLL is not supported by DB2 Query Patroller.
User Response: Ensure that the WINSOCK version is supported by DB2 Query Patroller. Query Patroller supports the following versions: 0.0, 1.0, 1.1 Note that some WINSOCK.DLL report a version number of 0.0
| DB210018E | Could not register signal handler for process ID "<process-ID>", reason code = "<reason-code>". |
Explanation: Failed to create the signal handler for the event object.
User Response:
| DB210019E | Could not wait for signal handler semaphore for process ID "<process-ID>", reason code = "<reason-code>". |
Explanation: Failed to wait for the signal handler for the event object.
User Response:
| DB210020E | Could not create a thread for the signal handler for process ID "<process-ID>", reason code = "<reason-code>". |
Explanation: Failed to create a thread object for the signal handler for the current process.
User Response:
| DB210021E | Could not post a signal semaphore for process ID "<process-ID>", reason code = "<reason-code>". |
Explanation: Failed to set the state of the event to be signaled for the current process.
User Response:
| DB210022E | Could not logon, reason code = "<reason-code>". |
Explanation: The user ID and password probably are not correct, or the user has not been granted the required privileges.
User Response: Check the user ID and password, or ask the system administrator to grant the appropriate privileges for your user ID.
| DB210023E | Could not switch to a different user ID, reason code = "<reason-code>". |
Explanation: DB2 Query Patroller was unable to switch to a different user ID, because the target user ID was already logged on.
User Response: None.
| DB210024E | Loading failed with reason code = "<reason-code>". |
Explanation: Failed to load data from files, tapes, or named pipes into a DB2 table.
User Response: Ensure that the data sources exist.
| DB210025E | Loading failed after reading "<rows>", reason code = "<reason-code>". |
Explanation: Failed to load data after reading "<rows>", reason code = "<reason-code>".
User Response:
| DB210026E | Loading failed when reading "<line>" from "<file-name>". |
Explanation: Error encountered when reading "<line>" from "<file-name>".
User Response: Ensure that the message file "<file-name>" exists.
| DB210027E | The "<user-profile>" or the "<userID>" is already defined. |
Explanation: The user ID "<userID>" already exists for DB2 Query Patroller.
User Response: Define a unique user ID for DB2 Query Patroller.
| DB210028E | Destination "<destination-name>" is already defined. |
Explanation: The result destination already exists for DB2 Query Patroller.
User Response: Define a unique result destination name for DB2 Query Patroller.
| DB210030E | MAPI is not initialized, reason code = "<reason-code>". |
Explanation: Failed to initialize the Messaging Application Programming Interface (MAPI).
User Response: Ensure that the file MAPI32.dll exists.
| DB210031E | MAPI is not available on this machine. |
Explanation: Messaging Application Programming Interface (MAPI) is not installed on this machine.
User Response: Ensure that MAPI is correctly installed and initialized. Ensure that the file MAPI32.dll exists.
| DB210032E | Could not invoke iwm_cmd program. |
Explanation: Failed to invoke iwm_cmd process.
User Response: Check if the DB2 Query Patroller server is running.
| DB210033E | The mail "<mail-subject>" could not be sent to "<mail-address>", reason code = "<reason-code>". |
Explanation: The mail "<mail-subject>" could not be sent to "<mail-address>".
User Response: Ensure that Messaging Application Programming Interface (MAPI) is correctly installed and initialized. Ensure that the file MAPI32.dll exists.
| DB210036N | Result table "<result-table>" does not exist. |
Explanation: Result table "<result-table>" does not exist in the database.
User Response: The selected result table "<result-table>" does not exist, please select another one.
| DB210037I | DQPSTART processing was successful. |
Explanation: The command to start DB2 Query Patroller completed successfully.
| DB210038I | DQPSTOP processing was successful. |
Explanation: The command to stop DB2 Query Patroller completed successfully.
| DB210039E | DQPSTART or DQPSTOP command is already in progress. |
Explanation: The DB2 Query Patroller is currently processing a start or a stop command.
User Response: There is another instance of DB2 Query Patroller start or stop command being processed.
User Response: Wait until the currently processing command completes. If there are no other processes starting or stopping the DB2 Query Patroller, you can remove 'dqpstst.lck' file from the 'ctrl' directory in the instance path and retry the command.
| DB210040W | DB2 Query Patroller service did not start properly. |
Explanation: One or more processes may not have started successfully.
User Response: Check the 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210041E | Request for DB2 Query Patroller license failed. |
Explanation: DB2 Query Patroller could not be started without a valid license file.
| DB210044E | Unexpected command parameter "<commnad-token>" was encountered. |
Explanation: The issued command is invalid.
User Response: Check the documentation for valid syntax.
| DB210045E | DB2 Query Patroller encountered a system error which terminated processing. |
Explanation: An error occured which terminated processing.
User Response: Check the 'syserr.log' and 'db2diag.log' for more diagnostic information.
| DB210046E | File seek operation on "<filename>" has failed (reason = "<reason-code>"). |
Explanation: During processing, the file may have become corrupted or otherwise un operational.
User Response: Retry the command and if the problem persists, check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210047E | Change of access permissions on file "<filename>" has failed (reason = "<reason-code>"). |
Explanation: The file access permissions could not be set. This condition may be due to unavailability of the file or other system condition that prevented the adjustment of file permissions.
User Response: Retry the command and if the problem persists, check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210048E | Invalid file format of file "<filename>" at line "<line-number>". |
Explanation: Processing could not continue due to the unexpected tokens or an invalid file format.
User Response: Check the documentation for a proper setup.
| DB210049E | Could not retrieve instance path (reason = "<reason-code>"). |
Explanation: The instance path could not be retrieved.
User Response: Ensure the DB2 is setup properly before issuing the command again. If the problem persists, check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210050E | Could not retrieve the install path (reason = "<reason-code>"). |
Explanation: The DB2 installation path could not be retrieved.
User Response: Ensure the DB2 is setup properly before issuing the command again. If the problem persists, check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210051E | Could not retrieve instance configuration (reason = "<reason-code>"). |
Explanation: The instance database manager configuration could not be retrieved.
User Response: Ensure DB2 is setup properly before issuing the command again. If the problem persists, check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210052E | Could not get local host or computer name (reason = "<reason-code>"). |
Explanation: The computer name (NT) or host name (UNIX) could not be retrieved.
User Response: Contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210053E | Could not resolve host name (reason = "<reason-code>"). |
Explanation: The host name could not be resolved.
User Response: Contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210054E | DQPSTART processing failed. |
Explanation: DB2 Query Patroller could not be started.
User Response: Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210055E | System error. Registering service control handler failed. |
Explanation: System error occurred which terminated processing.
User Response: Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210056E | System error. Check for service start-pending status failed. |
Explanation: System error occurred which terminated processing.
User Response: Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210057E | System error. Initialization of service security descriptor failed. |
Explanation: System error occurred which terminated processing.
User Response: Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210058E | System error. Create event failed. |
Explanation: System error occurred which terminated processing. Check 'syserr.log' and 'db2diag.log' for more diagnostics.
User Response: Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210059E | Processing of configuration file "<filename>" failed (reason = "<reason-code>"). |
Explanation: The configuration file could not be processed because it is in an invalid format, has unexpected tokens, or is otherwise corrupted.
User Response: Check the documentation for proper formatting of the file. If the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210060E | Attempt to start service "<service-name>" failed (reason = "<reason-code>"). |
Explanation: The service could not be started because the service is not registered, already started, or cannot accept control messages at this time.
User Response: Retry the command and if the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210061E | Attempt to stop service "<service-name>" failed (reason = "<reason-code>"). |
Explanation: The service could not be stopped because the service is not registered, not running, or cannot accept control messages at this time.
User Response: Retry the command and if the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210062E | System error. Common initialization routines failed (reason = "<reason-code>"). |
Explanation: Environment could not be initialized.
User Response: Retry the command and if the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210064E | System error. Message queue failed (reason = "<reason-code>"). |
Explanation: System error occurred which terminated processing.
User Response: Retry the command and if the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210065E | DB2 Query Patroller node is not activated. |
Explanation: The selected node is not setup for processing.
User Response: Ensure that the specified node is defined in 'dqpnodes.cfg' and retry the command.
| DB210066E | Node start or stop processing results could not be retrieved from file "<filename>" (reason = "<reason-code>"). |
Explanation: The contents of the communication file could not be retrieved. The file does not exist or could not be opened.
User Response: Ensure that the specified file is accessible and retry the command. If the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210067E | Node start or stop processing has reached timeout value. |
Explanation: The DB2 Query Patroller start or stop command has reached a timeout value while waiting for results from the processing node(s). The result files contents could not be obtained because they were not created or not accessible.
User Response: Ensure that 'dqpnodes.cfg' is setup correctly and all host names and IP addresses and computer names are resolvable. See the documentation for proper setup. Check for proper setup of DQP_SERVER and DQP_NET variables and their corresponding entries in the 'services' file. On EEE check for proper setup of the 'rah' utility. Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210068E | Communication error has been encountered while waiting for node(s) to complete processing (reason = "<reason-code>"). |
Explanation: The DB2 Query Patroller start or stop command could not continue due to invalid result file generated by one of the processing nodes. The result file could not be interpreted correctly.
User Response: Retry the command and if the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210069E | Process "<process-name>" has failed. |
Explanation: Process failed.
User Response: Retry the command and if the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210070E | Execution of process "<process-name>" has failed (reason = "<reason-code>"). |
Explanation: Process could not be started.
User Response: Retry the command and if the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210071E | Execution of process "<process-name>" was interrupted (reason = "<reason-code>"). |
Explanation: Running process was interrupted.
User Response: Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210072E | An external program "<program-name>" could not be located (reason = "<reason-code>"). |
Explanation: Could not find a specified executable.
User Response: Check your installation or contact your system administrator before retrying the command. Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210073E | An external program "<program-name>" could not be invoked due to insufficient resources (reason = "<reason-code>"). |
Explanation: Could not allocate resources to launch the process.
User Response: Retry the command and if the problem persists, contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210074E | An external program "<program-name>" could not be invoked due to insufficient authority (reason = "<reason-code>"). |
Explanation: The user invoking the program does not have sufficient authority to do so.
User Response: Contact your system administrator or check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210075E | DQPSTART processing has completed. "<number-of>" node(s) were started successfully, "<number-of>" node(s) were already started, "<number-of>" node(s) have failed. |
Explanation: DB2 Query Patroller start manager completed processing however at least one node reported a warning or an error while processing the node start command.
User Response: Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210076E | DQPSTOP processing has completed. "<number-of>" node(s) were stopped successfully, "<number-of>" node(s) were already stopped, "<number-of>" node(s) have failed. |
Explanation: DB2 Query Patroller stop manager completed processing however at least one node reported a warning or an error while processing the node stop command.
User Response: Check 'syserr.log' and 'db2diag.log' for more diagnostics.
| DB210085E | The operation was aborted because it would violate configuration consistency constraint. SQLSTATE="<state-code>". |
Explanation: SQLSTATE=88000,88001: Operation failed because it would violate one of the following constraints on the IWM003_JOB_QUEUE table:
MAX(MAX_JOBS) <= IWM003_DATA_SOURCE.MAX_JOBS AND MAX(MAX_COST) <= IWM003_DATA_SOURCE.COST_THRESHOLD
SQLSTATE=88002,88003,88004: Operation failed because it would violate one of the following constraints on the IWM003_DATA_SOURCE table:
MAX_JOBS >= MAX(IWM003_JOB_QUEUE.MAX_JOBS) AND MAX(MAX_JOBS) <= IWM003_SYS_PARMS.QRY_THRESHOLD AND COST_THRESHOLD >= MAX(IWM003_JOB_QUEUE.MAX_COST) AND MAX(COST_THRESHOLD) <= IWM003_SYS_PARMS.COST_THRESHOLD
SQLSTATE=88005: Operation failed because it would violate one of the following constraints on the IWM003_SYS_PARMS table:
QRY_THRESHOLD >= MAX(IWM003_DATA_SOURCE.MAX_JOBS) AND COST_THRESHOLD >= MAX(IWM003_DATA_SOURCE.COST_THRESHOLD)
SQLSTATE=88006,88007: Table IWM003_SYS_PARMS can have at most one row. This single row may be deleted if the table IWM003_DATA_SOURCE is empty.
SQLSTATE=88008: A user or a group profile with matching name and possibly different case already exists.
User Response: Please revise your configuration and specify a valid value for the field.
| DB210101E | Read queue operation failed while waiting for a response from "<process>". Return code = "<return-code>". Queue handle = "<queue-handle>". Timeout = "<timeout-value>". |
Explanation: A read queue operation failed while waiting for a response from "<process>". This error can occur if the timeout period is too short or if the queue handle is invalid.
User Response: Set DQP_CHILD_WAIT DB2 profile variable to a value greater than the "<timeout-value>" and try again. If the problem persists, contact your system administrator to remove "<queue-handle>" from your system.
| DB210102E | The DB2 instance was not found. Reason code = "<reason-code>". |
Explanation: The DB2 instance was not found. The DB2INSTANCE environment variable is not set to a valid DB2 instance.
User Response: Please ensure that DB2INSTANCE environment variable or DB2 profile variable DB2INSTDEF is set to a valid DB2 instance.
| DB210103E | Error deleting message queue. Reason code = "<reason-code>". Queue handle = "<queue-handle>". |
Explanation: An error occurred deleting message queue "<queue-handle>".
User Response: Please contact your system administrator to remove "<queue-handle>" from your system.
| DB210104E | Error initializing message queue. Reason code = "<reason-code>". Queue name = "<queue-name>". |
Explanation: An error occurred initializing message queue "<queue-name>". This error can occur if a queue with that name already exists.
User Response: Please contact your system administrator to remove "<queue-name>" from your system.
| DB210105E | Error writing to the primary message queue. Reason code = "<reason-code>". Queue handle = "<queue-handle>". Request type = "<request-type>". Action type = "<action-type>". Set type = "<group-type>". Trace = "<trace-flag>". |
Explanation: An error occurred writing to the primary message queue "<queue-handle>". This error can occur if the queue handle is invalid.
User Response: Please contact your system administrator to remove "<queue-handle>" from your system.
| DB210106E | Error reading from the primary message queue. Reason code = "<reason-code>". Queue handle = "<queue-handle>". Timeout = "<timeout-value>" seconds. |
Explanation: An error occurred reading from the primary message queue "<queue-handle>". This error can occur if the queue handle is invalid.
User Response: Please contact your system administrator to remove "<queue-handle>" from your system.
| DB210107E | Error opening message queue. Reason code = "<reason-code>". Queue name = "<queue-name>". |
Explanation: An error occurred opening message queue "<queue-name>". This error can occur if a queue with the name "<queue-name>" already exists and this process does not have the authority to open it.
User Response: Please contact your system administrator to remove "<queue-name>" from your system.
| DB210108E | Error acquiring lock on file "<file-name>". Reason code = "<reason-code>". |
Explanation: Error acquiring a file lock on file "<file-name>". This error can occur if this process does not have the authority to lock file "<file-name>"" in the /tmp directory.
User Response: If the file "<file-name>"" exists in the /tmp directory, please contact your system administrator to remove it from your system.
| DB210109E | Error sending message on queue. Reason code = "<reason-code>". Queue handle = "<queue-handle>". Message = "<message>". |
Explanation: An error occurred sending message "<message>" on queue "<queue-handle>". This error can occur if this process does not have authority to write to the queue.
User Response: Please contact your system administrator to remove "<queue-handle>" from your system.
| DB210110E | Error closing message queue. Reason code = "<reason-code>". Queue handle = "<queue-handle>". |
Explanation: An error occurred closing message queue "<queue-handle>". This error can occur if the process does not have the authority to close the queue.
User Response: Please contact your system administrator to remove "<queue-handle>" from your system.
| DB210111E | For the selected interval and frequency, no jobs can be scheduled between the chosen start date and time and the end date and time. |
Explanation: The selected interval and frequency does not allow any jobs to be scheduled between the chosen start date and time and the end date and time.
User Response: To enable job scheduling, perform one of the following options:
| DB210112E | The DB2 Query Patroller server process or processes "<server-process>" have stopped. The remaining DB2 Query Patroller server processes have also stopped. |
Explanation: If one or more DB2 Query Patroller server processes, such as iwm_logmon, iwm_net, iwm_server, iwm_remote, iwm_nodemgr, or iwm_sched have stopped, the other DB2 Query Patroller server processes also stop.
User Response: Check the syserr.log file to diagnose the cause of the stopped DB2 Query Patroller server processes. Restart the DB2 Query Patroller server.