16.5.5 Changing command options and index rebuild options during re-execution
This subsection explains the effects of changing command options and index rebuild options when the adbidxrebuild command is re-executed.
- Organization of this subsection
(1) Changing command options
Whether changed command options take effect depends on the cancellation timing of the adbidxrebuild command. The following table shows the processing at the restart when command options have been changed.
|
No. |
Command option that has been changed |
Timing of the cancellation#1 |
||
|---|---|---|---|---|
|
During table data retrieval processing |
During sort processing |
During creation of B-tree and text indexes |
||
|
1 |
-u option |
N |
N |
N |
|
2 |
-p option |
N |
N |
N |
|
3 |
-g option |
Y |
C |
C |
|
4 |
-w option |
Y |
C |
C |
|
5 |
-z option |
Y |
Y |
Y |
|
6 |
-i option#2 |
Y#3 |
-- |
-- |
|
7 |
--create-temp-file |
Y#4 |
-- |
-- |
|
8 |
--force |
Not applicable (because when --force is specified, the processing is restarted forcibly from the beginning)#5 |
||
|
9 |
table-to-be-processed |
N |
N |
N |
- Legend:
-
Y: Change takes effect.
C: For a single-chunk table, change is ignored (the setting in effect before the change is used for execution). For a multi-chunk table, change takes effect beginning with the processing of the next chunk. If the adbidxrebuild command is canceled while the final chunk is being processed, the change is ignored.
N: If a change is made, the command will not re-execute.
--: Change is ignored (the setting in effect before the change is used for execution).
- #1
-
For details about the timing of cancellation, see the following:
- Single-chunk table: Table 16‒3: Whether the re-execute facility is applied depending on when the adbidxrebuild command was canceled (for a single-chunk table)
- Multi-chunk table: Table 16‒4: Restart processing depending on when the adbidxrebuild command was canceled (for a multi-chunk table)
- #2
-
Do not change the value of the -i option when you use the re-execute facility for a multi-chunk table. If the -i option value is changed in such a case, the change might or might not take effect, depending on conditions, and the re-execute facility might become unavailable.
- #3
-
In the case of a multi-chunk table, the change takes effect only when the processing is restarted at the point of data retrieval from the first chunk. If the processing is restarted at a subsequent chunk, the change is ignored.
- #4
-
If, after the adbimport command is stopped, the adbidxrebuild command executed with the --create-temp-file option specified is canceled, the adbidxrebuild command will have the --create-temp-file option specified the next time it is executed. In this case, index rebuild processing resumes from the point of table data retrieval. (If the table to be processed is a multi-chunk table, index rebuild processing resumes from the point of table data retrieval in the chunk that was being processed when the adbimport command stopped.)
Even if you change the specification of the --create-temp-file option when re-executing the adbidxrebuild command, the change is invalid. However, if you specify the --force option, this specification goes into effect.
- #5
-
If, after the adbimport command is stopped, the adbidxrebuild command executed with the --force option specified is canceled, the adbidxrebuild command will have the --force option specified the next time it is executed. In this case, index rebuild processing is forcibly re-executed from the beginning. (The KAFF80215-I message is issued.)
Even if you change the specification of the --force option when you re-execute the adbidxrebuild command, the change is invalid.
(2) Changing index rebuild options
Whether changed index rebuild options take effect depends on the cancellation timing of the adbidxrebuild command. The following table shows the processing at the restart when index rebuild options have been changed.
|
No. |
Index rebuild option that has been changed |
Timing of the cancellation# |
||
|---|---|---|---|---|
|
During table data retrieval processing |
During sort processing |
While creating B-tree and text indexes |
||
|
1 |
adb_idxrebuild_rthd_num |
Y |
Y |
Y |
|
2 |
adb_idxrebuild_scan_buff_size |
Y |
C |
C |
|
3 |
adb_idxrebuild_buff_blk_num |
Y |
C |
C |
|
4 |
adb_idxrebuild_sort_buff_size |
Y |
Y |
C |
|
5 |
adb_idxrebuild_dvix_rdbuff_size |
Y |
Y |
Y |
|
6 |
adb_idxrebuild_dvix_wtbuff_size |
Y |
Y |
Y |
|
7 |
adb_idxrebuild_txt_buff_size |
Y |
Y |
Y |
- Legend:
-
Y: Change takes effect.
C: For a single-chunk table, change is ignored but checking of the number of threads will be performed. For a multi-chunk table, change takes effect beginning with the processing of the next chunk. If the adbidxrebuild command is canceled while the final chunk is being processed, the change is ignored.
- #
-
For details about the timing of cancellation, see the following:
- Single-chunk table: Table 16‒3: Whether the re-execute facility is applied depending on when the adbidxrebuild command was canceled (for a single-chunk table)
- Multi-chunk table: Table 16‒4: Restart processing depending on when the adbidxrebuild command was canceled (for a multi-chunk table)