DBT6000-7999

DBT6000N

The utility is unable to update the global database configuration file because the file was created using a different DB2 version or is corrupt.

1. Ensure that the database product that you are using on the secondary system is at the same level as the one that you are using on the primary system.
2. If the file is corrupt, restore the original split mirror copy of the database if the copy is still available. If the configuration file is still corrupt after the restore operation, take a new split mirror copy of the database.
3. Rerun the utility.

DBT6001N

You can rename or relocate a database using the db2relocatedb command. You specify the details of the new configuration for the database by passing the name of a configuration file that contains configuration keyword-value pairs.

This message is returned when an attempt is made to change one or more storage paths of a database by calling the db2relocatedb command with a configuration file that includes the STORAGE_PATH keyword, and the database manager is unable to move the storage path or paths.

The reason code indicates the reason why the database manager was unable to move the storage path or paths:

1. One or both of the storage group control files, SQLSGF.1 or SQLSGF.2 was not successfully upgraded.
2. The old storage path that was specified with the STORAGE_PATH keyword in configuration file does not match any existing storage paths.

Respond to this error according to the reason code:

Reason code 1:

1. Validate that the storage control files, SQLSGF.1 and SQLSGF.2, are consistent and upgraded properly, using the db2dart tool with /TSF option.

Reason code 2:

1. Determine which storage paths exist using one of the following methods:
   • Refer to the db_storage_path monitor element
   • Call the ADMIN_GET_STORAGE_PATHS table function
2. Run the db2relocatedb command again, specifying a configuration file that contains only valid old storage paths with the STORAGE_PATH keyword.

DBT6100I

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

Command processing completed without any errors.

No further action is required.

DBT6101W

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

The db2ida command did not start all of the embedded processes of the in-database analytics provider on all database partitions. The in-database analytics functionality will be unavailable until all of the embedded processes of the in-database analytics provider are running on all database partitions.

Correct the problem on the failed database partitions and resubmit the command.

DBT6102W

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

The db2ida command did not stop all of the embedded processes of the in-database analytics provider on all database partitions. If you are planning to perform maintenance that involves the in-database analytics provider, the planned maintenance might not be successful because some of the related processes are still running.

Correct the problem on the failed database partitions and resubmit the command.

DBT6103N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

An invalid parameter was passed to the db2ida command.

Run the db2ida command again, specifying valid parameters.

DBT6104N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

This message is returned if an unsupported value is specified with the -provider parameter.

Run the db2ida command again, specifying a valid value for the -provider parameter.

DBT6105N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

In order for the db2ida command to successfully start the embedded processes of the in-database analytics provider, the given registry variable must be set.

1. Set the given option for the given registry variable.
2. Run the db2ida command again.

DBT6106N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

There were insufficient system resources for the database manager to run the db2ida command on the local or remote database partition.

1. Check the system workload status.
2. Release some system resources.
3. Run the db2ida command again.

DBT6107N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

A required executable to start the embedded process could not be located under the database manager instance directory.

1. Ensure that the database product is properly installed.
2. Ensure that the database manager instance has been created successfully.
3. Run the db2ida command again.

DBT6108N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

The embedded processes for an in-database analytics provider cannot be started if the database manager is not running on all database partitions.

1. Determine on which database partitions the database manager is not up and running.
2. Start the database manager on all database partitions using the db2start command.
3. Run the db2ida command again.

DBT6109N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

This message is returned when the db2ida command fails to receive a response from the embedded processes of the in-database analytics provider.

1. Increase the value of the start_stop_time database manager configuration parameter.
2. Run the db2ida command again.

DBT6110N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

A system error occurred. Some possible reasons for this error are:

• The physical host for the database partition cannot be reached because of a network problem.
• The physical host for the database partition has powered down.
• The remote command service is not installed or running on the host from which the command was issued.

1. Ensure that the hosts for the database manager instance are running.
2. Ensure that the remote command service is running on the host.
3. Run the db2ida command again.

DBT6111N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

This message is returned when the db2ida command did not have the required authorization to run necessary DB2 database-related utilities. The db2ida command runs with the same authorization as the user who executed the command.

Run the db2ida command again, as a user with the required authorization.

DBT6112N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

The library for the in-database analytics feature is part of the installation of the provider. Some possible reasons for this error are:

• The library for the embedded process could not be found in the library path.
• The library could not be loaded by the database manager.

