- 最新
- 最多得票
- 最多評論
The approach to fix/address this issue depends on the type of segment that block is holding i.e. if its a temporary table, application table, index.
Meaning, if this block turns out to be holding temporary table, then you can skip that block after following this - https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.CommonDBATasks.Database.html#Appendix.Oracle.CommonDBATasks.SkippingCorruptBlocks
If its an index, you can rebuild it or use dbms packages to repair it.
If its an application table, then do a PITR using the backups, skip the corrupted block(s) and import the table from restored RDS.
I would say, validate the database using RMAN to see if there are any more corruptions ( https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.CommonDBATasks.RMAN.html#Appendix.Oracle.CommonDBATasks.ValidateDB )and reach out to support for more help.
相關內容
- 已提問 10 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 4 年前
- AWS 官方已更新 2 年前