Notes

After changing RDAREAs from a HiRDB single server configuration to a HiRDB parallel server configuration, be sure to terminate the HiRDB single server configuration normally.
If you partition a row-partitioned table into multiple back-end servers, the system does not partition its non-partitioning key indexes, resulting in a mismatch in the non-partitioning key indexes when the HiRDB parallel server configuration is started. Therefore, redefine such non-partitioning key indexes so that they are partitioned into multiple back-end servers.
If you are placing a dictionary server in another (added) server machine after migrating from a HiRDB single server configuration to a HiRDB parallel server configuration, move the master directory RDAREAs, data directory RDAREAs, data dictionary RDAREAs, data dictionary LOB RDAREAs, registry RDAREAs, and registry LOB RDAREAs to the server machine where the dictionary server is located before starting the HiRDB parallel server configuration.
If you are changing the server structure specifying RDAREAs, and the RDAREA for the table is different from the RDAREA for the table's indexes, place each RDAREA in the same server machine. However, you should delete a non-partitioned index of a row-partitioned table beforehand.
If a stored procedure or a user-defined stored function is registered, all such stored procedures and user-defined stored functions become disabled after the migration. For any stored procedures or user-defined stored functions that have been disabled after the migration, you need to re-create all SQL objects by starting the HiRDB parallel server configuration and executing ALTER PROCEDURE (with ALL specified) or ALTER ROUTINE. For details about ALTER PROCEDURE and ALTER ROUTINE, see the HiRDB Version 9 SQL Reference.
If the registry facility is used, re-register the registry manipulation stored procedure after the migration using the registry facility initialization utility (pdreginit) specifying -k renew. If you are using the following plug-in, re-register the plug-in by executing the pdplgrgst -a command:
- HiRDB Image Search Plug-in
During the migration, do not change the HiRDB identifier in the system common definition pd_system_id.
If generations of a HiRDB file system area are managed, its RDAREAs cannot be changed from a HiRDB single server configuration to a HiRDB parallel server configuration (an attempt results in an error).
While shared tables and shared indexes are defined, do not change RDAREAs from a HiRDB single server configuration to a HiRDB parallel server configuration. Before you can change the configuration, you must delete all shared tables and shared indexes defined in HiRDB.

7.10.4 Notes