1. Ensure that the library path for the in-database analytics library of the provider exists.
2. Run the db2ida command again.

DBT6113N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

The main entry function could not be found in the library, and the embedded process failed.

Respond to this error by performing the following troubleshooting steps:

• Resubmit the action.
• Reinstall the in-database analytics provider library.
• Contact technical support for the in-database analytics provider.

DBT6114N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

The database manager instance does not have enough shared memory to allocate for communication buffers between the database server and the embedded process. One possible reason for this error is that the DB2_FMP_COMM_HEAPSZ registry variable was set too low.

Respond to this error by performing the following troubleshooting steps:

1. Increase the value of the DB2_FMP_COMM_HEAPSZ registry variable.
2. Restart the database manager instance.
3. Run the db2ida command again.

DBT6115N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

The embedded process was still involved in an uncompleted transaction. The database manager could not stop the embedded process.

Respond to this error in one of the following ways:

• Wait until the transaction completes and then issue the db2ida command again.
• Force the embedded process to stop by issuing the db2ida command with the -stopforce parameter.

DBT6116W

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

Other activities to start or stop the embedded process were running concurrently in the database manager instance. Concurrent activities include the following:

• Forced termination of an unresponsive embedded process
• Automatic restart of a previously terminated embedded process
• Other running db2ida commands

1. Wait until other activities complete.
2. Run the db2ida command again.

DBT6117N

You can stop or restart embedded processes for an in-database analytics provider without stopping and restarting the database manager instance using the db2ida command.

A TCP/IP communication error occurred while the db2ida command was attempting to establish a connection with a database partition.

Complete the following troubleshooting steps:

• Ensure that the database partition has the proper authorization defined in the rhosts or host.equiv file.
• Ensure that the application is not using more than 500 + (1995 - 2 * total_number_of_dbpartitions) file descriptors simultaneously.
• Ensure that all environment variables are defined, and that the profile is written in Korn Shell script format.
• Ensure that all of the hosts that are defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
• Ensure that the DB2FCMCOMM registry variable is set correctly.

DBT7000I

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the db2caem utility has completed.

Review the files generated by the db2caem utility in the named output path.

DBT7001E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when a syntax error is made in the db2caem command.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, and then rerun the command with valid syntax.

DBT7002E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when invalid input data is specified.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, and then rerun the command with valid input.

DBT7003E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when no database is specified.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, and then rerun the command specifying a database with the -d parameter.

DBT7004E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You must specify either query statement options or event monitor options when you issue the command. This message is returned when no query statement options are specified and no event monitor options are specified.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, and then rerun the command specifying either query statement options or event monitor options.

DBT7005E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify a user id with the -u parameter and the password for that user ID with -p parameter.

You must specify both -u and -p or neither. This message is returned when only one of -u or -p is specified.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, then rerun the command specifying a user ID with the -u parameter and a password with the -p parameter.

DBT7006E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, and then rerun the command specifying all of the required parameters.

DBT7007E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify a SQL statement for which activity event monitor data should be collected using the -st parameter. You can specify a file that contains a SQL statement for which activity event monitor data should be collected using the -sf parameter. The -st parameter and the -sf parameter cannot both be specified. This message is returned when the -st parameter and the -sf parameter are both specified.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, and then rerun the command specifying either the -st parameter or the -sf parameter, not both.

DBT7008E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify either query statement options or event monitor options when you issue the command, but not both options. This message is returned when both query statement options and event monitor options are specified.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, and then rerun the command specifying either query statement options or event monitor options.

DBT7009E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the database name that is specified is longer than length limits imposed on DB2 database names.

Rerun the command specifying a valid database name.

DBT7010E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the user ID that is specified is longer than length limits imposed on user names by DB2 database.

Rerun the command specifying a valid user id.

DBT7011E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the password that is specified is longer than length limits imposed on passwords by DB2 database.

Rerun the command specifying a valid password.

DBT7012E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the SQL statement in the file specified with the -sf parameter is longer than SQL statement length limits. This message can also be returned when the terminating character is missing or invalid in the specified SQL statement.

Rerun the command specifying a valid SQL statement.

DBT7013E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify a file that contains a SQL statement for which activity event monitor data should be collected using the -sf parameter. You can specify the compilation environment information in a file using the -compenv parameter. This message is returned when the db2caem utility cannot access the file path for one of these specified files.

There are several reasons why the db2caem utility might not be able to access the specified file path:

