This chapter provides information about the log file and the messages that display in DB2 Query Patroller.
| 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.
| 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\",\n\"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:
| 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 resumbit 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. /p>
| 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 = "<program_name>"). |
Explanation: Error encountered while executing "<program_name>".
User Response: Determine if the problem can be fixed and retry the operation.
| 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:
| DB29826E | Error encounterd when executing job "<job_id>" with SQL "<SQL_statement>". Error "<sqlcode>". |
Explanation: The "<SQL_statement>" failed for the job.
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: Check SQL statement for correctness.
| 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 satement 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 "<socker>". 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 cannt 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 cannt 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.
| 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.
Messages written to the log file display in the following format:
<date-time> <node> <program> <pid> <message-id> <source-line> <text>
where:
The log server file name is syserr.log. By default, DB2 Query Patroller creates this file in the $IWM_RUNTIME/log directory. However, if the user sets the $IWMLOG environment variable, DB2 Query Patroller creates the file in that directory.