本文详细介绍了Oracle 19c中关于闪回特性的管理，包括DB_FLASHBACK_RETENTION_TARGET参数如何影响闪回日志的自动删除。在系统崩溃后，讨论了如何恢复CDB和PDB中的数据文件，以及RMAN双工备份集的工作原理和持久配置设置。此外，还探讨了优化器统计顾问的功能，如手动运行、建议改进统计收集和使用DBMS_STATS包进行分析。
Q26:
Which two are true about flashback features in Oracle Database 19c and later releases? (Choose two.)
- A. Flashback logs are automatically purged when DB_FLASHBACK_RETENTION_TARGET is set lower than the time they have already been retained.
- B. Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET only after there is space pressure.
- C. Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET before there is space pressure.
- D. Flashback logs are monitored for being older than the retention period defined in DB_FLASHBACK_RETENTION_TARGET and can be deleted by an administrator written event trigger.
- E. Flashback logs are automatically purged whenever the value of DB_FLASHBACK_RETENTION_TARGET is changed.
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. T
最低0.47元/天 解锁文章
2017
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