• The specified file path does not exist.
• The db2caem utility runs with the same authority as the user who executes the db2aem command. This means that you must be able to access the file path specified with the -sf parameter and the -compenv parameter. This message can be returned when the user who executes the db2caem command does not have access to the specified file path.

Rerun the command specifying a file path that exists and that you can access.

DBT7014E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify a file that contains a SQL statement for which activity event monitor data should be collected using the -sf parameter. This message is returned when the db2caem utility cannot open the file specified with the -sf parameter.

There are several reasons why the db2caem utility might not be able to open the specified file:

• The specified file does not exist.
• The db2caem utility runs with the same authority as the user who executes the db2aem command. This means that you must be able to open the file specified with the -sf parameter. This message can be returned when the user who executes the db2caem command does not have authority to open the specified file.

Rerun the command specifying a file path that exists and that you can open.

DBT7015W

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the db2caem utility cannot access an internal, temporary file at run time. The db2caem utility can complete successfully despite this warning.

No user response is required.

DBT7016E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify a file that contains a SQL statement for which activity event monitor data should be collected using the -sf parameter. You can specify a file that contains compilation environment information using the -compenv parameter. This message is returned when the full name, including the path, of the file specified with the -sf parameter or the -compenv parameter is too long.

Rerun the command specifying a SQL file name that is a valid length.

DBT7017E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify a table space name for which activity event monitor data should be collected using the -tbspname parameter. This message is returned when the table space name specified with the -tbspname parameter is too long.

Rerun the command specifying a table space name that is a valid length.

DBT7018E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify an activity event monitor name for which activity event monitor data should be collected using the -actevm parameter. This message is returned when the activity event monitor name specified with the -actevm parameter is too long.

Rerun the command specifying an activity event monitor name that is a valid length.

DBT7019E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify an application ID for which activity event monitor data should be collected using the -appid parameter. This message is returned when the application ID specified with the -appid parameter is too long.

Rerun the command specifying an application ID that is a valid length.

DBT7020E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify the path in which the db2caem utility will generate output files using the -o parameter. This message is returned when the db2caem utility cannot access the path specified with the -o parameter.

There are several reasons why the db2caem utility might not be able to access the specified path:

• The specified path does not exist.
• The db2caem utility runs with the same authority as the user who executes the db2aem command. This means that you must be able to access the path specified with the -o parameter. This message can be returned when the user who executes the db2caem command does not have access to the specified output path.

Rerun the command specifying a output path that exists and that you can access.

DBT7021E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

An out-of-memory error is a system error that prevents the command from completing. This message is returned when the db2caem utility encounters an out-of-memory error while attempting to capture activity event monitor data.

1. Free memory that is being used by other processes.
2. Rerun the db2caem command.

DBT7022E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify the path in which the db2caem utility will generate output files using the -o parameter. The db2caem utility creates subdirectories in the output directory. This message is returned when the db2caem utility is unable to create subdirectories in the output directory.

1. Determine why db2caem is unable to create subdirectories in the output directory by reviewing diagnostic information in the db2diag log files or the db2caem.log file, if it was created.
2. Resolve the problem or problems that are preventing the db2caem utility from creating subdirectories in the output directory.
3. Execute the db2caem command again.

DBT7023E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify the path in which the db2caem utility will generate output files using the -o parameter. This message is returned when the name of the output path specified with the -o parameter is too long.

Rerun the command specifying a output path name that is a valid length.

DBT7024E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility performs a variety of database tasks to collect the activity event monitor data. This message is returned when the db2caem utility fails to perform one of these internal database tasks such as failing to determine the path for a specified file.

The db2caem utility cannot proceed.

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support

DBT7025E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility queries the specified table to collect information about the query statement that is specified with the -st parameter, that is contained in the file specified with the -sf parameter, or that is obtained from an existing event monitor specified with the -actevm parameter. The db2caem utility found unexpected rows that were returned by this query. Thus, an error condition might exist that you cannot resolve.

Rerun the db2caem command.

If the problem persists, perform the following steps:

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support

DBT7026E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility queries the specified table to collect information about the query statement that is specified with the -st parameter, that is contained in the file specified with the -sf parameter, or that is obtained from an existing event monitor specified with the -actevm parameter. The db2caem utility expects at least one row to be returned by this query. If no rows are returned by this query, then an error condition might exist that you cannot resolve.

