042-007

7:      The UNDO_RETENTION parameter in yourdatabase is set to 1000 and undo retention is not guaranteed.Which statementregarding retention of undo data is correct?

A.     Undo data becomes obsolete after 1,000 seconds.

B.     Undo data gets refreshed after every 1,000 seconds.

C.     Undo data will be stored permanently after 1,000 seconds.

D.     Committed undo data would be retained for 1,000 seconds if free undo space is available.

E.      Undo data will be retained in the UNDO tablespace for 1,000 seconds,then it gets moved to the TEMPORARY tablespace to provide read consistency.

PropertyDescriptionParameter typeIntegerDefault value900ModifiableALTER SYSTEMRange of values0 to 2³² - 1 (max value represented by 32 bits)Real Application ClustersOracle recommends that multiple instances have the same value.

UNDO_RETENTION specifies (in seconds) the low threshold value of undo retention. For AUTOEXTEND undo tablespaces, the system retains undo for at least the time specified in this parameter, and automatically tunes the undo retention period to satisfy the undo requirements of the queries. For fixed- size undo tablespaces, the system automatically tunes for the maximum possible undo retention period, based on undo tablespace size and usage history, and ignoresUNDO_RETENTION unless retention guarantee is enabled.

The setting of this parameter should account for any flashback requirements of the system. Automatic tuning of undo retention is not supported for LOBs. The RETENTION value for LOB columns is set to the value of theUNDO_RETENTION parameter.

The UNDO_RETENTION parameter can only be honored if the current undo tablespace has enough space. If an active transaction requires undo space and the undo tablespace does not have available space, then the system starts reusing unexpired undo space. This action can potentially cause some queries to fail with a "snapshot too old" message.

The amount of time for which undo is retained for the Oracle Database for the current undo tablespace can be obtained by querying the TUNED_UNDORETENTION column of the V$UNDOSTAT dynamic performance view.

D