11G ADG automatic repair corrupt data blocks(ABMR自动坏块修复)测试二
standby site 的ABMR没有成功, 后来是怀疑buffer header中有mrec 的block, 现在我接着测试如果buffer header 中没有此类block,ABMR是否成功?以前用bbed 标记corrupt block的方式, 如果有corrupt block时rman backup 又会怎么样?
提供综合数据库运维服务与优化方案(不限Oracle MySQL PG GaussDB GoldenDB OceanBase等), 微信/Tel:(+86)134-365-60330
standby site 的ABMR没有成功, 后来是怀疑buffer header中有mrec 的block, 现在我接着测试如果buffer header 中没有此类block,ABMR是否成功?以前用bbed 标记corrupt block的方式, 如果有corrupt block时rman backup 又会怎么样?
Automatic block repair allows corrupt data blocks to be automatically repaired as soon as the corruption is detected. This feature reduces the amount of time that data is inaccessible due to block corruption.
今天刚搭建的一个Data guard环境,一开始在日志传输时遇到ora-12592错误,ORA-12592: TNS:bad packet
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DDE: Problem Key ‘ORA 312’ was flood controlled (0x5) (no incident)
ORA-00312: online log 2 thread 1: ‘/oracle/oradata/icme/redo02.log’
Error 19527 creating/clearing online redo logfile 2
Manually create physical standby with rman;
Primary role and Primary standby role switchover;
Converting Physical Standby to Logical Standby ;
如果primary db 丢失或不再需要的physical standby ,想把这些库(standby)利用起来,logical standby 本来就可以write open,11g ADG也可以APPLY LOG时open,但是read only,下面演示如果把off-line standby 转为primary,open read/write mode.