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 Chapter 11. "SQL Messages" in this guide.
DB20000I 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 -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 -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.
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 "<user_id>" does not have administrative authority to use QueryAdministrator.
Explanation: User "<user_id>" does not have Administrative authority defined in the DB2 Query Patroller User Profile table.
User Response: Have a DB2 Query Patroller ensure that "<user_id>" has the authorization necessary to perform the operation.
DB29703E User "<user_id>" is not defined in User Profile.
Explanation: User "<user_id>" is not defined in the DB2 Query Patroller user profile table.
User Response: Have a DB2 Query Patroller ensure that "<user_id>" 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 "<user_id>" is already defined.
Explanation: The "<user_id>" specified is already defined. "<user_id>" must be unique.
User Response: Specify an unique "<user_id>".
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 "<user_id>" does not have the necessary authority to use QueryMonitor.
Explanation: User "<user_id>" is defined in the DB2 Query Patroller User Profile table but has no authority.
User Response: Have a DB2 Query Patroller ensure that "<user_id>" 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:
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 Environment variable "<environment_variable>" is not set.
Explanation: The required "<environment_variable>" is not set.
User Response: Set the "<environment_variable>" and retry the operation.
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 "<user_id>" is undefined.
Explanation: "<user_id>" is not defined on the operating system.
User Response: Create an operating system user account or use a correct user id.
DB29806E Cannot change to effective user id to "<user_id>". 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>". 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 "<user_id>" with SQLCODE "<sqlcode>"
Explanation: The SQL statement could not be PREPARED.
User Response:
DB29841E "<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 userid "<user_id>". Error code: "<sqlcode>".
Explanation: The SQL CONNECT failed.
User Response:
DB29844E User "<user_id>" 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 userid 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:
DB29988E The IWM_SERVER environment variable is not set!
Explanation: Environment variable IWM_SERVER was not set.
User Response: Set the environment variable IWM_SERVER to [host]:[port] where [host] refers to IP address of the machine where DB2 Query Patroller Server is installed and [port] refers to the TCP port that the DB2 Query Patroller Server can use for communication.
DB29990E The IWM_RUNTIME environment variable is not set!
Explanation: Environment variable IWM_RUNTIME was not set.
User Response: Set the environment variable IWM_RUNTIME to the fully qualified path where DB2 Query Patroller is installed.
DB29991E DB2 Query Patroller Server does not seem to be installed correctly!
Explanation: DB2 Query Patroller Server was not installed correctly!
User Response: Please reinstall DB2 Query Patroller Server.