Hitachi

Hitachi Advanced Database Command Reference


16.5.2 Identifying the cause of the error and taking corrective action

The following figure shows the procedural flow to follow if the adbidxrebuild command terminates abnormally.

Figure 16‒10: Procedural flow to follow if the adbidxrebuild command terminates abnormally

[Figure]

Procedure
  1. Check the messages that have been issued and identify the cause of the error.

  2. Take appropriate action to eliminate the cause of the error.

  3. Re-execute the adbidxrebuild command.

  4. If the re-executed adbidxrebuild command terminates abnormally, check the message that was issued and execute the adbidxrebuild command.

    For details, see 16.5.6 If an error occurs during re-execution of the adbidxrebuild command.

When the following indexes are being rebuilt, see 16.5.3 If the target table is a single-chunk table:

If the indexes defined for the multi-chunk table are being rebuilt, see 16.5.4 If the target table is a multi-chunk table.

■ When the multi-node function is used

If the adbidxrebuild command is canceled and the table to be processed becomes non-updatable, release the base table from updatable status by re-executing the canceled adbidxrebuild command.

If the master node was switched due to abnormal termination of the HADB server on the master node, execute the adbidxrebuild command on the new master node to release the base table from non-updatable status. At this time, execute the adbidxrebuild command with the --create-temp-file option specified.

For details about how to switch the master node to another node, and how to start the HADB server without using the multi-node function, see the topic Problems related to startup or termination of the HADB servers in the multi-node configuration in Troubleshooting (when the multi-node function is being used) in Operations When Using the Multi-Node Function in the HADB Setup and Operation Guide.

For details about the --create-temp-file option of the adbidxrebuild command, see --create-temp-file in (2) Explanation of options in 16.2.1 Explanation of the specification format and options.