View the Exhibit and examine the undo tablespace attributes. Your database instance is experiencing
a large volume of transactions from non-DBA users in the last one hour. The undo tablespace
NDOTBS1 is full with transactions and no transaction was committed more than one hour ago. The
database has two more undo tablespaces. What happens to the new DML operations in this
scenario?
What happens to the new DML operations in this scenario?
A.
The DML commands will fail
B.
The undo data generated by the DML is stored in one of the two other undo tablespace
C.
The undo data generated by the DML will overwrite the extents that contain committed undo
data
D.
The undo data generated by the DML is stored in the SYSTEM undo segment of the SYSTEM
tablespace
Exhibit not showing
This question is not correctly written
“and no transaction was committed more than one hour ago” is ambiguous and the answer depends on this ambiguous information.
Assuming it states that it has been over an hour since the last commit, now we just went over the hour so therefore the retention guarantee does not now hold (the 60 minuets have just past), therefore we should in theory be able to start overwriting the undo extents again.
Above settings , there is no automatic extension of the undo tablespace , and undo table space is full, but the retention guarantee that is provided to ensure retention time of 60 minutes.
Therefore, the new DML can not overwrite the old one , and the new transaction will fail .