What could be the reason, if the TEST_TBS tablespace does not include autoextensible data files?

An online tablespace, TEST_TBS, is full and you realize that no server-managed tablespace
threshold alerts were generated for the TEST_TBS tablespace. What could be the reason, if
the TEST_TBS tablespace does not include autoextensible data files?

An online tablespace, TEST_TBS, is full and you realize that no server-managed tablespace
threshold alerts were generated for the TEST_TBS tablespace. What could be the reason, if
the TEST_TBS tablespace does not include autoextensible data files?

A.
TEST_TBS is a small file tablespace.

B.
TEST_TBS is a bigfile tablespace (BFT).

C.
TEST_TBS is the default temporary tablespace.

D.
TEST_TBS is a dictionary-managed tablespace.



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Jake from SF

Jake from SF

D is correct:

https://oracle-base.com/articles/8i/locally-managed-tablespaces

Extent size within LMTs is determined by the UNIFORM and AUTOALLOCATE clauses. If UNIFORM is specified, all extents within the tablespace will be the same size, with 1M being the default extent size. The AUTOALLOCATE clause allows you to size the initial extent leaving Oracle to determine the optimum size for subsequent extents, with 64K being the minimum.