Which things should be considered while deciding the size of undo tablespace in your database ( choose three)
-
The size of an undo block
-
The size of the redo log files
-
The size of the database buffer cache.
-
The value of the UNDO_RETENTION parameter.
-
Undo blocks generated per second.
When sizing undo tablespace, you need to consider: the undo block size (determines space efficiency per transaction), the UNDO_RETENTION parameter (how long undo data must be kept for flashback/consistency), and the rate of undo blocks generated per second (transaction workload). Redo log files and buffer cache size don't directly determine undo tablespace requirements.
Sizing an undo tablespace depends on three factors: the size of an undo block, the UNDO_RETENTION setting (how long committed undo must be kept for read consistency and flashback), and the rate of undo generation in blocks per second (UPS) during peak load. Multiplying retention time by generation rate and block size gives the minimum tablespace size Oracle recommends. Redo log size and buffer cache size affect other tuning areas but don't factor into undo sizing math.