Nonstop Database, HiRDB Version 9 Command Reference

[Contents][Index][Back][Next]

5.3.4 Information to be specified depending on the data loading method

For details about an applicable item, see the section indicated.

Item Reference target
Option Control statement or file
Database update log is acquired or not acquired -l 5.4.2(4) -- --
Synchronization points are specified to load a large amount of data -- -- option statement 5.4.16
The pdload execution time is to be monitored -- -- option statement 5.4.16
Default value for the DEFAULT clause is to be stored in a table for which the DEFAULT clause is specified -- -- option statement 5.4.16
EasyMT is used -f 5.4.2(11) mtguide statement 5.4.3
emtdef statement 5.4.3
UOC is used -- -- srcuoc statement 5.4.11
Processing is to be cancelled if invalid input data is detected#1 -e 5.4.2(13) Error information file 5.6
-r 5.4.2(14) option statement 5.4.16
When invalid input data is detected, data loading is to be ignored -- -- option statement 5.4.16
When the automatic numbering facility is used during data loading -- -- option statement 5.4.16
When data is loaded from input data files in UTF-16 to a table defined in a UTF-8 environment -- -- option statement 5.4.16
Percentage of free table space is to be changed during data loading#2 Storing data to unused area -y 5.4.2(16) -- --
Storing data in unused area based on the specified percentage of free space -- -- option statement 5.4.16
Data loading status message is to be output in units of lines other than 100,000 -m 5.4.2(18) -- --
When output of information messages is suppressed
Response time for server-to-server communication is to be monitored -x 5.4.2(19) -- --
Batch output data loading is to be conducted using a local buffer, not a global buffer#3 -n 5.4.2(8) -- --
Authorization identifier of the user who executes data loading is to be changed to a value other than the one specified in the PDUSER environment variable#4 -u 5.4.2(9) -- --
The input data files for a table are to be divided into input data files that enable parallel data loading into each RDAREA -- -- src_work statement 5.4.14
Input data values of the FLOAT and SMALLFLT types are to be corrected to values supported by the OS and then the data is to be loaded -F 5.4.2(23) -- --

--: Not applicable

#1: Suppose that data loading is executed on a table with repetition columns using an input data file in the DAT format. The input data is created in VV format, but it is treated as being in FF format if the elmtype operand is omitted, in which case all input data results in an error, thereby creating an unneeded error information file and error data file. In this case, processing should be cancelled when an error is detected to avoid creating unneeded files or executing unneeded operations.

#2: During additional data loading, data is usually stored in unused pages according to the percentage of free table space. If the system runs out of unused pages, an error results, and rollback occurs. If this occurs, you must reorganize the table with the database reorganization utility or add or extend RDAREAs with the database structure modification utility before re-executing the data loading. In this case, if you change the percentage of free table space during data loading, you may be able to complete the processing without having to take such actions.

#3: If you specify the number of batch output pages, the system outputs the specified number of pages in batch mode, thereby reducing the number of input/output operations.

#4: If you specify nothing, the value of the PDUSER environment variable takes effect. If you have not specified the PDUSER environment variable, the system assumes the user name of the login window.