1Z0-082 · Question #109
Which two statements are true about views used for viewing tablespace and datafile information? (Choose two.)
The correct answer is B. V$TABLESPACE displays information that is contained in the controlfile about tablespaces E. A datafile can be renamed when the database is in MOUNT state and the new file name is. See the full explanation below for the reasoning.
Question
Which two statements are true about views used for viewing tablespace and datafile information? (Choose two.)
Options
- ATablespace free space can be viewed in V$TABLESPACE
- BV$TABLESPACE displays information that is contained in the controlfile about tablespaces
- CV$TABLESPACE displays information about tablespaces contained in the data dictionary
- DTablespace free space can be viewed in DBA_TABLESPACES
- EA datafile can be renamed when the database is in MOUNT state and the new file name is
How the community answered
(43 responses)- A5% (2)
- B77% (33)
- C14% (6)
- D5% (2)
Topics
Community Discussion
3B and E, and this is one of those questions where Oracle trips people up on purpose by mixing the V$ views with the DBA_ views. V$TABLESPACE reads directly from the controlfile, not the data dictionary, so C is wrong right out of the gate, and V$TABLESPACE has never exposed free space, that has always lived in DBA_FREE_SPACE, which kills A and D in the same swing. For E, renaming a datafile the old-fashioned way with ALTER DATABASE RENAME FILE requires the database to be in MOUNT state, and that behavior has been consistent since at least 8i, nothing changed there in 19c or 21c. MOS Note 1547098.1 walks through the full procedure if you want to see Oracle's own steps side by side with the online method introduced for locally managed tablespaces later.
B and E are locked, bank them and move on, this one should cost you under 45 seconds. V$TABLESPACE pulls straight from the controlfile, not the data dictionary, which is the exact trap Oracle sets by listing DBA_TABLESPACES in the distractors, and renaming a datafile with ALTER DATABASE RENAME FILE requires MOUNT state because the database must be closed to users but the controlfile still accessible.
B and E are the correct pair, and the Oracle documentation makes the distinction clear: V$ views, including V$TABLESPACE, draw their data from the control file and from memory structures, not from the data dictionary, which is exactly what option B states. Option C is the trap because it flips that source, and many people confuse the V$ namespace with DBA_ views, which do query the data dictionary. For free space specifically, the Oracle Database Reference points you to DBA_FREE_SPACE, not DBA_TABLESPACES and certainly not V$TABLESPACE, which eliminates A and D cleanly. On my actual exam I paused on E because the option text was cut off in the interface just like it appears here, but the underlying concept is well-covered in the Administering Oracle Database guide: renaming a datafile with ALTER DATABASE RENAME FILE is a control-file-level operation that requires the database to be in MOUNT state, so the file is not being accessed by any instance while the rename is recorded.