This command moves/renames a data file online. Let’s evaluate:
A. DML may be performed on tables with one or more extents in this data file during the execution of this command.
Explanation:True. Introduced in 12c and refined in 23ai, MOVE DATAFILE is an online operation, allowing DML (e.g., INSERT, UPDATE) on tables within the file. Oracle ensures consistency via redo and undo.
Mechanics:The file is copied to the new location/name while tracking changes, then switched atomically.
Practical Use:Minimizes downtime in production systems.
B. If Oracle Managed Files (OMF) is used, then the file is renamed but moved to DB_CREATE_FILE_DEST.
Explanation:False. With OMF, omitting the TO clause would place the file in DB_CREATE_FILE_DEST, but here, TO '\u01/sales01.dbf' explicitly specifies the target, overriding OMF defaults.
Mechanics:OMF only applies if the destination is unspecified (e.g., MOVE DATAFILE ... without TO).
Why Incorrect:Explicit path trumps OMF behavior.
C. The tablespace containing SALES1.DBF must be altered READ ONLY before executing the command.
Explanation:False. READ ONLY isn’t required; the operation is online and supports active use.
Why Incorrect:Conflicts with Oracle’s online move feature.
D. The file is renamed and stored in the same location.
Explanation:True. The command renames /u01/sales1.dbf to /u01/sales01.dbf (correcting \u01 to /u01 as a Windows/Unix typo), keeping it in /u01/. REUSE allows overwriting if sales01.dbf exists.
Mechanics:File is copied and renamed in-place within the same filesystem directory.
E. The tablespace containing SALES1.DBF must be altered OFFLINE before executing the command.
