At the request of a user, you issue the following command to restore a dropped table:
flashback table BIN$F2JFfMq8Q5unbC0ceE9eJg==$0 to before drop;
Later, the user notifies you that the data in the table seems to be very old and out of date. What
might be the problem?
A.
Because a proper range of SCNs was not specified, the wrong data was restored.
B.
A proper range of timestamps was not specified, so the wrong data was restored.
C.
A previous Flashback Drop operation had been performed, resulting in multiple versions of the
table being stored in the Recycle Bin.
D.
Either option A or B could be correct. Not enough information was provided to determine which.
E.
None of the above.
E. A Flashback Drop operation restores dropped objects from the Recycle Bin. It does not use SCN or timestamp ranges, so options A, B, and D are incorrect. Also, Flashback Drop operations don’t create objects in the Recycle Bin (they move them out of the Recycle Bin), so C is incorrect. The likely cause is that multiple versions of the table existed in the Recycle Bin and the wrong one was restored.
The recyclebin may contain several versions of a dropped object. Oracle restores them in LIFO order; you can restore older versions by repeatedly restoring until you get the version you want, or by using the correct version’s BIN$… name directly.
Agreed with Javier, answer is E