7.6.4 Notes
- If you delete an RDAREA, the HiRDB files used in that RDAREA are also deleted.
- If an error occurs during RDAREA deletion process, the RDAREA subject to deletion is not restored. In this case, re-execute the remove rdarea statement on the corresponding RDAREA because the HiRDB files may have already been deleted.
- Once an RDAREA has been deleted, you need to modify the pdbuffer operand in the system common definitions after HiRDB terminates normally. Otherwise, more memory is used than is actually needed. For details about the system common definitions, see the HiRDB Version 8 System Definition.
- If you are deleting a replica RDAREA and its inner replica attribute is the current RDAREA, you must use the pddbchg command to change it to a sub-RDAREA.
- If you have deleted a replica RDAREA, use pdcopy to make a backup of the original RDAREA, master directory RDAREA, and data dictionary RDAREA.
- If you have deleted all replica RDAREAs of an original RDAREA, the inner replica facility is no longer applicable to that RDAREA.
- If a data dictionary RDAREA containing a database state analyzed table and a database management table is deleted, the database state analyzed table and database management table are also deleted.
- If an RDAREA stores a referencing table or check constraint table, and if it uses the inner replica facility, and if only the table information in its specific replica RDAREA is in check pending status, and if this replica RDAREA is deleted, all of its generations are placed in non-check pending status but the data dictionary table is not released from check pending status. When the data dictionary table is not released from check pending status, use pdconstck to perform integrity checking and then release the data dictionary table from check pending status.