Which two are true about flashback features in Oracle Database 19c and later releases? (Choose two.)

Question

Options

• AFlashback logs are automatically purged when DB_FLASHBACK_RETENTION_TARGET is set
• BFlashback logs are monitored and proactively deleted when beyond the retention period defined
• CFlashback logs are monitored and proactively deleted when beyond the retention period defined
• DFlashback logs are monitored for being older than the retention period defined in
• EFlashback logs are automatically purged whenever the value of

• A
  72% (23)
• B
  9% (3)
• D
  13% (4)
• E
  6% (2)

Explanation

Starting with Oracle Database Release 19c, the management of space in the fast recovery area is simplified. Oracle Database monitors flashback logs in the fast recovery area and automatically deletes flashback logs that are beyond the retention period. When the retention target is reduced, flashback logs that are beyond the retention period are deleted immediately. In scenarios where a sudden workload spike causes a large number of flashback logs to be created, the workload is monitored for a few days before deleting flashback logs that are beyond the retention period. This avoids the overhead of recreating the flashback logs, if another peak workload occurs soon after.

No community discussion yet for this question.