There are a lot of operational considerations that need to be taken into account when using the ADMIN_MOVE_TABLE() procedure. For example, moving a table during low activity is preferred. Other considerations are as follows:
- Avoid concurrent moves into the same tablespace.
- Run during low activity on the source table, if possible.
- Run using multi-step operations. Execute the REPLY phase several times, to keep the STAGE table small, and then run SWAP when activity is low. Run INIT and COPY any time.
- Always consider an offline move first.
- The staging table is populated using triggers on the source. Keep in mind that some DDL and utilities can occur without firing a trigger. A new table-level state flag prevents these ...