15.9.1 Steps to take when unfinished status is applied to a B-tree index

If you define a B-tree index for a base table to which segments for storing rows are assigned, that B-tree index is placed in unfinished status (a status in which no B-tree index data can be created). For details about the status in which segments for storing rows are assigned, see 5.3.1 Notes on defining B-tree indexes (unfinished status of B-tree indexes).

When a B-tree index is placed in unfinished status, the following operations end in an error.

■ Operations that end in an error

• Executing a SELECT statement that uses an unfinished B-tree index

• Executing the INSERT, UPDATE, or DELETE statement on a table for which an unfinished B-tree index is defined

• Executing the adbimport command without the -d option specified on a base table for which an unfinished B-tree index is defined

• Executing the adbmergechunk command on a base table for which an unfinished B-tree index is defined

• Executing the adbunarchivechunk command on an archivable multi-chunk table for which a B-tree index in unfinished status is defined

Note

The TRUNCATE TABLE statement can be executed. If the TRUNCATE TABLE statement is used to delete all rows from a base table, B-tree index data is also deleted, and therefore, the B-tree index is released from unfinished status.

A B-tree index is placed in unfinished status for the following reasons:

• You define a B-tree index for a base table to which segments for storing rows are assigned.

• The adbimport or adbidxrebuild command terminated abnormally.

The way you release a B-tree index from unfinished status depends on the cause of the unfinished status.

Organization of this subsection

• (1) If you define a B-tree index for a base table to which segments for storing rows are assigned

• (2) When the adbimport or adbidxrebuild command has terminated abnormally