You want to recover one or more tablespaces to a point in time older than the rest of the database.
Which of the following are the recovery situations in which tablespace Point-in-Time Recovery
(TSPITR) should be used? Each correct answer represents a part of the solution. Choose all that
apply.

A.
To recover a tablespace that contains rollback segments.

B.
To recover a table that has become logically corrupted.

C.
To recover a DML statement that has affected only a subset of the database.

D.
To recover a tablespace on a very large database.

Explanation:
Following are the situations in which tablespace Point-in-Time Recovery (TSPITR) should be used:
To recover from an erroneous drop or truncate table operation.
To recover a table that has become plausibly corrupted.
To recover from an erroneous batch job or other DML statement that has affected only a subset of
the database.
To recover one independent schema to a point dissimilar from the respite of a physical database (in
cases where there are multiple
independent schemas in individual tablespaces of one physical database).
To recover a tablespace on a very large database (VLDB) instead of restoring the whole database
from a backup and carrying out a
complete database roll-forward.
Point-in-time recovery is a technique used to back up any database object or recover any database
object to a particular target SCN. When
the target SCN is specified using the date and time, it is known as time-based recovery.
Following types of point-in-time recoveries are known:
Tablespace point-in-time recovery (TSPITR)
Database point-in-time recovery (DBPITR)
Answer A is incorrect. Tablespace Point-in-Time Recovery cannot be used on the SYSTEM
tablespace, an UNDO tablespace, or any
tablespace that contains rollback segments.