View the following SQL statements: Transaction T1 SQL> INSERT INTO hr.regions 2 VALUES (5,'Pole'); 3 COMMIT; Transaction T2 SQL> UPDATE hr.regions 2 SET region_name='Poles' 3 WHERE region_id = 5; 4…

Question

Options

• AIt is possible, but transaction T3 also backs out.
• BIt is possible with the NOCASCADE_FORCE option.
• CIt is possible with the NONCONFLICT_ONLY option.
• DIt is not possible because it has conflicts with transaction T3.

• A
  2% (1)
• B
  78% (32)
• C
  12% (5)
• D
  7% (3)

Explanation

Table 12-2 Flashback TRANSACTION_BACKOUT Options Backs out specified transactions and all dependent transactions in a post-order fashion (that is, children arebacked out before parents are backed out). Without CASCADE, if any dependent transaction is not specified, an error occurs. Default. Backs out specified transactions, which are expected to have no dependent transactions. Firstdependent transactions causes an error and appears in *_FLASHBACK_TXN_REPORT. Backs out specified transactions, ignoring dependent transactions. Server runs undo SQL statements forspecified transactions in reverse order of commit times.If no constraints break and you are satisfied with the result, you can commit the changes; otherwise, you canroll them back. NONCONFLICT_ONLY Backs out changes to nonconflicting rows of the specified transactions. Database remains consistent, buttransaction atomicity is lost.

No community discussion yet for this question.