Users notify you that their application is failing every time they try to add new records. Because of
poor application design, the actual ORA error message is unavailable. What might be the problem?(Choose the best answers.)
A. The application user has exceeded their undo quota.
B. The FLASHBACK GUARANTEE option is set on the undo tablespace.
C. The table is currently being queried by a Flashback Transaction Query operation.
D. The table is currently being queried by a Flashback Versions Query operation.
E. The RETENTION GUARANTEE option is set on the undo tablespace.
The likely causes are that the RETENTION GUARANTEE option has been set on the undo tablespace and there are no expired transactions to remove to make room for new transactions,or that the user has exceeded the undo quota that has been set by the database resource manager.
The UNDO_RETENTION parameter is ignored for a fixed size undo tablespace. The database always tunes the undo retention period for the best possible retention, based on system activity and undo tablespace size. See "Automatic Tuning of Undo Retention" for more information.
For an undo tablespace with the AUTOEXTEND option enabled, the database attempts to honor the minimum retention period specified by UNDO_RETENTION. When space is low, instead of overwriting unexpired undo information, the tablespace auto-extends. If the MAXSIZE clause is specified for an auto-extending undo tablespace, when the maximum size is reached, the database may begin to overwrite unexpired undo information. The UNDOTBS1 tablespace that is automatically created by DBCA is auto-extending.