Oracle OCP 1Z0 053 Q43(Flashback Transaction(NOCASCADE_FORCE))

abstractcyj發表於2016-04-03
43.View the following SQL statements:
Transaction T1 INSERT INTO hr.regions VALUES (5,'Pole');COMMIT;
Transaction T2 UPDATE hr.regions SET region_name='Poles' WHERE region_id = 5; COMMIT;
Transaction T3 UPDATE hr.regions SET region_name='North and South Poles' WHERE region_id = 5;
You want to back out transaction T2. Which option would you use?
A. It is possible, but transaction T3 also backs out.
B. It is possible with the NOCASCADE_FORCE option.
C. It is possible with the NONCONFLICT_ONLY option.
D. It is not possible because it has conflicts with transaction T3.
Answer: B

這裡是FLASHBACK Transaction特性的知識點:
過程:DBMS_FLASHBACK.TRANSACTION_BACKOUT

NOCASCADE_FORCE - The user forcibly backs out the given transactions without considering the dependent transactions. The RDBMS executes the UNDO SQL for the given transactions in reverse order of their commit times. If no constraints break, and the result is satisfactory, the user can either COMMIT the changes or else ROLL BACK.

參考:https://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_flashb.htm

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/8520577/viewspace-2074467/,如需轉載,請註明出處,否則將追究法律責任。

相關文章