This message can be returned when an invalid terminating character is used in the SQL file specified with the -sf parameter or when an invalid event monitor name is specified with -actevm parameter.

1. Determine what the internal error is, based on the return code.
2. Resolve the source of the internal error.
3. Execute the db2caem command again.

DBT7027E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify the path in which the db2caem utility will generate output files using the -o parameter. The db2caem utility creates subdirectories in the output directory. The db2caem utility generates names for these subdirectories using a naming format that includes a timestamp. This message is returned when the db2caem utility is unable to obtain a timestamp to use in the output directory names.

The db2caem utility cannot proceed.

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support

DBT7028E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the database server cannot process the input options specified with the db2caem command and the SQL statement specified with the -st parameter or contained in the SQL file specified with the -sf parameter.

This message can be returned when there is a syntax error with the specified SQL statement.

1. Review available diagnostic information.
2. Correct the invalid input parameters or invalid SQL syntax.
3. Rerun the db2caem command.

DBT7029E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. This message is returned when the db2caem utility encounters an internal DB2 database error while performing those tasks.

Perform the activity event monitor data activity again:

1. Review available diagnostic information.
2. Resolve the problem or problems that caused the failure.
3. Rerun the db2caem command.

If the problem persists, perform the following steps:

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support.

DBT7030E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. This message is returned when the db2caem utility encounters an internal DB2 database error while performing those tasks.

Perform the activity event monitor data activity again:

1. Review available diagnostic information.
2. Resolve the problem or problems that caused the failure.
3. Rerun the db2caem command.

If the problem persists, perform the following steps:

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support.

DBT7031E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. This message is returned when the db2caem utility encounters an internal DB2 database error while performing those tasks.

Perform the activity event monitor data activity again:

1. Review available diagnostic information.
2. Resolve the problem or problems that caused the failure.
3. Rerun the db2caem command.

If the problem persists, perform the following steps:

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support.

DBT7032W

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. This message is returned when the db2caem utlity encounters an internal DB2 database warning while performing those tasks.

This message can be returned when the db2caem utility cannot retrieve an environment variable.

Rerun the db2caem command.

If the problem persists, perform the following steps:

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support .

DBT7033E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the database server encountered an error while processing the SQL statement specified with the -st parameter or contained in the SQL file specified with the -sf parameter.

This message can be returned for several reasons, including the following reasons:

• There is a syntax error with the SQL statement.
• An invalid terminating character is used in the SQL statement.

1. Review available diagnostic information.
2. Correct the invalid input parameters or invalid SQL syntax.
3. Rerun the db2caem command.

DBT7034E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. For example, the db2caem command executes the db2exfmt command to format the contents of the EXPLAIN table for the specified SQL statement. This message is returned when the db2caem utility encounters an error while running the db2exfmt utility.

The db2caem utility can proceed despite the db2exfmt error.

No response is required.

DBT7035W

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. For example, the db2caem utility uses the connection attribute to verify the connection to the database while the command runs. This message is returned when the db2caem utility encounters an error while running the GET CONNECTION ATTRIBUTE command.

The fact that the db2caem utility failed to obtain the connection attribute might indicate a problem with the database connection.

When the db2caem command completes, review output information and diagnostic information to confirm that the activity event monitor data was successfully collected.

DBT7036W

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. This message is returned when the db2caem utility encounters an error while disconnecting from the database specified with the -d parameter.

The db2caem utility can complete successfully despite failing to disconnect from the database.

No response is required.

DBT7037W

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. This message is returned when the db2caem utility encounters an error while freeing internal resources.

The db2caem utility can complete successfully despite failing to free this CLI handle.

No response is required.

DBT7038I

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. For example, the db2caem utility must connect to the specified database.

No response is required.

DBT7039I

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data. For example, the db2caem utility must connect to and disconnect from the specified database.

No response is required.

DBT7040E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

To collect activity event monitor data, the db2caem utility must be able to explain or execute the specified statement. This message is returned when the specified SQL statement cannot be explained or will not be executed. This can happen for the following reasons:

• A statement might not be explainable if the statement creates, alters, or drops database objects, for example.
• The db2caem utility will not execute CALL statements because executing CALL statements might have undesirable side-effects in the specified database.

The db2caem utility cannot collect the requested activity event monitor data.

1. Modify the SQL statement specified with the -st parameter or included in the SQL file specified with the -sf parameter so that the statement is explainable and does not include the CALL keyword.
2. Rerun the db2caem command with the altered statement.

