In an environment that uses the inner replica facility, if consistency is lost between the definitions of the HiRDB files constituting an RDAREA and the entity for the following reasons, this function enables you to copy the configuration information for the entity.
- An RDAREA was expanded or re-initialized, and then the entity was adjusted in an environment in which the number of component files, the page length, the segment size, or the number of segments does not match in the inner replica group.
- There was inconsistency in the configuration information between the original and replica RDAREAs, but another replica RDAREA was defined on the basis of the replica RDAREA structure files (in this case, the configuration information is based on the original RDAREA definitions).
- Prerequisites
- To copy configuration information for an RDAREA, the target RDAREA must be in command shutdown and closed status. If the target RDAREA is a shared RDAREA, it must be in command shutdown and closed status at all back-end servers.
- When copying the configuration information for an RDAREA, make sure that the number of the HiRDB files constituting the RDAREAs does not exceed the specified maximum value (pd_max_file_no). If this value is exceeded, you must use the pdchgconf command to change the system common definition or terminate the HiRDB system normally and then change the system common definition.
- When configuration information is copied for a shared RDAREA, the system assumes that the configuration information has been copied for that RDAREA at every back-end server (even if configuration information has not been copied for a back-end server, the system assumes that the configuration information has been copied). If the maximum permissible number of HiRDB files constituting RDAREAs is exceeded at any of the back-end servers, the configuration information cannot be copied for the shared RDAREA at all.