- Executor: HiRDB administrator, DBA privilege holder, and table owner
Data can be moved to another table by executing the pdrorg or pdload command. The migration method depends on whether or not the migration source table and the migration target table have identical definitions. The table definitions are considered to be identical when all the following are true:
- Both are either FIX or non-FIX tables.
- They have the same number of columns.
- Their column definitions are the same (same column names, data types, NULL or NOT NULL, data sizes, sequence of column definitions, repetitions counts).
Figure 13-83 shows how to migrate data to a table with the same table definition as the source table. Figure 13-84 shows how to migrate data to a table with a different table definition.
Figure 13-83 Migrating data to a table with the same table definition
![[Figure]](figure/zu130030.gif)
Figure 13-84 Migrating data to a table with a different table definition
![[Figure]](figure/zu130040.gif)
- Important
- After data migration, execute the optimizing information collection utility (pdgetcst command) for the migration destination table if necessary. For details about whether or not execution of the optimizing information collection utility is required, see the manual HiRDB Version 8 Command Reference.
- If you wish to migrate to another HiRDB system a table that has columns of the abstract data type, you must apply the constructor parameter reverse generation function when you use the database reorganization utility (pdrorg command) to unload data of the abstract data type.
- Organization of this section
- 13.16.1 Example 1: Migrating data to a table with the same table definition
- 13.16.2 Example 2: Migrating data to a table with a different table definition
- 13.16.3 Specification examples of column structure information files