DBT7041I

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data, including connecting to the specified database.

No response is required.

DBT7042I

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data, including issuing the indicated statement with the -st option is specified or the -sf option is specified.

No response is required.

DBT7043I

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The db2caem utility must perform a variety of database tasks to collect the activity event monitor data, including connecting to and disconnecting from the specified database.

No response is required.

DBT7044E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

You can specify a file that contains a SQL statement for which activity event monitor data should be collected using the -sf parameter. You can specify a file that contains compilation environment information using the -compenv parameter. This message is returned when the db2caem utility cannot obtain information from the operating system about the file specified with the -sf parameter or the file specified with the -compenv parameter.

There are several reasons why the db2caem utility might not be able to access the specified file:

• The specified file does not exist.
• The db2caem utility runs with the same authority as the user who executes the db2aem command. This means that you must be able to open the file specified with the -sf parameter or the file specified with the -compenv parameter. This message can be returned when the user who executes the db2caem command does not have authority to open the specified file.

Rerun the command specifying a file path that exists and that you can access.

DBT7045E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

The db2cklog utility runs with the same authority as the user who ran the db2cklog command. This message is returned when the db2cklog utility cannot verify a log file because the db2cklog utility cannot open the log file. The db2cklog utility might not have been able to open the log file for the following reasons:

• The log file exists in a path that the db2cklog utility cannot access
• The db2cklog utility does not have read permission for the log file

Rerun the command specifying an archived log file or range of archived log files that exist in a path that you can access.

DBT7046E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility failed to allocate enough memory to perform the tasks associated with validating log files.

Perform the log file validation operation again:

1. Review available diagnostic information.
2. Resolve the problem or problems that caused the failure.
3. Rerun the db2cklog command.

If the problem persists, perform the following steps:

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support.

DBT7047E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility is able to open a log file to verify the file, but the db2cklog utility is then unable to close the log file. The db2cklog utility might not have been able to close the log file for the following reasons:

• The log file no longer exists in the same location as when the db2cklog command was run
• Another file operation has affected the log file

Rerun the db2cklog command ensuring that the specified archived log file or range of archived log files, and the directories in which the log file or files are located, persist for as long as the db2cklog utility is running.

DBT7048E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

The db2cklog utility examines many different aspects of the specified log file or files and determines whether the files are in a valid format and whether the contents are valid. This message is returned when the db2cklog utility finds that one of the specified log files is invalid and therefore cannot be used for rollforward recovery purposes.

1. Determine whether you have a secondary copy of the specified archived log file by referring to the value of the logarchmeth2 configuration parameter, which determines how your database server handles secondary archived log files.
2. If you have a secondary copy of the archived log file, perform the following steps:
   1. Verify the validity of the secondary log file by running the db2cklog command against the secondary copy.
   2. If the secondary copy of the log file passes validation, replace the log file that the db2cklog utility cannot read with the valid, secondary copy of the log file.
3. If you have only one copy of the archived log file, or if the db2cklog utility failed to verify the secondary log file, the log file is beyond repair and cannot be used for rollforward recovery purposes. Establish a new, more recent recovery point that does not depend on the unusable log file for rollforward recovery by making a full database backup as soon as possible.

DBT7049E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7050E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7051E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7052E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7053E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7054E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7055E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7056E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7057E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7058E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7059E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7060E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7061E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7062E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7063E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7064E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7065E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7066E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7067E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7068E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7069E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7070E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7071E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7072E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7073E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7074E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7075E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when an invalid parameter or value is specified with the db2cklog command.

1. [Optional] View the command syntax by running the db2cklog command without specifying any parameters.
2. Rerun the command specifying only supported command syntax.

DBT7076E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility. You can specify the absolute or the relative path of the archived log files using the ARCHLOGPATH parameter.

The db2cklog utility runs with the same authority as the user who ran the db2cklog command. This message can be returned when the person who ran the db2cklog command does not have read permission for the specified path.

1. Work with a system administrator to acquire read permission for the archived log path.
2. Rerun the command specifying an archived log file path using the ARCHLOGPATH parameter that you can access.

DBT7077E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility. You can specify the absolute or relative path of the archived log files using the ARCHLOGPATH parameter with the db2cklog command.

This message is returned when the string passed as the value of the ARCHLOGPATH parameter with the db2cklog command is longer than a defined maximum length. The maximum length of archived log path that can be specified with the ARCHLOGPATH parameter varies, depending on the operating system.

