1Z0-060 · Question #121
Examine these two statements: Which three are true about the MRKT tablespace? (Choose three.)
The correct answer is C. Users who were using the old default tablespace will have their default tablespaces changed to D. No more data files can be added to the tablespace. E. The relative file number of the tablespace is not stored in rowids for the table rows that are stored. This question tests knowledge of BigFile tablespace properties and the effects of setting a tablespace as the database default.
Question
Examine these two statements:
Which three are true about the MRKT tablespace? (Choose three.)
Exhibit
Options
- AThe MRKT tablespace is created as a small file tablespace, because the file size is less than the
- BThe MRKT tablespace may be dropped if it has no contents.
- CUsers who were using the old default tablespace will have their default tablespaces changed to
- DNo more data files can be added to the tablespace.
- EThe relative file number of the tablespace is not stored in rowids for the table rows that are stored
How the community answered
(26 responses)- A8% (2)
- B15% (4)
- C77% (20)
Why each option
This question tests knowledge of BigFile tablespace properties and the effects of setting a tablespace as the database default.
BigFile tablespaces are characterized by supporting a single very large file (up to 128TB), not by having a file size below a threshold - a small file size describes a SmallFile tablespace instead.
MRKT cannot be dropped while it is designated as the current default tablespace; the default must first be reassigned to another tablespace even if MRKT is empty.
When a new default tablespace is set via ALTER DATABASE DEFAULT TABLESPACE, Oracle automatically reassigns the default tablespace for any user whose prior default was the old default, so those users are migrated to MRKT without manual intervention.
A BigFile tablespace contains exactly one data file by definition; its structure prohibits adding additional data files, so no more files can be added to MRKT.
BigFile tablespaces use absolute file numbers rather than relative file numbers in extended rowids, so the relative file number field is unused and not stored for rows in a BigFile tablespace.
Concept tested: BigFile tablespace characteristics and default tablespace assignment
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-tablespaces.html
Topics
Community Discussion
No community discussion yet for this question.
