Why should you back up a duplicated tablespace after a TSPITR is complete?
A.
The tablespace cannot be duplicated or restored to any point in time after the duplication.
B.
The tablespace cannot be duplicated or restored to the point in time before the duplication.
C.
The entire database cannot be restored after a TSPITR, so a backup is required.
D.
You cannot bring the tablespace online until it�s been backed up.
E.
There is no requirement to do so, as RMAN will back up the tablespace after the TSPITR.
Backing Up Recovered Tablespaces After TSPITR
It is very important that you backup recovered tablespaces immediately after TSPITR is completed.
After you perform TSPITR on a tablespace, you cannot use backups of that tablespace from before the TSPITR was completed and the tablespace put back on line. If you start using the recovered tablespaces without taking a backup, you are running your database without a usable backup of those tablespaces. For this example, the users and tools tablespaces must be backed up, as follows:
RMAN> BACKUP TABLESPACE users, tools;
You can then safely bring the tablespaces online, as follows:
RMAN> SQL “ALTER TABLESPACE users, tools ONLINE”;
Your recovered tablespaces are now ready for use.