Respond to this message in one of the following ways:

• Run the db2cklog command from the directory in which the archived log file is located, and do not use the ARCHLOGPATH parameter at all.
• If the length of the absolute path of the archived log file is shorter than or equal to the maximum length of the string that can be passed with the ARCHLOGPATH parameter, rerun the db2cklog command specifying the absolute path with the ARCHLOGPATH parameter.
• If the length of the archived log path relative to the directory in which the db2cklog command is being run is shorter than or equal to the maximum length of the string that can be passed with the ARCHLOGPATH parameter, rerun the db2cklog command specifying the relative path using the ARCHLOGPATH parameter.

DBT7078E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

If a path is specified using the ARCHLOGPATH parameter with the db2cklog command, then the db2cklog utility will search for the specified archived log file or range of archived log files in the specified path. However, if the ARCHLOGPATH parameter is not passed to the db2cklog command, the db2cklog utility will search for the specified archived log file or range of archived log files in the directory from which the db2cklog command was run. This message is returned when the db2cklog utility cannot find the specified archived log file in either of these locations.

Respond to this message in one of the following ways:

• Run the db2cklog command from the directory in which the archived log file is located.
• Rerun the db2cklog command, specifying the location of the archived log file using the ARCHLOGPATH parameter.

DBT7079E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

To perform the tasks associated with validating log files, the command depends on various system resources and software components. This message is returned when there is a problem with one of these resources or components.

Perform the log file validation operation again:

1. Review available diagnostic information.
2. Resolve the problem or problems that caused the failure.
3. Rerun the db2cklog command.

If the problem persists, perform the following steps:

1. Collect the following diagnostic information:
   • db2diag logs
2. Contact IBM support.

DBT7080E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7081W

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This warning is returned when the db2cklog utility finds information that could indicate that a log file is active. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7082W

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This warning is returned when the db2cklog utility finds information that could indicate that a log file is active. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7083W

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This warning is returned when the db2cklog utility finds information that could indicate that a log file is active. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7084W

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This warning is returned when the db2cklog utility finds information that could indicate that a log file is active. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7085W

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This warning is returned when the db2cklog utility finds information that could indicate that a log file is active. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7086W

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This warning is returned when the db2cklog utility finds information that could indicate that a log file is active. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7087W

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility. The db2cklog utility should only be used to validate archived log files, not active log files.

Active database log files are the primary and secondary log files that are currently needed for recovery and rollback. Active logs might be open and database logging information might still be written to active logs. Archived database log files are closed and no longer needed for normal processing. These files are retained, or archived, for use in rollforward recovery.

When an attempt is made to run the db2cklog utility against an active log file, this warning is returned because the db2cklog utility might not be able to accurately check the validity of an active log file.

Rerun the command specifying only archived log files, not active log files.

DBT7088W

When you run the db2support -install command, diagnostic data is collected from several sources on a host machine. Sources for diagnostic data include log files stored on the file system and output returned by executing other, diagnostic commands. If diagnostic data for one of these sources cannot be obtained, this warning is returned.

If possible, always run the db2support -install command with root authority. Running the command with root authority ensures that the most complete set of diagnostic data possible is collected.

If you are already running the command with root authority, you do not need to respond to this message. The details are useful for alerting IBM support personnel to missing diagnostic data only.

DBT7089E

When running the db2support command included with the installation image, only a subset of the db2support syntax is available for you to use, and the command syntax you include must be specified in a valid form.

Reissue the command with the correct syntax and parameters.

DBT7090E

A host name cannot be validated as specified and no diagnostic data has been collected for this host.

Verify that the host name is spelled correctly. Include only valid host names with the -host option, then reissue the command.

DBT7091E

The db2support command requires an ssh connection to collect diagnostic data from hosts other than the local host. If an ssh connection cannot be established, diagnostic data collection fails.

An ssh connection can fail because ssh is not configured on the host or it is configured in such a way so as to prevent the db2support command from connecting.

Verify that ssh is configured correctly, then reissue the command.

DBT7092W

When you run the db2support -install command, diagnostic data is collected from several sources on a host machine, such as log files stored on the file system and output returned by executing other, diagnostic commands. If the user invoking the db2support command does not have the required level of authorization to access one of these sources, some diagnostic data will not get collected.

For the most complete collection of diagnostic data, always invoke the db2support -install command with root authority. If you cannot run the command with root authority, you do not need to respond to this message. If necessary, this message will alert IBM support personnel that diagnostic data might be missing.

