ASM Disk Imbalance
As per MOS note 1980292.1 which was referenced as workaround, we have below questions.
1. For RAC production database, we have 2 standby's ( ADG and Physical Standby) so do we need to run thru setting hidden parameter in all ASM instances of Primary and Standby along with running Disk repair command?
2. Based on our run in pre-prod we have identified that ASM disk repair is taking several hours.
Is this expected behaviour with repair command?
If we have to run same in Production and disk repair is taking time then what is impact associated?
Will there be a performance degradation?
As we have Informatica IDR in production which reads archivelogs on ASM we want to understand impact with running below in production