Hitachi

Hitachi Advanced Database Command Reference


15.5.2 If the command terminated abnormally while collecting cost information for a specific table

To troubleshoot if the command with the -t option specified terminated abnormally while collecting cost information for a specific table:

  1. Check if the KFAA80285-I message was issued.

    If the KFAA80285-I message (indicating that cost information for a table was collected) was issued, the cost information has been collected. No action is needed.

    If the KFAA80285-I message was not issued, go to the next step.

  2. Check the date and time cost information was collected.

    Retrieve the system tables to check the date and time cost information was collected for the table specified in the -t option and for any indexes defined for that table.

    The following SELECT statement checks the names of all tables for which cost information was collected and the dates and times the cost information was collected:

    SELECT "TABLE_SCHEMA","TABLE_NAME","COLLECT_TIME"
         FROM "MASTER"."STATUS_TABLES"

    The following SELECT statement checks the names of all indexes for which cost information was collected and the dates and times the cost information was collected:

    SELECT "TABLE_SCHEMA","INDEX_NAME","COLLECT_TIME"
         FROM "MASTER"."STATUS_INDEXES"
    Important

    Issue the COMMIT statement immediately after you retrieve the system tables. However, if you terminate the adbsql command after you retrieve the system tables, there is no need to execute the COMMIT statement.

    If the dates and times the cost information was collected for the tables and indexes are after the date and time the adbgetcst command was executed, the cost information has been collected. In this case, no action is needed.

    If the dates and times the cost information was collected for the tables and indexes are before the date and time the adbgetcst command executed or no cost information is stored in the system tables (base tables), go to the next step.

  3. Check the message that was issued.

    Eliminate the cause of the error according to the information provided in the message.

  4. Re-execute the adbgetcst command.

    Re-execute the adbgetcst command with the same options.