DBT7093E

To collect diagnostic information on a remote host, the db2support command must be able to connect to the host over the network.

There are several reasons why a host cannot be reached:

• The network cabling has been disconnected, the network adapter is unresponsive, or the network configuration is preventing network access.
• The host machine is offline (the host is not powered up or in the process of rebooting, for example).

Resolve the problem that is preventing the host from being reachable, then reissue the command.

DBT7094E

You must to be the instance owner to invoke the db2support command with the options specified.

As instance owner, invoke the db2support command from the database product install path.

DBT7095E

When running the db2support command included with the installation image, only a subset of the db2support syntax is available for you to use, and the command syntax you include must be specified in a valid form. When you specify the -install option, it can be specified together with the -host option only.

Reissue the command with valid syntax and parameters.

DBT7096W

When you run the db2support -install command, diagnostic data is collected from several sources on a host machine, including output returned by executing the db2instance -list command. If the instance name that must be specified with the db2instance -list command cannot be determined, this warning is returned.

You do not need to respond to this message. The details are useful for alerting IBM support personnel to missing diagnostic data only.

DBT7097E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7098E

You can determine whether an archived log file or a range of archived log files are valid for rollforward recovery using the db2cklog utility.

This message is returned when the db2cklog utility finds that a log file is invalid. The detailed information printed in this message is useful for helping IBM support personnel investigate how the log file became invalid.

You do not need to respond to this message. The details are useful for helping IBM support personnel only.

DBT7099E

One of the following authority levels is required to run the db2checkCOL command:

• SYSADM
• SYSCTRL
• SYSMAINT
• SYSMON

The input user ID must hold one of the following authorizations:

• DATAACCESS authority
• SELECT privilege on the system catalog tables and all column-organized tables in the database

Write access to the current directory is also required.

Have a user with the required authorization issue the command.

DBT7100E

Command syntax:

 db2checkCOL -checkFP             <database-alias>             [ <user-ID> <password> ] 

Issue the command again, specifying valid parameters and options.

DBT7101E

 db2checkCOL -checkFP             <database-alias>             [ <user-ID> <password> ] 

Issue the command again, specifying required parameters and options.

DBT7102E

The db2checkCOL utility connects to the specified database to test the tables in the database. This message is returned when the db2checkCOL utility cannot test any tables because the utility cannot connect to the database.

1. Refer to the details of the given sqlcode.
2. Resolve the underlying problem.
3. Issue the db2checkCOL command again.

DBT7103E

The db2checkCOL utility uses DB2 Call Level Interface (CLI) to test the tables in the database. This message is returned when the db2checkCOL utility is unable to test any tables because the utility cannot initialize the CLI environment.

1. Refer to the details of the given sqlcode.
2. Resolve the underlying problem.
3. Issue the db2checkCOL command again.

DBT7104E

The db2checkCOL utility tests the tables in the specified database by issuing queries against the tables. This message is returned when the utility is unable to test a table because the utility does not have access to the table space in which the table is located.

1. Refer to the details of the given sqlcode.
2. Resolve the underlying problem that is preventing the db2checkCOL utility from accessing the table space.
3. Issue the db2checkCOL command again.

DBT7105E

The db2checkCOL utility tests the tables in the database by issuing queries against the tables. This message is returned when the db2checkCOL utility is unable to test a table because of an unexpected, internal error.

The reason code indicates the nature of the internal error:

1

An SQL query issued against the table failed.

2

Fetching results of an SQL query failed.

3

Retrieving required diagnostic details from an SQL query failed.

4

Processing diagnostic details from an SQL query failed.

1. Refer to the details of the given sqlcode.
2. Resolve the underlying problem.
3. Issue the db2checkCOL command again.

DBT7106E

The db2checkCOL command tests tables in the database by using the DB2 Call Level Interface (CLI) to issue queries against the tables. This message is returned when the db2checkCOL utility encountered an out-of-memory error condition while using the CLI environment to issue queries against the tables and process result sets.

Make more memory available for the database manager, the CLI environment, and the db2checkCOL utility. For example, set the database_memory configuration parameter to AUTOMATIC. Then reissue the db2checkCOL command.

DBT7107E

The db2checkCOL utility tests tables in the database by issuing queries against the tables using the DB2 Call Level Interface (CLI). This message is returned when the db2checkCOL utility is unable to perform testing tasks because of an internal error. The runtime tokens are for the use of IBM software support only.

