13.13 Notes

1. If the adbdbstatus command terminates normally, it does not output a start message or a termination message with a return code. If the adbdbstatus command has terminated abnormally, check the displayed message or message log file and take appropriate action.

2. The lock of the adbdbstatus command differs depending on the specified option. When you execute the adbdbstatus command concurrently with another SQL statement or command, make sure that a lock conflict does not occur. For details about locks for SQL statements and commands, see the following in the HADB Setup and Operation Guide: Locked resources that are reserved and their lock modes, and Locks performed when the adbdbstatus command is executed (to analyze the database status) in Examples of locks.

   When summary information for DB areas is output

   A definition SQL statement or adbmodarea command cannot be executed concurrently with the adbdbstatus command.

   When information other than summary information for DB areas is output

   A definition SQL statement or adbmodarea command cannot be executed concurrently with the adbdbstatus command.

   Also note that the adbdbstatus command that processes DB areas cannot be executed concurrently with an SQL statement or command that updates those DB areas.

   In addition, the adbdbstatus command that processes tables or indexes cannot be executed concurrently with an SQL statement or command that updates the DB area where those tables and indexes are stored.

   Note that the adbdbstatus command with the --shared-lock option specified can be executed concurrently with other SQL statements and commands. For details about the --shared-lock option, see --shared-lock option in (3) Explanation of options in 13.2.1 Explanation of the specification format and options (outputting summary information or usage information).

3. Use the adbcancel command to cancel execution of the adbdbstatus 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.

4. DB status analysis processing is performed by server processes. Therefore, using the Ctrl+C keys to forcibly terminate the adbdbstatus command process will not interrupt database status analysis processing that is being performed by server processes (this processing continues). When the DB status analysis processing is complete, the KFAA81001-I message is output to the message log file.

5. Because the adbdbstatus command does not change any contents of DB areas, tables, or indexes, there is no need to restore tables or indexes in the event of abnormal termination of the adbdbstatus command. In such a case, re-execute the adbdbstatus command as needed.

6. If the adbdbstatus command is executed while the table is non-updatable due to cancellation of one of the following commands, latest values might not be displayed for items relating to the number of pages, segments, or chunks. (The values that existed when the relevant command started might be displayed.)

   • adbimport command (when background import is performed)

   • adbidxrebuild command (executed with the --create-temp-file option specified after background import is canceled)

   • adbunarchivechunk command

7. If the adbdbstatus command is executed following any of the events listed below, the values output for the number of segments in use and the number of pages in use might not be correct:

   • Abnormal termination of the HADB server while the database was being updated.

   • Output of the KFAA30919-E error message indicating that a global buffer shortage occurred during database update processing in multiple transactions.

   • Error termination of a command or of an SQL statement (such as a definition SQL statement) that releases segments.

8. If merge-source chunks have not been completely deleted by the adbmergechunk command, the number of chunks created for the table in the summary information for the table will include the system chunk that is used temporarily during merge chunk processing. Therefore, the number of chunks created for the table in the table summary information might be greater by one than the maximum number of chunks specified in the table definition.

9. If table segments are merged by the adbmergechunk command, the number of pages that cannot be reused might increase, resulting in an increase in the number of pages that are used. Therefore, when you use the adbdbstatus command to check the number of pages in use, the values before and after the merge chunk processing might differ (might increase afterwards).

10. When the following items are output in megabytes or gigabytes (M or G, respectively, is specified in the -S option), the value of each item is rounded up and output as positive integers or as 0.

    • Output items for usage amounts (summary information or usage information)

      Table 13‒2: Display units and column titles for usage amount output items in (3) Explanation of options in 13.2.1 Explanation of the specification format and options (outputting summary information or usage information)

    • Output items for the necessity of reorganization (information about the need for reorganization)

      Table 13‒14: Display units and column titles for the output items for the necessity of reorganization in (2) Explanation of options in 13.2.2 Explanation of the specification format and options (outputting information about the need for reorganization of column store tables)

    If the value of each item is small (such as less than 102.4 kilobytes when usage amounts are output in megabytes, or less than 102.4 megabytes when usage amounts are output in gigabytes), 0 is output for each item. If you want to obtain accurate values, specify K in the -S option so that the items will be output in kilobytes.

11. The display units for the following items are shown in the title line.

    • Output items for usage amounts (summary information or usage information)

      Table 13‒2: Display units and column titles for usage amount output items in (3) Explanation of options in 13.2.1 Explanation of the specification format and options (outputting summary information or usage information)

    • Output items for the necessity of reorganization (information about the need for reorganization)

      Table 13‒14: Display units and column titles for the output items for the necessity of reorganization in (2) Explanation of options in 13.2.2 Explanation of the specification format and options (outputting information about the need for reorganization of column store tables)

    To check the display units for each item, you must omit the -t option so that the title line will be output. When you save the output results of the adbdbstatus command, save both the title line and the output results so that you can check the display units.

12. When any of the types of information listed below are output, information related to the tables and indexes used by HADB is output for the rows that are related to dictionary DB areas and system-table DB areas. (Information other than the tables and indexes defined by HADB users is output.)

    • Table summary information

    • Index summary information

    • Usage information for DB areas, tables, and indexes

13. If an error occurs during execution of the adbreorgsystemdata command, the remaining pre-reorganization data, if any, is output as deletion-pending chunk.

To Page Top