ASM Header Block Corruption: Do you Monitor for It?
From: <fmhabash_at_gmail.com>
Date: Fri, 18 Mar 2016 11:26:05 -0400
Message-ID: <56ec1e0e.28086b0a.d4612.2c48_at_mx.google.com>
Recently, we got affected by a nasty ASM header block corruption. We were able to kfed repair and, subsequently, mount the DG. We realized, though, that such corruption will not affect the cluster/DB while it is running. It only gets you when ASM is restarted and it needs to mount the DG.
Thanks
Date: Fri, 18 Mar 2016 11:26:05 -0400
Message-ID: <56ec1e0e.28086b0a.d4612.2c48_at_mx.google.com>
Recently, we got affected by a nasty ASM header block corruption. We were able to kfed repair and, subsequently, mount the DG. We realized, though, that such corruption will not affect the cluster/DB while it is running. It only gets you when ASM is restarted and it needs to mount the DG.
Given this scenario, I believe it is best practice, then, to monitor such corruption in some regular automated fashion. I never had to, but this incident, making it look it is necessary.
How are you addressing this potential issue?
Thanks
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Mar 18 2016 - 16:26:05 CET