The database users regularly complain about the difficulty in performing transactions. On
investigation, you find that some users perform long-running transactions that consume huge
amounts of space in the undo tablespace, which caused the problem. You want to control the
usage of the undo tablespace only for these user sessions and you do not want these sessions to
perform long-running operations.
How would you achieve this?
A.
Implement a profile for the users.
B.
Implement external roles for the users.
C.
Set the threshold for the undo tablespace.
D.
Implement a Database Resource Manager plan.
I think answer is D: Implement a database resource manager plan.
as per Oracle Doc
Establishing User Quotas for Undo Space
The Oracle Database Resource Manager can be used to establish user quotas for undo space. The Database Resource Manager directive UNDO_POOL allows DBAs to limit the amount of undo space consumed by a group of users (resource consumer group).
You can specify an undo pool for each consumer group. An undo pool controls the amount of total undo that can be generated by a consumer group. When the total undo generated by a consumer group exceeds its undo limit, the current UPDATE transaction generating the undo is terminated. No other members of the consumer group can perform further updates until undo space is freed from the pool.
When no UNDO_POOL directive is explicitly defined, users are allowed unlimited undo space.
Check below, are some absolutely unrelated websites to ours, nevertheless, they may be most trustworthy sources that we use.