Issue the db2checkCOL command again.

If the problem continues, record the values of the runtime tokens and contact IBM software support for assistance.

DBT7108E

The db2checkCOL utility performs some tests in the database by using output from the db2pd utility. This message is returned when the db2checkCOL utility encounters an error while using the db2pd utility.

The reason code indicates the nature of the internal error:

1

The db2pd command failed.

2

Reading the primary db2pd output file failed.

3

Reading the secondary db2pd output file failed.

4

Interpreting diagnostic details in the db2pd output file failed.

The runtime tokens are for the use of IBM software support only.

Issue the db2checkCOL command again. If the problem continues, record the values of the runtime tokens and then contact IBM software support for assistance.

DBT7109E

The db2checkCOL utility performs some tests in the database by using output from the db2pd utility. This message is returned when the db2checkCOL utility encounters an error while using the db2pd utility.

Issue the db2checkCOL command again. If the problem continues, record the values of the runtime tokens and then contact IBM software support for assistance.

DBT7110E

The db2checkCOL utility performs some tests in the database by using output from the db2pd utility. This message is returned when the db2checkCOL utility encounters an error while using the db2pd utility.

The db2checkCOL utility performs some tests in the database by using output from the db2pd utility. This message is returned when the db2checkCOL utility encounters an error while using the db2pd utility.

DBT7111I

This message is returned when the db2checkCOL utility has completed successfully.

No response is required.

DBT7112E

This message is returned when the db2checkCOL utility finds one or more tables that require action.

Rebuild the table-level compression dictionary for each of the affected tables by issuing the LOAD command with the REPLACE option.

DBT7113E

This message is returned when the db2checkCOL utility finds one or more tables that require action and there are one or more tables that the utility failed to test.

1. Rebuild the table-level compression dictionary for each of the affected tables by issuing the LOAD command with the REPLACE option.
2. Issue the db2checkCOL command again to test the tables that the db2checkCOL utility was unable to test. If the problem continues, contact IBM software support for assistance.

DBT7114E

This message is returned when the db2checkCOL utility finds no tables that require action, but there are one or more tables that the utility failed to test.

Issue the db2checkCOL command again to test the tables that the db2checkCOL utility was unable to test. If the problem continues, contact IBM software support for assistance.

DBT7116E

When you issue the db2support command specifying collection level 1 or higher, the db2support utility will use the explain facility to collect information about the access plan that the optimizer chooses for a given SQL statement.

This message is returned when the db2support utility invokes the explain facility and the explain facility encounters an error while analyzing the given SQL statement. When the explain facility encounters an error, the db2support command fails and creates a log file called optimizer.log.

Perform the following troubleshooting steps:

• Review error details in the log file, optimizer.log
• Verify the syntax of the specified SQL statement
• Verify the database objects referenced in the SQL statement
• Verify that the SQL statement has a correct terminating character
• Specify the full name of referenced database objects, either by explicitly including the schema name in the SQL statement or by specifying the schema with the -cs parameter with the db2support command

If the error persists, issue the following command and then contact IBM Software Support:

 db2support -d <database-name> -cl 0 -nodb2look 

DBT7117W

You can determine whether a log file or a range of log files are from a different database product version by using the db2cklog utility.

This warning is returned when the db2cklog utility finds information that indicates that a log file is from a different database product version. This warning is to assist in manual log file management post upgrade.

If the log file is no longer needed for recovery or the log file is not archive pending then you may consider the file for manual log file management.

DBT7118E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the schema name that is specified is longer than length limits imposed on DB2 schema names.

Rerun the command specifying a valid schema name.

DBT7119E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the function path that is specified is longer than length limits imposed on DB2 function paths.

Rerun the command specifying a valid function path.

DBT7120E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

This message is returned when the tenant name that is specified is longer than length limits imposed on DB2 tenant names.

Rerun the command specifying a valid tenant name.

DBT7121E

You can capture activity event monitor data, which can be used to analyze SQL statement performance, using the db2caem utility.

The -compenv parameter and the -cs -fp parameters cannot both be specified. This message is returned when the -compenv parameter and the -cs -fp parameters are both specified.

You can view the db2caem command syntax by running the following command:

 db2caem -h 

Review the db2caem command syntax, and then rerun the command specifying either the -compenv parameter or the -cs -fp parameters, not both.