1Z0-062 · Question #114
Examine these two statements: Which three are true about the MRKT tablespace?
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. A BIGFILE tablespace contains exactly one data file, does not store relative file numbers in rowids, and setting it as the database default reassigns the default tablespace for affected users.
Question
Examine these two statements:
Which three are true about the MRKT tablespace?
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
(19 responses)- A11% (2)
- B11% (2)
- C79% (15)
Why each option
A BIGFILE tablespace contains exactly one data file, does not store relative file numbers in rowids, and setting it as the database default reassigns the default tablespace for affected users.
Whether a tablespace is smallfile or bigfile is determined by the BIGFILE or SMALLFILE keyword in the CREATE TABLESPACE statement, not by the size of the data file.
While a tablespace with no contents can be dropped, this choice is misleading in context; a tablespace that has been set as the default or contains objects is not simply dropped, and the question's focus is on properties of a bigfile tablespace.
When a new default permanent tablespace is assigned at the database level, Oracle automatically updates the default tablespace attribute for any users whose prior default was the old database-level default, redirecting them to the newly specified tablespace.
A BIGFILE tablespace is architecturally restricted to a single data file regardless of size; Oracle does not permit additional data files to be added to a bigfile tablespace.
In a BIGFILE tablespace, rowids use the absolute file number rather than the relative file number because only one data file exists per tablespace, making the relative file number field in the rowid unused.
Concept tested: Bigfile tablespace properties 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.
