Database Reference
In-Depth Information
9 AND TS2_NAME IN ('USERS','INDEX_TBS')
10* )
SQL> /
no rows selected
If you were to plan to transport only the USERS tablespace, then you would see the fol-
lowing error:
SQL> SELECT ts1_name, ts2_name, reason
2 FROM SYS.TS_PITR_CHECK
3 WHERE (
4 TS1_NAME IN ('USERS')
5 AND TS2_NAME NOT IN ('USERS')
6 )
7 OR (
8 TS1_NAME NOT IN ('USERS')
9 AND TS2_NAME IN ('USERS')
10* )
SQL> /
TS1_NAME TS2_NAME
---------- ----------
REASON
---------------------------------------------------------------------
USERS INDEX_TBS
Tables and associated indexes not fully contained in the recovery set
Lost Objects
When you perform a TSPITR recovery, it is possible that you will lose objects in the
tablespace that were created after the point in time to which you restore the tablespace.
You can export these objects before the TSPITR with Oracle Data Pump and then import
them after the TSPITR has completed.
By querying the view TS_PITR_OBJECTS_TO_BE_DROPPED , you can determine which
objects will be lost, as shown in this example:
SQL> SELECT OWNER, NAME, TABLESPACE_NAME,
2 TO_CHAR(CREATION_TIME, 'YYYY-MM-DD:HH24:MI:SS')
3 FROM TS_PITR_OBJECTS_TO_BE_DROPPED
4 WHERE TABLESPACE_NAME IN ('USERS')
5 AND CREATION_TIME >
6 TO_DATE('07-OCT-13:22:35:30','YY-MON-DD:HH24:MI:SS')
7 ORDER BY TABLESPACE_NAME, CREATION_TIME;
Search WWH ::




Custom Search