1Z0-052 · Question #7
Which two statements are true regarding the MRKT tablespace? (Choose two.) SQL> CREATE BIGFILE TABLESPACE MRKT 2 DATAFILE '/u01/app/oracle/oradata/orcl/mrkt.dbf' size 10M LOGGING 3 EXTENT MANAGEMENT…
The correct answer is A. No more data files can be added to the tablespace. C. A user created without being assigned a default tablespace uses this tablespace. A BIGFILE tablespace is restricted to exactly one datafile, and designating it as the database default means users created without an explicit default tablespace will be assigned to it.
Question
Which two statements are true regarding the MRKT tablespace? (Choose two.) SQL> CREATE BIGFILE TABLESPACE MRKT 2 DATAFILE '/u01/app/oracle/oradata/orcl/mrkt.dbf' size 10M LOGGING 3 EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; Tablespace created. SQL> ALTER DATABASE DEFAULT TABLESPACE MRKT; Database altered.
Options
- ANo more data files can be added to the tablespace.
- BSegment space is managed by free lists in the tablespace.
- CA user created without being assigned a default tablespace uses this tablespace.
- DThe tablespace can be dropped with the current setting with segments present in it.
How the community answered
(40 responses)- A75% (30)
- B18% (7)
- D8% (3)
Why each option
A BIGFILE tablespace is restricted to exactly one datafile, and designating it as the database default means users created without an explicit default tablespace will be assigned to it.
By definition, a BIGFILE tablespace can contain only one datafile (or tempfile), so after creation no additional datafiles can be added - this is the fundamental architectural difference between BIGFILE and SMALLFILE tablespaces.
The CREATE statement specifies SEGMENT SPACE MANAGEMENT AUTO, which uses bitmaps to track free space within segments; free lists are only used with SEGMENT SPACE MANAGEMENT MANUAL.
The ALTER DATABASE DEFAULT TABLESPACE MRKT command sets MRKT as the database-wide default, so any subsequently created user who is not assigned an explicit DEFAULT TABLESPACE clause will automatically use the MRKT tablespace.
A tablespace that contains segments cannot be dropped without specifying the INCLUDING CONTENTS clause; issuing DROP TABLESPACE without it will return an error when segments exist.
Concept tested: Oracle BIGFILE tablespace single datafile restriction and default tablespace
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.