Cause: The user called one of the Database System Monitor APIs and provided a null pointer instead of a required parameter.
The command can not be processed.
Action: The user should reissue the command with a valid parameter value.
Cause: An object type specified in the variable data area of the input data structure (sqlma) for Database System Monitor Snapshot API is not supported.
The command can not be processed.
Action: Reissue the command using a valid object type. Refer to the Embedded SQL Programming Guide and API Reference for further information about valid object types.
Cause: A required parameter is not specified in the input data structure (sqlma) of the Database System Monitor Snapshot or Estimate Buffer Size API.
The command cannot be processed.
Action: The user should reissue the command specifying a valid parameter value.
Cause: A null character is expected at the end of the character string parameter.
The command can not be processed.
Action: Add a null character at the end of the character string parameter and reissue the command.
Cause: The Database System Monitor Reset API was called for a specific database, but the database was not active.
The command completed successfully but no action was taken.
Action: Verify that the database alias is correct and the database has been started.
Cause: The Database System Monitor output buffer area is not large enough to accommodate the returned data. Likely causes are intense system activity when the call was made, or in the case of a Database Monitor API call within a user application, the user allocated a buffer too small to contain the returned data.
The command completed successfully and data collected prior to the buffer overflow is returned in the user's buffer.
Action: The user should reissue the command, or in the case of a Database Monitor API call within a user application, allocate a larger buffer or reduce the amount of information requested.
Cause: The database manager is out of working memory to process the Database System Monitor command.
The command can not be processed.
Action: Reduce the buffer size in the input parameter and reissue the command.
Cause: A Database System Monitor Snapshot or Estimate Buffer Size API call was issued specifying the same request for two or more database aliases in the sqlma input data structure, and they point to the same database.
Database System Monitor executes successfully, but returns only one copy of the information in the output buffer.
Action: No action is required. However, the user should verify that the database aliases specified on input are correct if information on different databases was expected.
Cause: A Database System Monitor API call was issued specifying the database alias of a remote database. Database System Monitor does not support monitoring of remote databases.
The command cannot be processed.
Action: The user should verify that the database alias specified on input is correct, and reissue the command with the correct database alias.
Cause: The user called one of the Database System Monitor APIs and specified an invalid value for the specified parameter.
The command can not be processed.
Action: The user should reissue the command with a valid parameter value.
Cause: None of the monitoring information requested by the users was available at the time the Database System Monitor API call was issued. This can occur when a requested database or application is inactive, or when a monitoring group such as the Table group is turned OFF, and Table information is requested.
Action: The command completed successfully, but no data is returned to the user.
The user should make sure that the databases or applications for which monitoring is desired are active at the time the Database System Monitor API is called, or that the desired monitoring groups are active.
Cause: The target path specified in the CREATE EVENT MONITOR statement is not a valid path name. The command could not be processed.
Action: Resubmit the statement with the correct event monitor target path.
sqlcode: -1612
sqlstate: 428A3
Cause: The option specified in the CREATE EVENT MONITOR statement is not valid. Possible causes include:
The command could not be processed.
Action: Resubmit the statement with the corrected event monitor options.
sqlcode: -1613
sqlstate: 428A4
Cause: An I/O error was detected when an event monitor was activated. <reason-code> is one of the following:
Action: Where possible, fix the problem described by the reason code, and resubmit the SET EVENT MONITOR statement.
sqlcode: -1614
sqlstate: 58030
Cause: An attempt was made to either activate an already active event monitor, or deactivate an already inactive event monitor. The SET EVENT MONITOR statement was ignored.
Action: No user response is required.
sqlcode: +1615
sqlstate: 01598
Cause: A maximum of 32 event monitors can be active simultaneously per database. This limit has already been reached. The specified event monitor cannot be activated.
Action: If possible, deactivate one of the active event monitors and resubmit the SET EVENT MONITOR statement.
sqlcode: -1616
sqlstate: 54030
Cause: The specified event monitor was created with a limit on the amount of data that would be allowed in the event monitor target directory. This limit has already been reached. The specified event monitor cannot be activated.
Action: If possible, delete some of the event monitor data files from the target directory, and resubmit the SET EVENT MONITOR statement.
sqlcode: -1617
sqlstate: 54031
Cause: The specified event monitor was created with the same target path as another event monitor. This other event monitor was activated at least once, and has left .evt and/or .ctl files in the target path. These files may be in use by application(s) that are reading the event information they contain.
Action: If the other event monitor is currently active, deactivate it. After ensuring no application(s) are using the files it created in the target path, remove the files Then resubmit the SET EVENT MONITOR statement.
Alternatively, recreate the required event monitor, specifying a different target path, and resubmit the SET EVENT MONITOR statement.
sqlcode: -1618
sqlstate: 51026
Cause: The specified event monitor is currently active, and therefore cannot be dropped.
Action: Deactivate the event monitor and resubmit the DROP EVENT MONITOR statement.
sqlcode: -1619
sqlstate: 55034
Cause: An event monitor cannot be activated until the transaction in which it was created has been committed.
Action: Commit the transaction in which the event monitor was created and then reissue the SET EVENT MONITOR statement.
sqlcode: -1621
sqlstate: 55033
Cause: The STATE value specified in the SET EVENT MONITOR STATE statement is not within the range of valid values, or the value is NULL as a result of an indicator variable.
Valid values for the Event Monitor State include:
The statement cannot be executed.
Action: Correct the event monitor state value and/or any indicator variable and reissue the statement.
sqlcode: -1622
sqlstate: 42815
Cause: The limit imposed on the number of objects that are permitted in the sqlma input structure has been exceeded.
Action: Reduce the number of objects in the sqlma parameter and try the call again.
Cause: The sqlma parameter contained references to databases that reside on different nodes.
Action: Modify the sqlma parameter so that all database objects reference the same node and then try the call again.
Possible types are as follows:
Cause: Conversion of data from the source code page to the target code page is not supported. This condition can occur under the following conditions:
This situation can occur when the monitor tries to convert data pertaining to a database whose code page is incompatible to that of the monitor application.
Action: Check your operating system documentation for a list of supported conversions and ensure that the appropriate ones are installed and accessible to the database manager.
If possible ensure that the database being monitored and the monitoring application are in the same codepage.
Possible types are as follows:
Cause: The monitor is unable to convert the data due to space constraints. The data is retained in its original form.
Action: If possible ensure that the database being monitored and the monitoring application are in the same codepage.
Cause: The user has attempted to call an API that is no longer supported in this version of the database manager.
Action: The function required may be supported by a different API call. Check in the API Reference and Embedded SQL Programming Guide to determine if the function is supported through a different API call.
Cause: Some new functionality is not supported against older DB2 server versions.
Action: Execute the request against a DB2 server where the latest DB2 server version has been installed, or upgrade the server to the latest DB2 server version.
Cause: Error occurred either opening, reading, writing, or closing a file.
Action: Check the db2diag.log for details. Also, check for disk full conditions, file permissions, and operating system errors.
Cause: A full path to a file where server information should be generated must be specified.
Action: Ensure that the profile path specified is correct and not null.
Cause: The instance path could not be returned.
Action: Check that the DB2INSTANCE path was specified correctly. Check that the complete path length specified is not approaching the maximum supported by the operating system.
Cause: A server system failure has occurred.
Action: Report the failure to your DB2 server administrator. More details of the failure can be found in the server's db2diag.log file.
Cause: DISCOVER = DISABLE is configured in the database manager configuration file.
Action: If DISCOVER functionality is required, change the discover type to KNOWN or SEARCH.
Cause: The search discovery request failed for one of the following reasons:
Check the db2diag.log for details.
Action:
DB2 Service can provide details about the error codes returned by the above functions and written to the db2diag.log.
Cause: The application program used an invalid input address list pointer. The address list points to nothing.
Action: Ensure that a valid input address list pointer is specified in the application program, and that it is not null.
Cause: The application program used an invalid input server address pointer. The server address points to nothing.
Action: Ensure that a valid input server address is specified in the application program, and that it is not null.
Cause: A KNOWN discovery request was issued against a DB2 server that is not a DB2 administration server. The communications information specified is not correct.
Action: Verify that DB2ADMINSERVER is set on the DB2 server instance you are accessing. This indicates that the server instance is a DB2 administration server. Retry the KNOWN discovery request with the correct communications information.