What is the main benefit of performing an ADMIN_MOVE_TABLE operation in multiple steps?
What is the main benefit of performing an ADMIN_MOVE_TABLE operation in multiple steps?
Performing an ADMIN_MOVE_TABLE operation in multiple steps allows the user to control when the table will be offline. By executing the table move one step at a time, particularly controlling the SWAP phase, the user can decide the precise moment the table is taken offline, minimizing disruption.
The answer C is correct. "There are two ways of calling the stored procedure: using the MOVE command to execute all the operations at one time; or by using the individual commands to execute the table move one step at a time. The main advantage of this second method is that you control when the SWAP phase actually occurs, thereby determining when the table is briefly taken offline." Reference: https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.sql.rtn.doc/doc/r0055069.html
The answer D is correct, you can use "ADMIN_MOVE_TABLE" in HADR environment. By, example, you can use ADMIN_MOVE_TABLE instead of REORG in HADR environment, see reference : https://www.ibm.com/support/pages/reorg-replay-may-cause-performance-issue-hadr-standby
The answer A is not correct, because,the swap phase applies an eXclusive-lock to the source table and target table. Indeed, during the swap phase, we request an eXclusive lock on both the source table and the target table. Once we havethe lock, we performa final replay to make sure the source and target table have the samedata. Since we have the eXclusive lock at this point, no new changes should have beenmade to the source table. The answer B is not correct, because, ADMIN_MOVE_TABLE create temporary database objects. See reference : https://www.ibm.com/developerworks/data/library/techarticle/dm-1306adminmovetable/index.html https://www.dbisoftware.com/media/IBM-Ergin-Babani-DB2LUW-Online-Table-Moves.pdf