Hitachi

Hitachi Advanced Database Command Reference


17.10.5 Whether the re-execute facility that starts from the processing to create B-tree indexes and text indexes can be applied

Depending on the adbimport command's cancellation timing, the re-execute facility that starts from the processing to create B-tree indexes and text indexes might or might not be applied when the adbimport command is re-executed.

The table below describes whether the re-execute facility that starts from the processing to create B-tree indexes and text indexes is applied, depending on the adbimport command's cancellation timing.

Note that the database recovery method is the same regardless of the cancellation timing.

Table 17‒17: Whether the re-execute facility that starts from the processing to create B-tree indexes and text indexes is applied, depending on the adbimport command's cancellation timing

-d option

Timing of the cancellation#1

While creating table data

During sort processing

During creation of B-tree and text indexes#2

Specified (creation mode)

  • Whether the re-execute facility is applied

    Not applied.#3

  • Table status

    The table is in one of the following statuses:

    • There is no data.

    • Status before the adbimport command was executed.

  • Index status

    A B-tree index, text index, or range index is in one of the following statuses:

    • There is no data.

    • Status before the adbimport command was executed.

  • Whether the re-execute facility is applied

    Applied.#4

  • Table status

    The table is non-updatable.

  • Index status

    Import of range indexes is complete.

    Import of B-tree and text indexes is incomplete.

Omitted (addition mode)

  • Whether the re-execute facility is applied

    Not applied.#3

  • Table status

    The table is in the status that it was in before the adbimport command was executed.

  • Index status

    A B-tree index, text index, or range index is in the status that it was in before the adbimport command was executed.

  • Whether the re-execute facility is applied

    Applied.#4

  • Table status

    The table is non-updatable.

  • Index status

    Import of range indexes is complete.

    B-tree and text indexes are in the status that they were in before the adbimport command was executed.

Legend:

Re-execute facility: Re-execute facility that starts from the processing to create B-tree indexes and text indexes

Note:

B-tree indexes include the B-tree index for the primary key.

#1

You can determine when the command was canceled by the messages that are issued, as shown in the following:

[Figure]

#2

If the KFAA80204-I message (whose return code is 0 or 4) has been issued, the table and indexes have been imported. In this case, there is no need to re-execute the adbimport command.

If the KFAA80204-I message is not output, execute the following command, and then check the second line in the output results (the column titles occupy the first line in the output results):

adbdbstatus -c table -n name-of-table-for-which-adbimport-command-was-canceled

Specify name-of-table-for-which-adbimport-command-was-canceled in the format schema-name.table-identifier.

■ When the value of the Command_status column (column 17) is abort and the value of the Rerun_command column (column 18) is adbimport

Import processing was not completed. Re-execute the adbimport command.

[Figure]

■ When no values are displayed in the Command_status column (column 17) and the Rerun_command column (column 18)

Import processing has been completed. There is no need to re-execute the adbimport command.

[Figure]

#3

When the adbimport command is re-executed, the data import processing is performed from the beginning.

#4

When the adbimport command is re-executed, the data import processing restarts from the point of B-tree and text index creation processing. However, if all the B-tree indexes and text indexes defined for the table to be processed are deleted before the adbimport command is re-executed, only command termination processing is performed.