5.13 Examples

Table 5-44 provides a list of the examples of using the database load utility.

Table 5-44 Examples of using the database load utility

ExampleDescriptionClassification
Example 1Loading data to a row-partitioned table
  • Explanation is based on the input data file in the DAT format and in the fixed-size data format.
  • The example uses a column structure information file.
S
Example 2Loading data to a row-partitioned table in units of tablesS
Example 3Loading data to a row-partitioned table in units of RDAREAsS
Example 4Loading data to a row-partitioned table in units of tables
  • The input data file is located in a utility special unit.
S
Example 5Loading data to a table with LOB columns
  • The example loads data to both a LOB column structure base table and LOB columns at the same time.
S
Example 6Loading data to a table with LOB columns
  • The example loads data only to the LOB column structure base table.
S
Example 7Loading data to a table with LOB columns
  • The example loads data only to the LOB columns.
S
Example 8Loading data into an audit trail table
  • The example loads data from audit trail files waiting for data loading into an audit trail table.
S
Example 9Loading data to a non-row-partitioned table
  • The input data file is located at the front-end server.
P
Example 10Loading data to a row-partitioned table
  • The input data file is located at the front-end server.
P
Example 11Loading data to a row-partitioned table
  • The input data file is located at each back-end server.
P
Example 12Loading data to a table with LOB columns
  • The example loads data to both LOB column structure base tables and LOB columns at the same time.
  • The table is row partitioned and the example loads data in units of RDAREAs.
  • The input data file is located at the back-end server that contains the RDAREAs subject to data loading.
P
Example 13Loading data to a table with LOB columns
  • The example uses a LOB column input file.
  • The table is row partitioned and the example loads data in units of tables.
  • The input data file is located at the front-end server.
P
Example 14Loading data using EasyMT
  • The table is row-partitioned and the example loads data in units of tables.
  • The input data file is located at the front-end server.
P
Example 15Loading data to a table with repetition columns
  • The table is row partitioned and the example loads data in units of tables.
  • The table has a cluster key index and the input data is sorted by the cluster key values; therefore, the example specifies an option to not check the sequence of cluster key values.
P
Example 16Loading data to a table using a plug-in
  • The table contains columns of SGMLTEXT type.
  • The input data file is in the DAT format.
  • The example uses a column structure information file to specify information about a constructor function.
P
Example 17Loading data to a table using a plug-in
  • The table contains columns of GEOMETRY type.
  • The input data file is in the fixed-size data format.
  • The example uses a column structure information file to specify information about a constructor function.
P
Example 18Loading data to a table using a plug-in
  • The table contains columns of SGMLTEXT type and LOB columns.
  • The example directly specifies the LOB parameters and the name of the LOB input file in the input data file, and provides a separate LOB input file.
P
Example 19Loading data to a table using a plug-in
  • The table contains columns of SGMLTEXT type and LOB columns.
  • The example loads data only to the LOB column structure base table at first, then loads data to the LOB columns concurrently at each back-end server.
  • The example directly specifies the LOB parameters and the name of the LOB input file in the input data file, and provides a separate LOB input file
P

S: HiRDB/Single Server

P: HiRDB/Parallel Server

Organization of this section
5.13.1 HiRDB/Single Server
5.13.2 HiRDB/Parallel Server