Table 5-44 provides a list of the examples of using the database load utility.
Example | Description | Classification |
---|
Example 1 | Loading 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 2 | Loading data to a row-partitioned table in units of tables | S |
Example 3 | Loading data to a row-partitioned table in units of RDAREAs | S |
Example 4 | Loading data to a row-partitioned table in units of tables
- The input data file is located in a utility special unit.
| S |
Example 5 | Loading 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 6 | Loading data to a table with LOB columns
- The example loads data only to the LOB column structure base table.
| S |
Example 7 | Loading data to a table with LOB columns
- The example loads data only to the LOB columns.
| S |
Example 8 | Loading 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 9 | Loading data to a non-row-partitioned table
- The input data file is located at the front-end server.
| P |
Example 10 | Loading data to a row-partitioned table
- The input data file is located at the front-end server.
| P |
Example 11 | Loading data to a row-partitioned table
- The input data file is located at each back-end server.
| P |
Example 12 | Loading 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 13 | Loading 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 14 | Loading 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 15 | Loading 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 16 | Loading 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 17 | Loading 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 18 | Loading 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 19 | Loading 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 |