15.6 Notes

1. Cost information collected on an HADB server whose version is earlier than 04-03 cannot be used on HADB servers whose version is 04-03 or later. Therefore, if the HADB server has been upgraded from a version earlier than 04-03 to 04-03 or later, you must collect cost information again by using the adbgetcst command.

2. If the adbgetcst command is executed while another command or application program is running, HADB might not be able to allocate the required number of processing real threads. If that happens, HADB waits until the required number of processing real threads can be allocated before executing the adbgetcst command. If allocation of processing real threads is placed in wait status, see the topic Points to consider about the number of processing real threads to be used during command execution in Points to consider when executing commands concurrently in Preparing Resources in the HADB Setup and Operation Guide and take appropriate action.

3. Cost-information collection processing for a table is skipped and the KFAA50291-W message is issued in the following cases:

   • The table to be processed is non-updatable.

   • The B-tree indexes, text indexes, or range indexes defined in the tables to be processed are in unfinished status.

   • The adbimport or adbidxrebuild command, executed on the tables to be processed, was canceled.

   When deleting cost information, the command deletes the cost information from the system table (base table) regardless of the status of the tables or the status of any B-tree, text, or range indexes defined for those tables.

4. When cost information is collected, the HADB server uses the SELECT statement to retrieve the target tables. Therefore, we recommend that you execute the command in an environment in which out-of-order execution is applied. For details about environments in which out-of-order execution is applied, see Database retrieval method (out-of-order execution) in the HADB Setup and Operation Guide.

5. Make sure that the cost-information collection-options file and the path of its storage directory differ from any of the files and directories used by a program other than the adbgetcst command. If there is any duplication, the data in the file might be lost. This also applies to symbolic link and relative path specifications.

6. You can use the adbcancel command to cancel execution of the adbgetcst command. For details about how to use the adbcancel command to suspend an executing command, see 1.6 When suspending (forcibly terminating) an executing command.

7. Cost-information collection and deletion processing is handled by server processes. Therefore, using the Ctrl+C keys to forcibly terminate the adbgetcst command process will not interrupt cost-information collection or deletion processing that is being performed by server processes (such processing continues). When the collection and deletion processing is completed, the command outputs the KFAA81001-I message to the message log file.

8. For information on reducing this command's execution time, see the topic Reducing the execution time of the adbgetcst command in Tuning to shorten command execution time in Tuning in the HADB Setup and Operation Guide.

To Page Top