7.15.4 Notes
- After RDAREAs are integrated, the definition of the replica RDAREA is deleted. The HiRDB files for the original RDAREA existing before the integration are also deleted.
- After integrating RDAREAs, delete the generation information for the HiRDB file system area from the original RDAREA's HiRDB files.
- After integrating RDAREAs, use pdcopy to make a backup of the target RDAREA, master directory RDAREA, and data dictionary RDAREA.
- If a replica RDAREA stores a referenced table, referencing table, or check constraint table, integrate RDAREAs while no table is in check pending status in the replica RDAREA and in any RDAREA storing a table that has a reference relationship with the table in the replica RDAREA. If any of the applicable tables is in check pending status, use pdconstck to perform integrity checking and then release the check pending status.
- In an RDAREA storing a referencing table or check constraint table, if only the table information in the original RDAREA is in check pending status, that table information is placed in non-check pending status as a result of RDAREA integration, but the data dictionary table is not released from check pending status. When the data dictionary table has not been released from check pending status, use pdconstck to perform integrity checking and then release the data dictionary table from the check pending status.
- You cannot integrate an in-memory RDAREA. To do so, first release the RDAREA from memory, and then integrate it.