Required options and control statements depend on the type of reload operation executed by the user.
The options listed in (1) and the control statements are mandatory. The items in (2) through (4) are related to the options and control statements presented in the Reference column. For details about the options, see Section 8.9.2.
Item | Reference | |||
---|---|---|---|---|
Option | Control statement | |||
Type of pdrorg processing | -k reld | (1) | ![]() | ![]() |
Reorganization of a user-defined table (can be omitted because the default is -c user) | -c user | (2) | ![]() | ![]() |
Name of the table to be reloaded | -t | (3) | ![]() | ![]() |
File containing the control statements | control-information-filename | (19) | ![]() | ![]() |
Information about an unload data file | ![]() | ![]() | unload statement | 8.9.4 |
Item | Reference location | |||
---|---|---|---|---|
Option | Control statement | |||
Indexes are defined | -i | (6) | index statement | 8.9.5 |
-o | (15) | idxwork statement | 8.9.7 | |
sort statement | 8.9.8 | |||
There are LOB columns | -j | (9) | lobunld statement | 8.9.9 |
There are columns of abstract data type provided by a plug-in (LOB attribute) | -j | (9) | reld_func statement | 8.9.14 |
There are constraint definitions | ![]() | ![]() | constraint statement | 8.9.15 |
Inner replica facility is used | -q | (18) | ![]() | ![]() |
: Not applicable
Item | Reference location | |||
---|---|---|---|---|
Option | Control statement | |||
Integrating data into a single file (-g option specified during unload operation) | -g | (8) | ![]() | ![]() |
Using EasyMT | -f | (12) | mtguide statement | 8.9.3 |
emtdef statement | 8.9.3 | |||
Using HiRDB files | -f | (12) | ![]() | ![]() |
: Not applicable
Item | Reference location | |||
---|---|---|---|---|
Option | Control statement | |||
Reloading only to some of the RDAREAs for a row-partitioned table | -r | (4) | ![]() | ![]() |
Acquiring or not acquiring database update log | -l | (5) | ![]() | ![]() |
Specifying synchronization points when reloading a large amount of data | ![]() | ![]() | option statement | 8.9.16 |
Monitoring the execution time of pdrorg | ![]() | ![]() | option statement | 8.9.16 |
Changing the pdrorg executor's user authorization identifier to a value other than the value of environment variable PDUSER1 | -u | (10) | ![]() | ![]() |
Reloading in batch input/output mode using local buffer instead of global buffer2 | -n | (11) | ![]() | ![]() |
Changing a reloading status message output interval to a value other than 100,000 lines | -m | (16) | ![]() | ![]() |
Monitoring the response time for server-to-server communication | -X | (17) | ![]() | ![]() |
Migrating table data to another table | ![]() | ![]() | tblname statement | 8.9.11 |
Using the same space character in the entire table data | ![]() | ![]() | option statement | 8.9.16 |
Changing the percentage of free space in table and index during reloading3 | ![]() | ![]() | option statement | 8.9.16 |
Obtaining tuning information during the execution of pdrorg | ![]() | ![]() | report statement | 8.9.17 |
: Not applicable
1 If omitted, the system assumes the value of the PDUSER environment variable. If the PDUSER environment variable has not been specified, the system assumes the user name in the login window.
2 By specifying the number of batch input/output pages, you can reduce the number of I/O operations because data is input/output in units of specified pages in batch mode.
3 If a space shortage occurs in an RDAREA during execution of pdrorg, you can complete the processing without having to expand the RDAREA temporarily (except for a table or index whose percentage of free space is 0).