在生产数据库中，由于误操作导致重要表格被清空。本文探讨了如何使用表空间时间点恢复（TSPITR）来恢复丢失的数据，而不会影响到其他模式中的对象。
130
In your production database, users report that they are unable to generate reports on an important table
because it does not contain any data. While investigating the reason, you realize that another user
executed the TRUNCATE TABLE command, which accidentally caused the data to be lost. Now you want
to recover the lost data of the table without affecting objects in other schemas.
Which method must you use to recover the lost data?
A. Complete Recovery with online redo log
B. Complete Recovery with archived redo log
C. Tablespace Point-in-Time Recovery (TSPITR)
Section: (none)
Explanation
Explanation/Reference:
Explanation:
RMAN TSPITR is most useful for the following situations:
– You want to recover data lost after DDL operations that change the structure of tables.
You cannot use Flashback Table to rewind a table to before the point of a structural change
such as a truncate table operation.
In your production database, users report that they are unable to generate reports on an important table
because it does not contain any data. While investigating the reason, you realize that another user
executed the TRUNCATE TABLE command, which accidentally caused the data to be lost. Now you want
to recover the lost data of the table without affecting objects in other schemas.
Which method must you use to recover the lost data?
A. Complete Recovery with online redo log
B. Complete Recovery with archived redo log
C. Tablespace Point-in-Time Recovery (TSPITR)
D. Incomplete Recovery with system change number (SCN)
Section: (none)
Explanation
Explanation/Reference:
Explanation:
RMAN TSPITR is most useful for the following situations:
– You want to recover data lost after DDL operations that change the structure of tables.
You cannot use Flashback Table to rewind a table to before the point of a structural change
such as a truncate table operation.
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
