7.7.5 Notes

  1. Once you start moving RDAREAs, do not execute any UAP or utility until the HiRDB restart has been completed. If you do not restart HiRDB after moving RDAREAs, operation cannot be guaranteed.
  2. You must delete the HiRDB file that constitutes the moved source RDAREA and create the HiRDB file that constitutes the target RDAREA. The path name of the HiRDB file that constitutes the target RDAREA must be the same as the source HiRDB file.
  3. Once an RDAREA has been moved, any routine using a table in the source RDAREA will be disabled. You must re-create such routines with the ALTER ROUTINE SQL statement.
  4. After moving RDAREAs, use pdcopy to make a backup of the moved RDAREAs, master directory RDAREA, and data dictionary RDAREA.
  5. In-memory RDAREAs cannot be moved. You must first release the RDAREA from in-memory and then move it.
  6. If you move an RDAREA containing a sequence generator, you must also move all RDAREAs storing tables that use the sequence generator at the same time. If you place these RDAREAs on separate servers, communication processing will be required each time the sequence generator is used, which will affect performance adversely.