Nonstop Database, HiRDB Version 9 System Operation Guide

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

12.2.1 Preparations for migrating a stored procedure to another HiRDB system

Organization of this subsection
(1) Limitations
(2) Information to be migrated
(3) Rules for migration
(4) Migration procedure

(1) Limitations

A procedure (stored procedure) specified in CREATE TYPE cannot be migrated to another HiRDB system.

(2) Information to be migrated

The following information is migrated:

(a) Procedure for migrating table definition information and table data

The table definition information and the table data for the table that is used by a stored procedure are migrated to the target system; for the migration procedure, see 12.1 Migrating a table to another HiRDB system.

This procedure can be skipped if the target system already contains the table definition information and table data for the table that is used by the stored procedure.

(b) Procedure for migrating the stored procedure

The dictionary import/export utility (pdexp command) to used to migrate a stored procedure from the data dictionary LOB RDAREAs to the target HiRDB system. The following figure shows the procedure for migrating a stored procedure using the dictionary import/export utility.

Figure 12-9 Migration of a stored procedure with the dictionary import/export utility

[Figure]

(3) Rules for migration

  1. The stored procedure and the table definition information cannot be migrated at the same time. The table definition information should be migrated first, then the stored procedure can be migrated.
  2. Before migration is performed, the table that is to be migrated and a schema for the stored procedure must be defined in the target system.
  3. Before migration is performed, the data dictionary LOB RDAREAs must be created in the target system.

(4) Migration procedure

The following figure provides an overview of the procedure for migrating a stored procedure.

Figure 12-10 Procedure for migrating a stored procedure

[Figure]