Oracle table recovery - unpredictable instance size

Hi everyone,

CV supports table level recovery for Oracle database.

But the problem is that we’re not able to assess the datafile size needs to be restored.

So table recovery can cause unexpected issue like lack of space while doing a restoration.

It says all related tablespaces are restored if the tablespace includes table to recover is not self-contained.

EXECUTE DBMS_TTS.TRANSPORT_SET_CHECK('sales_dept', TRUE);

SELECT * FROM TRANSPORT_SET_VIOLATIONS;

So we performed below procedure/command to validate how many tablespaces are dependent.

For our customer’s prod environment, only two tablespaces need to be restored for table recovery on top of the targeted tablespace. But the result was totally different what we expected.

A table recovery required almost all of the tablespace restore to an auxiliary instance.

Why CV restore so many tablespace just for a table recovery?

(Oracle DBA says there’s no reason these tablespaces need to be restored. For “Recover table” command since 12c requires only a tablespace restore except default tablespaces.   But we use Oracle duplicate way instead)

Any advice will be helpful for me.

Thanks