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.
Which two statements are true regarding the MRKT tablespace? (Choose two.)
A.
No more data files can be added to the tablespace.
B.
Segment space is managed by free lists in the tablespace.
C.
A user created without being assigned a default tablespace uses this tablespace.
D.
The tablespace can be dropped with the current setting with segments present in it.
A. BIGFILE can have only one data file. A is correct
B. Oracle Database automatically creates a locally managed tablespace with automatic segment space management. B is incorrect
C. ALTER DATABASE DEFAULT TABLESPACE MRKT; Setting the default space，Later user created data will be placed in the tablespace
D. The default space in use cannot be dropped
A bigfile tablespace is a tablespace with a single, but very large (up to 4G blocks) datafile. Traditional smallfile tablespaces, in contrast, can contain multiple datafiles, but the files cannot be as large.
Bigfile tablespaces are supported only for locally managed tablespaces with automatic segment space management, with three exceptions: locally managed undo tablespaces, temporary tablespaces, and the SYSTEM tablespace.
Bigfile tablespaces are intended to be used with Automatic Storage Management (ASM) or other logical volume managers that supports striping or RAID, and dynamically extensible logical volumes.
Creating Tablespaces –
Before you can create a tablespace, you must create a database to contain it. The primary tablespace in any database is the SYSTEM tablespace, which contains information basic to the functioning of the database server, such as the data dictionary and the system rollback segment.