8.1.4 Reloading to a table

Organization of this subsection
(1) What is reloading to a table?
(2) Migrating data into another table
(3) Modifying table partitioning conditions
(4) Reloading to a table with LOB columns or abstract data type columns provided by a plug-in (LOB attribute)
(5) Reloading a table for which a character set has been defined
(6) Reloading compressed tables
(7) Reloading tables with the FIX attribute for which reserved columns are defined
(8) Using a utility special unit
(9) Reloading with the synchronization point specification

(1) What is reloading to a table?

Table reorganization involves saving table data into a file and then storing the data from the file back into the table. The process for storing data from a file back into a table is called reloading a table.

You can reload a table in units of tables or RDAREAs (applicable to row-partitioned tables).

The figure below provides an overview of reloading a table.

Figure 8-9 Overview of reloading a table

[Figure]

(2) Migrating data into another table

For details about how to migrate data into another table, see 8.1.3 Unloading a table.

(3) Modifying table partitioning conditions

For details about how to modify table partitioning conditions, see 8.1.3 Unloading a table.

(4) Reloading to a table with LOB columns or abstract data type columns provided by a plug-in (LOB attribute)

As with table reorganization, you can reload to a LOB column structure base table and LOB columns at the same time or separately.

(5) Reloading a table for which a character set has been defined

When a table for which a character set has been defined is reloaded, whether pdrorg performs character code conversion depends on the character codes of the data in the unload data file. If the data in the unload data file uses the same character codes as in the character set-defined column, pdrorg stores the data as is in the database without performing character code conversion. If the data in the unload data file uses different character codes, pdrorg converts the character codes and then stores the data in the database.

(6) Reloading compressed tables

To reload compressed tables, if data in the unload data files is compressed, pdrorg stores the data as is in the database. If data in the unload data files is not compressed, pdrorg compresses the data, and then stores it in the database.

If an error occurred during table reorganization and the unload data file containing compressed data (the file unloaded by using pdrorg -k rorg) is to be reloaded, the compression settings (whether data is compressed and the split compression size) for the table must be the same between the source from which the data is unloaded and the target to which the data is reloaded. If the table contains any column whose compression settings do not match, pdrorg issues the KFPL15327-E message and terminates with an error.

(7) Reloading tables with the FIX attribute for which reserved columns are defined

If a table with the FIX attribute for which reserved columns are defined is to be reloaded, but the reserved column settings for the table differ between the source from which the data is unloaded and the target to which the data is reloaded, pdrorg issues the KFPL25343-E message and terminates abnormally. The table can be reloaded if its reserved column settings are the same between the source from which the data is unloaded and the target to which the data is reloaded, and the execution conditions are satisfied. For details about the execution conditions, see 8.4.3 Whether reloading is permitted when the table definitions of unload table and reload table do not match.

(8) Using a utility special unit

For details about how to use a utility special unit, see 8.1.2 Reorganizing a table.

(9) Reloading with the synchronization point specification

For details about how to reload with the synchronization point specification, see 8.1.2 Reorganizing a table.