What would you conclude from this?

View the Exhibit and examine the content. ALLOCATED_SPACE and FREE_SPACE are not
matching with the TABLESPACE_SIZE value.

What would you conclude from this?

View the Exhibit and examine the content. ALLOCATED_SPACE and FREE_SPACE are not
matching with the TABLESPACE_SIZE value.

What would you conclude from this?

A.
A new temporary file is added to the tablespace.

B.
The temporary space was not sufficient for sort operations.

C.
The temporary space allocated to large sort operations is not deallocated.

D.
TEMP_L is a default temporary tablespace because the numbers show some overhead on this
tablespace.



Leave a Reply 2

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


Carlos

Carlos

http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces007.htm

Shrinking a Locally Managed Temporary Tablespace
Large sort operations performed by the database may result in a temporary tablespace growing and occupying a considerable amount of disk space. After the sort operation completes, the extra space is not released; it is just marked as free and available for reuse. Therefore, a single large sort operation might result in a large amount of allocated temporary space that remains unused after the sort operation is complete. For this reason, the database enables you to shrink locally managed temporary tablespaces and release unused space.

You use the SHRINK SPACE clause of the ALTER TABLESPACE statement to shrink a temporary tablespace, or the SHRINK TEMPFILE clause of the ALTER TABLESPACE statement to shrink a specific tempfile of a temporary tablespace. Shrinking frees as much space as possible while maintaining the other attributes of the tablespace or tempfile. The optional KEEP clause defines a minimum size for the tablespace or tempfile.

L. Zhu

L. Zhu

C is right