Re: [suse-oracle] MD5 sums or archives differ between production andstandby
"Silviu Marin-Caea" <[email protected]>
| Newsgroups | gmane.linux.suse.oracle.general |
|---|---|
| Message-ID | <[email protected]> |
On Wednesday 03 December 2008 17:54:45 you wrote: > We were experiencing archive log corruption under heavy load some time > ago and we were running MD5 checksums on archive logs multiple times > throughout their life cycle. They definitely changed over time. The logs > on the standby would start out with the same MD5 as those on the primary > (after being fully written to disk) then as they were applied, they > would change and then they would revert to the original (if the > corruption didn't occur). We've since upgraded our release and that > behavior seems to have gone away (so is the corruption). The md5's are > now the same regardless once they are fully transmitted. I don't recall > the exact release numbers but they were all 9i. We have 10gR2 10.2.0.3 I can't find not even one archive that is identical between production and standby. I have run md5sum --check on all of them. > You don't mention whether you are physical or logical standby, I don't > know if that makes a difference or not. Physical standby. _______________________________________________ suse-oracle mailing list [email protected] http://listx.novell.com/mailman/listinfo/suse-oracle