If this error comes in
dataguard (physical standby) database, oracle will automatically delete the
corrupted archived log file and then we would require to copy the affected
archived log from the primary site and so that managed recovery could proceed.
I was thinking that oracle should automatically fetch the affected/corrupted
archived log itself from the primary site, but then I realized the reason of
not happening this automatically and I will explain the reason later.
Once this type of
corruption is detected, following type of message is shown in the alert log
file.
